On 2006-11-02 23:00, Jigish Gohil wrote:
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
It should be working. Are you certain you are trying to connect to the web server on IP 192.168.0.249, and not the router? There is no masquerading done within the internal zone, as it is not needed.