I am remotely adminstering a Suse 9.1 box. Using yast2 from the command line, I went in to edit/activate the firewall. I quite specifically left HTTP, HTTPS, and SSH *on* (I tripled checked myself). I hit "finish", and my SSH connection promptly closed. I tried to reconnect, with no success.

So I thought maybe I had to reboot first. Using the provider from whom I have purchased the dedicated server web's interface for the server, I reboot the box.

The box is back up (cause I can access the information using the dedicated server providers web tools). However, I still cannot SSH in. HTTP also does not work.

WTF? I explicitly told it to leave those ports open. Why can I not connect?

FYI, if I bring the firewall down, everything opens up. If I bring it up again, it all closes off.

cat /etc/sysconfig/SuSEfirewall2 | grep ^FW_SERVICES_EXT_TCP

gives

FW_SERVICES_EXT_TCP="http https pop3s smtp ssh"

Use Firestarter as a firewall..........best on the block

One thing I rely on is the routing ability that SuSEFirewall gives - I don't have a router, just a desktop that thinks it's one

Does Firestarter do this as well?