Messages in this thread | | | Date | Fri, 02 Dec 2005 12:08:17 -0800 | From | Ben Greear <> | Subject | Re: [RFC] ip / ifconfig redesign |
| |
Al Boldi wrote: > The current ip / ifconfig configuration is arcane and inflexible. The reason > being, that they are based on design principles inherited from the last > century. > > In a GNU/OpenSource environment, OpenMinds should not inhibit themselves > achieving new design-goals to enable a flexible non-redundant configuration. > > Specifically, '#> ip addr ' exhibits this issue clearly, by requiring to > associate the address to a link instead of the other way around. > > Consider this new approach for better address management: > 1. Allow the definition of an address pool > 2. Relate links to addresses > 3. Implement to make things backward-compatible. > > The obvious benefit here, would be the transparent ability for apps to bind > to addresses, regardless of the link existence. > > Another benefit includes the ability to scale the link level transparently, > regardless of the application bind state.
Can you do this with the current code by using scripts/whatever to move virtual IPs around the interfaces?
I guess I don't really understand what you are proposing...
Ben
> > And there may be many other benefits... (i.e. 100% OSI compliance) > > -- > Al > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >
-- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |