[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)

Hello.

I traced the problem a little more.
I'd like to know what's described in the following is as intended for the proper 
operation.
In network-bridge script, there's following command invoked in op_start(). 

  setup_bridge_port ${pdev}

In my case ${pdev} is peth0. Just before this command, the properties of
peth0 is the following

  2: peth0: <BROADCAST> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether
00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff inet 10.140.203.84/23 brd 10.140.203.255 
  scope global peth0

where 10.140.203.something are our network address.

After the command `setup_bridge_port` is completed, the properties are
chaned to
2: peth0: <BROADCAST,NOARP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 
  fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

I guess drop of properties of inet and brd is noticeable.

The setup_bridge_port, defined in xen-network-command.sh, contains the
following comannds

  ip link set ${dev} down
  ip link set ${dev} arp off
  ip link set ${dev} multicast off
  ip link set ${dev} addr fe:ff:ff:ff:ff:ff
  ip addr flush ${dev}
where ${dev} is the first argument. I checked these steps and I found that the last command `ip addr flush ${dev}` drops the properties of inet and brd. 

According to xenwiki/XenNetworking page, peth0 should have network
address since it comes the interface directly connected to the external.
The drop of inet and brd properties may be the reason of the problem that 
Dom0 cannot communicate with the external machines.

Does someone give comments to (verify) this message and hopefully a
method to solve the problem ?

-- toshinao

On 2006/12/13, at 18:20, Toshinao Ishii wrote:


Hello.
I found that the Dom0 has the network problem after invoking `network-bridge start` 
and the problem disappears when `network-bridge stop` is invoked.
Again the OS is Debian Etch and installed packages are slightly update as 
the following.

        linux-image-2.6.17-2-xen-amd64
        linux-modules-2.6.17-2-xen-amd64
        xen-hypervisor-3.0.3-2-amd64
        xen-tools (2.8-2)
        xen-utils-3.0.3-2
        xen-utils-common (3.0.3-0-2)
Following is log of new tests. I appreciate comments about what is wrong 
for Dom0 to communicate with others when network-bridge is started.

******* Here's network interface setting

# cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
        address 10.140.203.84
        netmask 255.255.254.0
        network 10.140.202.0
        broadcast 10.140.203.255
        gateway 10.140.203.254

******** At this point, network-bridge is stopped.

# cd /etc/xen/scripts
# ./network-bridge status
============================================================
2: eth0: <BROADCAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
    inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
    inet6 fe80::214:5eff:fe18:c59f/64 scope link
       valid_lft forever preferred_lft forever
Device "xenbr0" does not exist.
relache:/etc/xen/scripts# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask: 255.255.254.0 
          inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:1080 errors:0 dropped:0 overruns:0 frame:0
          TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:142879 (139.5 KiB)  TX bytes:51037 (49.8 KiB)
          Interrupt:16 Memory:ce000000-ce011100

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

# ./network-bridge start
Nothing to flush.
Waiting for peth0 to negotiate link....

******* starting network-bridge

# ./network-bridge status
============================================================
6: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
    inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
    inet6 fe80::214:5eff:fe18:c59f/64 scope link
       valid_lft forever preferred_lft forever
23: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever
bridge  name                    bridge  id              STP enabled     
interfaces
xenbr0  8000.feffffffffff       no              vif0.0
                                                        peth0
10.140.202.0/23 dev eth0  proto kernel  scope link  src 10.140.203.84
default via 10.140.203.254 dev eth0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface 10.140.202.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 0.0.0.0 10.140.203.254 0.0.0.0 UG 0 0 0 eth0 
============================================================


# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask: 255.255.254.0 
          inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2298 (2.2 KiB)  TX bytes:3548 (3.4 KiB)

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

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:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3100 (3.0 KiB)  TX bytes:3796 (3.7 KiB)
          Interrupt:16 Memory:ce000000-ce011100

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:26 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:3548 (3.4 KiB)  TX bytes:2298 (2.2 KiB)

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:44 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:5230 (5.1 KiB)  TX bytes:0 (0.0 b)

****** 10.140.203.254 is the ip address of default router.

# ping 10.140.203.254
PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data.
From 10.140.203.84 icmp_seq=1 Destination Host Unreachable
From 10.140.203.84 icmp_seq=2 Destination Host Unreachable
From 10.140.203.84 icmp_seq=3 Destination Host Unreachable

--- 10.140.203.254 ping statistics ---
8 packets transmitted, 0 received, +3 errors, 100% packet loss, time 7014ms 
, pipe 3
# ./network-bridge stop
# ./network-bridge status
============================================================
2: eth0: <BROADCAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
    inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
    inet6 fe80::214:5eff:fe18:c59f/64 scope link
       valid_lft forever preferred_lft forever
Device "xenbr0" does not exist.
relache:/etc/xen/scripts# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask: 255.255.254.0 
          inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:494 (494.0 b)  TX bytes:334 (334.0 b)
          Interrupt:16 Memory:ce000000-ce011100

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

# ping 10.140.203.254
PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data.
64 bytes from 10.140.203.254: icmp_seq=1 ttl=255 time=2.47 ms
64 bytes from 10.140.203.254: icmp_seq=2 ttl=255 time=0.425 ms
64 bytes from 10.140.203.254: icmp_seq=3 ttl=255 time=0.386 ms
64 bytes from 10.140.203.254: icmp_seq=4 ttl=255 time=0.377 ms

--- 10.140.203.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 0.377/0.916/2.476/0.900 ms
relache:/etc/xen/scripts# exit


On 2006/12/13, at 10:37, Toshinao Ishii wrote:


Hello Henning,

Thank you for comments.

On 2006/12/12, at 21:46, Henning Sprang wrote:


If then everything is O.K. then, what is the problem? O.K.
network.dummy is not ideal to get networking for the domu's. I don't
see any other obvious problems...

And: it really *does* work with network-dummy, and *does not* work
with network-bridge?


It is true whether it is a problem or not depends how one recognizes.
For me, it is a problem. If one looks around, there are much more
documents about configuring DomUs under the case other than
network-dummy. (For example, 2006-11/msg00884.html)

If "work" means, communication of Dom0 with external machines,
network-dummy really does work and network-bridge really does
not work under the configuration I explained.


Do you have any firewalling stuff running?


Yes. This is because Debian package xen-hypervisor-3.0.3-1-amd64
needs iproute to be installed and recommends bridge-utils to be
installed. I do not need firewalling capability.

I want to be able to setup with these packages.


I think, you need to restart your machine after changing the
networs-script stuff, because there are some situations where changes don't apply when just restarting xend. (it's a quite complex change to 
the network devices, so a reboot is cleaner when changing something
fundamentalk like this, I think)


For most of the tests, I restarted the machine. I will keep this way.

-- toshinao






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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

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