Just for the record, the routes with strange "ifN" interfaces seem to be added by the kernel if the host has this route but the guest has no corresponding interface defined. Which is fine by me I guess...
Otherwise, everything works as expected. Thanks, peter. On Wednesday 06 September 2006 22:09, Herbert Poetzl wrote: > On Tue, Sep 05, 2006 at 05:46:55PM +0200, Peter Sabaini wrote: > > On Monday 04 September 2006 22:08, Herbert Poetzl wrote: > > > On Wed, Aug 30, 2006 at 03:20:28PM +0200, Peter Sabaini wrote: > > > > Hi list, > > > > -- snip -- > > > > > > I've got a small question concerning networking and VLANs on a box > > > > I'of mine; m puzzled by additional routes which seem to get added > > > > I'automatically. > > > > > > > > On the host: > > > > > > > > kili# pwd > > > > /etc/vservers/kili-dns/interfaces/eth5.10 > > > > kili# ll > > > > total 8.0K > > > > -rw-r--r-- 1 root root 8 2006-08-29 17:47 dev > > > > -rw-r--r-- 1 root root 11 2006-08-29 17:31 ip > > > > -rw-r--r-- 1 root root 0 2006-08-29 17:41 novlandev > > > > kili# cat ip dev > > > > 10.2.0.193 > > > > eth5.10 > > > > > > > > In the vserver: > > > > > > > > kili-dns# ip route show > > > > 10.2.0.0/24 dev eth5.10 proto kernel scope link src 10.2.0.1 > > > > 10.0.0.0/24 dev if6 proto kernel scope link src 10.0.0.2 > > > > > > hmm, somehow I doubt that the if6 is related > > > to linux-vserver or the setup ... > > > > I'm not really sure I've got to admit > > > > > > The first line is expected; does anyone have any idea how the > > > > route to 10.0.0.0/24 via the (unknown) interface "if6" got added? > > > > > > maybe some hotplug events or something similar? > > > > Unlikely; theres not hotplugging/HAL system on this machine. Moreover, > > there *is* no real interface device, running "ip link show" on the guest > > gives: > > > > # ip link show > > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 > > link/ether 00:15:17:0e:18:7a brd ff:ff:ff:ff:ff:ff > > > > My first guess was that the ip utility added some automatic routes, but > > then the interface would show up as 'eth0' not some dummy interface. > > > > Any further ideas how to debug this? > > well, first 'idea' would be to get a recent kernel > (e.g. 2.6.17.11) together with the stable 2.02 > release and check if you see any of those issues > there, if they persist, we can look into it in > more detail ... > > TIA, > Herbert > > > TIA, > > peter. > > > > > best, > > > Herbert > > > > > > > These are both Ubuntu systems running dapper; vserver-info: > > > > > > > > kili# vserver-info > > > > Versions: > > > > Kernel: 2.6.15-27-server > > > > VS-API: 0x00020001 > > > > util-vserver: 0.30.210; Jul 17 2006, 14:33:18 > > > > > > > > Features: > > > > CC: gcc, gcc (GCC) 4.0.3 (Ubuntu > > > > 4.0.3-1ubuntu5) CXX: g++, g++ (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5) > > > > CPPFLAGS: '' > > > > > > > > CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time' > > > > > > > > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 > > > > -funit-at-a-time' build/host: i486-pc-linux-gnu/i486-pc-linux-gnu > > > > Use dietlibc: yes > > > > Build C++ programs: yes > > > > Build C99 programs: yes > > > > Available APIs: v13,net > > > > ext2fs Source: e2fsprogs > > > > syscall(2) invocation: alternative > > > > vserver(2) syscall#: 273/glibc > > > > > > > > Paths: > > > > prefix: /usr > > > > sysconf-Directory: /etc > > > > cfg-Directory: /etc/vservers > > > > initrd-Directory: $(sysconfdir)/init.d > > > > pkgstate-Directory: /var/run/vservers > > > > vserver-Rootdir: /var/lib/vservers > > > > > > > > > > > > > > > > Thanks, > > > > peter. > > > > _______________________________________________ > > Vserver mailing list > > Vserver@list.linux-vserver.org > > http://list.linux-vserver.org/mailman/listinfo/vserver -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter Sabaini ARC Seibersdorf research GmbH Biomedical Engineering / eHealth systems Reininghausstrasse 13/1, 8020 Graz, Austria T: +43(0)316 586570-55, F:+43(0)316 586570-12 [EMAIL PROTECTED], http://www.arcsmed.at/ehs _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
