Bug 964 – AODV does not work with host addressed interfaces

Bug 964 - AODV does not work with host addressed interfaces


Summary:	AODV does not work with host addressed interfaces

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	aodv
Version:	pre-release
Hardware:	All All

Importance:	P5 normal
Assigned To:	Elena Buchatskaya

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-07-23 18:12 EDT by Tom Henderson
Modified:	2010-08-04 13:55 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
patch (7.08 KB, patch) 2010-07-23 18:12 EDT, Tom Henderson	Details \| Diff
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 Tom Henderson 2010-07-23 18:12:19 EDT

Created attachment 951 [details]
patch

MANET address architecture (in development at IETF) specifies that MANET interfaces should use a /32 address; see section 6.2 of
http://tools.ietf.org/html/draft-ietf-autoconf-adhoc-addr-model-03

Attached patch reworks some of the socket-related code to allow either a /32 or a non-/32 address.  there appears to be some trace divergence due to this patch in the aodv regression tests that needs to be investigated.

Comment 1 Elena Buchatskaya 2010-08-02 09:45:41 EDT

The only difference in traces is the UDP source port selected in Ipv4EndPointDemux::AllocateEphemeralPort ("Bug 772 UDP/TCP chain regression test"). After applying patch, AODV in NotifyInterfaceUp (uint32_t i) calls the socket->BindToNetDevice (l3->GetNetDevice (i)) resulting in selection the port, that before patch was used for binding socket in OnOff application. Thus socket in OnOff application is forced to use next port number.

I believe that this is not a bug and propose to generate new regression traces.

Comment 2 Elena Buchatskaya 2010-08-04 13:55:24 EDT

changeset 48625d668186