3006.102.5 Guest Network Pro issues in Aimesh nodes after reboot

[Seth Harman]

Thank you very much for the response. That’s exactly where the problem is. I believe the node is broadcasting the SSID correctly, because devices can connect to the network, but they don’t get an IP address from the DHCP server. However, if they connect to the main router, they do get an IP address. I ran a series of tests, and when I set the port connecting the switch to the mesh node to ‘access mode’ and allowed VLAN 52 through, it worked — although obviously only for the kids’ WiFi

I'd suggest you factory reset your managed switch(es) so it isn't/they aren't doing anything related to VLANs at all, you don't need any Ethernet-based VLAN stuff going on if you're talking about wireless clients only.

 

[i5Js]

Will do, thanks!

 

[128bit]

DId you did a factory reset on the nodes after going to stock? Also..I assume it's the latest stock per model correct?

Did you had to do a clean install after moving from 102.4 to 102.5? Thanks!

i had problems with guest connections after running 3006 stock (main/mesh). it was the previous 3006 release. when i loaded merlinware's 3006/102_4, guests still failed to get an ip. things began to work with a dirty upgrade to 102_5 and the latest stockware on the mesh node.

now i need to "play" with the guest settings to see what else i can do cause guest is very different with 3006, but for now, since everything's working, i've gotten lazy. @bbunge was very helpful / knowledgeable.

lastly, dong has been around for a long time but he takes a very broad look. generally, i've found advice on this blog to be a bit more relevant. bottom line, the guidance is clear - your mesh node(s) should use stock code. that's written in at least a few places.

 

[i5Js]

Will do, thanks!

New tests, but same results.... I can't get an ip from the mesh node, I've reset the switches to the default settings, and L2, it didn't work.

With dumb switches, it works.

Honestly, I don't know what else I should need to configure in in the management switches to make it work

 

[Seth Harman]

I use YazDHCP in my GNP setup on the main network so that's likely not it, to me what you're describing is an indicator that your AiMesh nodes are not properly supporting Guest Network Pro.

 

[i5Js]

Hey, thanks

Yes the nodes support it, with a non management switches, everything works

 

[Seth Harman]

Hey, thanks

Yes the nodes support it, with a non management switches, everything works

Then you probably had a misconfigured managed switch or something is wrong with it. A managed switch routes Ethernet traffic exactly the same way as an unmanaged switch if you don't enable/configure any of the managed features, i.e. out the box it's just an unmanaged switch.

 

[i5Js]

Agreed, I will check all the sg300-28 settings to disable or I will reset it again

 

[i5Js]

I've changed/tried different settings in the sg300, nothing has worked. I'm starting to think it never will with managements switches.

 

[jksmurf]

Perhaps try the setup detailed here and the TP Link Community Forums post @visortgw refers to?

I've changed/tried different settings in the sg300, nothing has worked. I'm starting to think it never will with managements switches.

 

[i5Js]

Finally I made it!. It's late here, so tomorrow I will share the details to configure a SG300-28 in between.

 

[Seth Harman]

Perhaps try the setup detailed here and the TP Link Community Forums post @visortgw refers to?

He's apparently not trying to use any wired clients in any of his GNP VLANs so none of that is relevant to his scenario.

 

[jksmurf]

He's apparently not trying to use any wired clients in any of his GNP VLANs so none of that is relevant to his scenario.

Ah ok

 

[i5Js]

Hello,

Well, this is what I did in my sg300-28

1. Create the VLAN
   
2. Choose the port that connects to the Amesh node, and set the following settings:
   
3. Go to the Port to VLAN settings and should be like following:
   
4. Go to Port VLAN Membership, and should be like following:
   

And that's it... then it started to work. I'm very noob in networking so I don't know if it makes sense.

The interesting point now is, if I enable the LACP in the ASUS, and configure the same in the switch level, it doesn't work

I hope it helps

 

[Seth Harman]

Hello,

Well, this is what I did in my sg300-28

1. Create the VLANView attachment 67901
2. Choose the port that connects to the Amesh node, and set the following settings:View attachment 67902
3. Go to the Port to VLAN settings and should be like following:View attachment 67903
4. Go to Port VLAN Membership, and should be like following:View attachment 67904

And that's it... then it started to work. I'm very noob in networking so I don't know if it makes sense.

The interesting point now is, if I enable the LACP in the ASUS, and configure the same in the switch level, it doesn't work

I hope it helps

Glad to hear it's working, but out of curiosity which port has the Ethernet cable that connects to the main router? And are you using a wireless or Ethernet backhaul for the AiMesh node?

 

[i5Js]

Hey,

I have two sg300 (big house with existing lan cables)So, without LACP: from ASUS LAN1 to SG300-28 LAN1, from SG300-28 LAN 17 to SG300-10 LAN 5 and finally from SG300-10 LAN 7 to Asus Mesh node. That works fine, without LACP

With LACP, I presume there is something missing in the ASUS bond.

I'm using Ethernet backhaul.

 

[Seth Harman]

Hey,

I have two sg300 (big house with existing lan cables)So, without LACP: from ASUS LAN1 to SG300-28 LAN1, from SG300-28 LAN 17 to SG300-10 LAN 5 and finally from SG300-10 LAN 7 to Asus Mesh node. That works fine, without LACP

With LACP, I presume there is something missing in the ASUS bond.

I'm using Ethernet backhaul.

So if I understand correctly:

Main Asus Router (port 1) <-cable-> SG300-28 (port 1) - (port 17) <-cable-> SG300-10 (port 5) - (port 7) <-cable-> AiMesh node

If I'm correct what you've done is configured port 17 on the SG300-28 to allow traffic with VLAN ID 1 and VLAN ID 52 to flow through it, which it should have done by default anyway without any VLANs configured on it (which is why wireless traffic connecting to the AiMesh node using the GNP SSID you created and being assigned VLAN ID 52 can flow through the SG300-10 with no configuration). So again, I'm confused as to why you had to setup anything at all on the SG300-28 for this configuration to work.

 

[i5Js]

Hold on, I had to configure the SG300-10 to allow the VLAN on ports 5 and 7 too

Man, I don't know... again, I'm not expert in networking but... it works. , I still don't know why it doesn't work with LACP, or what is missing in the ASUS settings...

 

[Seth Harman]

Hold on, I had to configure the SG300-10 to allow the VLAN on ports 5 and 7 too

Man, I don't know... again, I'm not expert in networking but... it works. , I still don't know why it doesn't work with LACP, or what is missing in the ASUS settings...

I'm not familiar at all with Cisco managed switches so maybe it's a requirement that you configure them to allow VLAN tagged traffic to flow through them when present. But both managed and unmanaged switches should, by default out of the box, allow all traffic (regardless of VLAN tagging) across all ports. One of the main points of a managed switch is to allow an admin to put restrictions on that behavior by using various configuration settings. This is why if you replace those managed switches with unmanaged switches it just works.

But hey, that being said it's all working now so we shouldn't be looking gift horses in the mouth