Drew,
You appear to have found a bug in the ifup script of SuSE 9.1. The
bug is not specific to the loopback device. Try "ifup eth0:1" with an
ifcfg-eth0:1 file in /etc/sysconfig/network. Same error.
However, the following work:
ifconfig lo:1 192.168.13.99
Also
ifconfig eth0:1 210.0.0.99
HTH,
Jeffrey
Quoting Drew Como
Jeff,
Actually, this didn't work. Within my network folder, I have a file that uses the MAC Address for it's name after the ifcfg. (ie. ifcfg-eth-id-00:06:5b:xx:xx:xx) I've made a copy of that and added a :1 to the end and change the information within. (This is how I used to do it using RedHat/Fedora.) It doesn't seem to be working for me.
I tried using the lo:1 interface that you discussed, however that is a local loopback device and it doesn't allow a 'real' IP to be bonded.
What else can I try?
Thanks :-)
Drew
wrote:
Quoting Drew Como
: Other than running a manual ipconfig to bring up a secondary IP, what it the best way in SuSE 9.1 to add a secondary IP into a NIC?
Add a ifcfg file in /etc/sysconfig/network. You can use Yast2 or a text editor. For example, ifcfg-lo:1 contains:
# Loopback (lo:1) configuration IPADDR=192.168.13.99 NETMASK=255.255.255.0 NETWORK=192.168.13.0 BROADCAST=192.168.13.255 STARTMODE=onboot
HTH, Jeffrey
__________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail
!DSPAM:40d85e5720371075489056!
On Thu, Jun 24, 2004 at 10:08:15AM -0500, Jeffrey Taylor wrote:
Drew, You appear to have found a bug in the ifup script of SuSE 9.1. The bug is not specific to the loopback device. Try "ifup eth0:1" with an ifcfg-eth0:1 file in /etc/sysconfig/network. Same error.
I don't see any bug in ifup script. It's just that SuSE switched to use ip command instead of ifconfig, and that happened around version 8.1 or 8.2
However, the following work:
ifconfig lo:1 192.168.13.99
Also
ifconfig eth0:1 210.0.0.99
But, ifup uses ip command, not ifconfig, to configure interfaces.
To temporarily add an alias to an interface eth0 I run something like this:
/sbin/ip addr add 192.168.59.249/24 dev eth0
And then it shows up in the output of ip show command:
/sbin/ip addr show eth0
2: eth0:
Quoting Kastus
On Thu, Jun 24, 2004 at 10:08:15AM -0500, Jeffrey Taylor wrote:
Drew, You appear to have found a bug in the ifup script of SuSE 9.1. The bug is not specific to the loopback device. Try "ifup eth0:1" with an ifcfg-eth0:1 file in /etc/sysconfig/network. Same error.
I don't see any bug in ifup script. It's just that SuSE switched to use ip command instead of ifconfig, and that happened around version 8.1 or 8.2
This is all very nice, but the manual indicates that the old way still works. "man ifup" also indicates that the way I described should work.
However, the following work:
ifconfig lo:1 192.168.13.99
Also
ifconfig eth0:1 210.0.0.99
But, ifup uses ip command, not ifconfig, to configure interfaces.
To temporarily add an alias to an interface eth0 I run something like this:
/sbin/ip addr add 192.168.59.249/24 dev eth0
And then it shows up in the output of ip show command:
[snip]
HTH, -Kastus
Yes, you have found another work around. But ifup is still broken. It does not match the printed manual or the man pages. Jeffrey
On Sat, Jul 03, 2004 at 01:20:52PM -0500, Jeffrey L. Taylor wrote:
Quoting Kastus
: This is all very nice, but the manual indicates that the old way still works. "man ifup" also indicates that the way I described should work.
I would consider that manual is lagging behind the code. [snip]
Yes, you have found another work around. But ifup is still broken. It does not match the printed manual or the man pages.
Actually, it wasn't me. Mads Martin Joergensen once posted the way it works to this list, and there is also an article in SDB explaining changes with introduction of ip command. http://portal.suse.com/sdb/en/2002/03/mmj_network80.html Qoute from the article: "Another important issue for network configuration is a switch to using the ip command instead of ifconfig and route. These commands will not go away or stop working. They only fall short if specific features only provided by ip are used." -Kastus
Quoting Kastus
On Sat, Jul 03, 2004 at 01:20:52PM -0500, Jeffrey L. Taylor wrote:
Quoting Kastus
: This is all very nice, but the manual indicates that the old way still works. "man ifup" also indicates that the way I described should work. I would consider that manual is lagging behind the code.
[snip]
Yes, you have found another work around. But ifup is still broken. It does not match the printed manual or the man pages.
Actually, it wasn't me. Mads Martin Joergensen once posted the way it works to this list, and there is also an article in SDB explaining changes with introduction of ip command. http://portal.suse.com/sdb/en/2002/03/mmj_network80.html
Qoute from the article:
"Another important issue for network configuration is a switch to using the ip command instead of ifconfig and route. These commands will not go away or stop working. They only fall short if specific features only provided by ip are used."
-Kastus
What does this have to do with the original question that had to do with ifup? I can make aliases work with ifconfig. What does your reply have to do with making ifup work as advertised? Jeffrey
On Sat, Jul 03, 2004 at 03:29:15PM -0500, Jeffrey L. Taylor wrote:
What does this have to do with the original question that had to do with ifup? I can make aliases work with ifconfig. What does your reply have to do with making ifup work as advertised?
I apologize, the subject of this thread still reads "Adding a secondary IP onto NIC"... I am replying to the subject, I am not starting new thread. I was just trying to explain how to do it the way SuSE designed it in 9.1, not how it used to work before 8.0. Regards, -Kastus
On Sat, 2004-07-03 at 11:09, Kastus wrote:
On Thu, Jun 24, 2004 at 10:08:15AM -0500, Jeffrey Taylor wrote:
Drew, You appear to have found a bug in the ifup script of SuSE 9.1. The bug is not specific to the loopback device. Try "ifup eth0:1" with an ifcfg-eth0:1 file in /etc/sysconfig/network. Same error.
I don't see any bug in ifup script. It's just that SuSE switched to use ip command instead of ifconfig, and that happened around version 8.1 or 8.2
Interesting I seem to have man pages for both ip and ifconfig. I did use ifconfig when setting up for university access. CWSIV
participants (4)
-
Carl William Spitzer IV
-
Jeffrey L. Taylor
-
Jeffrey Taylor
-
Kastus