On February 28, 2005 11:48 pm, Kevin P. Fleming wrote:
> IMO, this is completely the wrong way to go. Creating VLAN interfaces
It wasn't perfect no. It was one of those cases of "I have 5 minutes to get it
done, need to hack existing script to add vlan capabilities."
> should be the domain of a "vlan" service script, not "ipv4-static",
> which assigns IPV4 addresses to existing interfaces.
I just combined the two so IP addresses can be added right away instead of
having to run two scripts.
> Then, in the ifconfig.eth0 directory, I create two files called "vlan10"
> and "vlan20". Each of these files looks like this:
>
> I then have two more directories, named ifconfig.eth0.10 and
> ifconfig.eth0.20, which each contain an "ipv4" file that uses the
> ipv4-static script to assign an IP address to that VLAN interface.
>
> This works very well, I have no trouble with "link up" being applied to
> the wrong place (although I've not yet updated to Nathan's latest
> bootscripts, which have been changed for some reason I don't understand...)
Your method would do the trick too yes, as long as ifconfig.eth0 gets run
before ifconfig.eth0.{10,20}. It seems that is the case seeing how things
sort alphabetically. Then you get the link up on eth0 first, then on eth0.10.
Now a hypothetical situation: what if things didn't order alphabetically that
way for some reason? There's no dependency information here so things could
be fragile in other situations and possible be run in the wrong order.
--
Gerard Beekmans
/* If Linux doesn't have the solution, you have the wrong problem */
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
