Bug 402 – IPv4 GlobalRouting does not handle /32 interfaces

Bug 402 - IPv4 GlobalRouting does not handle /32 interfaces

Summary:

IPv4 GlobalRouting does not handle /32 interfaces

Status:	RESOLVED INVALID

Product:	ns-3
Component:	routing
Version:	ns-3-dev
Platform:	All All

Importance:	P3 normal
Assigned To:	Tom Henderson

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-11-07 10:27 EDT by Tom Henderson
Modified:	2009-06-30 00:54 EDT (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Tom Henderson 2008-11-07 10:27:06 EDT

Fails with:
Ipv4::GetIfIndexByAddress failed

This should be later tested as part of routing refactoring.

------- Comment #1 From Tom Henderson 2008-11-17 17:33:41 EDT -------

Lowering priority (aim for 3.4 release).  Not expected to be an important use
case for the moment.

------- Comment #2 From Tom Henderson 2008-12-08 09:32:55 EDT -------

Use case:

/32 netmasks are sometimes used in MANET routing over WiFi; each node gets a
/32 address.  However, /32 netmasks are illegal for broadcast links in OSPF
(which is what global routing is patterned after).

If global routing is run over such a configured MANET today, it will fail. 
This is because the WifiNetDevice is identified as a broadcast interface.

The solution seems to be to add support for point-to-multipoint logic in global
routing (which can handle the /32), and to somehow flag that the WifiNetDevice
is not a typical broadcast link so that global routing can pick this up and
treat it accordingly.

------- Comment #3 From Tom Henderson 2009-06-30 00:54:49 EDT -------

not sure this is a valid report anymore; examples/global-routing-slash32.cc has
been checked in in the meantime