[mythtv-users] Mythbackend not binding IPv6 ULA

Hika van den Hoven hikavdh at gmail.com
Wed Nov 19 14:50:57 UTC 2014


Hoi Rob,

Wednesday, November 19, 2014, 3:28:15 PM, you wrote:

> On Tue, Nov 18, 2014 at 8:23 PM, Bill Meek <keemllib at gmail.com>wrote:

> On 11/18/2014 06:31 PM, Rob Jensen wrote:
>  
>  My backend seems to be refusing to bind any unique local addresses to its
>  network connection, which is causing issues with my frontends who are using
>  IPv6.  Mythbackend should see an address beginning with fdxx, but it's only
>  finding the global and link-local addresses.  I'm able to work around this
>  on a temporary basis by specifying my global/public IPv6 address in the
>  backend setup, however things get FUBAR'ed whenever my ISP updates my
>  backend's IPv6 address.  Does anyone else have similar experiences or
>  pointers as to where I should be looking for a fix?
>  
>  
>  FWIW, I've been using ULAs since IPv6 became available to MythTV users.
>  The difference is that I explicitly define the addresses in mythtv-setup
>  under: Local Backend/IPv6 address and Master Backend IP address:.
>  
>  Right now:
>  If you start your backend with --loglevel debug, you'll see the message:
>  
>      Skipping address: your ULA here...
>  
>  I <think> because in this:
>  
>     
> https://code.mythtv.org/cgit/mythtv/tree/mythtv/libs/libmythbase/serverpool.cpp#n256
>  
>  there's no test for ULAs. If you look near line 26 in the same file,
>  there's no definition such as:
>  
>      static QPair<QHostAddress, int> kUniqueLocalAddress =
>                              QHostAddress::parseSubnet("fd00::/8");
>  
>  But I'm not familiar with the rules used there. Personally, it looks
>  like you found a bug. I also don't know if it should be fc00::/7.
>  
>  My solution has always been to put my ULAs in the 2 fields mentioned
>  in the 1st paragraph of my response. So I've never noticed what you
>  found.

> I didn't even think to explicitly define the IPv6 address in the
> Master Backend IP address field.  Once I changed that from the
> hostname to the specific ULA, everything began working again.  I'll
> submit a bug ticket, hopefully the fix is relatively easy. 

You should consider it being a DNS problem!

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens



More information about the mythtv-users mailing list