Difference between wan and wan6?

munch · May 8, 2018, 8:20pm

Hi everyone,

I have just installed LEDE latest version on my WNDR3700. I have connected the WAN interface to a Fibre (FTTP) router that is in bridge mode. LEDE is awesome! I have mwan3 running as well to failover to my secondary line - works a treat!

WAN interface has PPOE enabled with my providers credentials entered.

Question - should I be using WAN or WAN6, and what is the difference? Both interfaces appear to work and both get ipv4 and ipv6 addresses. In fact if i enable both together i get two seperate ipv4 addresses, one on each interface

My ipv6 address is a /128

Possibly related question question is why I only seem to get 1/2 bandwidth on any one connection. My connection is 30Mb/s but each download gets max 15Mb/s. I can however run two downloads and get the full 30Mb/s.

thanks all

lleachii · May 8, 2018, 8:29pm

Odd, WAN6 should only display IPv6, and WAN should show IPv4...WAN6 is only an alias to get an IPv6 address from the same interface.

What hardware are you running?
Are you running QoS or traffic shaping of any kind?

What are the speeds of your two WAN connections?

munch · May 8, 2018, 8:36pm

Running a Netgear WNDR3700 (v1 i believe) and LEDE Reboot 17.01 going through a Billion Fibre Gateway in bridge mode PPOE.

The only change additional package I have installed is mwan3 and assigned eth0.4 to wan2 as a failover wan. This failover is connected to the LAN side of an ADSL router.

No QoS or traffic shaping of any kind is running.

FTTP is 30Mb/s down 3Mb/s up. ADSL is ~3Mb/s down ~1Mb/s up.

Are you saying that my PPOE credentials should be entered in both wan and wan6? I have 'stopped' wan6 for the time being as wan seems to work fine and gives an IPv6 address

lleachii · May 8, 2018, 8:43pm

What does this mean?

It should be connected to a port you setup as WAN2. This means you have to properly setup a Switch Port for VLAN 4 as well. I just want to ensure that you didn't plug this into your LAN.

No, I'm saying:

If you look at your configs, you'll see there isn't a way to add credentials. The config only says "@wan" and should use DHCPv6 to get an IP.

munch · May 8, 2018, 8:53pm

Router WAN connected to Fibre router in bridge mode
Router LAN port 1 VLAN1 connected to internal network
Router LAN port 4 VLAN4 connected to ADSL Router using DHCP. This port is assigned to wan firewall group. This is definitely not connected to my main LAN.

This is all setup using the GUI, but happy to provide config if required.

Ok - so in the config for wan6 interface what is the username and password field for (again, I am using the web gui).

thanks for your help!

lleachii · May 8, 2018, 9:11pm

Did you change WAN6's interface type?

munch · May 8, 2018, 9:24pm

I set protocol = PPOE, same as WAN

lleachii · May 9, 2018, 12:17am

As I noted, by default:

If you changed it, that's the problem.

jow · May 9, 2018, 8:24am

The wan6 interface is mostly a logical container for driving the IPv6 RA and DHCP client. It is usually set to be an alias interface of wan (using the ifname @wan notation) and will inherit the layer 3 interface from the parent wan interface. Due to this, both the wan and wan6 networks share the same Linux net device pppoe-wan which causes LuCI to display the same IP address info for both (its like calling ifconfig pppoe-wan twice).

In short, this is nothing to worry about and expected.

munch · May 9, 2018, 8:07pm

ok - thanks for your help. I changed the interface to "@wan" and it is showing an ipv6 address, however the LEDE diagnostics page ping ipv6 says destination unreachable

My /etc/config/network:

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

config globals 'globals'
	option ula_prefix 'removed::/48'

config interface 'lan'
	option type 'bridge'
	option proto 'static'
	option netmask '255.255.255.0'
	option ipaddr '192.168.5.1'
	option _orig_ifname 'eth0.1 radio0.network1 radio1.network1'
	option _orig_bridge 'true'
	option ifname 'eth0.1'
	option ip6assign '64'

