atom feed18 messages in org.freebsd.freebsd-netreading routing table
FromSent OnAttachments
Debarshi RaySep 1, 2008 5:06 am 
Bruce M. SimpsonSep 1, 2008 5:53 am 
Bruce M. SimpsonSep 1, 2008 6:01 am 
Debarshi RaySep 1, 2008 6:18 am 
Debarshi RaySep 1, 2008 6:23 am 
Bruce M. SimpsonSep 1, 2008 6:34 am 
Debarshi RaySep 1, 2008 8:15 am 
Julian ElischerSep 2, 2008 12:00 am 
Debarshi RaySep 2, 2008 12:17 am 
Robert WatsonSep 2, 2008 2:19 am 
Luigi RizzoSep 2, 2008 3:48 am 
Bruce M. SimpsonSep 2, 2008 7:55 am 
Robert WatsonSep 2, 2008 2:01 pm 
Luigi RizzoSep 2, 2008 2:28 pm 
Julian ElischerSep 2, 2008 3:10 pm 
Debarshi RaySep 18, 2008 1:01 am 
Bruce M. SimpsonSep 18, 2008 2:59 pm 
Julian ElischerSep 18, 2008 4:57 pm 
Subject:reading routing table
From:Debarshi Ray (deba@gmail.com)
Date:Sep 1, 2008 5:06:44 am
List:org.freebsd.freebsd-net

I am implementing a library/utility which basically encompasses the features of the traditional route utilities and those of newer tools (like ip from iproute2), which are mostly specific to a particular kernel. The overpowering objective is to make the library/utility work uniformly across all different kernels, so that programs like NetworkManager have a portable library/utility to use instead of the Linux-kernel specific ip which is now being used.

I was going through the FreeBSD and NetBSD documentation and the FreeBSD sources of netstat and route. I was suprised to see that while NetBSD's route implementation has a 'show' command, FreeBSD does not offer any such thing. Moreover it seems that one can not read the entire routing table using the PF_ROUTE sockets and RTM_GET returns information pertaining to only one destination. This suprised me because one can do such a thing with the Linux kernel's RTNETLINK.

Is there a reason why this is so? Or is reading from /dev/kmem the only way to get a dump of the routing tables?

Thanks, Debarshi