|
Bugzilla – Full Text Bug Listing |
| Summary: | OLSR ignores specified outgoing interface in RouteOutput() | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Tom Henderson <tomh> |
| Component: | routing | Assignee: | Gustavo J. A. M. Carneiro <gjcarneiro> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jpelkey, ns-bugs |
| Priority: | P2 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | patch enforcing the oif parameter | ||
Created attachment 721 [details]
patch enforcing the oif parameter
Comment on attachment 721 [details]
patch enforcing the oif parameter
No comments on the patch. Looks plausible, and you know the new routing API better them I, so...
Gustavo, can you push this one? Committed. changeset: 5946:4fef76630d66 tag: tip user: Tom Henderson <tomh@tomh.org> date: Wed Feb 03 15:17:27 2010 +0000 summary: Bug 778 - OLSR ignores specified outgoing interface in RouteOutput() |
OLSR does not do anything with the oif parameter, which may be set by Socket::BindToDevice(). This was changed from an interface index to a device pointer, but OLSR has not been handling this parameter yet. Ptr<Ipv4Route> RoutingProtocol::RouteOutput (Ptr<Packet> p, const Ipv4Header &header, Ptr<NetDevice> oif, Socket::SocketErrno &sockerr) It says: // TBD: oif is unused; can be used to restrict the outgoing interface // of the found route if application bound to a source interface