Networking problems with debian packages

Networking problems with debian packages

[Christian Wicke]

[-- Attachment #1: Type: text/plain, Size: 4207 bytes --]

Hello,

my domain-0 loses it network when xend starts.
It uses a dhcp client on eth0 to receive its ip address (192.168.1.2). 

If I run 
$ dhclient xen-br0
$ /etc/init.d/networking restart

then I have the network, but route shows now two routes to 192.168.1.0:
$ LANG=EN route -n
Kernel IP routing table
Destination     Gateway        Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0 xen-br0
192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0 xen-br0

Does anyone know what is the correct way to make this work?


A second problem: I cannot ping to domU.

I think the problem is that there is no IP4-address assigned to to the vif 
interface. But assigning an ip address with ifconfig didn't help

Here is the output from ifconfig after I started my domU:
eth0      Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:e2ff:fe7d:84fa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4269 (4.1 KiB)  TX bytes:8874 (8.6 KiB)
          Interrupt:10 Base address:0x7000

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

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:924 (924.0 b)  TX bytes:70 (70.0 b)

xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4497 (4.3 KiB)  TX bytes:378 (378.0 b)

I searched for both problems in the mailing list but couldn't find anything 
that helped me.

I attached the config for the domU.
My /etc/network/interfaces looks like this:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 192.168.5.2
        netmask 255.255.255.0
        network 192.168.5.0
        gateway 192.168.5.1

route on domU gave:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.5.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.5.1     0.0.0.0         UG    0      0        0 eth0

ifconfig on domU gave
eth0      Link encap:Ethernet  HWaddr AA:00:00:03:C8:C3
          inet addr:192.168.5.2  Bcast:192.168.5.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:70 (70.0 b)  TX bytes:2016 (1.9 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1368 (1.3 KiB)  TX bytes:1368 (1.3 KiB)

I use Adam Heath's latest (2.0.4-4) packages from 
http://people.debian.org/~doogie/packages/ on debian sarge

Thanks a lot for your help
Christian

[-- Attachment #2: speedyU.conf --]
[-- Type: text/plain, Size: 2962 bytes --]

#  -*- mode: python; -*-
#============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm create'.
# You use a separate script for each domain you want to create, or 
# you can set the parameters for the domain on the xm command line.
#============================================================================

#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/boot/xen-linux-2.6.10cxu3"

# Optional ramdisk.
ramdisk = "/boot/initrd.img-2.6.10cxu3"

# The domain build function. Default is 'linux'.
#builder='linux'

# Initial memory allocation (in megabytes) for the new domain.
memory = 64

# A name for your domain. All domains must have different names.
name = "speedyU"

# Which CPU to start domain on? 
#cpu = -1   # leave to Xen to pick

#----------------------------------------------------------------------------
# Define network interfaces.

# Number of network interfaces. Default is 1.
#nics=1

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ]

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.

#disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:vg2/xenU,sda1,w', 'phy:vg2/xenUswap,sda2,w' ]
#----------------------------------------------------------------------------
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the domain's
# IP config doesn't, e.g. in ifcfg-eth0 or via DHCP.
# You can use 'extra' to set the runlevel and custom environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).

# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
netmask="255.255.255.0"
# Set default gateway.
gateway="192.168.5.1"
# Set the hostname.
#hostname= "vm%d" % vmid
hostname= "speedyU"
ip = "192.168.5.2"

# Set root device.
root = "/dev/sda1 ro"

# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = '169.254.1.0'  
# Root directory on the nfs server.
#nfs_root   = '/full/path/to/root/directory'

# Sets runlevel 4.
extra = "4"

#----------------------------------------------------------------------------
# Set according to whether you want the domain restarted when it exits.
# The default is 'onreboot', which restarts the domain when it shuts down
# with exit code reboot.
# Other values are 'always', and 'never'.

#restart = 'onreboot'

#============================================================================

Re: Networking problems with debian packages

[Leigh Brown]

Christian Wicke said:
> Hello,
>
> my domain-0 loses it network when xend starts.
> It uses a dhcp client on eth0 to receive its ip address (192.168.1.2).
>
> If I run
> $ dhclient xen-br0
> $ /etc/init.d/networking restart
>
> then I have the network, but route shows now two routes to 192.168.1.0:
> $ LANG=EN route -n
> Kernel IP routing table
> Destination     Gateway        Genmask         Flags Metric Ref    Use
> Iface
> 192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0
> xen-br0
> 192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0
> eth0
> 0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0
> xen-br0
>
> Does anyone know what is the correct way to make this work?
>
>
> A second problem: I cannot ping to domU.
>
> I think the problem is that there is no IP4-address assigned to to the vif
> interface. But assigning an ip address with ifconfig didn't help
>
> Here is the output from ifconfig after I started my domU:
> eth0      Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
>           inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::200:e2ff:fe7d:84fa/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:50 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:4269 (4.1 KiB)  TX bytes:8874 (8.6 KiB)
>           Interrupt:10 Base address:0x7000
>
> 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:2065 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2065 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:130380 (127.3 KiB)  TX bytes:130380 (127.3 KiB)
>
> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:22 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:4 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:924 (924.0 b)  TX bytes:70 (70.0 b)
>
> xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:114 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4497 (4.3 KiB)  TX bytes:378 (378.0 b)
>
> I searched for both problems in the mailing list but couldn't find
> anything that helped me.
[...]

There is no IP address on the xen-br0 interface - and there should
be.

I had this problem the other day when I had forgotten to install
iproute.  I'd hope the debian packages would make that a dependency
but you never know.  Is iproute installed?

Cheers,

Leigh.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Christian Wicke]

> There is no IP address on the xen-br0 interface - and there should
> be.
>
> I had this problem the other day when I had forgotten to install
> iproute.  I'd hope the debian packages would make that a dependency
> but you never know.  Is iproute installed?

iproute was not installed. This solved my first problem. 
Maybe Adam can add a dependency for the next packages.
route looks better now:
# LANG=EN route -n
Kernel IP routing table
Destination     Gateway        Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0 xen-br0
0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0 xen-br0

Thanks for the tip!

But I still cannot ping to the domU. After 
# xm create -f speedyU.conf
ifconfig shows an interface vif1.0, but nowhere anything with 192.168.5. (I 
configured my domU to 192.168.5.2)

Do you have a tip for this, too?

Thanks
Christian

# LANG=EN ifconfig
eth0      Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:e2ff:fe7d:84fa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:526 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:137510 (134.2 KiB)  TX bytes:60090 (58.6 KiB)
          Interrupt:10 Base address:0x7000

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

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 MULTICAST  MTU:1500  Metric:1
          RX packets:48 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2016 (1.9 KiB)  TX bytes:160 (160.0 b)

xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.255
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:429 errors:0 dropped:0 overruns:0 frame:0
          TX packets:463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:132018 (128.9 KiB)  TX bytes:55218 (53.9 KiB)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Gerd Knorr]

