Cudy Switches; do they pass VLAN tags like tp-link do ?

[jzchen]

Yeah, I had the same result with a TEG-S380: doesn't pass VLAN-tagged packets. In these unmanaged switches I think it comes down to which behavior the chipset defaults to.

I was connected to the 2.5 Gb ports on the TEG-S762. Hmmm...

 

[TheLostSwede]

Just out of curiosity, which hardware revision of the TEG-S380, as there's V1.0, V1.xR and V2.
They don't appear to be based on the same hardware.

 

[jzchen]

Mine's "V1.0R".

 

[tgl]

Just out of curiosity, which hardware revision of the TEG-S380, as there's V1.0, V1.xR and V2.

Mine says "V1.0R".

 

[TheLostSwede]

Mine's "V1.0R".

Mine says "V1.0R".

Right, I have a V2, which is much more compact, but unfortunately I don't use VLANs for anything, but is there some simple test I could do to test if that version works?

The internals are quite different. Looks like the V2 is "cheaper".

TRENDnet TEG-S380 8-port 2.5GbE Switch Review

In our TRENDnet TEG-S380 review, we see how this 8-port 2.5GbE unmanaged switch performs as the lowest-cost version we could find

www.servethehome.com

TRENDnet TEG-S380 8-Port Unmanaged 2.5G Switch Review - EnosTech.com

Today we are delving back into the networking world by looking at the TRENDnet TEG-S380 8-Port 2.5Gbe unmanaged network switch review. TRENDnet was founded in Southern California in 1990 and has gone from strength to strength in networking and surveillance products. Their unmanaged switches are...

www.enostech.com

 

[jzchen]

Do you have two ASUS routers that can create/support a guest network, in AiMesh?

Create a guest network and if possible just use the node radio, (switch in the middle of course). If you have trouble connecting any device to that network, that's pretty much it...

EDIT- I bought a TEG-S762 recently and received a V2. It's significantly smaller than V1, you are very correct. (I did not open it though so can't comment on the quality)...

 

[TheLostSwede]

Do you have two ASUS routers that can create/support a guest network, in AiMesh?

Create a guest network and if possible just use the node radio, (switch in the middle of course). If you have trouble connecting any device to that network, that's pretty much it...

EDIT- I bought a TEG-S762 recently and received a V2. It's significantly smaller than V1, you are very correct. (I did not open it though so can't comment on the quality)...

That's it? I think I could test that, give me a couple of days though, as I don't have time right now.

 

[jzchen]

That's it? I think I could test that, give me a couple of days though, as I don't have time right now.

No rush on my behalf.

I was wondering why I was having so much trouble when these were my main switches and I guess I now know why, (and all clients are on my main network)...

 

[TheLostSwede]

No rush on my behalf.

I was wondering why I was having so much trouble when these were my main switches and I guess I now know why, (and all clients are on my main network)...

Ok, sorry, took me forever to even attempt this, but I can't even get ai mesh to work, so I can't test it, sorry.

 

[jzchen]

Ok, sorry, took me forever to even attempt this, but I can't even get ai mesh to work, so I can't test it, sorry.

Did you get to try changing settings on your AX6000 via the App, (the ones that weren't working on the Web GUI)?

I am on a managed switch now so I have that headache to deal with. (Don't even need to keep it in mind. I already know the result is unpleasant)...

 

[TheLostSwede]

Did you get to try changing settings on your AX6000 via the App, (the ones that weren't working on the Web GUI)?

I am on a managed switch now so I have that headache to deal with. (Don't even need to keep it in mind. I already know the result is unpleasant)...

I had no problems changing the GT-AX6000 to aimesh, but it just wouldn't find the other router. They're on different major firmwares, so I guess that could be an issue? No matter what I tried, starting the setup on the RT-AX68U or doing it via the app, the GT-AX6000 just wouldn't detect it. I believe I ended up resetting the RT-AX68U a dozen times today, with no luck. If I was a normal consumer and if this was something I just purchased, I would've taken it back to the shop.
Bridge mode works perfectly fine though and the two have no issue communicating that way.

 

[jzchen]

I had no problems changing the GT-AX6000 to aimesh, but it just wouldn't find the other router. They're on different major firmwares, so I guess that could be an issue? No matter what I tried, starting the setup on the RT-AX68U or doing it via the app, the GT-AX6000 just wouldn't detect it. I believe I ended up resetting the RT-AX68U a dozen times today, with no luck. If I was a normal consumer and if this was something I just purchased, I would've taken it back to the shop.
Bridge mode works perfectly fine though and the two have no issue communicating that way.

I have a lot of experience with AiMesh... Most of the time they can find in another room... Are you able to move them close enough to connect ethernet from LAN of router to WAN of potential node?

 

[jzchen]

Try Ethernet (and avoid those switches) or maximum one...

 

[TheLostSwede]

I have a lot of experience with AiMesh... Most of the time they can find in another room... Are you able to move them close enough to connect ethernet from LAN of router to WAN of potential node?

I tried all the options and they were just one wall apart. I guess I can try plugging it in directly to the GT-AX6000, but that'll have to wait.

 

[jzchen]

I had to do Ethernet for some reason on same firmware 5.0 but BE router to add another BE router... Once added can remove the Ethernet cord...

 

[Tech9]

Did you get to try changing settings on your AX6000 via the App

There is a high chance @TheLostSwede is usung Asuswrt-Merlin firmware and ASUS App is oficially not supported. There is a high chance wireless node detection issues are also related to the firmware choice.

 

[jzchen]

There is a high chance @TheLostSwede is usung Asuswrt-Merlin firmware and ASUS App is oficially not supported. There is a high chance wireless node detection issues are also related to the firmware choice.

Sadly I have been experiencing difficulty adding nodes to routers with ASUSwrt 5.0, (specifically on the BE19000AI). When I first received it, I could add the BE98 Pro upstairs in my son's room, via WiFi found and added. (Not sure why it did not find it connected to the 10G WAN port, but yes WAN port choice also matters). After the latest firmware, and I decided to try again, it failed! I then proceeded to move it closer, still failed. I ended up within 7 ft line of site, still failed wirelessly to find. (Exactly as @TheLostSwede notes but I forgot because my weekend was lost and the parents' have been sleep depriving me). Of course at this point I'm shooting a message to my friend at ASUS.... He asked me if I tried an ethernet cord, (wondering why I didn't just add it via ethernet since he knows my house is wired). Connecting them directly together with ethernet, (because they were connected through switch(es)) and failed to find, I was able to add it. Then when I disconnected the cable immediately AiMesh went down, (self healing failed to work). About 5 minutes later, I noticed the wireless backhaul was established.

Topology of network also matters, (in ways you may not expect).

I had both BE19000Ai and EBG15 connected to a Layer 3 managed switch, and the switch to the wall jack/rest of my network. I added nodes to the EBG15 just fine.

I moved the switch to the communications box in the upstairs closet, so I had to rearrange the BE19000Ai and EBG15:

EBG15 - BE19000Ai - wall jack - L3 switch.

Tried to add AiMesh node to the EBG15, no-go, no-go, no-go, no-go (Toggling Ethernet Backhaul Mode, bypassing the L3 switch (which worked through in the prior arrangement)! Finally changed to:

BE19000Ai - EBG15 - wall jack - L3 switch.

Ding ding ding, winner winner chicken dinner!

***I don't think Merlin firmware has AiMesh issues, for a while now as he notes, (EDIT- unless the underlying GPL has AiMesh issues as I noted on this post, which he merged)***

 

[Tech9]

I don't think any of Asuswrt-Merlin versions are tested for AiMesh compatibility before release. This ASUS closed source firmware part is in "as is" state and 3rd party modifications on top of it can only break it, never make it better. The base for Asuswrt-Merlin is also very often completely different snapshot never released as official firmware and it may have AiMesh issues itself. In my own experience with AiMesh all devices running Asuswrt have less issues. As some say - YMMV. The fact you need to use Ethernet connection to pair the nodes indicates something is broken. This AiMesh may fail after if self-healing mechanism (wireless) isn't working.

 

[jzchen]

I go by GPL, the higher the number, is the one I choose. For the highest models ASUS seems to release higher GPL than Merlin, so both BE19000Ai and GT-BE98 Pro have been running ASUSwrt 5.0 stock firmware. This is stock firmware, not able to find an AiMesh node via WiFi within 7 ft line of site from each other...

 

[Tech9]

Newer in not always better. If you check firmware release threads for different models you'll find people reverting to previous firmware after encountering issues with latest release. ASUS own QC is not the best.