First off, let me just say I love LnS. The only firewall that is a firewall and not everything else. I have a couple of questions that I need resolved if my setup us going to be satisfactory in LnS. I'm using the enhanced ruleset; 1. If I have the "All other packets" rule enabled my Ethernet connection fails after a short period of time and i have to reset/troubleshoot it to make it work again. I don't know why but I remember observing the same behaviour with PeerGuardian a long time ago; So some type of packet that is getting blocked between the router and Ethernet card causes the connection to go awry. Any ideas? (BTW, this is not a overload of traffic issue and I don't need to restart the actual hardware, only need to rightclick icon and "repair") 2. I'm trying to setup my RDP and SSH server; If "TCP : Any other packet" is enabled I can't connect to any of them from the outside. I've tried to edit the rule to "everything not equal to 3389", and I've also tried making a new rule specifying - Ethernet type: IP, Protocol: TCP, IP-address: equals my @ (in the left-side pane). I've placed these rules on top to reserve those ports before the other rules are implemented. So what am I missing? This is really basic functionality and I must misinterpret the GUI somehow.. I mean, how is the rule order implemented? The higher ones on the list supercedes the lower ones? As soon as I disable the 2 rules in question I don't loose my Ethernet connection and I can connect to my services from the outside. Disabling the rules also doesn't seem to affect the security report at f.example Shields Up (http://www.grc.com/intro.htm). So if I get this solved or not aside; How important are those to rules when I'm already behind a router administered by me with only neccessary ports open? Finally, a sort of bug I noticed: When I reset/repair the connection, the firewall stops working. I have to either 1. quit the firewall and start it again, or 2. go to options, select a different adapter, apply, then select the correct adapter and apply again. This seems like a bit sneaky and dangerous securitywise... I mean, who checks their firewall status at regular intervals?