SuSE 9.1 multiple IP woes (desperate!)
Hi, I'm at wit's end here. I've added a network config file for the additional interface in /etc/sysconfig/network called ifcfg-eth1:0 and on the boot I get this error message: etting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: 3Com Corporation 3c905 100BaseTX [Boomerang] eth0 configuration: eth-id-00:60:08:9a:8f:70 eth0 IP address: 69.55.227.107/24 done eth1 device: Intel Corp. 82801BD PRO/100 VE (LOM) Ethernet Controller (rev 81) eth1 configuration: eth-id-00:0c:f1:fa:71:d7 eth1 IP address: 69.55.227.101/24 doneWaiting for mandatory devices: eth1:0 19 18 17 16 15 14 13 11 10 9 8 7 6 5 4 3 2 1 0 eth1:0 interface could not be set up failedSetting up service network . . . . . . . . . . . . . . . .failed My ifcfg-eth1:0 file looks like this: PADDR='69.55.227.108' NETMASK='255.255.255.0' NETWORK='69.55.227.0' STARTMODE=onboot So I figured, okay I'll kludge it and I added a script to run ifconfig to add the interfaces. I've tried running the script in run level 2 and run level 3. I tried running the script out of boot.local. It didn't work at any level. I get the following error message: Adding network interfaces...<notice>startproc: execve (/sbin/ifconfig) [ /sbin/ifconfig eth0:0 69.55.227.102 netmask 255.255.255.0 broadcast 69.55.227.255 up ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux progress=19 INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=80 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin DO_CONFIRM= vga=0x311 RUNLEVEL=S PWD=/ PREVLEVEL=N LINES=30 kscripts=45 SHLVL=3 sscripts=45 splash=silent _=/sbin/startproc DAEMON=/sbin/ifconfig ] SIOCSIFADDR: No such device eth0:0: unknown interface: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth0:0: unknown interface: No such device eth0:0: unknown interface: No such device startproc: exit status of parent of /sbin/ifconfig: 255 <notice>startproc: execve (/sbin/ifconfig) [ /sbin/ifconfig eth0:1 69.55.227.103 netmask 255.255.255.0 broadcast 69.55.227.255 up ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux progress=19 INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=80 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin DO_CONFIRM= vga=0x311 RUNLEVEL=S PWD=/ PREVLEVEL=N LINES=30 kscripts=45 SHLVL=3 sscripts=45 splash=silent _=/sbin/startproc DAEMON=/sbin/ifconfig ] SIOCSIFADDR: No such device eth0:1: unknown interface: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth0:1: unknown interface: No such device eth0:1: unknown interface: No such device startproc: exit status of parent of /sbin/ifconfig: 255 But here's the thing: If I log on right after the boot and run the script, it works perfectly fine. So I know the script works, but it doesn't work on the boot. What am I doing wrong???? TIA, Jeff
On Saturday 22 May 2004 3:11 pm, root@sid.armstrong.com wrote:
Hi,
I'm at wit's end here. I've added a network config file for the additional interface in /etc/sysconfig/network called ifcfg-eth1:0 and on the boot I get this error message:
[snip]
So I figured, okay I'll kludge it and I added a script to run ifconfig to add the interfaces. I've tried running the script in run level 2 and run level 3. I tried running the script out of boot.local. It didn't work at any level. I get the following error message:
[snip]
But here's the thing: If I log on right after the boot and run the script, it works perfectly fine. So I know the script works, but it doesn't work on the boot. What am I doing wrong????
TIA, Jeff
I am sorry to say I have no advice to give on this one. But, Jeff and others affected by this issue, I hope you will stay to the end of this, because it probably needs raising with feedback: http://www.suse.de/cgi-bin/feedback.cgi I too am struggling with the issue of a second interface. Although I saw the earlier thread on this issue, it remains on the back burner, until I have sorted out the boot delay problem [another thread]. Fortunately, I am only trying 9.1 on a spare partition, I still have my 9.0 working. My requirements are different from yours, although under 9.0, like you, I use an ifcfg-eth0:0 file. I run 2 virtual LANs, one for SAMBA which has fixed IP and no route to the internet, which is the only LAN boxes booted to windows are allowed to see. The other is DHCP, with a route to the internet, only for boxes booted to Linux. The latest sysconfig scheme does not appear able to open 2 interfaces on 1 device, with static and DHCP. Whether this is a deficiency of sysconfig, or its documentation I am not sure. As much as I read in /usr/share/doc/packages/sysconfig/README, is that for various reasons, it has been decided to clarify the abstractions of 'device' and 'interface', to better cope with hot-plugging and otherwise optional hardware and provide consistent interface names over reboots and hotplug events. So far so good, I understand what they are trying to do, and I think it is the right thing [in the long run]. However, the implementation is immature, [and or] the README referenced is incomplete and there is no adequate documentation. In my opinion, sysconfig should not have been released in its present state. I think that SUSE really must make a serious decision here. 1] If sysconfig can actually support mutiple IP in all the ways which posters on the topic are trying to use it, so that if they did something before without a script, they still can, and if they did something before with a script, the script either still works or can be easily changed, then SUSE need to put out some comprehensive documentation QUICKLY. 2] If 1] does not apply, then SUSE should QUICKLY put up a YOU patch to revert sysconfig to 9.0. Alll the best Vince Littler
Hi, On Saturday 22 May 2004 17:30, Vince Littler wrote:
1] If sysconfig can actually support mutiple IP in all the ways which posters on the topic are trying to use it, so that if they did something before without a script, they still can, and if they did something before with a script, the script either still works or can be easily changed, then SUSE need to put out some comprehensive documentation QUICKLY.
2] If 1] does not apply, then SUSE should QUICKLY put up a YOU patch to revert sysconfig to 9.0.
From /var/lib/YaST2/you/mnt/i386/update/9.1/patches/yast2-network-51427 --- snip ----- Longdescription.english: Fixes saving changes in ISDN internet service providers, for example toggling Dial on Demand. Also allows entering 4 WEP keys and re-adds support for multiple IP addresses per interface. --- snap ----- ==> run YOU. Greetings from Bremen hartmut
On Sunday 23 May 2004 9:06 pm, Hartmut Meyer wrote:
Hi,
On Saturday 22 May 2004 17:30, Vince Littler wrote:
1] If sysconfig can actually support mutiple IP in all the ways which posters on the topic are trying to use it, so that if they did something before without a script, they still can, and if they did something before with a script, the script either still works or can be easily changed, then SUSE need to put out some comprehensive documentation QUICKLY.
2] If 1] does not apply, then SUSE should QUICKLY put up a YOU patch to revert sysconfig to 9.0.
From /var/lib/YaST2/you/mnt/i386/update/9.1/patches/yast2-network-51427
--- snip ----- Longdescription.english: Fixes saving changes in ISDN internet service providers, for example toggling Dial on Demand. Also allows entering 4 WEP keys and re-adds support for multiple IP addresses per interface. --- snap -----
==> run YOU.
Thanks Hartmut Can't say SUSE are not responsive! This probably belongs in the "Wrong Order" thread, because the patch is dated 19 May... Right, I'm off to get the patch. Vince
On Sun, May 23, 2004 at 10:06:29PM +0200, Hartmut Meyer wrote:
Hi,
On Saturday 22 May 2004 17:30, Vince Littler wrote:
1] If sysconfig can actually support mutiple IP in all the ways which posters on the topic are trying to use it, so that if they did something before without a script, they still can, and if they did something before with a script, the script either still works or can be easily changed, then SUSE need to put out some comprehensive documentation QUICKLY.
2] If 1] does not apply, then SUSE should QUICKLY put up a YOU patch to revert sysconfig to 9.0.
From /var/lib/YaST2/you/mnt/i386/update/9.1/patches/yast2-network-51427
--- snip ----- Longdescription.english: Fixes saving changes in ISDN internet service providers, for example toggling Dial on Demand. Also allows entering 4 WEP keys and re-adds support for multiple IP addresses per interface. --- snap -----
==> run YOU.
I applied yast2-network-2.9.43-0.2.i586.rpm and it had no effect. On the
boot none of the additional interfaces comes up. But if I run
network restart *after* I log back in from the reboot, then all the
additional IP addresses come up.
However now that I've applied the patch, I get this message in the
boot.msg log:
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done eth0 device: 3Com Corporation 3c905 100BaseTX [Boomerang]
eth0 configuration: eth-id-00:60:08:9a:8f:70
eth0 IP address: 69.55.227.107/24
IP address: 69.55.227.108/24
IP address: 69.55.227.109/24
IP address: 69.55.227.110/24
IP address: 69.55.227.111/24
IP address: 69.55.227.112/24
IP address: 69.55.227.113/24
IP address: 69.55.227.114/24
IP address: 69.55.227.115/24
done eth1 device: Intel Corp. 82801BD PRO/100 VE (LOM) Ethernet
Controller (rev 81)
eth1 configuration: eth-id-00:0c:f1:fa:71:d7
eth1 IP address: 69.55.227.101/24
IP address: 69.55.227.102/24
IP address: 69.55.227.103/24
IP address: 69.55.227.104/24
IP address: 69.55.227.105/24
IP address: 69.55.227.106/24
doneSetting up service network . . . . . . . . . . . . . .
. .done
Based on that message, you would *think* the additional IP addresses
came up on the boot. They did not. I had to run "network restart" in
order to bring them up. I've now lost two weeks on this problem.
Jeff
--
#include
participants (4)
-
Hartmut Meyer -
Jeff Fulmer -
root＠sid.armstrong.com -
Vince Littler