Hello all,
I''m having a very weird problem with a Xen server and one of the NICs
on
that server. The eth1 interface on the server behaves normally, I can
send and receive packets normally, I get ARP requests - everything is
happy. On eth0 however, I do not get ARP requests, or for that matter,
anything sent to a broadcast address - but I can send out ARP broadcasts
and get back replies all day long. This happens in both the Dom0 and
well as the DomU''s. I''ve gone over the switch configs and
both ports
are configured the same, nothing remarkably different about the vlans.
Does anyone have any ideas? I searched and the only thing I really
found was setting LANG="C" in the scripts, which I did but still to no
effect. If anyone has any ideas, I would really appreciate it. Thanks
in advance,
.r''
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif1.0
peth0
vif0.0
xenbr1 8000.feffffffffff no vif1.1
peth1
vif0.1
# iptables -nL
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 PHYSDEV
match --physdev-in vif1.0
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:48:32:12:D8
inet addr:172.25.8.124 Bcast:172.25.8.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe32:12d8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8219 errors:0 dropped:0 overruns:0 frame:0
TX packets:435 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:737171 (719.8 KiB) TX bytes:125622 (122.6 KiB)
eth1 Link encap:Ethernet HWaddr 00:30:48:32:12:D9
inet addr:172.25.254.6 Bcast:172.25.254.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe32:12d9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8511 (8.3 KiB) TX bytes:804 (804.0 b)
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: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)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:17637 errors:2 dropped:0 overruns:0 frame:1
TX packets:3987 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1995054 (1.9 MiB) TX bytes:929996 (908.1 KiB)
Base address:0x2000 Memory:c8200000-c8220000
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:940 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:69282 (67.6 KiB) TX bytes:2692 (2.6 KiB)
Base address:0x2020 Memory:c8220000-c8240000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:2006 errors:0 dropped:0 overruns:0 frame:0
TX packets:12859 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:334649 (326.8 KiB) TX bytes:1185100 (1.1 MiB)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1524 (1.4 KiB) TX bytes:13112 (12.8 KiB)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1839 errors:0 dropped:0 overruns:0 frame:0
TX packets:12637 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:547173 (534.3 KiB) TX bytes:1566406 (1.4 MiB)
vif1.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:524 (524.0 b) TX bytes:12713 (12.4 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:4062 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:488706 (477.2 KiB) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:83 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:13024 (12.7 KiB) TX bytes:0 (0.0 b)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Robert Long wrote:> Hello all, > > I''m having a very weird problem with a Xen server and one of the NICs on > that server. The eth1 interface on the server behaves normally, I can > send and receive packets normally, I get ARP requests - everything is > happy. On eth0 however, I do not get ARP requests, or for that matter, > anything sent to a broadcast address - but I can send out ARP broadcasts > and get back replies all day long. This happens in both the Dom0 and > well as the DomU''s. I''ve gone over the switch configs and both ports > are configured the same, nothing remarkably different about the vlans. > > Does anyone have any ideas? I searched and the only thing I really > found was setting LANG="C" in the scripts, which I did but still to no > effect. If anyone has any ideas, I would really appreciate it. Thanks > in advance, > > .r'' > > > > > # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif1.0 > peth0 > vif0.0 > xenbr1 8000.feffffffffff no vif1.1 > peth1 > vif0.1 > > > > # iptables -nL > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 PHYSDEV > match --physdev-in vif1.0 >I see that the above FORWARD rule only covers one of your interfaces. You can use a wildcard, "+", to cover all of them, e.g. iptables -A FORWARD -m physdev --physdev-in vif+ -j ACCEPT Maybe that will help. :m) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users