On 11/1/06, steve reilly wrote:

On Wednesday 01 November 2006 02:03, Jigish Gohil wrote:

Hi,

not quite sure what you have cut and pasted into the email here, but I didnt have to do any of that. Its simply done from the config panel of your router. my linksys address is 192.168.1.1. you just need to configure port forwarding on the router. forward port 80 to whatever internal ip you want. should take 30 seconds .......... tops.

Thanks Steve I am using SUSE box as router, so all that configuration goes there. -J

---------- Forwarded message ---------- From: Jigish Gohil Date: Nov 2, 2006 4:35 PM Subject: Re: [SLE] Port forwarding issue To: Darryl Gregorash On 11/2/06, Darryl Gregorash wrote:

On 2006-11-01 01:03, Jigish Gohil wrote:

...

FW_FORWARD_MASQ="0/0,192.168.0.249,tcp,80,80,0/0" The way I read this, the last field is not a net/mask, rather a single IP, despite what the CoolSolutions webpage says. AFAIK, the field isn't even necessary. Since you are not doing any port redirection, the second "80" is not needed. Thus:

FW_FORWARD_MASQ="0/0,192.168.0.249,tcp,80"

...

That didn't work either. Is there anything else I need to activate for forwarding to work? Does anyone have working /etc/sysconfig/SuSEfirewall2 for SLE 10 or openSUSE 10.2 that can be shared? prime:~/scripts # cat /proc/sys/net/ipv4/ip_forward 1 I have tried shutting down apparmor, and also the script that works on fedora boxes. http://pastebin.ca/234209 Would it be possible for anyone to test port forwarding and if it doesn't then I'd file a bug. -J

On 11/2/06, Darryl Gregorash wrote:

On 2006-11-02 05:07, Jigish Gohil wrote:

...

-<snip>

...

FW_FORWARD_MASQ="0/0,192.168.0.249,tcp,80"

...

That didn't work either.

Is there anything else I need to activate for forwarding to work?

I cannot see why it isn't working. Are you logging dropped packets? If so, perhaps the firewall logfile will show what is happening.

The results of "iptables-save" will show the exact state of your firewall. Could you post that output?

Here is the iptables-save output: http://rafb.net/paste/results/N0Nplw78.html All this while I was testing this from the router and intranet, access from outside works!! Now how do we get it to work from intranet too? Thanks a bunch. -J

On 11/3/06, Darryl Gregorash wrote:

On 2006-11-02 06:14, Jigish Gohil wrote:

...

<snip>

It would have been nice to know this from the beginning. I assumed the problem was on the external device.

I thought so too, as I had not tested from outside. Sorry about that. I am happy that it works.

...

Now how do we get it to work from intranet too?

I cannot make any sense of the rules for the internal zone as the firewall stands now. Get rid of the word "any" from FW_DEV_EXT, restart the firewall, and repost the results.

The setup below for port forwarding works from outside. FW_DEV_EXT="eth-id-00:15:f2:52:f8:8a" FW_DEV_INT="eth-id-00:08:a1:65:d7:c6" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="192.168.0.0/24" FW_FORWARD="" FW_FORWARD_MASQ="0/0,192.168.0.249,tcp,80" FW_REDIRECT="" iptables-save result: http://rafb.net/paste/results/Znuyph56.html