[My apologies to John for the earlier, direct reply, it was mend to go to the list). John Andersen wrote:
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? [..]
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.
I fully agree. Shorewall is very much easier to maintain and do off-track things with. Plus: it's IPv6 capable now, which SuseFW isn't (yet?). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org