Re: network problem: configuration/DNS? cannot access internal machine using our external IP

[Jerome "Lacoste (Frisurf)" <lacostej@frisurf.no>]

On Thu, 2003-02-13 at 19:13, Mark Ferlatte wrote:
> Jerome Lacoste (Frisurf) said on Thu, Feb 13, 2003 at 10:41:12AM +0100:
> > > Your gateway/router is working as designed.  The internal (LAN) and
> > > external (WAN/Internet) are kept separated.  This means that no WAN IP
> > > can try to connect directly with an internal address.  Nor is it allowed
> > > to use a LAN IP from outside.  When you try to connect to your public
> > > address from within the LAN, the name resolves to your own address.  So
> > > the router sees it as an internal address trying to get in, and that's
> > > not allowed.
> > 
> > OK. Is there a trick I can use so that I can access this machine from
> > inside AND outside our LAN using the same name?
> 
> Yes.  You want a NAT.

I've got NAT. 

> > Would be handy for CVS configuration (which for example keeps
> > information in CVS/Root)
> 
> For this, I actually use ssh tunnels:
> 
> ssh -f -L2401:cvs.foo.com:2401 user@host.that.can.see.cvs.com sleep 3600
> 
> cvs -d :pserver:config@localhost:2401:/cvs login
> cvs -d :pserver:config@localhost:2401:/cvs co config

Sounds nice. not sure if that can solve my problem as the hosts that can
see my cvs are outside my LAN, as inside I must use the CVS host IP.

Or perhaps I missed something.

Thanks a lot,

Jerome