I recently got an ipv6 address from the ISP and, wan is configured with vlan35, like eth1.35. So shuld dhcpv6 wan configured as eth1 or eth1.35? Its actually configured as eth1 not eth1.35 unlike pppoe wan.
I think this might help you:
If you encounter any problems/anomalies,
please post your current configuration and interface status:
cat /etc/config/network; ifstatus wan; ifstatus wan6
2 Likes
I don't clearly understand those. Most of them they put it as "@wan" on that field. Does that mean alias interface?
root@OpenWrt-BE450:~# cat /etc/config/network; ifstatus wan; ifstatus wan6
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
list ipaddr '127.0.0.1/8'
config globals 'globals'
option dhcp_default_duid 'eqwewqeqw'
option ula_prefix 'fd3f:ewqeqeqw::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth2'
list ports 'lan1'
list ports 'lan2'
option igmp_snooping '1'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ip6assign '60'
list ipaddr '192.168.7.1/24'
config interface 'wan'
option device 'eth1.35'
option proto 'pppoe'
option username 'ewqewqe@ttnet'
option password 'ewqewqe'
option ipv6 'auto'
option norelease '1'
config interface 'wan6'
option device 'eth1.35'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option norelease '1'
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 38293,
"l3_device": "pppoe-wan",
"proto": "pppoe",
"device": "eth1.35",
"updated": [
"addresses",
"routes"
],
"metric": 0,
"dns_metric": 0,
"delegation": true,
"ipv4-address": [
{
"address": "ewqeeqweq6",
"mask": 32,
"ptpaddress": "eqweqeeeq"
}
],
"ipv6-address": [
{
"address": "qeqwewqeq",
"mask": 128
}
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [
{
"target": "0.0.0.0",
"mask": 0,
"nexthop": "qweqeqwwq",
"source": "0.0.0.0/0"
}
],
"dns-server": [
"eqweq"
],
"dns-search": [
],
"neighbors": [
],
"inactive": {
"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
],
"dns-search": [
],
"neighbors": [
]
},
"data": {
}
}
{
"up": false,
"pending": true,
"available": true,
"autostart": true,
"dynamic": false,
"proto": "dhcpv6",
"device": "eth1.35",
"data": {
}
}
If you want, you can also try this (in case it changes something):
adapted to what you currently have set:
config interface 'wan'
option proto 'pppoe'
option device 'eth1.35'
option username 'ewqewqe@ttnet'
option password 'ewqewqe'
option ipv6 '1' # Force IPv6 to be enabled on the connection.
# if your ISP broadcasts an IPV6 address
# theoretically this part could be skipped (the one under this comment)
# since a WAN6 on pppoe protocol should not be needed, do some tests
# to see if the situation changes with or without this section.
config interface 'wan6' # theoretically this part could be skipped
option proto 'dhcpv6' # theoretically this part could be skipped
option device '@wan' # theoretically this part could be skipped
option reqaddress 'try' # theoretically this part could be skipped
option reqprefix 'auto' # theoretically this part could be skipped
from what you sent:
I assume you have this problem (I'm not 100% sure)
Can your ISP provide an IPV6 address ?
An IPv6 /128 prefix represents a single, specific IPv6 address rather than a network.
The smallest usable IPv6 prefix you can delegate is /64, as it’s the minimum required for proper IPv6 subnet functionality.
Have you tried asking their tech support?
The only error I found is this:
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
# list ipaddr '127.0.0.1/8' # remove this line
2 Likes
Seeing as my problem was quoted above and I recently cleaned up my IPv6 config I might as well post what I have been using. After getting the wan interface online I initially tried to use the auto-generated wan_6 interface but found it more customisable to manually create a basic wan6 interface using a device alias as follows:
config interface wan6
option device '@wan'
option proto 'dhcpv6'
This way the IPv6 interface automatically follows the wan interface and you can still add customisations. Once that is done I have nothing major in the config and IPv6 delegation is working. I have just a static route for the gateway and standard ip6assign options set for the segments I wish to use with IPv6:
config route6
option interface 'wan'
option target '::/0'
config interface 'lan'
....
option ip6assign '64'
I have a ULA set but I don’t believe this is required, it should appear by default.
1 Like
I mean ipv6 kinda works for me, but couldn't know for sure. I even set up traffic rule to my PC. And I can see that on open ipv6 port checker sites. Since ipv6 doesn't have NAT, instead of port forwarding, we instead set up traffic rule.
But, ipv6 keeps disappearing. I think they support ipv6 experimentally. I am trying @wan as interface