Rodney Baker wrote:
On Sat, 21 Feb 2009 10:37:59 David C. Rankin wrote:
Listmates:
I guess this situation is a port forwarding situation, but I'm not sure how to attack the problem. I have a limited number of IP entries in my router that I can use to forward traffic through to other machines on my office LAN from the outside. I need to learn how to setup ports on my primary server that will send/receive information to and from other computers on the lan. What is the best way to do this?
In the past the only experience I have had with this is ssh port forwarding to forward X or reach other machines behind the router. Is that what I need to do even though the traffic isn't ssh?
Do I need to set up IP tables? Can I do that with SuSEfirewall?
The layout I need is like this:
internet server port:12344 <==============>[ ]<----------------->[ ] client1 port:12345
|\ | \<---------------->[ ] client2 port:12346 |\ | \<---------------->[ ] client3 port:12347
[ ] client4 port:12348
What mechanism do I need to go learn so that I can set up something like this generically without relying on ssh only?
David,
IPtables is what you're looking for. I don't know if you can setup port forwarding rules using Yast/SuSEFirewall as I've never actually used that. I use my router's firewall and prior to that I used IPCop.
SuseFirewall can do this stuff for you. Its a basic NAT setup. I find Shorewall far easier to manage and more flexible than SuseFirewall and adding an inbound route is usually one line of text in a plain text file. (I know, its old school, sue me!). Shorewall.net Its an excellent package. Glad to help off-list if you need it David. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org