Date: Wed, 03 Mar 2004 22:53:31 +0100 From: Andre Oppermann <andre@freebsd.org> To: James <haesu@towardex.com> Cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack Message-ID: <404653DB.186DA0C2@freebsd.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
James wrote: > rewriting of routing stack and implementing FIB-like structure as what andre > proposed in this thread is very welcoming. Just wait a few month and then have a look at what I put up. :-) > there are still other things freebsd lacks. such as uRPF that _SERVICE_PROVIDER_ > can use. ipfw2 has verrevpath but all it does from what i know is strict uRPF > only. service providers like myself, if we were to use freebsd boxen to run our > network, i am not spending money on a router that doesn't do loose-check uRPF. > this sounds like something linux does too but i refuse to use that :P That is pretty easy to implement. I should have it by Friday at latest, depends on when exactly I find time for it. ip verify unicast source reachable-via [any|ifn] The ipfw2 command would look like this: ... versrcreach [fxp0] What else is missing in FreeBSD? -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?404653DB.186DA0C2>