AX88U router - stop AiMesh Vlan tags going to the WAN

Rimmel

Occasional Visitor
AX88U latest firmware - BT Full Fibre UK.

I have asked this in another thread but it seems to have been swallowed up by other replies/fault finding. So I am asking the specific question here.


Does anyone out there know how to do this?

thanks
 

ColinTaylor

Part of the Furniture
The reply in your other thread here said that this only happens when using guest network #1. You replied by saying that you weren't using any guest networks, so there should be nothing you need to do.
 

Rimmel

Occasional Visitor
The reply in your other thread here said that this only happens when using guest network #1. You replied by saying that you weren't using any guest networks, so there should be nothing you need to do.
Not quite... the other thread ALSO said "Another user who does have AIMESH stopped those tags from going to the WAN and it also fixed it for them."

and this is what I am trying to do.
 

ColinTaylor

Part of the Furniture
Ah, OK I didn't realise you were actively using AiMesh (even though you implied it in the title :oops:). Maybe @drinkingbird can post a link to the "other user's" solution.

I don't use AiMesh so can't be of much help. But for future reference it might be helpful if you could post the output of ifconfig -a
 

Rimmel

Occasional Visitor
Ah, OK I didn't realise you were actively using AiMesh (even though you implied it in the title :oops:). Maybe @drinkingbird can post a link to the "other user's" solution.

I don't use AiMesh so can't be of much help. But for future reference it might be helpful if you could post the output of ifconfig -a
Hi - yes that's what I wanted from the first thread. But can't get a reply sadly:

[email protected]:/tmp/home/root# ifconfig -a
bcmsw Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:116525237 errors:0 dropped:40 overruns:0 frame:0
TX packets:143484771 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:90821281756 (84.5 GiB) TX bytes:172944737780 (161.0 GiB)

bcmswlpbk0 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

br0 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
inet addr:192.168.1.234 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:30387413 errors:0 dropped:0 overruns:0 frame:0
TX packets:56934601 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2689582291 (2.5 GiB) TX bytes:85027420815 (79.1 GiB)

dpsta Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
inet addr:169.254.53.133 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:56783640 errors:0 dropped:0 overruns:0 frame:0
TX packets:30115866 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:85283330333 (79.4 GiB) TX bytes:3317824818 (3.0 GiB)

eth1 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
UP BROADCAST ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth2 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:25012 errors:0 dropped:29 overruns:0 frame:0
TX packets:47238 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3121884 (2.9 MiB) TX bytes:11335776 (10.8 MiB)

eth3 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
UP BROADCAST ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth4 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:29862180 errors:0 dropped:3026 overruns:0 frame:0
TX packets:56643347 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2708121349 (2.5 GiB) TX bytes:84689224571 (78.8 GiB)

eth5 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:23129 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:5891682 (5.6 MiB)

eth6 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:18
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:61685 errors:0 dropped:17 overruns:0 frame:0
TX packets:57308 errors:0 dropped:28 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58837016 (56.1 MiB) TX bytes:35815041 (34.1 MiB)

eth7 Link encap:Ethernet HWaddr 3C:7C:3F:54:2D:1C
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:643488 errors:0 dropped:16 overruns:0 frame:0
TX packets:304763 errors:0 dropped:325 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:700159858 (667.7 MiB) TX bytes:316149482 (301.5 MiB)

ifb0 Link encap:Ethernet HWaddr 96:4D:DA:B2:EC:37
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ifb1 Link encap:Ethernet HWaddr 5A:13:6A:8E:B5:B0
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

imq1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

imq2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1452 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1
RX packets:697831 errors:0 dropped:0 overruns:0 frame:0
TX packets:697831 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:148345004 (141.4 MiB) TX bytes:148345004 (141.4 MiB)

lo:0 Link encap:Local Loopback
inet addr:127.0.1.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1

