Re: [expert] bringing up virtual interfaces at boot
You should probably write a startup script that contains what you have put in your rc.local, and just ensure that it runs before smb,named,dhcp etc by ensuring that the symlink in your run-level directory has a lower value than the first newtork service. Look in your /etc/rc3.d directory ... Buchan Tib wrote: [EMAIL PROTECTED]"> My machine has one interface (tried putting more in, but the pci expansion bus is next to impossible to deal with) and so I've had to create virtual interfaces to create the illusion of a separated network for firewall security etc.. The problem is this though. If I put a line in rc.local of 'ifconfig blahblahblah' then it doesn't create the interface in time for services like dhcp and samba to start up, so they try to start and bind to an interface that doesn't exist, and die. Plus, named doesn't bind to that interface either which means I have to hand restart (or script, whatever) 3 services in order for it to work properly. As mentioned above, I've scripted a work around, but that means that should that script for some reason fail - I'm screwed unless I'm at the terminal. Is it possible to setup files under the network-scripts path that are for the virtual interfaces? ie: ifcfg-eth0:1 etc scripts? I created some modeled off of ifcfg-eth0, but haven't rebooted yet. will this work or should I just rely on my scripts? EOL Tib
Re: [expert] bringing up virtual interfaces at boot
On Mandrake (7.1 at least), there is no need to muck around with rc.local. Simply create a file similar to the following: # cat /etc/sysconfig/network-scripts/ifcfg-eth0:1 DEVICE=eth0:1 BOOTPROTO=static IPADDR=111.111.22.111 NETMASK=255.255.255.0 NETWORK=111.111.22.0 BROADCAST=111.111.22.255 -Mark Tib wrote: My machine has one interface (tried putting more in, but the pci expansion bus is next to impossible to deal with) and so I've had to create virtual interfaces to create the illusion of a separated network for firewall security etc.. The problem is this though. If I put a line in rc.local of 'ifconfig blahblahblah' then it doesn't create the interface in time for services like dhcp and samba to start up, so they try to start and bind to an interface that doesn't exist, and die. Plus, named doesn't bind to that interface either which means I have to hand restart (or script, whatever) 3 services in order for it to work properly. As mentioned above, I've scripted a work around, but that means that should that script for some reason fail - I'm screwed unless I'm at the terminal. Is it possible to setup files under the network-scripts path that are for the virtual interfaces? ie: ifcfg-eth0:1 etc scripts? I created some modeled off of ifcfg-eth0, but haven't rebooted yet. will this work or should I just rely on my scripts? EOL Tib -- Mark Belanger LTX Corporation
[expert] bringing up virtual interfaces at boot
My machine has one interface (tried putting more in, but the pci expansion bus is next to impossible to deal with) and so I've had to create virtual interfaces to create the illusion of a separated network for firewall security etc.. The problem is this though. If I put a line in rc.local of 'ifconfig blahblahblah' then it doesn't create the interface in time for services like dhcp and samba to start up, so they try to start and bind to an interface that doesn't exist, and die. Plus, named doesn't bind to that interface either which means I have to hand restart (or script, whatever) 3 services in order for it to work properly. As mentioned above, I've scripted a work around, but that means that should that script for some reason fail - I'm screwed unless I'm at the terminal. Is it possible to setup files under the network-scripts path that are for the virtual interfaces? ie: ifcfg-eth0:1 etc scripts? I created some modeled off of ifcfg-eth0, but haven't rebooted yet. will this work or should I just rely on my scripts? EOL Tib
