[emong007]

i have a static ip broad band. i have the broad band running into a router and the server & work stations connected to it. i have the suse linux box runing as the local server and workstations connected to it's samba share.... that works great.. what i want to do is get to where the static ip hits the linux box from the outside & and still allow other users access to the server & the web...

[tsunam]

If i'm understanding right, you want to connect to your suse box outside the network? Or anyone and everyone? Basically for that the safest way would be to use SSH change the port away from 22...say something like port 20000 something you'll remember easy and then you will be pretty secure for remote access.

[emong007]

what is SSH?

[tsunam]

...


http://www.openssh.com/

[lynch]

Originally Posted by emong007

i have a static ip broad band.

Is this cable or dsl? With the static IP, my guess is dsl but it's worth asking.

i have the broad band running into a router and the server & work stations connected to it.

Is this two seperate devices? As in a cable or dsl modem that connects to a router? Or is it a combo device? Either way, the router should be getting the IP. Does the router have a web interface for configuration? You can setup how the network can access the web from that.

i have the suse linux box runing as the local server and workstations connected to it's samba share.... that works great.. what i want to do is get to where the static ip hits the linux box from the outside & and still allow other users access to the server & the web...

I would hope you keep the server behing the router. If you know the IP, then pointing the rest of the comps on your network to the router as the default gateway should get web access for the rest of your lan.
Is that what you were asking? If so, I HTH
lynch

[tdi_veedub]

This is how my network is setup at home:

Internet -> Linksys router (Ports 22, 80, 25 forwarded to Linux Box, rest are closed).
|
->Linux Box(Ports 21, 22, 80, 25, 20000, 10000 open, the rest
are closed with iptables.
->Workstation (no open ports)
->Workstation (no open ports)
->Workstation (no open ports)

This allows public access to ports 80, 22, and 25 on the linux box while keeping the rest of the workstations secure. Also, since ports 21, 20000, 10000 are not forwarded by the router, only the local network has access to them.

I also have IPtables setup on the Linux box, for added security. I only want ports 20000 (usermin), 10000 (webmin), and 21 (ftp) open for the LAN. Having them open to the internet is a BIG security risk. for outside FTP, SFTP using SSH is used. This is much more secure than wide open FTP or TELNET.

The Workstations have no restrictions, and share files amongst themselves and the server freely. This setup does pretty much everything you need to do with the exception of samba (wich could be setup very easily, I don't need it though)

Hopefully this helps you a little.

[Squashman]

So what is the problem. You got 22 and 80 being forwarded to the Linux box. If SSH and Apache are running, you should be able to access the box from the Internet.