IPS with IPv6 + PPPOE + VLAN : setup __BOTH__ WAN and WAN6?

Installing and Using OpenWrt
1

My new ISP gives a FTTH with

  • IPv6 with PD/56
  • PPOE with VLAN 100

I’ using an OpenWrt 24,10,5 with Flint 2, connected to the externao ONT.

FIRST TRY

To set a working WAN connection with PPPOE and VLAN100, we need to:

  • rearch Network → Interface
  • choose the WAN, or WAN6, or BOTH (??)
  • Protocol:change the protocol to PPOE
  • Device: add a custom device with the VLANID suffix, in my case Eth1.100
  • PAP user: the username provided by ISP
  • PAP pwd: the password provided by ISP

PROBLEM

the strange thing is that I tried BOTH solutions, and….. BOTH works !!!….. BUT:

    1. configuring ONLY the wan interface (ONE new wan_6 will be created; notice the “_”)
    1. configuring BOTH the wan and wan6 interfaces (TWO new wan_6 and wan6_6 will be created)

Notice that in the “vanilla” configuration (just after flash) the wan6 is NOT reported to be a @alias interface, but a “normal” interface.

Consequently the TWO different IPv6 upstream created with solution n°2,
get TWO different local link addresses….

It is difficult to understand if this is the requested behavior or an unuseful complication …

QUESTION

Both cases seem working but….

Is there an official documentation/explanation on WHICH configuration is better to setup to PPOE: WAN or both WAN & WAN6 ?

Thanks in advance

Giuliano

PS

BTW, I got the same result, creating first a new 802,1q device (eth1.100), and then configuring the WAN/WAN6 interface and linking to the previously created device.

ppoe-wan
ppoe-wan1733×918 195 KB

ppoe-wan-wan6
ppoe-wan-wan61613×1245 291 KB

2

And...

See WAN interface protocols. option ipv6 can take the value:

0: disable IPv6 on the interface
1: enable IPCP6 negotiation on the interface, but nothing else. If successful, the parent interface will be assigned a link-local address (prefix fe80::/10). All other IPv6 configuration is made in the wan6 interface which must be configured manually, as described below.
auto: (default) enable IPv6 on the interface. Spawn a virtual interface wan_6 (note the underscore) and start DHCPv6 client odhcp6c to manage prefix assignment. Ensure the lan interface has option ip6assign 64 (or a larger prefix size) set to redistribute the received prefix downstream.

You describe the behavior of option ipv6 auto, but maybe you want option ipv6 1 ?

2 Likes
3

It has wan_6 with ip6 - you just add that to wan firewall zone and you are set?

4

UPDATE:

I noticed that after RE-flashing the router to reset it,
and try configuring ONLY the WAN to the PPOE protocol,
many host on the wired network did NOT get the ip4 address, (even restarting the lan daemon, even rebooting the host).

After many hours, I reverted back to a “double PPPOE WAN”
RE-configuring ALSO the WAN6 as PPOE,
and “magically” got back the ipv4.

Is it a expected behavior ?

BELOW are the ACTUAL (double PPOE on wan and wan6) config in /etc/config/network:

@wokkocher

config file /etc/config/network has option ipv6 'auto' on both wan6 and wan

Do you mean that that

  • setting option ipv6 '1'
  • wan shoud get the IPv4, and manage DHCPv4
  • wan6 shoud get IPv6, and manage DHCPv6, and RA ?

about option ipv6 “auto”..

if you see the screen shot, even if both interface wan and wan6 got ipv6 ‘auto”
BOTH parent interface are assigned a DIFFERENT link-local address (prefix fe80::/10)
as if it would be configured as ipv6 ‘1’

(i.e. following the documentation, the different LLAs fe80 is the expected result IF I would have set ipv6 ‘1’,…)

@brada4

the /etc/config/firewall

  • defined “from begining” firewall _zone_ wan
  • containing both _network_ wan and wan6

so it seems that configuring both _network_ wan&wan6 on ppoe, keep the __zone_ unchanged..

root@OpenWrt:~# cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fdec:8885:cfd::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'
	list ports 'lan5'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.0.1'
	option netmask '255.255.255.0'
	option ip6assign '64'
	option ip6hint 'a'
	option delegate '0'

config interface 'wan'
	option device 'eth1.100'
	option proto 'pppoe'
	option username 'ftth206745'
	option password 'REMOVED'
	option ipv6 'auto'
	option norelease '1'

config interface 'wan6'
	option device 'eth1.100'
	option proto 'pppoe'
	option username 'ftth206745'
	option password 'REMOVED'
	option ipv6 'auto'
	option norelease '1'
5

This is correct IMO, but you should change the device associated with the wan6 interface, I've tried to link it with pppoewan device which seems like the obvious option, but the interface would fail some times, so you could set it to use @wan as an alias.

6

If using ipv6 auto in the primary wan gives a properly functioning wan_6, you don't need a wan6 and should delete it.

If automatic wan_6 does not work, then you need to know how your ISP implements IPv6 and configure a wan6 appropriately. In the primary wan, set ipv6 1 if your IPv6 is inside the ppp tunnel, and ipv6 0 if it is outside or uses a second ppp tunnel.

7

Is there any functional difference between using wan6 and the auto spawned wan_6?

My isp works both ways, I'm currently using ipv6 1 with default settings in wan6 except the option to request a specific address/prefix, not sure if I'm missing something?