Changes between Initial Version and Version 2 of Ticket #10921


Ignore:
Timestamp:
Jul 18, 2012, 1:55:09 PM (13 years ago)
Author:
Raymond Wagner
Comment:

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

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10921

    • Property Milestone changed from unknown to 0.27
    • Property Summary changed from FE/BE connection doesn't work via IPv6 to FE/BE connection doesn't work using Link Local IPv6 addresses

  • Ticket #10921 – Description

    initial v2  
    1 As a follow-up to ticket #10909, on a combined FE/BE that has been configured to use IPv6, the FE doesn't get a connection to the BE, and RAOP binding doesn't work either, unless I add the bitmask suffix to the IPv6 address.
    2 
    3 frontend.log is from using fe80::21f:1fff:fe23:a434 in the settings, frontend2.log from using fe80::21f:1fff:fe23:a434%ra0 as suggested by jya in ticket #10909.
     1When 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.