Difference between revisions of "IPv4 cleanup"
From Nsnam
(→Bugs and cleanup) |
(→Bugs and cleanup) |
||
| Line 11: | Line 11: | ||
* some XXXs remain around the multi-address (ip aliasing) code | * some XXXs remain around the multi-address (ip aliasing) code | ||
* case 4) of Ipv4L3Protocol::Send() is not implemented | * case 4) of Ipv4L3Protocol::Send() is not implemented | ||
| + | * should some of the routing protocol interfaces be aggregated to node? Not clear. | ||
== New features needed == | == New features needed == | ||
Revision as of 04:54, 1 June 2009
Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects
Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers
This page lists things that need to be done for IPv4 and routing protocols.
Bugs and cleanup
- IpForward attribute (ipv4.cc) doesn't do anything
- Ipv4L3Protocol::GetStaticRouting() needs to be deleted
- in general, Ipv4L3Protocol needs a lot of cleanup, and bugs/limitations documented in the tracker
- Ipv4L3Protocol needs a unit test
- some XXXs remain around the multi-address (ip aliasing) code
- case 4) of Ipv4L3Protocol::Send() is not implemented
- should some of the routing protocol interfaces be aggregated to node? Not clear.
New features needed
- Tunneling net device (Ipv4 in ipv4)
- Netlink-like routing API
- Public API to look at the ARP cache
- Multicast group membership, and non-source-specific multicast
- Ability to dump routing tables for logging/output
- helpers to provide iproute2-like interface
