WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Bizarre Networking

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Bizarre Networking
From: Simon Dean <sjdean@xxxxxxxxxxxxxxxx>
Date: Tue, 10 Jun 2008 07:24:36 +0100
Delivery-date: Mon, 09 Jun 2008 23:25:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)
Hi,

I've bit the bullet and gone with Xen, but I get some odd networking.

Basically, this was the original idea.

eth0 external
eth1 internal

create bridge br0 for eth0
create bridge br1 for eth1

Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu.

Booting into Xen, my eth1 becomes eth2, I also get an eth0.bak and an eth2.bak! peth2 is sort of explainable I would imagine. So I create a br0 bridge, give eth0 ip address 0.0.0.0 and give the original IP address to br0. Despite my ifcfg-eth2 having

DEVICE=eth2
ONBOOT=yes
BOOTPROTO=none
HWADDR=5c:6c:c0:7d:1d:00
NETMASK=255.255.255.0
IPADDR=10.0.0.30
GATEWAY=10.0.0.35
TYPE=Ethernet

The IP address for eth2 seems to be got by DHCP! I've reassigned using ifconfig eth2 10.0.0.30... which worked.

I've woke up this morning and now eth2 is back to using a DHCP address while eth0 has now used my static address from eth2 - 10.0.0.30.

I also don't know why I need the additional interfaces, vif1.0, vif1.1, vif2.0, tap0, tap1 and tap2.

So er, why did eth1 get renamed eth2 in my xen kernel? Why does eth2 keep getting a dynamic address? Why have my IP addresses swapped between interfaces? Why do I need all those additional interfaces?

Something screwy here, but let me know what else I can provide.

Fedora Core 8 i386, on AMD 3500, 2 x Network Cards - eth2 is reported as my mainboard network card (nVidia nforce 1 Gigabit), eth0 is reported correctly as my 3Com - Direct connection to ADSL Router.

Here's some log details.... from messages

Cheers
Simon

