Re: Knowing a route multiply.
From: Bruce M Simpson (bms_at_spc.org)
Date: 11/18/03
- Previous message: Jamie Heckford: "RE: Problem with Racoon/IPSec/Setkey - Routing to/from multiple netwo rks"
- In reply to: David Gilbert: "Knowing a route multiply."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 18 Nov 2003 11:47:09 +0000 To: David Gilbert <dgilbert@dclg.ca>
On Mon, Nov 17, 2003 at 10:58:47AM -0500, David Gilbert wrote:
> This works on Linux ... and fails miserably on FreeBSD. I would like
> to change this behaviour to either a) replace the route with the
> interface route or b) know two routes for a destination and choose
> one.
Have you tried filtering the route on Router B to ensure it doesn't get
added in the first place as a workaround?
Have you run 'route -nv monitor' during the process and observed what
the sequence of events is as far as the routing socket is concerned?
a) I'd be curious as to whether an RTM_ADD or an RTM_CHANGE is issued
in this case.
Strictly speaking, RTM_CHANGE shouldn't work, but it does... according to
Keith Sklower's paper on the original 4.2BSD routing implementation, changing
the destination/next-hop of a route isn't allowed.
b) is the ideal behaviour but we can't implement until after 5.2-RELEASE
is out the door.
BMS
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Jamie Heckford: "RE: Problem with Racoon/IPSec/Setkey - Routing to/from multiple netwo rks"
- In reply to: David Gilbert: "Knowing a route multiply."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
