Date: Tue, 13 Jan 2009 07:14:00 +0200 From: "Dimitar Vasilev" <dimitar.vassilev@gmail.com> To: freebsd-net@freebsd.org Subject: setfib+pf Message-ID: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, I originally posted my message to questions, however no response for about a week. Therefore I'm reposting here. Original question available at http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190056.html For those who prefer reading human text, here are my questions: I'd like to ask on the best options for using setfib and pf in a non-BGP environment. I will run 2 uplinks, with VLANs for internal networks and want to fail over external links if one of them fails.(Extended note as of 13.01: Uplink routers will be a WRT54GL with OpenWRT and an Alix box hopefully. Vlan tagging also possible there. Alix will be the controlling router station for failover). Currently pf supports to the best of my knowledge: a) rtable - this means i can create the routing tables with setfib and then use pass from .... rtable N( N >1 <16) or give out directly network ranges b) route-to - pass in/out on X from ... route-to c) packet tagging - i can tag networks and use standalone or through routing tags. Anyone aware if is it ok to use /etc/gateways without running routed or how can i label routes alternatively? If I apply the same for /etc/networks or both /etc/gateways and networks will it be ok? pass in from any to $big_salad via $fridge keep state for example? d) pass in from route N(192.168.1.1 for example) to... - saw this on http://www.mail-archive.com/pf@benzedrine.cx/msg07220.html and requires BGP to make tags speak anything but network numbers. e) use the vlan id's I'd much appreciate if someone thinks with me for the best options of using the setfib features along with pf. Thanks and regards, Dimitar Vassilev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59adc1a0901122114v15efa47ahba8beef6ace4ddb0>