From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Sun 06 Feb 2005 - 00:06:45 GMT
On Fri, Feb 04, 2005 at 10:18:51AM +0100, primero wrote:
> Darryl Ross wrote:
>
> >Yes, that is normal, at least in my experience. You will notice if you
> >look closer that you can't see the IP address of the actual eth0 device.
> >
> What you mean with "you can't see" ?
hmm, maybe this is 'normal' for debian, but here it
looks like this:
$ vserver XXXX enter
ipv4root is now 192.168.0.2
New security context is 1001
[root_at_vserver:XXXX /]ifconfig
eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:144 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:8640 (8.4 Kb)
Interrupt:9 Base address:0xc100
eth0:XXXX Link encap:Ethernet HWaddr 52:54:00:12:34:56
inet addr:192.168.0.2 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0xc100
lo Link encap:Local Loopback
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:112 errors:0 dropped:0 overruns:0 frame:0
TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9217 (9.0 Kb) TX bytes:9217 (9.0 Kb)
with 1.2.10 (2.4.29) and
vserver XXXX enter
ipv4root is now 192.168.0.2
New security context is 1001
[root_at_vserver:XXXX /]ifconfig
eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:4620 (4.5 Kb)
Interrupt:9 Base address:0xc100
eth0:XXXX Link encap:Ethernet HWaddr 52:54:00:12:34:56
inet addr:192.168.0.2 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0xc100
with 1.9.4-rc4 (on 2.6.11-rc3)
(using hide_netif flag, which is default with 0.30.196++)
HTH,
Herbert
> this is my output:
>
> ------------------------------------------------------------
>
> Shadow root # vserver template-debian enter
> WARNING: can not find configuration, assuming legacy method
> ipv4root is now 192.168.101.2
> New security context is 3
> mesg: /dev/pts/4: Operation not permitted
> template-debian:/# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:11:2F:A7:B3:87
> inet addr:192.168.101.130 Bcast:192.168.101.63
> Mask:255.255.255.192
> inet6 addr: fe80::211:2fff:fea7:b387/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:960550 errors:0 dropped:0 overruns:0 frame:0
> TX packets:696334 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1112512141 (1.0 GiB) TX bytes:84828908 (80.8 MiB)
> Interrupt:169 Memory:f7d00000-0
>
> eth0:temp Link encap:Ethernet HWaddr 00:11:2F:A7:B3:87
> inet addr:192.168.101.2 Bcast:192.168.101.63
> Mask:255.255.255.192
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:169 Memory:f7d00000-0
>
> 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:2405 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2405 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2973599 (2.8 MiB) TX bytes:2973599 (2.8 MiB)
>
> template-debian:/#
>
> -------------------------
>
> As you can check i see both "eth0" and "eth0:template-debian" inside the
> vserver ... i was wondering what would happens if i start another one
> vserver on a second alias interface ... would i see all the three
> interfaces?
>
> btw ... if it sounds normal i'll don't mind too much. :)
>
> >Regards
> >Darryl
> >
> Bye
> P.
>
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver