Bug in tunnelbroker.net when updating endpoint IP from Microsoft Edge Canary

[sebastiannielsen]

Noticed a weird bug when updating Client endpoint IP for my tunnel in:
Version 124.0.2437.0 (Officiell version) canary (64 bitar)

When entering the new Client IP in tunnel settings, and then clicking anywhere else to confirm, it would just do nothing. It would only react if you entered a deliberately incorrect IP (as in... 256.256.256.256 - then it would say incorrect format).

I first tought the server which sends the ICMP had changed from 66.220.2.74 (my ICMP permit firewall rule is pinned to 66.220.2.74) but then I looked in firewall logs and saw no rejected ICMP packets.

So apparently it would not fire a request to tunnelbroker's servers when updating client IP.

So I switched browser to a older version:
Version 123.0.2420.10 (Officiell version) beta (64 bitar)

THEN it worked to update client IP and the ICMP packet was sent.


So you might want to look into the page and check the javascript code that handles updating Client IP, and check why it doesn't work in:
Version 124.0.2437.0 (Officiell version) canary (64 bitar)
but does work in:
Version 123.0.2420.10 (Officiell version) beta (64 bitar)

[kcochran]

That code is a simple, very basic blur(), called on every update, even the invalid IP one.  If that breaks, I'd wonder more about the Canary build having some odd issue.