I am using this as a main router with pppoe vlan 35. eth1.35 more spesicially, and wan6 is on eth1.35 too. It works for a few hours, then it's gone. I've tried wan6 interface as "eth1", "@wan" they both lose connection after some time. I am using a TP-Link Archer AX80
Do you have an allow rule for dhcpv6 in your firewall rules?
Check your rules in firewall on the tab traffic rules.
It's not your first time asking questions so you already know that without your network config and details about your ISP nobody can give you a meaningful answer.
2 Likes
I even used @wan but that didnt get me an ipv6. Only eth1 gave me an ipv6 addr but that only works like 2 hours at most.
root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
config globals 'globals'
option dhcp_default_duid '0004b37f807bb112408c98b9c9bbe53f55f3'
option ula_prefix 'fd40:fb5d:c384::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan0'
list ports 'lan1'
list ports 'lan2'
config device
option name 'lan0'
option macaddr 'dldldlsşş'
config device
option name 'lan1'
option macaddr 'wlelelel'
config device
option name 'lan2'
option macaddr 'dödödll'
config device
option name 'lan3'
option macaddr 'slslslsl'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ip6assign '64'
list ipaddr '192.168.5.1/24'
config interface 'wan'
option device 'eth1.35'
option proto 'pppoe'
option username 'dkdkdkdl@ttnet'
option password 'wlwlwşwş'
option ipv6 '1'
option norelease '1'
config interface 'wan6'
option proto 'dhcpv6'
option device '@wan'
option reqaddress 'try'
option reqprefix 'auto'
option norelease '1'
It is not clear if you mean the upstream ipv6 fails, or if client devices have their ipv6 connection fail, after initially working.
Use ip addr to see what is going on.
Your issue may well be a fairly common one, depending on your config and the upstream config and whether it is the upstream that fails, or just client that fails.
Look for the word "deprecated" in the ip addr output.
You might find, when ipv6 drops, a deprecated connection.
Typically you will see something like:
valid_lft XXXXsec preferred_lft 0sec
But you have proto pppoe and I have never used that so not sure what is going on with your setup.
Also I see
I could be wrong, but I thought option ipv6 was deprecated? If it is, this will do nothing I guess.
AFAIK the default for norelease is 1 anyway so you can leave this out. But these are probably just cosmetic.
I think we need to see your dhcp config, so show the output of:
uci export dhcp
as well as confirmation of whether it is upstream failure or just client failure.
root@OpenWrt:~# uci export dhcp
package dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
list server '/mask.icloud.com/'
list server '/mask-h2.icloud.com/'
list server '/use-application-dns.net/'
list server '127.0.0.1#5053'
list server '127.0.0.1#5054'
option doh_backup_noresolv '-1'
option noresolv '1'
list doh_backup_server '/mask.icloud.com/'
list doh_backup_server '/mask-h2.icloud.com/'
list doh_backup_server '/use-application-dns.net/'
list doh_backup_server '127.0.0.1#5053'
list doh_backup_server '127.0.0.1#5054'
list doh_server '127.0.0.1#5053'
list doh_server '127.0.0.1#5054'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
list ra_flags 'managed-config'
list ra_flags 'other-config'
option ra_preference 'medium'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option leasefile '/tmp/odhcpd.leases'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
option piodir '/tmp/odhcpd-piodir'
option hostsdir '/tmp/hosts'
If you set the wan6 Device to eth1 it will be sending untagged IP packets on the port, outside the pppoe tunnel. Which is sort of an unusual way for an ISP to handle IPv6.
Setting ipv6 inside the pppoe wan Interface will cause the driver to bring up a new interface called wan_6 (not the same as wan6) during connection, if during the negotiation of the connection the ISP advertises that IPv6 is supported inside the pppoe tunnel.
Check if a wan_6 interface exists and has an IPv6 while connected.
Isn't that only if set to auto? I don't have pppoe, but had to consult the wiki.
I have a wan6 interface by default at openwrt. Should I delete it or something? I am really confused, don't get angry at me but, even AI literally don't help me. I ask AI1 is eth1 true, it says yes. AI2 says no, AI1 is wrong do eth1.35 . 
I think I fixed it, you know below there at dhcp6 there is an ipv6 address with /64 prefix? I took that and wrote inside the "IPv6 routed prefix" textbox, and it worked. Now I get ipv6. But that seems it's only temporary. ISP changes this prefix sometimes.
Doesn’t make any sense, from what I can see, your wan and wan6 with pppoe are correctly set up, the big question for me is, if your firewall rules are ok. Can you post output of: cat /etc/network/firewall
From what I can understand,
ifstatus wan6
"ipv6-prefix": [ ],
"ipv6-prefix-assignment": [
These lines on is empty, so doesn't that mean that ISP doesn't give me a shareable prefix to share to the LAN clients? I think this might be fault at ISP side.
What's interesting is, I sometimes use my Freshtomato router too, it works fine for 17-18 days uptime. Even ipv6 changes, electricity goes at night, but still I can get ipv6 just fine without touching anything.
You did not answer my question.
I will rephrase it:
Is the problem just for user/client connections?
You say "I lose ipv6 after a few hours".
This is fairly typical for user/client devices under some circumstances and is a consequence of isp/openwrt not quite "lining up" and is usually fixed by setting re_lifetime accordingly.
From your screenshots, It looks like your ISP only gives you a /64 , If this is the case then you need to use the relay method in order to get ipv6 on your lan interface. and notice how your lan interface only has a ula fdxxx prefix and not a gua from the same range as on your wan_6 interface? check this post Adapting IPv6 setting from TP-Link to Openwrt - #14 by 13en for the relay config
1 Like
I think I fixed it by a small hack like this: Extend prefix
Extend 3GPP WAN interface /64 prefix via PD to LAN (RFC 7278)
I ticked on this and it works. But for how long though.