Christian Wicke <xen.christian@safersignup.com> writes:

> Does anyone know what is the correct way to make this work?

The xen start script network setup doesn't work very good for me as
well.  Sometimes it works, sometimes it doesn't, havn't figured yet
why.

I simply make eth0 a bridge early in the boot process, before the
network setup.  Hooking into /etc/init.d/boot.local works for me, see
below for the few script lines.  Then let the distribution start
scripts configure the eth0 device as usual.  Disable
/etc/xen/scripts/network (by inserting "exit" at line #2 for example),
so xend will not try to do the bridge setup again.  Configure your xen
domains to use eth0, i.e. "vif = [ 'bridge=eth0' ]".  Works fine for
me.

HTH,

  Gerd

# make eth0 a bridge
ip link set name hw-eth0 dev eth0
brctl addbr eth0
brctl addif eth0 hw-eth0
ip link set up hw-eth0

-- 
#define printk(args...) fprintf(stderr, ## args)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Christian Wicke]

(I hope this mail doesn't come twice. I tried to send it three hours ago.)
> There is no IP address on the xen-br0 interface - and there should
> be.
>
> I had this problem the other day when I had forgotten to install
> iproute.  I'd hope the debian packages would make that a dependency
> but you never know.  Is iproute installed?

iproute was not installed. This solved my first problem. 
Maybe Adam can add a dependency for the next packages.
route looks better now:
# LANG=EN route -n
Kernel IP routing table
Destination     Gateway        Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0 xen-br0
0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0 xen-br0

Thanks for the tip!

But I still cannot ping to the domU. After 
# xm create -f speedyU.conf
ifconfig shows an interface vif1.0, but nowhere anything with 192.168.5. (I 
configured my domU to 192.168.5.2)

Do you have a tip for this, too?

Thanks
Christian

# LANG=EN ifconfig
eth0      Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:e2ff:fe7d:84fa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:526 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:137510 (134.2 KiB)  TX bytes:60090 (58.6 KiB)
          Interrupt:10 Base address:0x7000

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

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 MULTICAST  MTU:1500  Metric:1
          RX packets:48 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2016 (1.9 KiB)  TX bytes:160 (160.0 b)

xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.255
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:429 errors:0 dropped:0 overruns:0 frame:0
          TX packets:463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:132018 (128.9 KiB)  TX bytes:55218 (53.9 KiB)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Adam Heath]

On Thu, 3 Mar 2005, Leigh Brown wrote:

> There is no IP address on the xen-br0 interface - and there should
> be.
>
> I had this problem the other day when I had forgotten to install
> iproute.  I'd hope the debian packages would make that a dependency
> but you never know.  Is iproute installed?

Not a depends, maybe a suggest or recommends.  You can use routing instead of
bridging.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Nicholas Lee]

