[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] xenbr0, no peth0, problem with network configuration



Hello mailinglist,

i have a really strange problem.

Short summary:

I have a Server with Debian 4.0 (Etch) and a self-compiled Xen 3.1.

I am using bridged network, after compiling Xen 3.1 and restarting the system, 
my "ifconfig" does not show any "peth0" and/or "vif0.0".

My ifconfig-output looks like this:

eth0      Link encap:Ethernet  HWaddr MYMACADDRESS
          inet addr:MYIPDADRESS  Bcast:XX.XX.XX.XX  Mask:XX.XX.XX.XX
          inet6 addr: fe80::290:27ff:XXX:XXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2309564 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1393806 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3054013310 (2.8 GiB)  TX bytes:178940054 (170.6 MiB)

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:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1344 (1.3 KiB)  TX bytes:1344 (1.3 KiB)

xenbr0    Link encap:Ethernet  HWaddr MYMACADDRESS
          inet addr:MYIPADDRESS  Bcast:XX.XX.XX.XX  Mask:XX.XX.XX.XX
          inet6 addr: fe80::290:27ff:XXX:XXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2096254 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1216404 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2895065662 (2.6 GiB)  TX bytes:106636769 (101.6 MiB)

Look there, the IP-Address off eth0 and xenbr0 are identical. 


The xenbr0-part of other Servers looks like this:

xenbr0    Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 SendewarteschlangenlÀnge:0
          RX bytes:15558 (15.1 KiB)  TX bytes:0 (0.0 b)


I have compiled Xen 3.1 correctly,  because it is working great on other 
(identical) systems. The config-files are from the Xen 3.1 package, nothing 
changed.

Summary:
1) no peth0
2) no vif0.0
3) xenbr0 has IP, MAC (...) of eth0

A "ip r" shows this:

# ip r
NETWORKIP/30 dev xenbr0  proto kernel  scope link  src IPADDRESS
default via GATEWAYIP dev xenbr0


Other correct working systems say:

# ip r
NETWORKIP/30 dev eth0  proto kernel  scope link  src IPADDRESS
default via GATEWAYIP dev eth0


One more thing (look at the differences):

The "wrong" working systems says at dmesg:

Bridge firewalling registered
ADDRCONF(NETDEV_CHANGE): xenbr0: link becomes ready
device eth0 entered promiscuous mode
audit(1188330852.072:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 1(eth0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 1(eth0) entering forwarding state
eth0: no IPv6 routers present
xenbr0: no IPv6 routers present

###
ADDRCONF(NETDEV_CHANGE): xenbr0: link becomes ready
###
Look at the second line.

A correct working system says at dmesg:

Bridge firewalling registered
device vif0.0 entered promiscuous mode
audit(1188582851.818:2): dev=vif0.0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 1(vif0.0) entering learning state
peth0:  setting full-duplex.
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
peth0: Setting promiscuous mode.
device peth0 entered promiscuous mode
audit(1188582851.868:3): dev=peth0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 2(peth0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 2(peth0) entering forwarding state
vif0.0: no IPv6 routers present
peth0: no IPv6 routers present
eth0: no IPv6 routers present


I am using 100Mbit/s Intel NICs (PCI) on all my systems, "e100" Linux module.


There is something wrong, but i dont know what. :(

I hope you can help me.

Greetings,

Eduard
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.