Hello experts! I am trying to correctly configure my 952ui-5ac2nd. My ISP needs a VLAN tag of 10 on the WAN to create a connection. From the other articles I have read, I am going to have to do this in command line which I am comfortable with, but the other examples don’t exactly match my setup. Any help would be appreciated. Here is my config, default on new install:
Change the wan device from eth1 to eth1.10. This can be done in the GUI. When you pull down the list of devices, go all the way to the bottom, click in the box that says "custom" and type the new name and press enter.
You should change the name of this forum post to something more meaningful like “configuring wan vlan” or something similar.
Thanks, did you change it? First post, so I am learning.
Admin help called for.
No, on the Interfaces page that you posted, click the blue Edit button beside WAN and change the Device pull-down box setting on that page.
Most ISP configurations that call for a tagged WAN port also use protocol PPPoE instead of DHCP, so make sure you know what the ISP is requiring to be used.
HI
Not sure what you are trying to say here? You suggested I change the name of the forum post to something more meaningful like ‘“configuring wan vlan” or something’. I cannot recall what I called it originally, but it is currently labeled as “Configuring wan vlan on 952ui-5ac2nd”. Either I named it poorly before and you changed it to include the “Configuring wan vlan”, hence my question “Did you change it” or I had already labeled it “Configuring wan vlan” which makes your comment a little confusing, and your subsequent post “Admin help called for” even more so.
1 Like
The original topic title was "Configuring 952ui-5ac2nd" which was not descriptive of the specific issue. It was edited by one of the forum regulars to make the specific issue/request more clear. No action needed at this point.
More importantly, though -- has your problem been resolved, or are you still having issues connecting to the internet?
1 Like
Thank you for the feedback.
For reasons only they will know, all fibre ISP’s in NZ require a VLAN tag of 10 on the WAN, DHCP no PPPoE. I didn’t come right with using the GUI, not sure what I messed up. I did however try some changes based on this article:
I made changes to /etc/config/network. I edited config interface ‘wan’ and added the section on the end config switch_vlan as per this attachment:
Success!
Unless there is something horribly wrong with what I have done, thank you! It seems to be working.
Please paste the contents of your configuration as text (in code tags), as I'm not quite sure if your screenshots are complete or truncated.
That aside, the config does look weird (even though I can't look into the details right now --> phone)...
Your first screenshot suggests that wan is a dedicated interface, not just another port on a common switch - if so, adding it to the switch wouldn't be possible (use eth1.10 directly). But I can't be sure, as I don't know if the screenshot is complete, nor if the config was modified before.
Second, wan and wan6 should probably refer to the same interface/ vlan.
Third, if my hunch above were incorrect and wan would be on the switch, there'd still be a fatal overlap on port4 (untagged on lan, tagged on wan) - but I think there's even more amiss.
My suggestion would be to factory reset and then paste the default /etc/config/network without any changes. That makes it easier for others to know how it should be configured - and how to change it.
3 Likes
It has an Atheros 9531 chip, which has a separate dedicated CPU port for wan. So VLANs to the ISP should be invoked directly on eth1 without involving the switch. The switch is connected only to eth0.
With that said, breaking the switch configuration should not prevent wan from working, as you do have IPv4 wan on eth1.10. Either remove wan6 (if ISP does not support IPv6) or also change it to eth1.10. Once VLANs are being tagged on a CPU port, there should be no reference to the plain port without a VLAN number.
Hi All
Not sure I fully understand everything, which is why I have been struggling. This is the screenshot of the interfaces default installation, only LAN cable connected:
This is the default config:
option name 'eth1'
option macaddr 'cc:2d:e0:c8:ad:d1'
**config interface 'wan'**
** option proto 'dhcp'**
** option device 'eth1'**
config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0.1'
config device
option name 'eth0.1'
option macaddr 'cc:2d:e0:c8:ad:d2'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.1.1'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '1 2 3 4 0t'
I edited the BOLD section to be the following:
config interface 'wan'
option proto 'dhcp'
option device 'eth1.10'
and added the following:
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '6t 4t'
option vid '10'
This looks fine except for wan6 which should also use eth1.10 or removed entirely
Thank you. What would the danger be of removing it? Is it to assign IPV6 addresses from WAN?
Yes, if your ISP supports IPv6, this would provide your router (and your downstream devices) with proper IPv6 addresses, as distributed by your ISP.
Generally speaking, no danger in removing IPv6, unless you require IPv6 for anytihng in particular. We are now, and will continue to be in the world of 'dual stack' for a while to come, so most things on the internet still work with IPv4.