Hello, all! I have a Xen 3.0 setup on a server with two network cards, which are supposed to work in two totally independent virtual nets using bridging. Now, the first virtual net works as a charm, connecting several domUs. The problem is that with the second NIC (eth1) there''s no luck at all - everything is exactly the same, virtual infrastructure seems to be up and running, packets get through to domU just fine (visible with tcpdump on domU), but no packets ever get back to dom0. IP communication through the physical interface works in both directions w/o any trouble. In other words, it''s just like my virtual crossover cable dom0 <-> domU is half broken, and just on second virtual network. Has anyone ever experienced the same problem, or does anyone have an idea what might be wrong with this setup? Here are some details: # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif1.0 vif2.0 vif3.0 vif4.0 xenbr1 8000.feffffffffff no peth1 vif0.1 vif5.0 # ifconfig eth0 Link encap:Ethernet HWaddr 00:30:48:76:51:06 inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12042 errors:0 dropped:0 overruns:0 frame:0 TX packets:8772 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1942638 (1.8 MiB) TX bytes:3613117 (3.4 MiB) eth1 Link encap:Ethernet HWaddr 00:30:48:76:51:07 inet addr:192.168.11.1 Bcast:192.168.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3787 errors:0 dropped:0 overruns:0 frame:0 TX packets:247 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:228132 (222.7 KiB) TX bytes:14854 (14.5 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:13745 errors:0 dropped:0 overruns:0 frame:0 TX packets:10249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1561053 (1.4 MiB) TX bytes:2604788 (2.4 MiB) Base address:0x2000 Memory:d6000000-d6020000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:4505 errors:0 dropped:0 overruns:0 frame:0 TX packets:263 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:289242 (282.4 KiB) TX bytes:20221 (19.7 KiB) Base address:0x2040 Memory:d6020000-d6040000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8773 errors:0 dropped:0 overruns:0 frame:0 TX packets:12043 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3613267 (3.4 MiB) TX bytes:1942728 (1.8 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:247 errors:0 dropped:0 overruns:0 frame:0 TX packets:3788 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14854 (14.5 KiB) TX bytes:228222 (222.8 KiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1807 errors:0 dropped:0 overruns:0 frame:0 TX packets:6090 errors:0 dropped:13 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:167460 (163.5 KiB) TX bytes:404718 (395.2 KiB) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10913 errors:0 dropped:0 overruns:0 frame:0 TX packets:13350 errors:0 dropped:78 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1871574 (1.7 MiB) TX bytes:3105598 (2.9 MiB) vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6319 errors:0 dropped:0 overruns:0 frame:0 TX packets:10826 errors:0 dropped:14 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1199804 (1.1 MiB) TX bytes:1194303 (1.1 MiB) vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5897 errors:0 dropped:0 overruns:0 frame:0 TX packets:9882 errors:0 dropped:34 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1078680 (1.0 MiB) TX bytes:1059360 (1.0 MiB) vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:309 errors:0 dropped:0 overruns:0 frame:0 TX packets:3503 errors:0 dropped:4 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14490 (14.1 KiB) TX bytes:209580 (204.6 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3880 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:175444 (171.3 KiB) TX bytes:378 (378.0 b) xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3942 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:180614 (176.3 KiB) TX bytes:378 (378.0 b) -- Best Regards, Sinisa _____ avast! Antivirus <http://www.avast.com> : Outbound message clean. Virus Database (VPS): 0603-2, 17.01.2006 Tested on: 17.01.2006 22:59:30 avast! - copyright (c) 1988-2004 ALWIL Software. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, all! I have a Xen 3.0 setup on a server with two network cards, which are supposed to work in two totally independent virtual nets using bridging. Now, the first virtual net works as a charm, connecting several domUs. The problem is that with the second NIC (eth1) there''s no luck at all - everything is exactly the same, virtual infrastructure seems to be up and running, packets get through to domU just fine (visible with tcpdump on domU), but no packets ever get back to dom0. IP communication through the physical interface works in both directions w/o any trouble. In other words, it''s just like my virtual crossover cable dom0 <-> domU is half broken, and just on second virtual network. Has anyone ever experienced the same problem, or does anyone have an idea what might be wrong with this setup? Here are some details: # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif1.0 vif2.0 vif3.0 vif4.0 xenbr1 8000.feffffffffff no peth1 vif0.1 vif5.0 # ifconfig eth0 Link encap:Ethernet HWaddr 00:30:48:76:51:06 inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12042 errors:0 dropped:0 overruns:0 frame:0 TX packets:8772 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1942638 (1.8 MiB) TX bytes:3613117 (3.4 MiB) eth1 Link encap:Ethernet HWaddr 00:30:48:76:51:07 inet addr:192.168.11.1 Bcast:192.168.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3787 errors:0 dropped:0 overruns:0 frame:0 TX packets:247 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:228132 (222.7 KiB) TX bytes:14854 (14.5 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:13745 errors:0 dropped:0 overruns:0 frame:0 TX packets:10249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1561053 (1.4 MiB) TX bytes:2604788 (2.4 MiB) Base address:0x2000 Memory:d6000000-d6020000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:4505 errors:0 dropped:0 overruns:0 frame:0 TX packets:263 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:289242 (282.4 KiB) TX bytes:20221 (19.7 KiB) Base address:0x2040 Memory:d6020000-d6040000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8773 errors:0 dropped:0 overruns:0 frame:0 TX packets:12043 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3613267 (3.4 MiB) TX bytes:1942728 (1.8 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:247 errors:0 dropped:0 overruns:0 frame:0 TX packets:3788 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14854 (14.5 KiB) TX bytes:228222 (222.8 KiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1807 errors:0 dropped:0 overruns:0 frame:0 TX packets:6090 errors:0 dropped:13 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:167460 (163.5 KiB) TX bytes:404718 (395.2 KiB) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10913 errors:0 dropped:0 overruns:0 frame:0 TX packets:13350 errors:0 dropped:78 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1871574 (1.7 MiB) TX bytes:3105598 (2.9 MiB) vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6319 errors:0 dropped:0 overruns:0 frame:0 TX packets:10826 errors:0 dropped:14 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1199804 (1.1 MiB) TX bytes:1194303 (1.1 MiB) vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5897 errors:0 dropped:0 overruns:0 frame:0 TX packets:9882 errors:0 dropped:34 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1078680 (1.0 MiB) TX bytes:1059360 (1.0 MiB) vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:309 errors:0 dropped:0 overruns:0 frame:0 TX packets:3503 errors:0 dropped:4 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14490 (14.1 KiB) TX bytes:209580 (204.6 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3880 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:175444 (171.3 KiB) TX bytes:378 (378.0 b) xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3942 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:180614 (176.3 KiB) TX bytes:378 (378.0 b) -- Best Regards, Sinisa ________________________________ avast! Antivirus <http://www.avast.com> : Outbound message clean. Virus Database (VPS): 0603-2, 17.01.2006 Tested on: 17.01.2006 22:59:30 avast! - copyright (c) 1988-2004 ALWIL Software. _____ avast! Antivirus <http://www.avast.com> : Outbound message clean. Virus Database (VPS): 0603-2, 17.01.2006 Tested on: 17.01.2006 23:00:43 avast! - copyright (c) 1988-2004 ALWIL Software. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Peter.Weiss@ConSol.de
2006-Jan-18 10:12 UTC
Re: [Xen-users] Xen 3.0 networking trouble with eth1
On Jan 17 2006 "Sinisa Burina" <six@scnet.yu> wrote:> Hello, all! > > I have a Xen 3.0 setup on a server with two network cards, which are > supposed to work in two totally independent virtual nets using > bridging. Now, the first virtual net works as a charm, connecting several > domUs. > > The problem is that with the second NIC (eth1) there''s no luck at all - > everything is exactly the same, virtual infrastructure seems to be up and > running, packets get through to domU just fine (visible with tcpdump on > domU), but no packets ever get back to dom0. IP communication through the > physical interface works in both directions w/o any trouble. > > In other words, it''s just like my virtual crossover cable dom0 <-> domU is > half broken, and just on second virtual network. > > Has anyone ever experienced the same problem, or does anyone have an idea > what might be wrong with this setup? > > [...]Hello, I''ve tried the same here but didn''t come as far as you did. How did you get xenbr1 connected with peth1? If I run # /etc/xen/scripts/network-bridge start vifnum=1 bridge=xenbr1 netdev=eth1 the second bridge isn''t set up correctly. # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif1.0 xenbr1 8000.000000000000 no Peter -- Peter.Weiss@consol.de ConSol* Software GmbH Phone +49 89 45841-100 Consulting & Solutions Mobile +49 177 6040121 Franziskanerstr. 38 http://www.consol.de D-81669 München _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I''ve tried the same here but didn''t come as far as you did. > How did you get > xenbr1 connected with peth1? > > If I run > > # /etc/xen/scripts/network-bridge start vifnum=1 > bridge=xenbr1 netdev=eth1 > > the second bridge isn''t set up correctly. > > # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > vif1.0 > xenbr1 8000.000000000000 no > > PeterI have simply made a copy of /etc/xen/scripts/network-bridge, put it in /etc/init.d/ and configured it as an init script with hardcoded parameters at the beginning as follows: vifnum=1 bridge=xenbr1 netdev=eth1 antispoof=yes instead of the original: vifnum=${vifnum:-0} bridge=${bridge:-xenbr${vifnum}} netdev=${netdev:-eth${vifnum}} antispoof=${antispoof:-yes} But, on the other hand, this should basically be the same thing - calling network-bridge with extra parameters or hardcoding them in the copy of the script. I can''t really see the difference. Interesting enough, my second NIC does work correctly and I have perfect connaction from dom0 through vif0.1/peth1/eth1/xenbr1 to the rest of the world, but domU can''t return any packet through it. Exporting both NICs to domU makes no difference - eth0 in domU works just fine, while eth1 receives all packets, but can''t send any. -- Best Regards, Sinisa Burina _____ avast! Antivirus <http://www.avast.com> : Outbound message clean. Virus Database (VPS): 0603-2, 17.01.2006 Tested on: 18.01.2006 13:56:51 avast! - copyright (c) 1988-2004 ALWIL Software. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users