Displaying the routing table of a node

[ManiAm]

The routing table of nodes is messy and a sorting mechanism should be incorporated to make it more readable. For example look at the routing table of a router:

I think, the routing table should look similar to this:

All the interface routes are at the top, followed by all MANUAL routes (by the network administrator), followed by all routing protocol routes (RIP, OSPF, BGP). This is not only more readable, but also reflects the order that routes are added into the routing table: interface, ipv4configurator, routing protocol.

Edit: After digging further into the code, I found out that the routing entries are actually sorted in order to optimize for 'longest prefix match'.

inet/src/inet/networklayer/ipv4/Ipv4RoutingTable.cc

Line 527 in 09aee09

bool Ipv4RoutingTable::routeLessThan(const Ipv4Route *a, const Ipv4Route *b) const

And this:

inet/src/inet/networklayer/ipv4/Ipv4RoutingTable.cc

Line 644 in 09aee09

bool Ipv4RoutingTable::multicastRouteLessThan(const Ipv4MulticastRoute *a, const Ipv4MulticastRoute *b)

This kind of sorting, makes sense especially in big routing tables between autonomous systems in BGP. But still the routing table looks ugly! What do you suggest? Is there anyways to separate the search logic (under the hood) from the print/display logic?

[levy]

When you see the routing table in the GUI, it is just a direct visualization of the C++ member variable that is used to lookup the best matching route. The GUI component uses the so called WATCH feature of OMNeT++. There's not much we can change there, unless we are also willing to change the way we find the best matching route.

In general, optionally sorting the routing table in the GUI would be a nice feature to have. Unfortunately, I don't have any specific idea in mind how to do this easily. In principle, the routing table could have a parameter to keep the routes sorted in certain ways (including the current sorting method). If the sorting method is different the current one, then the routing table would have to do a full search when finding the best matching route. I don't know if I like this solution though, I'll think about it a bit more.

[mahlegha]

Hi,
I use inet/omnet++. I want to print each nodes routing table to a file and see the path/nexthop that ospf chooses for each packet from src to dst. how can i create such that file for each node?
i used **configure.dumproutes = true. it says that "dumpRoutes: if true, then the module prints configured and optimized routing tables for all nodes to the module output" according to inet/user-manual. so where can i find the output module? where does it mean?
I also used the module routingTableRecorder and it created a .rt file after simulation in results directory. but i don't want such that file.
any body knows this?

[levy]

This is not the right forum to ask questions. Please use the mailing list for this purpose.

[levy]

Bah, I accidentally closed this issue, but the original issue is still open.

[S-Slim]

Hi,
I'm asking if you already fixed the issue of the routing table to get the next hop table of each node.
Thx.
######################################
Hi,
I use inet/omnet++. I want to print each nodes routing table to a file and see the path/nexthop that ospf chooses for each packet from src to dst. how can i create such that file for each node?
i used **configure.dumproutes = true. it says that "dumpRoutes: if true, then the module prints configured and optimized routing tables for all nodes to the module output" according to inet/user-manual. so where can i find the output module? where does it mean?
I also used the module routingTableRecorder and it created a .rt file after simulation in results directory. but i don't want such that file.
any body knows this?