03:43 <user01> hi, how can i set time zone on libreelec 9.2.5?

03:44 <user01> also, i was wondering how to enable utf8 -- doesnt seem to support accented characters in radio

03:45 <user01> finally id like to know how to automount nfs share ... im use to fstab

03:47 <user01> im running on pi4b

04:33 <user01> ok i think i got timezone in settings expert

04:35 <user01> going to try western european ISO . . . wish there was utf8 though

14:31 <jasonwc> static address via DHCPv6.

14:31 <jasonwc> I was wondering if anyone had any idea why I am unable to assign a static IPv6 IP address on LibreELEC 9.2.5 (Rasberry PI 4B). When I assign the address and gateway and then save the configuration, it accepts the changes, but when I check to see whether the settings were applied, the config shows IPV6 as off. The auto mode works with both SLAAC and DHCPv6, but it changes the DUID on every reboot, preventing me from having the DHCP server assign a

14:33 <jasonwc> I tried manually based on https://forum.libreelec.tv/thread/20833-full-ipv6-support-in-libreelec/ but it won't accept the command

14:33 <jasonwc> https://pastebin.com/6Ye2PzBM

14:36 <jasonwc> ah, looks like you need to get the interface from the wifi scan. This appears to accept the command but doesn't change the IP - "connmanctl config wifi_dca632afc3f3_4a61736f6e20415020496f54_managed_psk ipv6 manual 2001:470:e1e0:9::250 64 2001:470:e9::1

14:36 <jasonwc> "

14:47 <jasonwc> oh duh, I was using the config for the wrong SSID. Now it works!

14:49 <pragmaticenigma> MAGIC!

14:52 <jasonwc> yeah, stupid mistake. I've never used connmanctl before and I was confused by the interface naming. I was expecting it to be wlan0, not a name specific to the SSID

14:53 <jasonwc> In any case, it appears to be consistent across reboots and now just shows the manually assigned IP

15:05 <pragmaticenigma> I wasn't aware that the MAC would randomly change on each reboot, preventing DHCP from assigning the designated IP address

15:31 <jasonwc> It's not the MAC that's changing. The DUID includes the MAC as well as other information and should be stable. See https://en.wikipedia.org/wiki/DHCPv6.

15:31 <jasonwc> The MAC is stable, which is why my IPv4 address wasn't changing. However, the DUID changed on every reboot - the MAC portion was static but the other portion changed. This is the only client I've seen that exhibits such behavior.

15:32 <jasonwc> However, connman has never had particularly great ipv6 support. On the earlier versions of LibreELEC, it didn't support DHCPv6 at all.

15:33 <jasonwc> DUID looks like this 00:01:00:01:26:f0:61:4c:dc:a6:32:af:c3:f3. The MAC is dc:a6:32:af:c3:f3. It's the part before the MAC that's changing.

15:35 <jasonwc> From RFC 8415: "iable in length

15:35 <jasonwc> and because it is not required in all DHCP messages. The DUID is

15:35 <jasonwc> for any specific client or server. That is, the DUID used by a

15:35 <jasonwc> client or server SHOULD NOT change over time if at all possible; for

15:35 <jasonwc> designed to be unique across all DHCP clients and servers, and stable

15:35 <jasonwc> example, a device's DUID should not change as a result of a change in

15:35 <jasonwc> the device's network hardware or changes to virtual interfaces"

15:35 <jasonwc> sorry for the paste wall. Didn't realize it would include the line breaks.

15:40 <pragmaticenigma> wish IPv6 was easier :-/

15:41 <jasonwc> It works great with proper hardware and software support. It's very nice having globally unique IPs for every device and 65,536 subnets to use for creating VLANs. Not having to deal with NAT is awesome.

15:44 <pragmaticenigma> that's what has always concerned me... NAT is a pain yes, but I feel more comfortable with NAT as a weak firewall than letting every device on my network be reachable from the Internet (this might just be my lack of knowledge on the topic though)

15:46 <jasonwc> NAT was never really designed to be a security tool. The default firewall on any router will block incoming connections to all devices on all ports. You have to whitelist incoming connections. Outgoing is open, but that's no different with NAT.

15:47 <jasonwc> The difference is that with NAT, you've got one port per public IP, which is not the case for IPV6

15:48 <jasonwc> Also, NAT goes from an annoyance to breaking the internet when you have CG-NAT

15:48 <jasonwc> Then you just can't host anything

15:48 <jasonwc> And CG-NAT/Large Scale NAT is becoming increasingly common outside the US

15:54 <pragmaticenigma> why doesn't have to get so complicated? :(

15:56 <pragmaticenigma> argh... can't type

15:56 <pragmaticenigma> *why does it have to get so complicated?

16:31 <jasonwc> pragmaticenigma, What's so complicated?

16:31 <jasonwc> pragmaticenigma, There's actually a lot of complexity now with IPv4 due to address exhaustion. There are a bunch of methods for getting through one layer of NAT, but now users are being two layers of NAT. Connecting from one user to another may involve 4 layers of NAT.

16:32 <jasonwc> For one obvious example, there's a long thread on Plex about setting up IPv6 connectivity (easy: just add a custom URL with your ipv6 server address) because users on DS-Lite are behind CG-NAT so they have no control of port forwarding (hundreds of users could be using a single public IP)

16:33 <jasonwc> That makes ipv4 useless for hosting a plex server unless you want to pay for a port forwarding service. IPv6 works perfectly - if only they would create the URL by default, you wouldn't even have to do anything.

17:05 <pragmaticenigma> Complicated in the sense that there are lots of embedded features into the protocol. I'd love to enable IPv6 on my network and with my ISP, but I have not found any definitive documentation that boils things down so a home user can understand how to make sure their home network and devices are secured from the Internet