Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
-R
Ryan B. Lynch ryan.b.lynch@gmail.com
On Fri, Aug 28, 2009 at 16:41:37 -0400, Ryan Lynch ryan.b.lynch@gmail.com wrote:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
You could run the ip commands to do this in a script. I have done that for some special stuff in the past. If you don't need it to work correctly when you up and down devices, but only at boot time, then it's pretty easy.
Ryan Lynch writes:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
On Fri, Aug 28, 2009 at 17:36, Sam Varshavchikmrsam@courier-mta.com wrote:
Ryan Lynch writes:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
That's exactly what I'm trying to avoid--I don't want Fedora to add the 'eth0:0', 'eth0:1', etc. labels. I'm wondering if the init scripts support multiple addresses WITHOUT aliases.
Ryan Lynch wrote:
On Fri, Aug 28, 2009 at 17:36, Sam Varshavchikmrsam@courier-mta.com wrote:
Ryan Lynch writes:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
That's exactly what I'm trying to avoid--I don't want Fedora to add the 'eth0:0', 'eth0:1', etc. labels. I'm wondering if the init scripts support multiple addresses WITHOUT aliases.
I've never been able to find a solution to that that didn't require running another script. /etc/rc.local is a kind of "catch all". There are also /etc/sysconfig/network-scripts/ifup-post and ifdown-post.
Using iproute2 certainly gives good control.
ip address add 10.20.30.40/8 dev eth0 ip address add 10.20.30.41/16 dev eth0 ip address add 10.20.30.42/24 dev eth0 ip address add 10.20.30.43/32 dev eth0 ip address add 192.168.1.1/24 dev eth0
is an example of how to add addresses to an interface.
You may also use the same command to setup routes for your new found diversity of addresses :)
On Fri, Aug 28, 2009 at 17:59, Mike Wrightmike.wright@mailinator.com wrote:
Ryan Lynch wrote:
On Fri, Aug 28, 2009 at 17:36, Sam Varshavchikmrsam@courier-mta.com wrote:
Ryan Lynch writes:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
That's exactly what I'm trying to avoid--I don't want Fedora to add the 'eth0:0', 'eth0:1', etc. labels. I'm wondering if the init scripts support multiple addresses WITHOUT aliases.
I've never been able to find a solution to that that didn't require running another script. /etc/rc.local is a kind of "catch all". There are also /etc/sysconfig/network-scripts/ifup-post and ifdown-post.
Using iproute2 certainly gives good control.
ip address add 10.20.30.40/8 dev eth0 ip address add 10.20.30.41/16 dev eth0 ip address add 10.20.30.42/24 dev eth0 ip address add 10.20.30.43/32 dev eth0 ip address add 192.168.1.1/24 dev eth0
is an example of how to add addresses to an interface.
You may also use the same command to setup routes for your new found diversity of addresses :)
I'm familiar with the manual method. What I'm wondering, now, is whether the init scripts support any method that achieve the same effect.
-R
Ryan Lynch wrote:
On Fri, Aug 28, 2009 at 17:59, Mike Wrightmike.wright@mailinator.com wrote:
Ryan Lynch wrote:
On Fri, Aug 28, 2009 at 17:36, Sam Varshavchikmrsam@courier-mta.com wrote:
Ryan Lynch writes:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
That's exactly what I'm trying to avoid--I don't want Fedora to add the 'eth0:0', 'eth0:1', etc. labels. I'm wondering if the init scripts support multiple addresses WITHOUT aliases.
I've never been able to find a solution to that that didn't require running another script. /etc/rc.local is a kind of "catch all". There are also /etc/sysconfig/network-scripts/ifup-post and ifdown-post.
Using iproute2 certainly gives good control.
ip address add 10.20.30.40/8 dev eth0 ip address add 10.20.30.41/16 dev eth0 ip address add 10.20.30.42/24 dev eth0 ip address add 10.20.30.43/32 dev eth0 ip address add 192.168.1.1/24 dev eth0
is an example of how to add addresses to an interface.
You may also use the same command to setup routes for your new found diversity of addresses :)
I'm familiar with the manual method. What I'm wondering, now, is whether the init scripts support any method that achieve the same effect.
Forget what I said about ifup-post and ifdown-post. That was a brain fart. I think there used to be ifup-local and ifdown-local but they no longer seem to be called. You could hack that into it, but from my point of view I'm trying to learn how to drink the fedora kool-aid. Looks like you are too. Sorry I couldn't be of more help.
Ryan Lynch wrote:
On Fri, Aug 28, 2009 at 17:36, Sam Varshavchikmrsam@courier-mta.com wrote:
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
That's exactly what I'm trying to avoid--I don't want Fedora to add the 'eth0:0', 'eth0:1', etc. labels. I'm wondering if the init scripts support multiple addresses WITHOUT aliases.
What is wrong with using the eth0:0 method? Is there some reason that it will not work for you?
Mikkel
Ryan Lynch wrote:
On Fri, Aug 28, 2009 at 17:36, Sam Varshavchikmrsam@courier-mta.com wrote:
Ryan Lynch writes:
Do the Fedora network init scripts support additional secondary IP addresses without the use of alias labels? Does an option for IPv4 addresses exist that works like IPV6ADDR_SECONDARIES?
I just skimmed /usr/share/doc/initscripts-*/sysconfig.txt, but I didn't see anything to that effect, so I'm guessing the answer is no, and I have to use aliases and 'ifcfg-eth?:0' files.
Yes, at least for IPv4. There is absolutely no support from the GUI, but you can manually install /etc/sysconfig/network-scripts/ifcfg-ethX:Y. For example, I have an ifcfg-eth1 and an ifcfg-eth1:1, with a second IP address. Just copy ifcfg-ethX to ifcfg-ethX:1, and stick in an additional IP address.
That's exactly what I'm trying to avoid--I don't want Fedora to add the 'eth0:0', 'eth0:1', etc. labels. I'm wondering if the init scripts support multiple addresses WITHOUT aliases.
At his point I think it would be good to explain what you are really trying to do, rather than how you would like to do it. What do you expect to see if you do what you want, and what tools would you use in place of the normal tools which expect an alias?
Note, adding a address via "ip" works in some odd ways you might not expect, and you have to set up routing by hand as well. What is wrong with the alias method which works for the rest of us?
On 2009-08-29, Bill Davidsen davidsen@tmr.com wrote:
Note, adding a address via "ip" works in some odd ways you might not expect, and you have to set up routing by hand as well. What is wrong with the alias method which works for the rest of us?
I'm aware of the differences in how iproute2 constructs interfaces, and the command syntax, (I do a lot of rule-based routing work), but I appreciate the concern.
I can believe that you've never encountered an application or situation where aliased interfaces become awkward. I didn't think it was asking a lot, to believe me that they do exist. But it sounds like maybe you don't, so here goes:
* Have you ever tried versioning your system/build configurations in SVN? * And did any of those system/build configurations include 'ifcfg-eth0:0'-style alias config files? * And then, did you try checking out those config SVN repos, for developer access, on Windows workstations?
If you don't have that experience, or something similar, then I can understand why you don't appreciate my grumbling over a "method which works for the rest of us."
Ryan Lynch wrote:
On 2009-08-29, Bill Davidsen davidsen@tmr.com wrote:
Note, adding a address via "ip" works in some odd ways you might not expect, and you have to set up routing by hand as well. What is wrong with the alias method which works for the rest of us?
I'm aware of the differences in how iproute2 constructs interfaces, and the command syntax, (I do a lot of rule-based routing work), but I appreciate the concern.
I can believe that you've never encountered an application or situation where aliased interfaces become awkward. I didn't think it was asking a lot, to believe me that they do exist. But it sounds like maybe you don't, so here goes:
- Have you ever tried versioning your system/build configurations in SVN?
- And did any of those system/build configurations include
'ifcfg-eth0:0'-style alias config files?
- And then, did you try checking out those config SVN repos, for
developer access, on Windows workstations?
I can assure you that my last Windows work was on Win-3.5 and that I would not in any event ever be checking out Linux developer files on a Windows workstation. I actually can't imagine those config files being useful on Windows, but if your point was that I don't share the problem, you're right, and thank God for it.
If you don't have that experience, or something similar, then I can understand why you don't appreciate my grumbling over a "method which works for the rest of us."
But now you have gotten to the real heart of the matter, which is not the aliases at all, but the filenames, if I read it correctly. And that opens up a whole can of solutions, depending on the part of Windows which is upset with the colon. Not knowing where the problem lies, I can't offer the slightest help, but there are other shells for Windows if the problem lies there, or whole Linux versions running in VM, paravirtualized, under qemu, or as a microkernel using colinux.
Your problem, if I understand it, is a Windows problem, not Fedora.
On 08/29/2009 04:18 PM, Bill Davidsen wrote:
But now you have gotten to the real heart of the matter, which is not the aliases at all, but the filenames, if I read it correctly. And that opens up a whole can of solutions, depending on the part of Windows which is upset with the colon. Not knowing where the problem lies, I can't offer the slightest help, but there are other shells for Windows if the problem lies there, or whole Linux versions running in VM, paravirtualized, under qemu, or as a microkernel using colinux.
I'm going to save you several hours' worth of researching: NTFS isn't capable of handling ':' characters in path names. There is no simple way to handle this, client-side, even in SVN.
You present a great idea, though--virtual machines! Each Windows user could install and run a whole virtual machine, and just switch over to using Linux. That sounds like a fantastic idea. It's so easy, too--all I'd have to do is:
- install virtualization software on those workstations - find or build a suitable Linux image - convince Windows users that the memory and disk sacrifices are worthwhile - teach/convince Windows users to use a Linux interface, dev tools, etc. - support the users, maintain the Linux images, etc.
Man, and I was going to write a 10-line BASH script that runs a couple of 'ip addr' commands. Crazy, I know--I'm glad I can use virtualization to solve this problem, instead.
Your problem, if I understand it, is a Windows problem, not Fedora.
That's a bit of a philosophical question, isn't it?
But this is getting kind of silly. My original question has been answered: The Fedora network init scripts DO NOT support multiple IPs, end of story.
-Ryan
Ryan B. Lynch wrote:
On 08/29/2009 04:18 PM, Bill Davidsen wrote:
But now you have gotten to the real heart of the matter, which is not the aliases at all, but the filenames, if I read it correctly. And that opens up a whole can of solutions, depending on the part of Windows which is upset with the colon. Not knowing where the problem lies, I can't offer the slightest help, but there are other shells for Windows if the problem lies there, or whole Linux versions running in VM, paravirtualized, under qemu, or as a microkernel using colinux.
I'm going to save you several hours' worth of researching: NTFS isn't capable of handling ':' characters in path names. There is no simple way to handle this, client-side, even in SVN.
You present a great idea, though--virtual machines! Each Windows user could install and run a whole virtual machine, and just switch over to using Linux. That sounds like a fantastic idea. It's so easy, too--all I'd have to do is:
- install virtualization software on those workstations
- find or build a suitable Linux image
- convince Windows users that the memory and disk sacrifices are worthwhile
- teach/convince Windows users to use a Linux interface, dev tools, etc.
- support the users, maintain the Linux images, etc.
Man, and I was going to write a 10-line BASH script that runs a couple of 'ip addr' commands. Crazy, I know--I'm glad I can use virtualization to solve this problem, instead.
I thought you rejected that manual method and wanted it done in system scripts. You said "I'm familiar with the manual method. What I'm wondering, now, is whether the init scripts support any method that achieve the same effect."
There are a number of images which include the whole virtualization environment and as I recall fit on a CD. Your ten line script could be run at startup, pull the files to a Windows filesystem with renaming, and terminate. I thought Windows could share files now so it could be done on one machine without forcing anyone to dedicate 500MB to soling their problem.
And when I had to do filesharing with Macs and couldn't handle a "/" in filenames it was a UNIX problem, so I think you have a Windows problem. MacOS, don't know if OS/X allows that.
The whole idea of Linux developers doing development on Windows workstations sounds like a pretty unusual situation, to be honest.
But this is getting kind of silly. My original question has been answered: The Fedora network init scripts DO NOT support multiple IPs, end of story.
That all depends on what you consider multiple IPs. You can do multiple ip addresses on the same network card with ip aliasing but they would need to be in the same subnet. You could also use vlans to put multiple ip address on a card with all the ip address going to different networks and you can even aliases ip address to the vlaned ip addresses. The init scripts will start all of those up as well.
The only thing the init scripts seem to really fail at is bringing up a bridge device that contains a bonded device as it forget to enable the bonded slaves. This is assuming you are not breaking the naming scheme of the config files.
-
Adam Hough -
Bill Davidsen -
Bruno Wolff III -
Mike Wright -
Mikkel -
Ryan Lynch -
Sam Varshavchik