Hi
I am seeing strange behavior.... may be I am
overlooking something here. Can anyone throw some
light ?
Thanks.
/Jd
-- brctl shows 2 bridges... by default the vif from
domU get connected to eth0 bridge...
-- eth0 bridge has peth0
With this configuration the domU n/w DOES NOT
WORK.
[root@f8-dev xen-3.1]# brctl show
bridge name bridge id STP enabled
interfaces
eth0 8000.001617b9e423 no
peth0
vif58.0
virbr0 8000.000000000000 no
== While there is another bridge that seems to have
no interfaces added... when I explicitly ask to use
virbr0 in domu config,
brctl shows as follows... and domU networking
WORKS !!. I do not see any connection beween virbr0
and any physical interface!!
[root@f8-dev xen-3.1]# brctl show
bridge name bridge id STP enabled
interfaces
eth0 8000.001617b9e423 no
peth0
virbr0 8000.feffffffffff no
vif61.0
== Here are interface details...
[root@f8-dev xen-3.1]# ifconfig virbr0
virbr0 Link encap:Ethernet HWaddr
FE:FF:FF:FF:FF:FF
inet addr:192.168.122.1
Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64
Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:252267 errors:0 dropped:0
overruns:0 frame:0
TX packets:468468 errors:0 dropped:0
overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13722402 (13.0 MiB) TX
bytes:704946849 (672.2 MiB)
[root@f8-dev xen-3.1]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr
00:16:17:B9:E4:23
inet addr:192.168.12.104
Bcast:192.168.12.255 Mask:255.255.255.0
inet6 addr: fe80::216:17ff:feb9:e423/64
Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:809669 errors:0 dropped:0
overruns:0 frame:0
TX packets:414008 errors:0 dropped:0
overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1160826922 (1.0 GiB) TX
bytes:27963943 (26.6 MiB)
[root@f8-dev xen-3.1]# ifconfig peth0
peth0 Link encap:Ethernet HWaddr
00:16:17:B9:E4:23
inet6 addr: fe80::216:17ff:feb9:e423/64
Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:809632 errors:0 dropped:0
overruns:0 frame:0
TX packets:414052 errors:0 dropped:0
overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1172165190 (1.0 GiB) TX
bytes:30524855 (29.1 MiB)
Interrupt:19
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Sunday 02 March 2008 01:33:18 pm jd wrote:> [root@f8-dev xen-3.1]# ifconfig virbr0 > virbr0 Link encap:Ethernet HWaddr > FE:FF:FF:FF:FF:FF > inet addr:192.168.122.1> [root@f8-dev xen-3.1]# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr > 00:16:17:B9:E4:23 > inet addr:192.168.12.104Your two bridge addresses are in different subnets. If the IP you assign in your domu is in the 192.168.122 range, it won''t be able to talk to anything on the 192.168.12 range. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
jim burns wrote:> On Sunday 02 March 2008 01:33:18 pm jd wrote: > >> [root@f8-dev xen-3.1]# ifconfig virbr0 >> virbr0 Link encap:Ethernet HWaddr >> FE:FF:FF:FF:FF:FF >> inet addr:192.168.122.1 >> > > >> [root@f8-dev xen-3.1]# ifconfig eth0 >> eth0 Link encap:Ethernet HWaddr >> 00:16:17:B9:E4:23 >> inet addr:192.168.12.104 >> > > Your two bridge addresses are in different subnets. If the IP you assign in > your domu is in the 192.168.122 range, it won''t be able to talk to anything > on the 192.168.12 range. >Unless and untill you enable ip forwarding in Dom0. Once you enable ip forwarding, you would be able to communicate with another network. SNAT/MASQUERADE rule is automatically added by libvirt for you. --Sadique> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users