[Ns-bugs] [Bug 188] global routing does not handle ip aliasing

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=188


gjcarneiro at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gjcarneiro at gmail.com
           Priority|P2                          |P1




------- Comment #12 from gjcarneiro at gmail.com  2008-06-10 14:07 -------
(In reply to comment #10)
> Comment from Tom:
> 
> Here is some more food for thought that we may consider about solving 
> this and bug 85.
> 
> In Linux, there is one ifIndex that refers to both the NetDevice (struct 
> net_device) and Ipv4Interface (struct in_device).  Each struct in_device 
> contains a list of struct in_ifaddr that actually hold the address bits.
> 
> So, it seems to me that a solution to these problems may lie in:
> 
> 1) adding support for multiple IP addresses for each Ipv4Interface
> - this changes the API and implementation for class Ipv4Interface, which 
> assumes a single address
> 
> 2) taking care to align ifIndex between NetDevice and Ipv4Interface
> 

I think this is a better solution.  For one thing, having different interface
indexes for L3 and L2 interfaces can be a source of confusion, especially wrt
to tracing.  Also it is always nice to align with a well known implementation,
Linux in this case.  Finally, for the IPv6 case it makes so much more sense,
because in IPv6 conceptually you have a single interface with a list of
addresses (even in ifconfig you only see eth0 with several ipv6 address, none
of the eth0:1, eth0:2... crap that is in ipv4).

Also, even if we have to drop "IP aliasing" support in IPv4, forever, would
anyone really be upset?


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.