案例一 一天，小王突然急匆匆的來找我，他說：“我在機子上剛裝的redhat怎麼老也ping不通服務器，我網卡的驅動都安裝了，ping 自己的兩塊網卡的IP都能通，可就時訪問不了服務器。我輸入http://172.31.0.101就提示‘當試圖與172.31.0.101聯系時，連接被拒絕’” 我來到小王的機器前查看了一下網絡配置。 [root@rhas root]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:D0:B7:C6:8F:1D inet addr:172.31.0.200 Bcast:172.31.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1306 (1.2 Kb) TX bytes:210 (210.0 b) Interrupt:10 Base address:0xe800 Memory:d9100000-d9100038 eth1 Link encap:Ethernet HWaddr 00:01:03:40:A4:15 inet addr:172.31.0.201 Bcast:172.31.0.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:32 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:1920 (1.8 Kb) Interrupt:11 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1430 errors:0 dropped:0 overruns:0 frame:0 TX packets:1430 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:143776 (140.4 Kb) TX bytes:143776 (140.4 Kb) [root@rhas root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.31.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 172.31.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 172.31.0.254 0.0.0.0 UG 0 0 0 eth1 到這一步我猜想網線可能沒有插到默認網關對應的網卡上即eth1(嗨！小王的機器被鑲在桌子裡不太好挪動。連他自己把網線插在那塊卡上都不知道了。) 接著我在一機子上ping 172.31.0.200和172.31.0.201,在小王的機器監聽 [root@rhas root]# tcpdump tcpdump: listening on eth0 19:32:29.109283 172.31.0.101 > 172.31.0.200: icmp: echo request (DF) 19:32:30.109337 172.31.0.101 > 172.31.0.200: icmp: echo request (DF) 19:32:31.109418 172.31.0.101 > 172.31.0.200: icmp: echo request (DF) 19:32:42.670162 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:32:43.670218 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:32:44.670291 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) ........................ ........................ 19:32:56.671040 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:32:57.671064 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:32:58.671133 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:32:59.671187 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:33:00.671257 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:33:01.671349 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:33:02.671377 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 19:33:03.671441 172.31.0.101 > 172.31.0.201: icmp: echo request (DF) 36 packets received by filter 0 packets dropped by kernel 沒有回應，看一下Firewall的設置。 [root@rhas3 123]# iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination 又不是防火牆的問題，想了一下，我越發肯定剛才的想法是正確的。 [root@rhas root]# cat /etc/modules.conf alias eth0 e100 alias eth1 3c59x alias sound-slot-0 via82cxxx_audio post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 : pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 : alias usb-controller usb-uhci [root@rhas root]#mii-tool eth0: negotiated 100baseTx-Fd flow-control, link ok eth1: no linkk 找到原因了，果然是插反了。既然不方便換端口最簡單的就把eth1即3Com網卡宕調就OK了 當然也可以把兩塊網卡分配在不同的網段。 [root@rhas root]# vi /etc/sysconfig/network-scripts/ifcfg-eth1 # 3Com Corporation3c905C-TX/TX-M [Tornado] DEVICE=eth1 BOOTPROTO=static BROADCAST=172.31.0.255 HWADDR=00:01:03:40:A4:15 IPADDR=172.31.0.201 NETMASK=255.255.255.0 NETWORK=172.31.0.0 ONBOOT=no TYPE=Ethernet~ ~ ~ "/etc/sysconfig/network-scripts/ifcfg-eth1" [已轉換] 10L, 207C 9,1 全部 或者在啟動哦時根本不要加載3Com網卡的驅動哦。 從啟動我們的網絡 [root@rhas root]# service network restart 正在關閉接口 eth0： [ 確定 ] 關閉環回接口： [ 確定 ] 設置網絡參數： [ 確定 ] 彈出環回接口： [ 確定 ] 彈出界面 eth0： [ 確定 ] [root@rhas root]# [root@rhas root]# [root@rhas root]# [root@rhas root]# ifconfig eth0 Link encap:Ethernet HWaddr 00:D0:B7:C6:8F:1D inet addr:172.31.0.200 Bcast:172.31.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:68 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5560 (5.4 Kb) TX bytes:504 (504.0 b) Interrupt:10 Base address:0xe800 Memory:d9100000-d9100038 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2041 errors:0 dropped:0 overruns:0 frame:0 TX packets:2041 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:209184 (204.2 Kb) TX bytes:209184 (204.2 Kb) [root@rhas root]# ping 172.31.0.101 PING 172.31.0.101 (172.31.0.101) 56(84) bytes of data. 64 bytes from 172.31.0.101: icmp_seq=0 ttl=64 time=0.542 ms 64 bytes from 172.31.0.101: icmp_seq=1 ttl=64 time=0.270 ms --- 172.31.0.101 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1004ms rtt min/avg/max/mdev = 0.270/0.406/0.542/0.136 ms, pipe 2 [root@rhas root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.31.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 172.31.0.254 0.0.0.0 UG 0 0 0 eth0 [root@rhas root]# 此時訪問網絡沒有問題，故障排除。
案例二 由此我又想相類似的案例，一win98用戶錯將”TCP/IP-->撥號適配器”設置了IP，結果造成他ping不通其他機器。 e.g.將撥號適配器設置ip=172.31.0.1 C:\>ipconfig/all Windows 98 IP Configuration Host Name . . . . . . . . . : R4U2L8 DNS Servers . . . . . . . . : Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No 0 Ethernet adapter : Description . . . . . . . . : PPP Adapter. Physical Address. . . . . . : 44-45-53-54-00-00 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 172.31.0.1 Subnet Mask . . . . . . . . :
