|
|
|
|
Re: Проблема с сетью на ноде [message #27675 is a reply to message #27651] |
Fri, 22 February 2008 10:54 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
blttll
Messages: 8 Registered: February 2008
|
Junior Member |
|
|
сетевые настройки на неработающей HN (BAD-HN):
BAD-HN ~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:48:62:F9:A4
inet addr:xx.xx.185.55 Bcast:xx.xx.185.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:734 errors:0 dropped:0 overruns:0 frame:0
TX packets:272 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:71712 (70.0 Kb) TX bytes:33734 (32.9 Kb)
Base address:0x2000 Memory:d8220000-d8240000
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:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4340 (4.2 Kb) TX bytes:4340 (4.2 Kb)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
BAD-HN ~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
xx.xx.184.0 0.0.0.0 255.255.254.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 xx.xx.184.1 0.0.0.0 UG 0 0 0 eth0
сетевые настройки на нормально работающей машине (GOOD-BOY):
GOOD-BOY ~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:48:90:13:60
inet addr:xx.xx.184.120 Bcast:xx.xx.185.255 Mask:255.255.254.0
inet6 addr: fe80::230:48ff:fe90:1360/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:467366900 errors:0 dropped:0 overruns:0 frame:0
TX packets:1908514865 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2803931854 (2674.0 Mb) TX bytes:2417080846 (2305.1 Mb)
Base address:0x2000 Memory:d8200000-d8220000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:25410 errors:0 dropped:0 overruns:0 frame:0
TX packets:25410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3224520 (3.0 Mb) TX bytes:3224520 (3.0 Mb)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:1567473273 errors:0 dropped:0 overruns:0 frame:0
TX packets:7726013 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2452285685 (2338.6 Mb) TX bytes:2965763816 (2828.3 Mb)
GOOD-BOY ~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
xx.xx.184.190 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
..
..
xx.xx.184.0 0.0.0.0 255.255.254.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 xx.xx.184.1 0.0.0.0 UG 0 0 0 eth0
Запускаю пинг с GOOD-BOY на BAD-HN:
GOOD-BOY / # ping BAD-HN
PING BAD-HN (xx.xx.185.55) 56(84) bytes of data.
From GOOD-BOY (xx.xx.184.120) icmp_seq=1 Destination Host Unreachable
From GOOD-BOY (xx.xx.184.120) icmp_seq=2 Destination Host Unreachable
From GOOD-BOY (xx.xx.184.120) icmp_seq=3 Destination Host Unreachable
--- BAD-HN ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4000ms
, pipe 4
Во время пинга был включен tcpdump и тут и там:
На GOOD-BOY:
GOOD-BOY ~ # tcpdump -ni eth0 arp host BAD-HN
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
13:26:00.811237 arp who-has xx.xx.185.55 tell xx.xx.184.120
13:26:01.811067 arp who-has xx.xx.185.55 tell xx.xx.184.120
13:26:02.810888 arp who-has xx.xx.185.55 tell xx.xx.184.120
13:26:03.810751 arp who-has xx.xx.185.55 tell xx.xx.184.120
13:26:04.811533 arp who-has xx.xx.185.55 tell xx.xx.184.120
13:26:05.811359 arp who-has xx.xx.185.55 tell xx.xx.184.120
6 packets captured
10 packets received by filter
0 packets dropped by kernel
на BAD-HN:
BAD-HN ~ # tcpdump -ni eth0 arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
при этом на самом деле сеть на BAD-HN работает, но как-то в одну сторону (напоминает stateful-firewall). То есть если пинг запустить в обратную сторону (с BAD-HN на GOOD-BOY), то
GOOD-BOY делает arp-reply, пинг идет (в tcpdump на обеих машинах видна соответствующая активность). Останавливаем пинг, и запускаем как и хотели (c GOOD-BOY на BAD-HN) - работае
т. Делаем на GOOD-BOY arp -d BAD-HN и все, пинги больше не пойдут.
Перезагружаем BAD-HN с не openvz-ядром и сеть начинает работать как положено.
|
|
|
|
|
|
|
|
|
|
|
|
|