-
-
Notifications
You must be signed in to change notification settings - Fork 73
Bridge errors seemingly related to trying to connect to IPv6 addresses on an IPv4 network #309
Copy link
Copy link
Open
Description
OS version: macOS 14.7.2
Browser version: 135.0
Extension version: 0.3.1
Bridge version: 0.3.0
Description
After installing the bridge and extension, the extension constantly reports that the bridge is not working.
Browser Console log reports messages like:
stderr output from native app fx_cast_bridge: Error: connect EHOSTUNREACH fe80::881f:87bd:9855:bde6:8009 - Local (:::50427)
stderr output from native app fx_cast_bridge: at internalConnect (node:net:931:16)
stderr output from native app fx_cast_bridge: at defaultTriggerAsyncIdScope (node:internal/async_hooks:465:18)
stderr output from native app fx_cast_bridge: at node:net:1022:9
stderr output from native app fx_cast_bridge: at processTicksAndRejections (node:internal/process/task_queues:78:11) {
stderr output from native app fx_cast_bridge: errno: -65,
stderr output from native app fx_cast_bridge: code: 'EHOSTUNREACH',
stderr output from native app fx_cast_bridge: syscall: 'connect',
stderr output from native app fx_cast_bridge: address: 'fe80::881f:87bd:9855:bde6',
stderr output from native app fx_cast_bridge: port: 8009
stderr output from native app fx_cast_bridge: }
I am not sure where the address fe80::881f:87bd:9855:bde6 comes from. I have 4 cast devices on the local network which is IPv4-only. Using the Discovery app I can see the mDNS responses from them and their IPv4 addresses.
Possibly this is related to #308 but I've never seen a permissions request prompt despite restarting the browser many times.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels