Re: fwd in ipfw module

Do you know solution (for GENERIC kernel) that can port forwarding? I found /usr/ports/net/rinetd -- View this message in context: http://freebsd.1045724.n5.nabble.com/fwd-in-ipfw-module-tp4642321p4661905.html Sent from the freebsd-ipfw mailing list archive at Nabble.com.

Re: fwd in ipfw module

On 03.08.2011 14:28, timp wrote: > Do you know solution (for GENERIC kernel) that can port forwarding? I found > /usr/ports/net/rinetd You can use pf(4). -- WBR, Andrey V. Elsukov ___ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailm

Re: fwd in ipfw module

Thanks! Спасибо, будем посмотреть 2011/8/3 Andrey V. Elsukov [via FreeBSD] < ml-node+4661936-176988-160...@n5.nabble.com> > On 03.08.2011 14:28, timp wrote: > > Do you know solution (for GENERIC kernel) that can port forwarding? I > found > > /usr/ports/net/rinetd > > You can use pf(4). > > -

weird results while ipsec + ipfv_nat (nat before vpn)

Hi, i faced weird for me situation, may somebody agree to help to win it, please? we need to see some http/s resources behind the Cisco PIX IPSEC i'm trying to get working this schema: SCHEMA (`nat before vpn' as i believe): -- +-> a.a.0.1/16 LAN | +-> a.a.a.2/24 FreeBSD b.b.b.1 <

Re: weird results while ipsec + ipfv_nat (nat before vpn)

On Wed, 3 Aug 2011, Zeus V Panchenko wrote: [..] I can't comment on your ipsec setup at all, but: > > cat /etc/ipfw.conf > ... > > add 000401 allow udp from x.x.x.x to y.y.y.y isakmp > add 000402 allow udp from y.y.y.y to x.x.x.x isakmp > add 000403 allow { esp or ipencap } from x.x.x.x t