Iwan Budi Kusnanto

> Though I wonder where you'd add them I was thinking on the `framed.next` in `peers.rs`, but now i'm not sure. > In general, the router should also detect broken...

> You're mainly looking for https://github.com/threefoldtech/mycelium/blob/master/mycelium/src/router.rs#L304 i've looked at this log. While `peers` log always printed when the issue happened, above log was not. I'll look at the timeout way...

Tested it again, Now on real android phone instead of emulator `ping` was failed for ~1 minute, no error there ```bash Croot@cilik:~# ping6 521:81b4:7f65:20c3:9a0f:2c45:8b92:5507 | ts Jun 06 11:29:00 PING...

There are many ideas about this 1. refresh peer when receive `network available` event. It is like what `yggdrasil-android` do. I don't think it would work: - the documentation about...

> ping was failed for ~1 minute, no error there > It ran every 10 seconds, but didn't detect the error (because error!("Peer {} is dead", peer.connection_identifier()); didn't printed. for...

i'll check if it is half-open issue. Maybe the peer closed the conn, but Android didn't know

Thinking about this, - the restriction doesn't apply on the host node: - otherwise `zos` housekeeping can be broken - the restriction only applied on the container/VM: - the rules...

Well, i thought that the brief specs in the issue description was a result of some discussions, but looks like it was not. I have some questions: 1. why we...

> The question remains if it could be made running in the background like tcp/ip and as on my linux laptop I'm not sure what you really mean with `background`....

> I hope I made myself more clear, thank you!! Yes, it is clear now. > I'd prefer to have this run at the boot of the phone > So,...