Bug 771 – Radvd does not set ttl value

Bug 771 - Radvd does not set ttl value


Summary:	Radvd does not set ttl value

Status:	RESOLVED FIXED

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

Importance:	P5 normal
Assigned To:	Sebastien Vincent

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-12-04 04:39 UTC by Fabian Mauchle
Modified:	2009-12-18 12:44 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
workaround (644 bytes, patch) 2009-12-04 04:39 UTC, Fabian Mauchle	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 Fabian Mauchle 2009-12-04 04:39:04 UTC

Created attachment 693 [details]
workaround

RFC 4861 defines a ttl value of 255 for Router Advertisements, but the RadvdApplication does not set this value. 
As the ns-3 IPv6 stack does not check this value, the stateless autoconfiguration works anyway within ns-3, but not with real nodes (windows & linux) in emulation.

The patch is only a quick workaround, which adds a SocketIpTtl value itself. This value should normally be set as a socket option, but raw sockets currently do not support this.

Comment 1 Sebastien Vincent 2009-12-16 11:42:55 UTC

Yes we still lake "true" raw socket implementation (like Unix do). So I am OK with your patch.

+1

Other comments before I commit this patch ?

Comment 2 Sebastien Vincent 2009-12-18 12:44:28 UTC

Done 035a59e5798e.