Clueless Network Prob

Michael Hipp mhipp
Mon May 17 11:33:50 PDT 2004


Correct. I'm trying to avoid turning this box into a firewall/router. 
Especially since I already have the router (a LinkSys). The subinterface 
looks like the way to go. How best to read up on it?

It's easy to tell the router to send inbound connection attempts to a 
particular addr or port on the LAN (and nowhere else). That makes it look 
like that one addr/port is on the Intenet but everything else remains 
invisible (a necessity since they're all Win boxes). My hope is to allow a 
few select secure connections (to this box only) for remote admin & data 
access.

Thankfully I don't need it working today. I've got a fair bit of learnin' to 
do.

Know anything about providing secure samba via SSH, VPN, ipSEC or somesuch?

Thanks,
Michael

On Monday 24 June 2002 09:06 am, Matthew Carpenter wrote:
> I was under the impression that this was supposed to be a firewall box.
> My apologies.  You probably want to do that using subinterfaces, although
> I'm not quite sure what it's gaining you.  I assume that the NAT router
> is an appliance, like a LinkSys DSL router or somesuch, correct?  You
> don't have the NAT Router allowing externally originated traffic to the
> server, do you?  (This would require a static NAT or PAT of some sort on
> the NAT Router).





More information about the Linux-users mailing list