Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosnetteam] || [Date Prev] [07-2006 Date Index] [Date Next] || [Thread Prev] [07-2006 Thread Index] [Thread Next]

[openbeosnetteam] Re: Interfaces

  • From: Nathan Whitehorn <nathanw@xxxxxxxxxxxx>
  • To: openbeosnetteam@xxxxxxxxxxxxx
  • Date: Tue, 11 Jul 2006 13:18:07 -0500 (CDT)


On Tue, 11 Jul 2006, Axel [iso-8859-15] Dörfler wrote:

Nathan Whitehorn <nathanw@xxxxxxxxxxxx> wrote:
IPv6 requires that every device have at least two addresses: a link-
local
address (fe80::) and a global address (e.g. 2001::). There is even an
additional domain beyond that for organizational internal routing,
and
machines adhering to the anonymous IPv6 address spec will typically
have
two global addresses at a time during an address transition.

Aliasing is also fantastically useful for IPv4 when hosts move or you
want
an internal/external addressing scheme like IPv6 uses. Maybe only a
few
people will use it, but it's good to have.

Okay, so I'm proposing the following: - if you create an interface /dev/net/ipro1000/0 it will be the first interface for this device - when you want another interface (with a different address), you would need to create another interface called /dev/net/ipro1000/0:n where n is a number greater than 0 (since that will refer to the first interface). - you can also refer to /dev/net/ipro1000/0 via /dev/net/ipro1000/0:0

IMO, that would make it simple and straight-forward to use.
Is everyone okay with this?

This would also eliminate the need for multiple address families per interface. If I have 2 IPv6 addresses and one IPv4 address for ipro1000/0, you can just create 3 interfaces. This seems like it would simplify things to some degree.
-Nathan




[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.