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...
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.
Mine says "V1.0R".Just out of curiosity, which hardware revision of the TEG-S380, as there's V1.0, V1.xR and V2.
Mine's "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?Mine says "V1.0R".
www.enostech.com
That's it? I think I could test that, give me a couple of days though, as I don't have time right now.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)...
No rush on my behalf.That's it? I think I could test that, give me a couple of days though, as I don't have time right now.
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.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)...
Did you get to try changing settings on your AX6000 via the App, (the ones that weren't working on the Web GUI)?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.
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.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.
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.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?
| Thread starter | Title | Forum | Replies | Date |
|---|---|---|---|---|
| J | Firmware Image for Cisco 250 Series and Cisco 350, 350X, and 550X Series Switches Release 2.5.9.55 | Switches, NICs and cabling | 1 |
We use essential cookies to make this site work, and optional cookies to enhance your experience.