ppp0 Link encap:point-to-Point Protocol
inet addr:147.148.238.125 P-t-P:172.16.17.40 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1492 Metric:1
RX packets:56782171 errors:0 dropped:0 overruns:0 frame:0
TX packets:30114552 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:84033744818 (78.2 GiB) TX bytes:2482588385 (2.3 GiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

spu_ds_dummy Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

spu_us_dummy Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
 

ColinTaylor

Part of the Furniture
Thanks for the info, it may prove helpful to other's more knowledgeable than myself.

I do note that you're using PPPoE which might complicate matters. Reading through your other thread I'm not convinced your problem is anything to do with VLANs. It sounds more like the oft-reported DHCP renewal issue that seems to plague a lot of PPPoE users. You could try disabling AiMesh (either don't use the node or use it as a wired AP) and seeing if the problem goes away. If it doesn't then you know it's not a VLAN problem.
 

drinkingbird

Very Senior Member
AX88U latest firmware - BT Full Fibre UK.

I have asked this in another thread but it seems to have been swallowed up by other replies/fault finding. So I am asking the specific question here.


Does anyone out there know how to do this?

thanks
I don't know if the AX88 uses robocfg or not, but this is what removes it from the WAN (port 0) on most of the AC routers:

robocfg vlan 501 ports "1t 2t 3t 4t 5t" - (the default also has 0t, this command removes that)
robocfg vlan 502 ports "1t 2t 3t 4t 5t" - (same as above)
killall eapd
eapd

The two eapd lines may or may not be necessary but they don't hurt.

You will need to confirm that your router does in fact have these VLANs (or some other vlan other than 1 or 2) configured and they are bound to port 0 or whatever your WAN port is. I don't use AIMESH and in my case if GW1 is not enabled, these VLANs are not created and not sent to the WAN. As soon as GW1 is created, VLAN 501 is created, then when reloaded 502 gets created. Both get sent to the WAN, and my FIOS ONT ignores VLAN tags and gets confused by all the DHCP requests. A guest ends up getting the WAN IP assigned to them causing the WAN to no longer work. With AIMESH enabled and guest disabled, I'm not sure if they are created or not.

You can use the below command to see what VLANs are bound to which ports (assuming your router uses robocfg). T means tagged, no T means untagged. On the AC68U and variants, port 0 is WAN, 1-4 are the switch, and 5 is the CPU. 7 and 8 are unused Yours is probably a bit different. I use some custom vlans but below is what it looked like before I did that (factory settings without GW1 enabled).

VLAN 1 is LAN and VLAN 2 is WAN.

robocfg show

Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: on mac: xxx
Port 1: 100FD enabled stp: none vlan: 1 jumbo: on mac: xxx
Port 2: 10FD enabled stp: none vlan: 1 jumbo: on mac: xxx
Port 3: 100FD enabled stp: none vlan: 1 jumbo: on mac: xxx
Port 4: DOWN enabled stp: none vlan: 1 jumbo: on mac: xxx
Port 5: 1000FD enabled stp: none vlan: 2 jumbo: on mac: xxx
Port 7: DOWN enabled stp: none vlan: 1 jumbo: on mac: xxx
Port 8: DOWN enabled stp: none vlan: 1 jumbo: on mac: xxx
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 1 2 3 4 5t
2: vlan2: 0 5


If you do end up needing to remove VLANs from port 0 you'll need to have a script to do this every time the router reboots.

If your router does not use robocfg it gets more complex, but you can still view what VLANs exist and what ports they're on etc relatively easily. You can look at this thread for info on vlanctl and ethctl - https://www.snbforums.com/threads/rt-86u-vlanctl-ethctl-usage-puzzle.54375/

If your WAN only has VLAN 2 assigned then that isn't your issue. @ColinTaylor mentions a DHCP PPPoE Bug so that may be your issue. Playing with the DHCP modes, i.e. trying aggressive etc may help, but I'm not familiar with that bug.
 

ColinTaylor

Part of the Furniture
If your router does not use robocfg it gets more complex, but you can still view what VLANs exist and what ports they're on etc relatively easily. You can look at this thread for info on vlanctl and ethctl - https://www.snbforums.com/threads/rt-86u-vlanctl-ethctl-usage-puzzle.54375/
His router doesn't use robocfg, that's the problem. I couldn't see in that other thread how you can tell whether the WAN interface is passing VLAN tagged traffic. If you could post a direct link I'd be grateful. In the ifconfig output I asked him to post earlier there's no signs of any VLANs being used as far as I can see.

@Rimmel Could you also post the output of cat /proc/net/vlan/config ? Thanks.
 

drinkingbird

Very Senior Member
His router doesn't use robocfg, that's the problem. I couldn't see in that other thread how you can tell whether the WAN interface is passing VLAN tagged traffic. If you could post a direct link I'd be grateful. In the ifconfig output I asked him to post earlier there's no signs of any VLANs being used as far as I can see.

@Rimmel Could you also post the output of cat /proc/net/vlan/config ? Thanks.

I don't think ifconfig will show the VLANs on these routers. Unfortunately I haven't played with the vlanctl and ethctl but there must be a command to show current vlans and bindings, may just need to use the ? or help etc to find it.

I suspect the GW VLAN bug probably isn't the issue here as you already mentioned so probably worth looking into DHCP and PPPoE settings etc.
 

ColinTaylor

Part of the Furniture
I don't think ifconfig will show the VLANs on these routers.
When the VLANs for guest networks #1 are created you can see them in the ifconfig output because they appear as separate interfaces with the VID as a suffix, e.g. eth1.501, eth2.501, etc. There's nothing like that in his output.
 

drinkingbird

Very Senior Member
When the VLANs for guest networks #1 are created you can see them in the ifconfig output because they appear as separate interfaces with the VID as a suffix, e.g. eth1.501, eth2.501, etc. There's nothing like that in his output.

I know they show up on mine, but his output isn't even showing VLAN 1 and 2 so was assuming it might be different on those 8x series routers that seem to have a totally different architecture. But I don't know, just making assumptions. From the output, seems to be a very different setup with various virtual interfaces and no vlans showing at all (but several software/virtual interfaces).
 

Rimmel

Occasional Visitor
Thanks for all the replies - to check to see if it is a "My Router" fault, I have put the original router back in place an double Nat'ing it (no firewall + DMZ etc) directly to the AX88U. (Firewall etc enabled on the AX88U) The AX88U uses Static IP to connect to the BT Router (Internet).

I have set up a little ping monitor program and will leave it running for a couple of days and see if it still drops.

I'll post back soon.

Thanks for all the help - really appreciated :)
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top