On Monday 28 July 2003 06:26 am, you wrote:
> On Sun, 27 Jul 2003, Jim Durham wrote:
> > On Sunday 27 July 2003 03:10 am, Wouter Clarie wrote:
> > > Yes, that's what I meant. It should work, since it does here.
> > > VNC Server on the internal network, accessed from outside.
> >
> > Interesting. Is
On Sat, 26 Jul 2003, Jim Durham wrote:
> On Saturday 26 July 2003 04:07 am, Wouter Clarie wrote:
>
> > VNC works through NAT just fine. Never had any problems with that.
>
> Yes, I do that all the time, but in this case, the VNC *server* was the
> one behind the NAT, instead of the client, which
On Saturday 26 July 2003 04:07 am, Wouter Clarie wrote:
> On Sat, 26 Jul 2003, Yar Tikhiy wrote:
> > Could you check if TELNET, HTTP, or SSH from the outside world to
> > the inside machine works? The problem may have to do with VNC
> > protocol peculiarities preventing it from working through NAT
On Saturday 26 July 2003 03:42 am, Yar Tikhiy wrote:
> On Fri, Jul 25, 2003 at 01:49:38PM -0400, Jim Durham wrote:
> > The procedure we used was to alias a 2nd public address to the
> > outside interface and use a redirect_address statement in
> > natd.conf to redirect connections to the new public
On Saturday 26 July 2003 03:13 am, you wrote:
> On Sat, Jul 26, 2003 at 02:22:05AM +0200, Clement Laforet wrote:
> > for incoming traffic, you must use -redirect_address, but for
> > outgoing you have to set -alias_address.
> > If you want to use a specific public IP to map incoming AND
> > outgoin
On Sat, 26 Jul 2003, Yar Tikhiy wrote:
> Could you check if TELNET, HTTP, or SSH from the outside world to the
> inside machine works? The problem may have to do with VNC protocol
> peculiarities preventing it from working through NAT. (However, the VNC
> FAQ claims VNC will work through NAT.)
V
On Fri, Jul 25, 2003 at 01:49:38PM -0400, Jim Durham wrote:
>
> The procedure we used was to alias a 2nd public address to the outside
> interface and use a redirect_address statement in natd.conf to
> redirect connections to the new public IP to the inside machine.
Just a remark: If this 2nd p
On Sat, Jul 26, 2003 at 02:22:05AM +0200, Clement Laforet wrote:
>
> for incoming traffic, you must use -redirect_address, but for outgoing
> you have to set -alias_address.
> If you want to use a specific public IP to map incoming AND outgoing
> packets, you need to run 2 natd, using ipfw matchin
On Friday 25 July 2003 08:22 pm, Clement Laforet wrote:
> On Fri, 25 Jul 2003 13:49:38 -0400
> Jim Durham <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> > I'm wondering about the characteristics of the redirect_address
> > option
> >
> > of natd. I tried this on -questions, but no one replied, so I
> > tho
On Fri, 25 Jul 2003 13:49:38 -0400
Jim Durham <[EMAIL PROTECTED]> wrote:
Hi,
> I'm wondering about the characteristics of the redirect_address option
>
> of natd. I tried this on -questions, but no one replied, so I thought
> I'd ask on here, hoping to find folks more familiar with kernel
> me
I'm wondering about the characteristics of the redirect_address option
of natd. I tried this on -questions, but no one replied, so I thought
I'd ask on here, hoping to find folks more familiar with kernel
mechanisms here.
Consider a FreeBSD NAT "gateway" between a public IP on one network
inte
11 matches
Mail list logo
