What I learned/surmised yesterday happened in a whirlwind, so the details aren't quite clear to me yet.

> Node fine, no issues
> apply newly learned firewall rules, go to sleep
> wake up, see force close
> panic
> firewall logs show blocked IP's to node while sleep
> nuke firewall rules

The particular network firewall rule was 'Drop invalid state', which I don't fully understand and blindly applied as part of an overall hardening guide.

So, to attempt answering your question given my limited knowledge:

An offline node doesn't seem to cause anything to get stuck, but an online node with broken LAN routing appears to be a real issue. 

Perhaps my node appeared as viable in the graph, accepted an htlc, but threw it in the fuckin trash? 🤷‍♂️

 

 What I just said doesn't quite add up to me, because I'm wondering why my own node would broadcast a force close if it was in fact the 'bad actor'. I was under the impression that other nodes in the route would force close as a result of my node not 'playing fairly'.

All I know is the only variable out of place here is that LAN firewall rule.