Avatar
singlebeam
2c443cc4d5b65495e4a64812e8bd6d75b2b728d1240c562c3fdae57e24dbebbb
Forestry. Geospatial. Lover of science and technology. #Nostr #Bitcoin #noderunner

I'm particularly interested in applying to those exact conditions...wildfire response and industrial timber stand data collection/analysis. I'm stoked!

I have not but thanks for the tip. This is precisely the sort of thing I want to play with and introduce/implement at work.

GN - I hope tomorrow you can find a solution to your ghost debacle!

Good morning 🌞

Saved my vacation and it starts now! Off till 1/3. Homelab here I come.

#m=image%2Fjpeg&dim=1920x1446&blurhash=%23QDJVG9E%253ayt8WVWBjZof%7EqD%25t6ayozWBWVj%5Bof%3FbD%25ofoff6ayayofj%5B%3FbIUWBt7WBj%5BWBofWB%25MM%7BRjt7WBfkafofayt7WVRjt7jaayayofWVogofRjofj%5Bafj%40ayay&x=14ea944e420e1737db6f037fbcb44a380cb5b369a05dc9f3e6fa16840c60e31e

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? 🤷‍♂️

I made a critical mistake last night while hardening my home network and inadvertently blocked necessary routing through my node with a dumb firewall rule. I didn't catch it and htlc's were stuck while I slept. My node broadcasted a force close commitment. 🤦‍♂️🤦‍♂️🤦‍♂️

I didn't think anyone played anymore. I used to run a CS server and played TF2 a lot.

I'm tempted to dig up my steam account if people still play!