12 Mar
2002
12 Mar
'02
18:15
Brian Topping writes: ok, lets summarize: eth0 is ext iface, eth1 is dmz iface, network 204.152.97.0/24 eth2 is int iface, network 192.168.0.0/24 So, where's your https Server? In your internal network? This might be the problem. I don't know in detail what rules SuSEFirewall2 creates, but I think it throws away packets forwarded to a "known service" port, i.e. packets to a port below 1023. To have your https server accessible from the outside you probably have to put it into the DMZ network. Instead of FW_FORWARD_MASQ use FW_FORWARD_MASQ, then. Robert