Bug 782 – TapBridge::CreateTap () requires IP and Mac addresses in modes other than CONFIGURE_LOCAL

Bug 782 - TapBridge::CreateTap () requires IP and Mac addresses in modes other than CONFIGURE_LOCAL


Summary:	TapBridge::CreateTap () requires IP and Mac addresses in modes other than CON...

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	devices
Version:	ns-3-dev
Hardware:	All All

Importance:	P4 minor
Assigned To:	Craig Dowell

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-12-22 09:20 EST by Andrey Mazo
Modified:	2010-01-05 21:37 EST (History)
CC List:	1 user (show)

See Also:

Attachments
proposed fix (2.64 KB, patch) 2009-12-22 10:13 EST, Andrey Mazo	Details \| Diff
proposed fix (fixed logic) (2.65 KB, patch) 2009-12-22 10:38 EST, Andrey Mazo	Details \| Diff
Show Obsolete (1) 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 Andrey Mazo 2009-12-22 09:20:02 EST

CreateTap () method tries to get IP address and Mac address from underlying NetDevice.
If IP address is not assigned to the underlying NetDevice, CreateTap () will die even if that IP address is not really required (not in CONFIGURE_LOCAL mode).

Currently it is possible to create a tap bridge only for an interface with an IP address.

Although it's always possible to assign address to all interfaces, it may be rather difficult to introduce additional stub IP subnets in complex topologies.

Comment 1 Andrey Mazo 2009-12-22 10:13:25 EST

Created attachment 706 [details]
proposed fix

Comment 2 Andrey Mazo 2009-12-22 10:38:16 EST

Created attachment 707 [details]
proposed fix (fixed logic)