Xen project Mailing List

From dom0

root@debian-xen:~# ifconfig -a
eth0      Link encap:Ethernet HWaddr 08:00:27:30:b9:53
          inet6 addr: fe80::a00:27ff:fe30:b953/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2449702 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:281121959 (268.0 MiB) TX bytes:12538172 (11.9 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:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:728 (728.0 B) TX bytes:728 (728.0 B)

vif1.0    Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
          RX packets:29951 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2324864 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:3215716 (3.0 MiB) TX bytes:269574095 (257.0 MiB)

xenbr0    Link encap:Ethernet HWaddr 08:00:27:30:b9:53
          inet addr:192.168.168.190 Bcast:192.168.168.255 Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe30:b953/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2460954 errors:0 dropped:0 overruns:0 frame:0
          TX packets:108212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:245381651 (234.0 MiB) TX bytes:8905548 (8.4 MiB)

root@debian-xen:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.08002730b953       no              eth0
                                                        vif1.0

Network Portion of xend-config.sxp on dom0

##
# NOTE:
# Please read /usr/share/doc/xen-utils-common/README.Debian for Debian specific
# informations about the network setup.

##
# To bridge network traffic, like this:
#
# dom0: ----------------- bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
#(network-script network-bridge)

#
# Your default ethernet device is used as the outgoing interface, by default.
# To use a different one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth0')
#
# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain. To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#

# The script used to control virtual interfaces. This can be overridden on a
# per-vif basis when creating a domain or a configuring a new vif. The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do the
# same here. The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover that,
# so there is no need to specify it explicitly.
#
# (vif-script vif-bridge)

## Use the following if network traffic is routed, as an alternative to the
# settings for bridged networking given above.
#(network-script network-route)
#(vif-script     vif-route)

## Use the following if network traffic is routed with NAT, as an alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script     vif-nat)

FROM domU

root@test-deb-2:/etc# ifconfig
eth0      Link encap:Ethernet HWaddr 00:16:3e:ac:f1:11
          inet addr:192.168.168.213 Bcast:192.168.168.255 Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:feac:f111/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2327701 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29977 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:237398493 (226.4 MiB) TX bytes:3643922 (3.4 MiB)
          Interrupt:17

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:2990 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2990 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1050903 (1.0 MiB) TX bytes:1050903 (1.0 MiB)

Re: [Xen-users] Bridged, have IP, can't ping anything, including the gateway