Jun  9 20:34:43 rutsey kernel: udev: renamed network interface eth0 to eth2
Jun 9 20:34:46 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0
.93.
Jun 9 20:34:46 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 9 20:34:46 rutsey avahi-daemon[2150]: Registering new address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.*. Jun 9 20:34:46 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.93 on eth2.IPv4. Jun 9 20:34:55 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.93 on eth2. Jun 9 20:34:55 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0
.93.
Jun 9 20:34:55 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 9 20:34:55 rutsey avahi-daemon[2150]: Withdrawing address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.
Jun  9 20:34:55 rutsey kernel: device peth2 entered promiscuous mode
Jun  9 20:34:55 rutsey kernel: eth2: port 1(peth2) entering learning state
Jun 9 20:34:55 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93 Jun 9 20:34:55 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 9 20:34:55 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.93 on eth2.IPv4.
Jun  9 20:34:55 rutsey kernel: eth2: topology change detected, propagating
Jun  9 20:34:55 rutsey kernel: eth2: port 1(peth2) entering forwarding state
Jun 9 20:34:55 rutsey dhclient: DHCPREQUEST on eth2 to 255.255.255.255 port 67 Jun 9 20:34:56 rutsey avahi-daemon[2150]: Registering new address record for fe80::5e6c:c0ff:fe7d:1d00 on peth2.*. Jun 9 20:34:57 rutsey avahi-daemon[2150]: Registering new address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.*. Jun 9 20:38:47 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.93 on eth2. Jun 9 20:38:47 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 9 20:38:47 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 9 20:38:47 rutsey avahi-daemon[2150]: Withdrawing address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.
Jun  9 20:38:47 rutsey kernel: eth2: port 1(peth2) entering disabled state
Jun  9 20:38:54 rutsey kernel: eth2: port 1(peth2) entering learning state
Jun  9 20:38:54 rutsey kernel: eth2: topology change detected, propagating
Jun  9 20:38:54 rutsey kernel: eth2: port 1(peth2) entering forwarding state
Jun 9 20:38:54 rutsey dhclient: DHCPREQUEST on eth2 to 255.255.255.255 port 67 Jun 9 20:38:54 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 9 20:38:54 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 9 20:38:54 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.93 on eth2.IPv4. Jun 9 20:38:54 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.93 on eth2. Jun 9 20:38:54 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 9 20:38:54 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 9 20:38:54 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 9 20:38:54 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 9 20:38:54 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.93 on eth2.IPv4. Jun 9 20:38:55 rutsey avahi-daemon[2150]: Registering new address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.*. Jun 9 20:41:43 rutsey system-config-network[4298]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth2
Jun  9 20:43:34 rutsey kernel: eth2: port 2(tap0) entering learning state
Jun  9 20:43:34 rutsey kernel: eth2: topology change detected, propagating
Jun  9 20:43:34 rutsey kernel: eth2: port 2(tap0) entering forwarding state
Jun  9 20:43:34 rutsey kernel: eth2: port 3(vif1.0) entering learning state
Jun  9 20:43:34 rutsey kernel: eth2: topology change detected, propagating
Jun 9 20:43:34 rutsey kernel: eth2: port 3(vif1.0) entering forwarding state Jun 9 20:51:35 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.93 on eth2. Jun 9 20:51:35 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 9 20:51:35 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 9 20:51:35 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.30. Jun 9 20:51:35 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 9 20:51:35 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.30 on eth2.IPv4. Jun 9 20:51:56 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.30 on eth2. Jun 9 20:51:56 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0.30. Jun 9 20:51:56 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 9 20:51:56 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.30. Jun 9 20:51:56 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 9 20:51:56 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.30 on eth2.IPv4.
Jun  9 21:11:00 rutsey kernel: eth2: port 4(tap2) entering learning state
Jun  9 21:11:00 rutsey kernel: eth2: topology change detected, propagating
Jun  9 21:11:00 rutsey kernel: eth2: port 4(tap2) entering forwarding state
Jun  9 21:11:00 rutsey kernel: eth2: port 5(vif2.0) entering learning state
Jun  9 21:11:00 rutsey kernel: eth2: topology change detected, propagating
Jun 9 21:11:00 rutsey kernel: eth2: port 5(vif2.0) entering forwarding state
Jun  9 23:12:18 rutsey dhclient: DHCPREQUEST on eth2 to 10.0.0.20 port 67
Jun 10 01:53:55 rutsey dhclient: DHCPREQUEST on eth2 to 255.255.255.255 port 67 Jun 10 02:38:42 rutsey dhclient: DHCPREQUEST on eth2 to 255.255.255.255 port 67
Jun 10 02:38:55 rutsey kernel: eth2: port 5(vif2.0) entering disabled state
Jun 10 02:38:55 rutsey kernel: eth2: port 4(tap2) entering disabled state
Jun 10 02:38:55 rutsey kernel: eth2: port 3(vif1.0) entering disabled state
Jun 10 02:38:55 rutsey kernel: eth2: port 2(tap0) entering disabled state
Jun 10 02:38:55 rutsey kernel: eth2: port 1(peth2) entering disabled state
Jun 10 02:38:55 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.30 on eth2. Jun 10 02:38:55 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0.30. Jun 10 02:38:55 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 10 02:38:55 rutsey avahi-daemon[2150]: Withdrawing address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.
Jun 10 02:38:55 rutsey kernel: eth2: port 5(vif2.0) entering learning state
Jun 10 02:38:55 rutsey kernel: eth2: port 4(tap2) entering learning state
Jun 10 02:38:55 rutsey kernel: eth2: port 3(vif1.0) entering learning state
Jun 10 02:38:55 rutsey kernel: eth2: port 2(tap0) entering learning state
Jun 10 02:38:55 rutsey kernel: eth2: port 1(peth2) entering learning state
Jun 10 02:38:55 rutsey kernel: eth2: topology change detected, propagating
Jun 10 02:38:55 rutsey kernel: eth2: port 5(vif2.0) entering forwarding state
Jun 10 02:38:55 rutsey kernel: eth2: topology change detected, propagating
Jun 10 02:38:55 rutsey kernel: eth2: port 4(tap2) entering forwarding state
Jun 10 02:38:55 rutsey kernel: eth2: topology change detected, propagating
Jun 10 02:38:55 rutsey kernel: eth2: port 3(vif1.0) entering forwarding state
Jun 10 02:38:55 rutsey kernel: eth2: topology change detected, propagating
Jun 10 02:38:55 rutsey kernel: eth2: port 2(tap0) entering forwarding state
Jun 10 02:38:55 rutsey kernel: eth2: topology change detected, propagating
Jun 10 02:38:55 rutsey kernel: eth2: port 1(peth2) entering forwarding state
Jun 10 02:38:55 rutsey dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 4 Jun 10 02:38:57 rutsey avahi-daemon[2150]: Registering new address record for fe80::5e6c:c0ff:fe7d:1d00 on eth2.*. Jun 10 02:38:59 rutsey dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 8 Jun 10 02:38:59 rutsey dhclient: DHCPREQUEST on eth2 to 255.255.255.255 port 67 Jun 10 02:38:59 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 10 02:38:59 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 10 02:38:59 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.93 on eth2.IPv4. Jun 10 02:38:59 rutsey avahi-daemon[2150]: Withdrawing address record for 10.0.0.93 on eth2. Jun 10 02:38:59 rutsey avahi-daemon[2150]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 10 02:38:59 rutsey avahi-daemon[2150]: Interface eth2.IPv4 no longer relevant for mDNS. Jun 10 02:38:59 rutsey avahi-daemon[2150]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.0.0.93. Jun 10 02:38:59 rutsey avahi-daemon[2150]: New relevant interface eth2.IPv4 for mDNS. Jun 10 02:38:59 rutsey avahi-daemon[2150]: Registering new address record for 10.0.0.93 on eth2.IPv4. Jun 10 06:59:35 rutsey system-config-network[7661]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth2
Jun 10 07:20:52 rutsey dhclient: DHCPREQUEST on eth2 to 10.0.0.31 port 67



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>