[quagga-dev 4829] Re: PtP not working in 0.99.7 on FreeBSD

David Young dyoung at pobox.com
Wed May 16 23:52:17 BST 2007

On Wed, May 16, 2007 at 08:47:03AM -0400, Andrew J. Schorr wrote:
> On Wed, May 16, 2007 at 12:13:15PM +0100, Paul Jakma wrote:
> > On Wed, 16 May 2007, Andrew Filonov wrote:
> > 
> > >Yes. After interface configuration, quagga doesn't detect right 
> > >broadcast address. After zebra's restart - interface will be 
> > >treated as PtP.
> > 
> > Yes, I see that too.
> > 
> > It seems that the bootstrap code (if_ioctl.c::interface_list_ioctl 
> > for FBSD, I /think/) does things differently. Possibly the FBSD 
> > kernel too.
> So is the conclusion that FreeBSD may be able to support
> these unusual interface address configurations, but the RTM_NEWADDR message
> is not communicating this information clearly (due to the
> fact that the message never seems to include the RTA_DST field)?

On FreeBSD, what does 'route -n monitor' tell you about the content of
the routing messages?  Just this moment I ran that on my NetBSD tunnel
concentrator, and this RTM_NEWADDR message appears to show a correct
RTA_DST field:

got message of size 124 on Sat Mar 17 13:07:18 2007
RTM_NEWADDR: address being added to iface: len 124, metric 0, flags: 
sockaddrs: <NETMASK,IFP,IFA,BRD>
 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff gre20001 2002:40c6:ff0c:1::1 2002:40c6:ff0c:1:20c:42ff:fe0d:2e68

It is possible that NetBSD's and FreeBSD's routing messages are not alike.


David Young             OJC Technologies
dyoung at ojctech.com      Urbana, IL * (217) 278-3933

More information about the Quagga-dev mailing list