But that still doesn't solve the problem: Having eth0:0 allows to add a special routing entry for that virtual device, just adding a second IP to eth0 does not. So this doesn't really help.
they *do* show up in the ifconfig output. As one poster mentioned, look
They don't do here:
galois home/fst# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:0A:5E:02:9B:39 inet addr:141.84.1.30 Bcast:141.84.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2263 errors:0 dropped:0 overruns:0 frame:0 TX packets:2203 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:418308 (408.5 Kb) TX bytes:357885 (349.4 Kb) Interrupt:169
galois home/fst# ip a 1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0a:5e:02:9b:39 brd ff:ff:ff:ff:ff:ff inet 141.84.1.30/24 brd 141.84.1.255 scope global eth0 inet 192.168.141.30/24 brd 192.168.141.255 scope global eth0
There is no problem calling "ifconfig eth0:0 192.168.141.30 up" to set up a virtual device. I just wonder why it is not possible to define a virtual device via an ifcfg-file so that /etc/init.d/network will set such a device up.
Hm? Is not the IPADDR / IPADDR_2 thing enough? -`J' -- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org