Date: Mon, 21 Dec 2015 17:47:35 +0800 From: bycn82 <bycn82@gmail.com> To: Julian Elischer <julian@freebsd.org> Cc: Ganbold Tsagaankhuu <ganbold@gmail.com>, "freebsd-ipfw@freebsd.org" <freebsd-ipfw@freebsd.org> Subject: Re: layer2 ipfw fwd Message-ID: <CAC%2BJH2xXVpnDfa5KUQGZ39uoqSiS5oB72ak6bAeaPqXgyCmd3Q@mail.gmail.com> In-Reply-To: <567795F1.5080605@freebsd.org> References: <CAGtf9xOzJ%2BcL-W=HP5cd2nyabY=03AgTyFLvDuQWN-xB6KqjCg@mail.gmail.com> <567795F1.5080605@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
why fwd based on MAC? Can share more info of your requirement? On Monday, 21 December 2015, Julian Elischer <julian@freebsd.org> wrote: > On 21/12/2015 10:20 AM, Ganbold Tsagaankhuu wrote: > >> Hi, >> >> Does ipfw support layer2 fwd to support transparent proxying on bridge? >> >> Does similar change like >> >> https://lists.freebsd.org/pipermail/freebsd-ipfw/2003-September/000526.html >> ever get committed? >> > I don't believe this was applied.. > I did similar when I worked for Ironport/Cisco. > But it's a trade-off between bloat and usefulness. > > >> thanks a lot, >> >> Ganbold >> _______________________________________________ >> freebsd-ipfw@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw >> To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC%2BJH2xXVpnDfa5KUQGZ39uoqSiS5oB72ak6bAeaPqXgyCmd3Q>