= Сообщение: 5230 из 7402 ============================================= IPV6 = От : Michiel van der Vlist 2:280/5555 11 Mar 18 12:46:58 Кому : Björn Felten 11 Mar 18 12:46:58 Тема : List of IPv6 nodes FGHI : area://IPV6?msgid=2:280/5555+5aa51a4a На : area://IPV6?msgid=2:203/2+5aa4619a = Кодировка сообщения определена как: CP850 ================================== Ответ: area://IPV6?msgid=2:203/2+5aa51ca2 ============================================================================== Hello Björn,
On Saturday March 10 2018 23:52, you wrote to me:
BF> {W32 API error 10065} A socket operation was attempted to an BF> unreachable host
BF> Now I get this:
BF> {W32 API error 10049} The requested address is not valid in its BF> context
I would not worry too much about the different error responses. In my experience the binkd error reports are always a bit cryptic and erratic.
The bottom line is that your he.net tunnel is not working.
o If this is due to your mobile ISP blocking protocol 41 as Tommi suggested, the only solution I see is to change provider.
o From my SixXs days, I remember I had a task running that pinged the SixXs side of my tunnel every second. I do not recall why this was needed, it is too long ago, but without it, the tunnel would not stay up.
o For my he.net tunnel I had to explicitly tell the firewall to pass prootol 41.
o Have you tried the heartbeat option of he.net? I have never used it myself, but from what i understand, it deals with tunnel endpoints at the client side that have a dynamic IPv4 address.
I hate to do this, but I am afraid I shall have to flag you as temporary IPv6 down in the list of IPv6 nodes. Accuracy over vanity...
