[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] No external network for domU's
- To: trilok nuwal <tc.nuwal@xxxxxxxxx>
- From: James Drenter <jdrenter@xxxxxxxxxxxxx>
- Date: Thu, 23 Aug 2007 12:34:45 -0400
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Thu, 23 Aug 2007 09:35:34 -0700
- Domainkey-signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=B36BM4nSyECjDaaq3xjKk5oAeGISirf56Cv+j6rWoipTeIj4KfheftSnsWVRS0e2
- List-id: Xen user discussion <xen-users.lists.xensource.com>
trilok nuwal wrote:
Did you configure eth0 of domU with mac address mac=00:16:3e:1a:19:23
adress.
If not then please first modify yr
/etc/syscongig/network-scripts/ifcfg-eth0. with the above mac as in
config file then add proper guest IP and NETASK and gateway same as
dom0. then restart the network.
then see ifconfig if yr eth0 is up in domU.
If it is then it should be ok.
Yes, this was already done. Results of ifconfig:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3E:1A:19:23
inet addr:10.74.154.202 Bcast:10.74.154.255 Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe1a:1923/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:322 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60237 (58.8 KiB) TX bytes:8759 (8.5 KiB)
Interrupt:11 Base address:0x8000
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:1186 errors:0 dropped:0 overruns:0 frame:0
TX packets:1186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1334668 (1.2 MiB) TX bytes:1334668 (1.2 MiB)
if not then you can check roting table into domU.
You prorbably need to configure the IP routing table in domU.
First see the routing atable to dom0 using below command.
#route -v
Then add the entryies for the domU also.
Also already verified, results of "route -n" from domU:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.74.154.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 10.74.154.1 0.0.0.0 UG 0 0 0 eth0
This route table is the same as what I get for dom0. As far as I can tell,
everything *should* be OK, but it still doesn't work.
Thanks,
Trilok
Thank you. Any and all help is appreciated!
-- James
On 8/23/07, James Drenter wrote:
I have been trying to get this to work for several days with no luck...
I'm using a RHEL5 (x86_64) dom0 with a single, eth0 physical
device. I'm trying to add a single domU with a network bridge (the
default). I can add the domU OK, but the network on the domU can
only access the dom0 (anything to the internet fails). I'm a bit of
a Xen newbie, but in 3 days of searching on-line, I haven't found
anything that has helped get this working.
Basic net settings:
dom0 IP = 10.74.154.200 <http://10.74.154.200>
domU IP = 10.74.154.202 <http://10.74.154.202>
NETMASK (both) = 255.255.255.0 <http://255.255.255.0>
GATEWAY (both) = 10.74.154.1 <http://10.74.154.1>
domU vif setting:
vif = [ 'type=ioemu, mac=00:16:3e:1a:19:23, bridge=xenbr0' ]
Clean boot of the system with just the dom0 running gives me the
following "ifconfig" and "brctl show" results:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:78:6E:67:16
inet addr:10.74.154.200
<http://10.74.154.200> Bcast:10.74.154.255
<http://10.74.154.255> Mask:255.255.255.0 <http://255.255.255.0>
inet6 addr: fe80::21b:78ff:fe6e:6716/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1153 errors:0 dropped:0 overruns:0 frame:0
TX packets:470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:128479 (125.4 KiB) TX bytes:58600 (57.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 <http://127.0.0.1> Mask:255.0.0.0
<http://255.0.0.0>
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2211 errors:0 dropped:0 overruns:0 frame:0
TX packets:2211 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2467028 (2.3 MiB) TX bytes:2467028 (2.3 MiB)
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:1324 errors:0 dropped:0 overruns:0 frame:0
TX packets:469 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:143989 (140.6 KiB) TX bytes:60460 (59.0 KiB)
Interrupt:16
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:475 errors:0 dropped:0 overruns:0 frame:0
TX packets:1154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:60182 (58.7 KiB) TX bytes:128539 (125.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:603 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:57878 (56.5 KiB) TX bytes:0 (0.0 b)
# brctl show xenbr0
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
Which seems all well and good, until I start the domU, then they
change to:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:78:6E:67:16
inet addr:10.74.154.200
<http://10.74.154.200> Bcast:10.74.154.255
<http://10.74.154.255> Mask:255.255.255.0 <http://255.255.255.0>
inet6 addr: fe80::21b:78ff:fe6e:6716/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5364 errors:0 dropped:0 overruns:0 frame:0
TX packets:1765 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:589948 (576.1 KiB) TX bytes:251014 (245.1 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 <http://127.0.0.1> Mask:255.0.0.0
<http://255.0.0.0>
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2211 errors:0 dropped:0 overruns:0 frame:0
TX packets:2211 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2467028 (2.3 MiB) TX bytes:2467028 (2.3 MiB)
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:6243 errors:0 dropped:0 overruns:0 frame:0
TX packets:1323 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:646776 (631.6 KiB) TX bytes:184156 (179.8 KiB)
Interrupt:16
tap0 Link encap:Ethernet HWaddr D6:D9:8F:58:83:79
inet6 addr: fe80::d4d9:8fff:fe58:8379/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:324 errors:0 dropped:0 overruns:0 frame:0
TX packets:3482 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:40371 (39.4 KiB) TX bytes:424098 (414.1 KiB)
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:1770 errors:0 dropped:0 overruns:0 frame:0
TX packets:5365 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:253640 (247.6 KiB) TX bytes:590008 ( 576.1 KiB)
vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST 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:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr D6:D9:8F:58:83:79
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:3494 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:345978 (337.8 KiB) TX bytes:0 (0.0 b)
# brctl show xenbr0
bridge name bridge id STP enabled interfaces
xenbr0 8000.d6d98f588379 no vif2.0
tap0
peth0
vif0.0
I don't know why it's changing the MAC address for xenbr0. Should
it be? I don't even know where that new MAC address is coming
from. Also, the only thing resembling an error in any of the logs
is in /var/log/messages (and dmesg):
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@xxxxxxxxxxxx
<mailto:maxk@xxxxxxxxxxxx>>
device tap0 entered promiscuous mode
audit(1187835845.166 :5): dev=tap0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 3(tap0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 3(tap0) entering forwarding state
device vif2.0 entered promiscuous mode
audit(1187835846.434:6): dev=vif2.0 prom=256 old_prom=0 auid=4294967295
ADDRCONF(NETDEV_UP): vif2.0: link is not ready
and that's where it ends. I'm pretty sure I should see a matching
"vif2.0: link becomes ready" line, but it never shows up.
I'm frustrated enough to consider dropping Xen altogether. If
anyone has any idea what may be going on, I would greatly appreciate
any help.
Regards,
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