On Thu, Mar 03, 2005 at 01:58:01PM +0100, Christian Wicke wrote:
> But I still cannot ping to the domU. After 
> # xm create -f speedyU.conf
> ifconfig shows an interface vif1.0, but nowhere anything with 192.168.5. (I 
> configured my domU to 192.168.5.2)

vif1.0 is just the p-t-p link for the tun device on the host side.

Set the ip address in the guest on eth0.

Nicholas


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Christian Wicke]

> > But I still cannot ping to the domU. After
> > # xm create -f speedyU.conf
> > ifconfig shows an interface vif1.0, but nowhere anything with 192.168.5.
> > (I configured my domU to 192.168.5.2)
>
> vif1.0 is just the p-t-p link for the tun device on the host side.
>
> Set the ip address in the guest on eth0.

I think I did:
speedyU:~# ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:75:E8:9F
          inet addr:192.168.5.2  Bcast:192.168.5.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1240 (1.2 KiB)  TX bytes:4620 (4.5 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2046 (1.9 KiB)  TX bytes:2046 (1.9 KiB)

speedyU:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 192.168.5.2
        netmask 255.255.255.0
        network 192.168.5.0
        gateway 192.168.5.1

On domain 0 I tried a 
# ifconfig vif1.0 192.168.5.1 pointopoint 192.168.5.2 up
ifconfig shows now the ip and route the route:
# LANG=EN ifconfig
eth0      Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:e2ff:fe7d:84fa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:720 errors:0 dropped:0 overruns:0 frame:0
          TX packets:896 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:369312 (360.6 KiB)  TX bytes:115735 (113.0 KiB)
          Interrupt:10 Base address:0x7000

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

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:104 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4872 (4.7 KiB)  TX bytes:1492 (1.4 KiB)

xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.255
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:812 errors:0 dropped:0 overruns:0 frame:0
          TX packets:815 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:361056 (352.5 KiB)  TX bytes:108721 (106.1 KiB)

# LANG=EN route -n
Kernel IP routing table
Destination     Gateway        Genmask         Flags Metric Ref    Use Iface
192.168.5.0     0.0.0.0        255.255.255.0   U     0      0        0 vif1.0
192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0 xen-br0
0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0 xen-br0

but ping to 192.168.5.2 still doesn't work. It doesn't work from domU either.

Thanks,
Christian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[B.G. Bruce]

Wouldn't that be better as a depends?  bridge-utils can be a
suggestion/recommends but iproute2 would be required whether or not you
are bridging or routing ... or am I missing something?
B.


On Thu, 2005-03-03 at 13:44, Adam Heath wrote:
> On Thu, 3 Mar 2005, Leigh Brown wrote:
> 
> > There is no IP address on the xen-br0 interface - and there should
> > be.
> >
> > I had this problem the other day when I had forgotten to install
> > iproute.  I'd hope the debian packages would make that a dependency
> > but you never know.  Is iproute installed?
> 
> Not a depends, maybe a suggest or recommends.  You can use routing instead of
> bridging.
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Nicholas Lee]

On Thu, Mar 03, 2005 at 10:14:44PM +0100, Christian Wicke wrote:
> > > But I still cannot ping to the domU. After
> > > # xm create -f speedyU.conf
> > > ifconfig shows an interface vif1.0, but nowhere anything with 192.168.5.
> > > (I configured my domU to 192.168.5.2)
> >
> > vif1.0 is just the p-t-p link for the tun device on the host side.
> >
> > Set the ip address in the guest on eth0.
> 
> I think I did:
> speedyU:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr AA:00:00:75:E8:9F
>           inet addr:192.168.5.2  Bcast:192.168.5.255  Mask:255.255.255.0

> # ifconfig vif1.0 192.168.5.1 pointopoint 192.168.5.2 up

> xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
>           inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.255


I think you are confused. Trying to use a routed setup with a bridged
configuration.

Please send though 'brctl show xen-br0'. However I suspect you need to
think like this.


In the bridged setup xen-br0 acts in two ways. As a virtual interface on
the host machine taking over the eth? role of provide an NIC interface
to the application layer. Second, as a virtual switch which other
interfaces on the host can plug into.


vif1.0 should have no IP in a bridged setup. It should only be connected
to the xen-br0 bridge. Packets from eth0 in domU go though the tun p-t-p
tunnel and hit the xen-br0 bridge. So eth0 on domU should be on the same
sbunet as xen-br0 on domO.


Try 
ifconfig eth0 addr:192.168.1.100

