Date: Wed, 21 Jan 2004 02:51:52 +0800 (MYT) From: Dinesh Nair <dinesh@alphaque.com> To: Gleb Smirnoff <glebius@cell.sick.ru> Cc: freebsd-net@FreeBSD.org Subject: Re: netgraph questions on ng_tee, ng_iface, ng_socket Message-ID: <20040121024916.K312-100000@prophet.alphaque.com> In-Reply-To: <20040120091732.GB10731@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Jan 2004, Gleb Smirnoff wrote: > Isn't ng_etf(4) the one you need? ng_etf does filtering, i'm planning on doing round robin IP tranmission, with source IP address set accordingly. see ng_one2many which gives an example for ethernet frames. i want to do the same thing in ng_one2many's EXAMPLE section, but with the added functionality of changing the ip address to match the ip address bound to the interface the packet is going out from. with this ip address, the next hop router(s) wont be able to route the reply back thru the same interface, especially if they're seeing non legit src addressed packets. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040121024916.K312-100000>