|
Bugzilla – Full Text Bug Listing |
| Summary: | Radvd does not set ttl value | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Fabian Mauchle <f1mauchl> |
| Component: | applications | Assignee: | Sebastien Vincent <vincent> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | faker.moatamri, ns-bugs |
| Priority: | P5 | ||
| Version: | ns-3-dev | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | workaround | ||
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 ? Done 035a59e5798e. |
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.