config interface 'wan'
	option ifname 'eth1'
	option _orig_ifname 'eth1'
	option _orig_bridge 'false'
	option proto 'pppoe'
	option username 'user'
	option password 'pass'
	option ipv6 'auto'
	option metric '10'

config interface 'wan6'
	option _orig_ifname 'eth1'
	option _orig_bridge 'false'
	option proto 'dhcpv6'
	option reqaddress 'try'
	option reqprefix 'auto'
	option ifname '@wan'

config switch
	option name 'switch0'
	option reset '1'
	option enable_vlan '1'
	option blinkrate '2'
	option enable_vlan4k '1'

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option ports '3 5t'

config switch_port
	option device 'switch0'
	option port '1'
	option led '6'

config switch_port
	option device 'switch0'
	option port '2'
	option led '9'

config switch_port
	option device 'switch0'
	option port '5'
	option led '2'

config switch_vlan
	option device 'switch0'
	option vlan '2'
	option ports '2 5t'

config interface 'Guest'
	option proto 'static'
	option ifname 'eth0.2'
	option ipaddr '192.168.60.1'
	option netmask '255.255.255.0'

config switch_vlan
	option device 'switch0'
	option vlan '3'
	option ports '1 5t'

config switch_vlan
	option device 'switch0'
	option vlan '4'
	option ports '0 5t'

config interface 'wan_dsl'
	option proto 'dhcp'
	option ifname 'eth0.4'
	option hostname 'LEDE'
	option metric '20'

munch · May 14, 2018, 7:42pm

Finally solved it - mwan3 does not like ipv6 in its default configuration. As soon as i disabled mwan3, ipv6 kicked into operation.

now to find a workaround

braian87b · August 6, 2018, 3:56pm

did you find a workaround?
do you need ipv6 for some mandatory reason on your LAN?
have you tried the same setup on 17.01.5 or 18.06.0 to see if it works ?

munch · August 8, 2018, 6:34pm

Yes I did - I found an undocumented variable "option family" than can be set to ipv4 or ipv6. Working config:

config interface 'wan'
	option enabled '1'
	list track_ip '8.8.4.4'
	list track_ip '8.8.8.8'
	option reliability '2'
	option count '1'
	option timeout '2'
	option interval '5'
	option down '3'
	option up '8'
	option family 'ipv4'

config interface 'wan_dsl'
	option reliability '1'
	option count '1'
	option timeout '2'
	option interval '5'
	option down '3'
	option up '8'
	option enabled '1'
	list track_ip '8.8.8.8'
	list track_ip '8.8.4.4'
	option family 'ipv4'

config member 'wan_m1_w3'
	option interface 'wan'
	option metric '1'
	option weight '3'

config member 'wan2_m1_w2'
	option interface 'wan_dsl'
	option metric '2'
	option weight '1'

config policy 'wan_only'
	list use_member 'wan_m1_w3'

config policy 'wan2_only'
	list use_member 'wan2_m1_w2'

config policy 'wan_wan2'
	option last_resort 'unreachable'
	list use_member 'wan_m1_w3'
	list use_member 'wan2_m1_w2'

config rule 'default_rule'
	option dest_ip '0.0.0.0/0'
	option proto 'all'
	option sticky '0'
	option use_policy 'wan_wan2'
	option family 'ipv4'

config interface 'wan6'
	option enabled '1'
	option reliability '1'
	option count '1'
	option timeout '2'
	option interval '5'
	option down '3'
	option up '3'
	option family 'ipv6'

config member 'wan6_m1_w2'
	option interface 'wan6'
	option metric '1'
	option weight '3'

config policy 'wan6_only'
	list use_member 'wan6_m1_w2'
	option last_resort 'unreachable'

config rule 'default_ipv6'
	option proto 'all'
	option sticky '0'
	option use_policy 'wan6_only'
	option family 'ipv6'
	option dest_ip '::/0'

I haven't tried 18.06 yet so not sure how it will work.