I think, but don't know for a fact, that if you don't specify a bridge interface in your config, you'll get a 'nat' address in your domU. I posted about it in my blog: http://yablog-gary.blogspot.com/2007/12/xen-what-i-learned-today.html -- maybe that will get you on the right track? thanks. On Dec 27, 2007 5:19 PM, Joseph L. Casale <jcasale at activenetwerx.com> wrote: > Hi, > I tried this post on the Xen list first with no answer. I have 4 machines > and 3 of which (all different) have no network access when booted into Xen. > I tried using Fedora Core 8 and it produced the same results. Is it normal > for the virbr0 interface to take an arbitrary IP? How does it decide what to > use? An ifconfig when booted into Xen shows the following: > > eth0 Link encap:Ethernet HWaddr 00:0C:29:4A:69:63 > inet addr:192.168.5.30 Bcast:192.168.5.255 Mask:255.255.255.0 > inet6 addr: fe80::20c:29ff:fe4a:6963/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:25 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1763 (1.7 KiB) TX bytes:594 (594.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:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:336 (336.0 b) TX bytes:336 (336.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:28 errors:0 dropped:0 overruns:0 frame:0 > TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1943 (1.8 KiB) TX bytes:1314 (1.2 KiB) > Interrupt:17 Base address:0x1400 > > 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:9 errors:0 dropped:0 overruns:0 frame:0 > TX packets:25 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:594 (594.0 b) TX bytes:1763 (1.7 KiB) > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:34 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:1881 (1.8 KiB) TX bytes:0 (0.0 b) > > Thanks for any pointers! > jlc > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20071228/2493a57e/attachment-0005.html>