Hi,
Following some short discussion on freebsd-pf I've written (mostly
copied, but let's skip that for a moment) short patch for ip_input.c,
that does uRPF check for incoming packets.
In some simple words, it's exactly the function ipfw2 is calling when
You specify a rule with `versrcreach', but
Łukasz Bromirski wrote:
Patch applies cleanly on ip_input.c version 1.301.2.3 dated 2005/10/09
(latest RELENG_5 checkout). It will also work with latest RELENG_4
checkout (ip_input.c version 1.130.2.55 dated 2005/01/02).
Sorry for small mistake - patch applies cleanly to:
ip_input.c v1.301.2
Hello,
On Tue, 03 Jan 2006, at 01:39, ?ukasz Bromirski wrote:
> Hi,
>
> Following some short discussion on freebsd-pf I've written (mostly
> copied, but let's skip that for a moment) short patch for ip_input.c,
> that does uRPF check for incoming packets.
>
> In some simple words, it's exac
Yann Berthier wrote:
>If this yet to be found wiser guy would not forget the loose check
>too (verrevpath in ipfw speaking), where packets matching the default
>route are ok ... :)
Actually it does that and will until we'll have option to have two
or more default routes.
Presently, i
On Tue, 03 Jan 2006, at 14:58, ?ukasz Bromirski wrote:
> Yann Berthier wrote:
>
> >If this yet to be found wiser guy would not forget the loose check
> >too (verrevpath in ipfw speaking), where packets matching the default
> >route are ok ... :)
>
> Actually it does that and will unt
Łukasz Bromirski wrote:
Yann Berthier wrote:
If this yet to be found wiser guy would not forget the loose check
too (verrevpath in ipfw speaking), where packets matching the default
route are ok ... :)
Actually it does that and will until we'll have option to have two
or more d
Julian Elischer wrote:
> Several routes with the same dest would be interesting but how do you
> select between them?
Via some sort of load-balancing or policy routing mechanism on
network stack level? There is so much we miss in current FreeBSD stack
in this area it's hard to say some single fea
