LAN Problem

[Tyladras]

OK, here's the deal, and before you ask I didn't know what to search for to get what I want here.

OK, in the very near future, I'll be getting a new box to run as my server, and I want the users of my current server to use the new one. Here's the current setup:

internet<->ardana (gateway, linux)<->rock(winblows xp)

And here is what I want:

internet<->ardana(gateway, linux)<->hub<->eden(server, linux)
.................................................. ............."..<->yggdrasil(linux)
.................................................. ............."..<->rock(winblows xp)

The hub is connected to all of the three of the right, by the way.

OK, what I want is for people to be able to connect to eden and perhaps yggdrasil too, but the users will be connecting via ssh. The question is how do they do it? My other alternative is to invest in a router, but again, would it be possible for users to connect to my multiple boxen?

OK, thanks in advance,

--Ty

[santellij]

Go for it - Plug them all into the HUB and you should be good to go. That is, plug all 4 into the HUB and set "ardana" as the GW.

As long as they are all configured to be on the same subnet thay should be able to "talk" to eachother. If there were more details then I might I could suggest other things but I would say just give it a shot.

[Tyladras]

That wasn't the problem. What I want is for remote users to connect to the non-gateway machines over the internet.

Sorry for confusion,

--Ty

[pbratkowski]

You can enable port forwarding on the gateway, so for instance if someone connects to ftp://your.wan.ip.address on port 20/21 it forwards it to your.lan.ip.address port 20/21...

i'm not sure how you would go about doing that in linux, but if you have a hardware based outer like a d-link, you can do it automatically

[santellij]

right - couldn't ask something easy could ya. :-)

I would need more info then. Do you have public IPs for the other machines and just want to route that traffic past the gateway or do you want the ssh traffic to be routed to the other Linux machines on an internal subnet.

In the second case I would use ipchains (http://www.netfilter.org/ipchains/HOWTO.html) or something else to handle the NAT. If you are willing to figure out how to set up simple forwarding and maquerading rules I don't see the need for a router.

[Tyladras]

Most likely the second one, so that if someone say connected to my gateway, ardana, on port 9000 it would divert them to eden, port 9000. Just to provide a simple example.

Thanks again for any further help,

--Ty

[jumpedintothefire]

search networking for "port forward", there are hundreds of examples of this using iptables.