Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Jul 2000 08:20:35 -0700 (PDT)
From:      Loren Koss <loren@pciway.com>
To:        Smith@ian.org
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: IPFilter NAT..
Message-ID:  <Pine.BSF.4.21.0007210818240.4835-100000@unix.pciway.com>
In-Reply-To: <Pine.LNX.4.21.0007210922420.10000-100000@user1.erieonline.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Whoa..  from outside your network you could telnet to y.y.y.y??  For me, I
wont be able to since it is a 192.168.1.x network.. from inside my
network, sure I can telnet to it..  Did you mean you could telnet to
x.x.x.x 79 and 13?

Regarding whats not working, when i call ipnat -f ipnat.conf it says FILE
EXISTS which I assume it is referring to the second line below since the
first one gets in the list properly..

I read something on some archive that someone else had seen this
bug.  Maybe there is a patch.  Dunno..

Loren Koss
http://www.checkthegrid.com
Before you go to the movies...Check The Grid!

On Fri, 21 Jul 2000 Smith@ian.org wrote:

> On Thu, 20 Jul 2000, Loren Koss wrote:
> > Has anyone tried to redirect more than one port using IPNat?  It doesn't
> > seem to work..  Is there a patch?
> > 
> > rdr rl0 a.b.c.d port 80 -> 192.168.1.10 port 80
> > rdr rl0 a.b.c.d port 2000 -> 192.168.1.10 port 2000
> > 
> > The second one wont work..
> 
> I just tried...
> 
> rdr wb0 x.x.x.x/32 port 79 -> y.y.y.y port 79 tcp
> rdr wb0 x.x.x.x/32 port 13 -> y.y.y.y port 13 tcp
> 
> ...and could telnet to both port 79 and 13 on y.y.y.y with no 
> problems.  What isn't working for you?
> 
> This is on FreeBSD 4.1-RC #0: Fri Jul 21 01:47:41 EDT 2000 that
> was CVSuped about noon EST on the 20th.
> 
> --
> Ian
> 
> 
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007210818240.4835-100000>