put it in /etc/boot.local On Thu, 2005-08-04 at 15:29 +0300, Michael Green wrote:

On 8/4/05, Ken Schneider wrote:

...

...

And what would be the proper way of making virtual aliases created with 'ip' permanent (survive reboot)?

Anyone? Have you tried using YaST to add the virtual IP's?

Yes, I tried. It wouldn't allow me top create an interface named 'eth0:1'

What I'm doing is adding another IP to eth0 (192.168.1.20)

ip addr add 192.168.1.100/24 label eth0:1 dev eth0

Then it shows up in ifconfig. but YaST wouldn't allow ':' to be part of the interface name/label. So I currently I have no choice but to run this manually after each reboot.

Now, I feel quite comfortable with NOT using YaST but then how do I make this permanent. there is no script in /etc/init.d/ that would allow me to run 'ip' in the manner as above. Should I write this script myself?

Surely, I'd love to hear what's the official SuSE's stance on this.. -- Warm regards, Michael Green

Actually in yast, select the interface you are dealing with, then choose advanced, then additional addresses. On Thu, 2005-08-04 at 15:29 +0300, Michael Green wrote:

On 8/4/05, Ken Schneider wrote:

...

...

And what would be the proper way of making virtual aliases created with 'ip' permanent (survive reboot)?

Anyone? Have you tried using YaST to add the virtual IP's?

Yes, I tried. It wouldn't allow me top create an interface named 'eth0:1'

What I'm doing is adding another IP to eth0 (192.168.1.20)

ip addr add 192.168.1.100/24 label eth0:1 dev eth0

Then it shows up in ifconfig. but YaST wouldn't allow ':' to be part of the interface name/label. So I currently I have no choice but to run this manually after each reboot.

Now, I feel quite comfortable with NOT using YaST but then how do I make this permanent. there is no script in /etc/init.d/ that would allow me to run 'ip' in the manner as above. Should I write this script myself?

Surely, I'd love to hear what's the official SuSE's stance on this.. -- Warm regards, Michael Green

On 8/4/05, Patrick Shanahan wrote:

There was discussion here earlier this year. As I recall, perhaps incorrectly, the use of "eth0" and "eth1" ... was not allowed. You may do a google list search and determine the correct naming, as it was explained in detail.

I''ll try to find it. I'm curious what's wrong with eth0:1 eth1:1 scheme though. -- Warm regards, Michael Green

Michael Green wrote:

On 8/4/05, Michael Green wrote:

...

On 8/4/05, Patrick Shanahan wrote:

...

There was discussion here earlier this year. As I recall, perhaps incorrectly, the use of "eth0" and "eth1" ... was not allowed. You may do a google list search and determine the correct naming, as it was explained in detail.

I''ll try to find it.

Ok, I can report success here with directly editing appropriate interface config files in /etc/sysconfig/network.

Found the discussion here (that helped) http://lists.suse.com/archives/suse-linux-e/2004-Jul/index.html#482

Why however YaST wouldn't swallow 'eth0:1' as 'Alias Name' in the Network Cards module is beyond my understanding.

This should have been explained in the archived articles. If you have multiple network cards, whichever one is assigned "eth0" depends on which is initialized first, and that can vary between boots. I remember seeing something somewhere about fixing the initialization order at boot time, but cannot recall where it was -- something dealing with the PCI bus, I think. Nevertheless, you still cannot use eth<n> to refer to a specific network card (nor in fact can you even use "eth<anything>" as a "persistent name" for a network device). It follows, if you cannot refer to a particular network card as eth0, that you also cannot refer to it by an alias such as eth0:1. As already explained by another responder, Yast/Network Devices --> Network Card; then select the appropriate device, click "Change", to bring up the configuration overview, then click "Edit" to bring up the details for that card. Select Advanced --> Additional Addresses, and add the necessary IP alias(es) for that device.

On 8/4/05, Doug Currey wrote:

Doesn't yast just add the lines to the proper ifcfg-eth******* file in the form of

IPADDR_20='192.168.1.20' LABEL_20='20'

This worked with 9.3 anyway.

I'll try that, thanks.. -- Warm regards, Michael Green