- From: Bartel Eerdekens <notifications@github.com>
- Date: Thu, 05 Dec 2024 13:41:28 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/url/issues/392/2521510923@github.com>
Hi, I am not sure if this email will reach you? But it won't work on any browser, not even on Windows. As what that GitHub issue is about, Chromium/Edge/Firefox/Safari won't support it, ever... Maybe the old Internet Explorer is an exception, but it's just a guess? Curl works because they do support IPv6 link local addresses... I don't know if a curl based browser exist? That could help. Any way, which device is it actually? Good to know which devices would be IPv6 only. Either way, if it has an IPv4 address, you always could configure it via that one. Or the other recommended way is to reach it via mDNS resolved hostname. Maybe you could use WireShark to sniff for packets from the specific MAC address and see if mDNS or other IPV4 packets are being sent. Good luck. Greets. Bartel On Thu, 5 Dec 2024, 19:26 Frédéric Tobias Christ, ***@***.***> wrote: > Hi guys, sorry to bother you but I stumbled upon this issue while trying > to figure out some weird issue. > I'm running a Linux system and I'd like to configure a new device I got. > > The manual states I can access the device via browser with an address that > can be generated from the MAC: http://[fe80::fe5c:44ff:febf:6974] in the > URL bar. > > That doesn't work at all in firefox showing NS_ERROR_FAILURE: > > configure-firefox-1.png (view on web) > <https://github.com/user-attachments/assets/dd9b37bc-e01b-4a0a-b557-6c7c0b9a33ff> > > Also this does not work with curl: > > $ curl -v http://[fe80::fe5f:49ff:febf:6974] > * Trying [fe80::fe5f:49ff:febf:6974]:80... > * Immediate connect fail for fe80::fe5f:49ff:febf:6974: Invalid argument > * Failed to connect to fe80::fe5f:49ff:febf:6974 port 80 after 0 ms: Could not connect to server > * closing connection #0 > curl: (7) Failed to connect to fe80::fe5f:49ff:febf:6974 port 80 after 0 ms: Could not connect to server > > So I did some research and it turned out that this is a link-local > address. Accessing link-local addresses with Linux require a zone > identifier. > > So with curl I can now successfully connect to the device: > > $ curl -v http://[fe80::fe5c:44ff:febf:6974%eno0] > * Trying [fe80::fe5c:44ff:febf:6974]:80... > * Connected to fe80::fe5c:44ff:febf:6974 (fe80::fe5c:44ff:febf:6974) port 80 > * using HTTP/1.x > > GET / HTTP/1.1 > > Host: [fe80::fe5c:44ff:febf:6974] > > User-Agent: curl/8.11.0 > > Accept: */* > > > * Request completely sent off > < HTTP/1.1 200 OK > < CACHE-CONTROL: no-cache > < Content-Length: 40469 > < Content-Type: text/html > < > <!DOCTYPE html> <html> <head> <title></title> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" > > But this doesn't work with Firefox or Chrome. > > When entering the address that works with curl, Firefox starts a search > instead: > > search-instead-interface.png (view on web) > <https://github.com/user-attachments/assets/b4298791-7488-4f70-b51f-e2e3d8f3cec0> > > I was told this does work on Windows however. But I'd rather not install > this just to configure some device. > > Can anyone please explain like I am 5 why this works in curl but not in > Firefox? I just want to configure my device. > > — > Reply to this email directly, view it on GitHub > <https://github.com/whatwg/url/issues/392#issuecomment-2521119117>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ASHRSDNBHIGSOT623MJ55T32ECLEXAVCNFSM6AAAAABTDCCD56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRGEYTSMJRG4> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/392#issuecomment-2521510923 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/392/2521510923@github.com>
Received on Thursday, 5 December 2024 21:41:32 UTC