My mycelium identity stopped working

[scottyeager]

I noticed recently that Mycelium wasn't working for me (no action on attempts to connect to SSH or ping other machines), even though it appeared to start up and run normally. After a bit of experimentation, I found that replacing my private key solved the problem.

While I can continue to use the network with a different key and IP, it's obviously not great if a given identity can suddenly become effectively invalid for use on the network without any obvious error being logged.

Here's a logfile generated with the debug flag enabled, showing what happens for about a minute after Mycelium starts up with this key file chosen. I also let a ping command to another Mycelium host run while capturing this log.

myc.log

I'm also happy to donate the private key file to science, if anyone wants to have a poke at it.

[LeeSmet]

I've checked the log file but nothing really stands out as unexpected behavior there. If the issue is consistently reproducible and visible towards multiple destinations, it indicates something wrong when data comes back, i.e. the packet probably reaches the destination, but the reply does not reach your machine again. I'd also be interested in seeing a traceroute output towards one of the destinations.

A new identity solving the issues is likely because that causes a new IP and routerID to be generated, thus a completely new entity in the newtork. This is then propagated in the network and doesn't seem to fall in the bad state (immediately)