on domU.


I haven't tested this myself, but I assume in a routed setup vif1.0 and
eth0 are more like two networks cards with a crossover. In this case
you'd ignore the 'pointopoint' part of the configuration for vif1.0.

'ifconfig eth0 192.168.5.2' and 'ifconfig vif1.0 192.168.5.1' would
probably be sufficent. Nicholas


Nicholas


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Nicholas Lee]

On Thu, Mar 03, 2005 at 03:45:11PM +0100, Gerd Knorr wrote:
> Christian Wicke <xen.christian@safersignup.com> writes:
> 
> > Does anyone know what is the correct way to make this work?
> 
> The xen start script network setup doesn't work very good for me as
> well.  Sometimes it works, sometimes it doesn't, havn't figured yet
> why.
> 

Debian has some useful bridge scripts:
# dpkg -S /etc/network/if-pre-up.d/bridge
bridge-utils: /etc/network/if-pre-up.d/bridge


Then from /etc/network/interfaces:

# External Bridged Network.
auto br0
iface br0 inet static
        address 202.89.35.97
        netmask 255.255.255.240
        network 202.89.35.96
        broadcast 202.89.35.111
        gateway 202.89.35.110
        bridge_ports eth1
        bridge_fd 0
        bridge_hello 0
        bridge_stp off


# Internal Bridged Network.
#  10.0.0.1 - stateless-int
auto uml-intbr
iface uml-intbr inet static
        address 10.0.0.1
        netmask 255.255.0.0
        network 10.0.0.0
        broadcast 10.0.255.255
        bridge_ports dummy0
        bridge_fd 0
        bridge_hello 0
        bridge_stp off


Note the above is from my current UML setup. I'm replacing it with a
similar configuration for my new Xen setup.

Note, with the above you simply ignore eth0 in /etc/network/interfaces.

This gets up at: /etc/rcS.d/S39ifupdown before networking at
S40networking.

Nicholas




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Christian Wicke]

> In the bridged setup xen-br0 acts in two ways. As a virtual interface on
> the host machine taking over the eth? role of provide an NIC interface
> to the application layer. Second, as a virtual switch which other
> interfaces on the host can plug into.
>
>
> vif1.0 should have no IP in a bridged setup. It should only be connected
> to the xen-br0 bridge. Packets from eth0 in domU go though the tun p-t-p
> tunnel and hit the xen-br0 bridge. So eth0 on domU should be on the same
> sbunet as xen-br0 on domO.

Understood. All interfaces that are bridged together must share the same 
subnet. There is one ip address for the whole bridge. Therefore I don't need 
to assign an ip address to the vif interfaces inside the bridge.

>
> Try
> ifconfig eth0 addr:192.168.1.100
>
> on domU.

This works, great!

>
> I haven't tested this myself, but I assume in a routed setup vif1.0 and
> eth0 are more like two networks cards with a crossover. In this case
> you'd ignore the 'pointopoint' part of the configuration for vif1.0.
>
> 'ifconfig eth0 192.168.5.2' and 'ifconfig vif1.0 192.168.5.1' would
> probably be sufficent. Nicholas

Yes, this is working, too. But vif1.0 must not be on the brigde together with 
eth0 then. I took eth0 off from the bridge so that only the vif interfaces 
are bridged:

# brctl delif xen-br0 eth0 
# ifconfig xen-br0 192.168.5.1
# dhclient eth0 
# echo 1 > /proc/sys/net/ipv4/ip_forward
# iptables -t nat -A POSTROUTING -o eth0 -s 192.168.5.2 -j MASQUERADE

I summarize the result: 
* If I have a local network with free ip addresses in my subnet, then I assign 
those addresses to my domUs. The debian packages plus iproute work out of the 
box.
* If I don't have free ip addresses in the subnet of eth0, I use local 
addresses for my domU. I can bridge the vif interfaces so that they the domUs 
can talk to each other, but eth0 must not be on the bridge. I need to set up 
masquerading and ip forwarding if domU wants to connect to the internet.

Thank you for your help!
Christian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Networking problems with debian packages

[Nicholas Lee]

On Sat, Mar 05, 2005 at 10:12:30AM +0100, Christian Wicke wrote:
> * If I have a local network with free ip addresses in my subnet, then I assign 
> those addresses to my domUs. The debian packages plus iproute work out of the 
> box.

Yes, bridged network.

> * If I don't have free ip addresses in the subnet of eth0, I use local 
> addresses for my domU. I can bridge the vif interfaces so that they the domUs 
> can talk to each other, but eth0 must not be on the bridge. I need to set up 
> masquerading and ip forwarding if domU wants to connect to the internet.


I suggest you create a second bridge interface for routed vs bridge
interfaces.

Nicholas


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click