Re: expose internal network to the outside world

2005-09-16 Thread Ken Irving
On Thu, Sep 15, 2005 at 11:27:21AM -0400, Angelo Bertolli wrote: > Matt Price wrote: > > >Thanks wim! and everyone else. I must have missed something in the > >admin screens, 'cause when I logged in this morning there was "virtual > >server" right in my face. I set up the ports just as wim desc

Re: expose internal network to the outside world

2005-09-15 Thread Angelo Bertolli
Matt Price wrote: Thanks wim! and everyone else. I must have missed something in the admin screens, 'cause when I logged in this morning there was "virtual server" right in my face. I set up the ports just as wim describes, and it works great! Only problem now is that when I use ssh from out

Re: expose internal network to the outside world

2005-09-15 Thread wim
No problem matt... you should stick to mutt :-) as I do... Cheers! Wim On Thu, Sep 15, 2005 at 10:18:49AM -0400, Matt Price wrote: > oops, sentthis to wim first by mistake -- sorry, still missing some mutt > features in thunderbird... > m > > wim wrote: > > >Hi Matt, > > > >It seems that opti

Re: expose internal network to the outside world

2005-09-15 Thread Matt Price
oops, sentthis to wim first by mistake -- sorry, still missing some mutt features in thunderbird... m wim wrote: >Hi Matt, > >It seems that option 2 may work for you. Installing a Debain box with >iptables seems a little bit of overkill to me ;-) >But that's my thought... > >you should NAT mydoma

Re: expose internal network to the outside world

2005-09-15 Thread wim
Hi Matt, It seems that option 2 may work for you. Installing a Debain box with iptables seems a little bit of overkill to me ;-) But that's my thought... you should NAT mydomain.dyndns.org port 2000 to 192.168.2.199 port 22 and mydomain.dyndns.org port 3000 to 192.168.2.254 port 22 Maybe you can

Re: expose internal network to the outside world

2005-09-14 Thread Angelo Bertolli
Matt Price wrote: ssh -p 2000 -l me mydomain.dyndns.org which gets to the router; the router sees that it's supposed to forward requests on port 2000 to 192.168.2.199; 192.168.2.199 picks up the request and an ssh tunnel is formed You won't need tunneling for this, just the NAT that your "r

Re: expose internal network to the outside world

2005-09-14 Thread Leonardo Sá
I agree with Sanchez. I run an old Pentium II as a NAT box with iptables and it gives me much more flexibility than a ("standalone") router. Routers dont need to be a cutting edge machine, old ones will do it just great for home networks. If you are not sure how to set up one, try reading the masqu

Re: expose internal network to the outside world

2005-09-14 Thread Roberto C. Sanchez
On Wed, Sep 14, 2005 at 10:16:49PM -0400, Matt Price wrote: > hi folks, > > I have 2 computers on a home network, connected to DSL through a modem > and a cheap SMC router (Barricade g = SMC2804WBRP-g). I would like to > be able to ssh into both of them form the outside world. I have > successf

expose internal network to the outside world

2005-09-14 Thread Matt Price
hi folks, I have 2 computers on a home network, connected to DSL through a modem and a cheap SMC router (Barricade g = SMC2804WBRP-g). I would like to be able to ssh into both of them form the outside world. I have successfully set up "inadyn" to associate a stable URL (x.dyndns.org) with my dy