multiple clients fail

[friedrich]

multiple clients fail

[raidenii]

I can confirm this issue. This sounds like a NAT traversal issue to me, seems that hans cannot handle multiple IPs behind the same NAT box.

[friedrich]

Thanks for reporting this! Hans identifies clients by their IP. This means it cannot handle multiple clients with one public IP. I will address this issue in the upcoming releases.

[raidenii]

Given the fact that NAT uses ICMP query ID to identify the machines behind NAT box, is it possible to do the same on hans? https://tools.ietf.org/html/rfc3022

[Masaq-]

Implemented in #16

Identifying clients by ICMP Query ID is a fine idea. However I use a carrier grade NAT which rewrites the Query ID too frequently. In my case the Sequence Number remains untouched instead. So I have added options to identify clients either by Query ID or by Sequence Number.

[Masaq-]

RFC 5508 says, "An ICMP Query session timer MUST NOT expire in less than 60 seconds. It is RECOMMENDED that the ICMP Query session timer be made configurable."

Apparently my carrier configured the carrier grade NAT to expire an ICMP session after one second. Ping still works with a one second timeout.

Hans default polling interval of 2000 ms is too long. I have made it configurable, and a polling interval of 900 ms maintains a Query ID mapping on my carrier grade NAT.

However I prefer not to use polling, and I still find the Sequence Number to be generally better suited as a client identifier.