From: Oliver Zimmermann (oz_at_bluemonk.de)
Date: Mon 20 Jan 2003 - 18:07:07 GMT
On Tue, 21 Jan 2003 03:22:53 +1300
Sam Vilain <sam_at_vilain.net> wrote:
> Assuming that your vserver has its IP root correctly configured and
> bound via chbind, you can't actually see any of the details of the
> other interfaces. Just that they are physically present in the
> system.
Aha, then the presence is the normal behaviour, thank you. -
I can live with that, nevertheless there is no need to present the a
user the MAC-address and the traffic on an interface if it can be
avoided. I found out, that a vserver-user actually can use this
interface for pinging from it, when I temporarily
activated CAP_NET_RAW for raw sockets. The only thing he needs to know
is a valid destination IP.
eth0 Link encap:Ethernet HWaddr 00:06:5B:80:21:5F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41656 errors:0 dropped:0 overruns:0 frame:0
TX packets:26529 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:8807616 (8.3 MiB) TX bytes:5147423 (4.9 MiB)
Interrupt:28
Guten Tag
Oliver