Opened 13 years ago

Closed 11 years ago

Last modified 11 years ago

#10921 closed Bug Report - General (fixed)

FE/BE connection doesn't work using Link Local IPv6 addresses

Reported by: Jan Schneider <jan@…> Owned by: Raymond Wagner
Priority: minor Milestone: 0.27.2
Component: MythTV - General Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description (last modified by Raymond Wagner)

When MythTV is told to use one specific link-local address using the IP settings in mythtv-setup, the client code for internal communications does not properly handle the scope ID, so no connection can be established.

Attachments (2)

frontend.log​ (64.4 KB) - added by Jan Schneider <jan@…> 13 years ago.
frontend2.log​ (64.4 KB) - added by Jan Schneider <jan@…> 13 years ago.

Download all attachments as: .zip

Change History (10)

Changed 13 years ago by Jan Schneider <jan@…>

Attachment: frontend.log​ added

Changed 13 years ago by Jan Schneider <jan@…>

Attachment: frontend2.log​ added

comment:1 Changed 13 years ago by JYA

Resolution: → Duplicate
Status: new → closed

Duplicate of #10909

comment:2 Changed 13 years ago by Raymond Wagner

Description: modified (diff)
Milestone: unknown → 0.27
Resolution: Duplicate
Status: closed → new
Summary: FE/BE connection doesn't work via IPv6 → FE/BE connection doesn't work using Link Local IPv6 addresses

I'd rather keep the two issues separate, and leave the other closed.

comment:3 Changed 13 years ago by Raymond Wagner

Owner: set to Raymond Wagner
Status: new → assigned

comment:4 Changed 13 years ago by JYA

Why? It's exactly the problem of #10909, which has more info

comment:5 Changed 13 years ago by Raymond Wagner

#10909 has a bunch of info on trying to have MythTV listen on "fe80::21f:1fff:fe23:a434/64", with the result that half of MythTV correctly identifies it as an invalid IP address and reverts to IPv4 operation, while the other half blindly tries (and fails) to resolve the string through the system's DNS configuration. That's an invalid bug, and at most merits a sanity check on the inputs in mythtv-setup. Being unable to use "fe80::21f:1fff:fe23:a434" either is a separate issue.

comment:6 Changed 11 years ago by Jean-Yves Avenard <jyavenard@…>

Resolution: → fixed
Status: assigned → closed

In 5594a6f32e73b0519b556b63983786a01a0f2228/mythtv:

Make Frontend/Backend? connection works when BE is set to use IPv6 link-local address

BackendServerIP6 has created by mythtv-setup will contain the scope Id. That scope id is only valid on the machine mythtv-setup was run on.
We must remove that scope id before attempting to use it, as otherwise the connection would fail.

IPv6 link-local addresses do cause a problem has all network interfaces have one. We attempt to determine the scope id by trying to connect to the backend using each active interfaces. Once the scope Id is found, we cache it for later use.

This fixes #10921

comment:7 Changed 11 years ago by Jean-Yves Avenard <jyavenard@…>

In 192e8181025032abf0ee4cb71e6c5b7a7575b9a9/mythtv:

Make Frontend/Backend? connection works when BE is set to use IPv6 link-local address

BackendServerIP6 has created by mythtv-setup will contain the scope Id. That scope id is only valid on the machine mythtv-setup was run on.
We must remove that scope id before attempting to use it, as otherwise the connection would fail.

IPv6 link-local addresses do cause a problem has all network interfaces have one. We attempt to determine the scope id by trying to connect to the backend using each active interfaces. Once the scope Id is found, we cache it for later use.

This fixes #10921

(cherry picked from commit 5594a6f32e73b0519b556b63983786a01a0f2228)

comment:8 Changed 11 years ago by JYA

Milestone: 0.27 → 0.27.2
Note: See TracTickets for help on using tickets.