Hello,
I was told to get 48 prefix, seems getting only 64 prefix which is completely useless, see the IMG attached.
And can’t ping the IPv6 addresses and Turris check connection also fails.
Many thanks.
Could you share your network config for wan interface?
Which ISP promised the /48?
config interface 'wan'
option proto 'dhcp'
option device 'eth2'
config interface 'wan6'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option device '@wan'
It is actually from Quantcom.cz via one of their dealers.
Seems fine, I get my /56 from my ISP with the same config.
Prefix 64 is completely useless, it is a single address and assigned to the router. Do these companies think they can fool people, especially IT people?
I need to ask again to see what the hell is going on.
A /64 prefix has 18446744073709551616 usable IP addresses. A single address is /128.
Maybe try setting reqprefix from auto to /48 or 48?
Yes but none of the clients will get a IPv6 address nor you can’t create subnets. It is useless. I need at least prefix 56.
1 Like
Didn’t help.
I see these kind of errors in logs
Jul 28 19:31:00 turris netifd: Failed to assign requested subprefix of size 60 for lan, trying other
Beside these after a reboot it takes ages to get a internet from wifi.
The long story short I moved to a new apartment and another isp now, dual stack. Connecting to the internet is a headache now.
From your logs it seems like it cannot assign /60 for lan. Try setting /48 for wan and /64 for lan interface
I can try this evening but the lan needs at least /60 because of the vlans.
Meanwhile I wrote to the ISP.
From the initial img which I attached is obvious they give only 64 prefix.
Jul 29 20:37:28 turris netifd: Failed to assign requested subprefix of size 64 for guest, trying other
Jul 29 20:37:28 turris netifd: Failed to assign requested subprefix of size 64 for lan2, trying other
Jul 29 20:37:28 turris netifd: Failed to assign requested subprefix of size 64 for lan, trying other
Jul 29 20:37:28 turris netifd: Failed to assign requested subprefix of size 64 for iot, trying other
Doesnt help, same.
ISP changed prefix to /56. Subnets also popped up.
DNS problem is still there, after reboot it takes about an hour to get internet working. The strange thing it starts to work fine itself after some time. No idea why. My setup uses CloudFlare DNS servers.
The other issue is that I can ping IPv6 addresses from the clients eg from Debian laptop, but can’t ping from the router.
That doesn’t sound like a DNS problem at all. More like IPv6 not working from the router, even though working from LAN.
1 Like
So I suspect that private IPv6 networking- ULA(fd72:aaaa:bbbb::/48) causing the problems.
Do I really need that and is there a way to remove it?
That seems very unlikely to cause kresd to consume lots of RAM. Not much difference from a global IPv6 address.
I’ve read that sometimes wan6 interface might get problems when using @wan (alias) try setting it to eth2 and make sure you actually get IPv6 on WAN not just prefix for your subnets
you can remove it from /etc/config/network or http://192.168.1.1/cgi-bin/luci/admin/network/network Global network options
If you do not actively use ULA, it is safe removing it.
This topic was automatically closed after 60 days. New replies are no longer allowed.