Date: Wed, 9 May 2007 06:52:37 -0300 From: AT Matik <asstec@matik.com.br> To: freebsd-ipfw@freebsd.org Cc: Kirk Davis <Kirk.Davis@epsb.ca>, Julian Elischer <julian@elischer.org> Subject: Re: Policy Routing natd+ipfw Message-ID: <200705090652.37906.asstec@matik.com.br> In-Reply-To: <463FBE30.90009@elischer.org> References: <33910a2c0705041812s2aaf0b62t785e16abc0decee6@mail.gmail.com> <DB9A31C316524A4A83E54A2C0D20655702216E5A@Exchange24.EDU.epsb.ca> <463FBE30.90009@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 07 May 2007 21:02:56 Julian Elischer wrote: > Kirk Davis wrote: > > Julian Elischer wrote: > >> in -current you can implement a routing table via FWD and tables. > >> in 6.x you need to specify the next hop. and an more explicit rule. > > > > Is there any information floating around on how to do this in current > > using the FWD rules and tables? Any pointer on where to look. > > man ipfw on -current > > basically you can implement alternate routing tables.. > > ipfw table 1 add 0.0.0.0/0 4.5.6.7 # default route for table 1 > ipfw table 1 add 2.3.4.0/24 5.4.3.2 # but not for packets to 2.3.4.x > ipfw table 2 add 0.0.0.0/0 7.6.5.4 #default route for table 2 > ipfw table 2 add 2.3.4.0/24 6.5.4.3 # but differnet route for packets to > 2.3.4.x > certainly this still are not routing tables but simplified forward table configurations right? what we still need is kind of route2 implementation like Linux does Joao A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705090652.37906.asstec>