Gone AWOL

Then, while accessing it via wired interface to check the log (which showed nothing special except it couldn't resolve network hosts), it suddenly connected again, shows up on the website under devices (heartbeat received) but no data being uploaded.

Any thoughts on how to figure out what's happening?

icarus75's picture

The last heartbeat was at 17:43. That's more than two hours ago. Seems like the network issue hasn't been entirely solved. Could you give a bit more background info:
1/ Did you configure the FLM in wifi or ethernet mode?
2/ Can you still ping your router from the FLM?
3/ What ISP do you use?

If you haven't yet restarted the FLM, then please don't. Let's try to get more info out of the system first.

Cheers
/Bart

petur's picture

It's in wifi mode, and my ISP is Telenet.

For the ping, I need to go to the garage and connect a cable so I can login. BRB ;)

petur's picture

The globe led had gone out again... Attached netbook, went up to look up the ssh credentials I needed, went down again and globe led on. Heartbeat received. Can ping the router. Still no data.

This is very puzzling, nothing has changed in my network setup for quite some time...

petur's picture

It thinks it's the seventies again... log says heartbeat ok (200) but no other clues. all the ntp servers it tried are unreachable according to the log, but now I can ping them OK.

petur's picture

Got lazy and opened the firewall so I can access it from my desk. Ping gives 80% packet loss

Went down with tablet running wifi analyzer, looks like somebody nearby installed a wireless network on the same channel and its AP is very near the FL2. Grrrrrr.

Changed to a better channel and packet loss went down to 15%. Guess it is time to give up on wireless and attach a cable :(

petur's picture

Data!

icarus75's picture

Yay!