search

djp952 / hdhomeruntray

HDHomeRun system tray application for Windows
Other
14 stars 1 forks source link

ipv4 missing in gui after latest beta, translate to ipv6 local now? #70

Open wazerstar opened 1 year ago

wazerstar commented 1 year ago

So in the latest beta firmware local ipv6 has been added, the tool no longer shows the ipv4 adress in the GUI, I assume its because the ip is now translated to ipv6 instead?

I added this topic since It confused me. https://forum.silicondust.com/forum/viewtopic.php?t=77386

Picture from gui https://i.imgur.com/XdLyONH.png

djp952 commented 1 year ago

Hi, sorry for the late response. I don't have any IPv6 enabled tuners and I haven't yet installed the IPv6 enabled update for the RECORD engine, assuming (correctly) that there would be problems (have bene proven right - LOL).

I think we need to think about this one a bit, and the resolution may depend on SiliconDust's updated IPv6 implementation and libhdhomerun defects/resolutions. I can totally understand that it's now a problem, but properly displaying IPv6 addresses would blow out the UI widthwise almost to a ridiculous extent to show generally nonsensical information. To me, if the only target IP information we can get is IPv6 it's better left omitted?

When I'm comfortable with the update enough to install it, I will be able to see how it looks for RECORD, but I might need to make some "asks" from you to help deciding how we should deal with IPv6 tuner targets.

I'm not entirely sure why SiliconDust opted into IPv6 in the first place; it's newer and cooler, but I fail to see the value for an ecosystem that exclusively lives on the end user's subnet(s), which will remain IPv4 for as long as I am likely to live ...

wazerstar commented 1 year ago

Hi, sorry for the late response. I don't have any IPv6 enabled tuners and I haven't yet installed the IPv6 enabled update for the RECORD engine, assuming (correctly) that there would be problems (have bene proven right - LOL).

I think we need to think about this one a bit, and the resolution may depend on SiliconDust's updated IPv6 implementation and libhdhomerun defects/resolutions. I can totally understand that it's now a problem, but properly displaying IPv6 addresses would blow out the UI widthwise almost to a ridiculous extent to show generally nonsensical information. To me, if the only target IP information we can get is IPv6 it's better left omitted?

When I'm comfortable with the update enough to install it, I will be able to see how it looks for RECORD, but I might need to make some "asks" from you to help deciding how we should deal with IPv6 tuner targets.

I'm not entirely sure why SiliconDust opted into IPv6 in the first place; it's newer and cooler, but I fail to see the value for an ecosystem that exclusively lives on the end user's subnet(s), which will remain IPv4 for as long as I am likely to live ...

I don't get why we are getting this forced upon us with latest firmware, I do not own any internally ipv6 addressees to my understanding and my ubiquity system has it ipv6 system totally disabled.

djp952 commented 1 year ago

I personally think this all a rather large mistake on SiliconDust's part and fail to see the value for their users, but ... it is what it is. All we can do is adapt.