UPDATE
I appear to have missed a few posts, re-reading the entire thread. Looks like my issue has been answered.
Zegor_mjol,
Having the same issue you mention in observation #2. I have an IoT VLAN with separate SSID and after deploying an AP One Rugged in mesh configuration for extended devices, the IoT decies will not obtain an IP via DHCP. If I use the main SSID without VLAN, the devices all connect without issues.
Were you ever able to find a fix?
Thanks.
Hi marc1, Yes, I believe this can be done as Iâve done so. You just have to enter the information for each device manually in their web admin panels.
I have set up a mesh with a Max BR1 Mk2 providing WAN support to a 2.4 and separate 5 GHz wifi network. The 2.4 net boradcasts on 2.4 and 5 GHz and the 5 GHz net only on 5.
The Mesh is setup using an AP One AC Mini. All seems to be working fine now except if I loose power on the Mini, the whole 2.4 Ghz net drops out for maybe 20 minutes. After about 10 minutes I can see the Mini is broadcasting again (although still offline via InControl), but it takes another 10 minutes before the mesh reconnects and I can log into the 2.4 GHz net. This seems way too long. What am I missing? The Max BR1 is DC wired while the Mini is currently powered via AC (to be changed to direct DC power). For now though, any blip i my AC power basically kills my access.
While the 2.4 GHz net is unavailable from any AP, I can still log into the 5 GHz net fine.
Any help in understanding what is happen here would be appreciated.
Thanks!
Weâre running the set of AP One Mini and Enterprise on FW 3.6.2s02 build 1941, and they have behaved well, with no issues. The set-up has not been stress-tested.
Z
Z,
Thank you. After re-reading the conversation I too installed FW 3.6.2s01 build 1940 on all my APOs and it appears to have resolved the DHCP VLAN issue. This is a personal use setup so its good enough for now.
Thanks again.
Hi, In the AP One-AX web interface (APâ>Setting) it says âUsing auto channel may affect performance of Mesh,â but when I change the channels to anything but âAuto,â it stops working. Could I be doing something else wrong?
Meshed APs will all use the same channel. i.e. Wired AP broadcasts on Channel 6, the meshed AP also needs to be on channel 6. Another tip is to always make sure the wired AP is available before the meshed AP is brought online. My experiences with these meshes is that they donât auto-recover very well. If it works on the first try â it will stay attached; but if that first attempt fails â they rarely recover without needing to power cycle the meshed AP.
There may be a series of settings to make it better, but I have needed to go manually reboot the meshed APs after a config sync to the wired AP on multiple occasions.
However, once they are attached â they do a good job of maintaining the connection. I have two meshed APs that have been up for over a month without any dropouts. I have all of my channels manually defined - so that may have something to do with it. I imagine channel changes will be hit and miss with the meshed APs.
That was exactly the info I needed, thanks you!
Hey guys,
is there any chance to get mesh working with two MAX Transit?
Wired Uplink â MAX Transit 1 ----- Mesh ----- Max Transit 2
I know, sounds weird, but i need a device with 10cm width in total and has external antenna connectors 
I tried this config here, but was unable to get the second Max Transit working as a Mesh Slave.
Thanks!
From the product page documentation, it says that the Max Transit and Max Transit Duo supports wifi-mesh - but the Max Transit Mini does not mention that it supports the feature. You didnât specify a duo or mini in your question - but since the names are so similar, I didnât want to assume. Also, I donât have any of the Max Transit devices available to me, so my advice is implied based on my experience with my Balance One Core and my access points - your mileage may vary and/or my advice may be absolute poopy-doop.
Make sure that both Max Transit devices have the latest firmware installed and running. My advice would be to configure both devices while they are both hardwired into the network, then to test the mesh â just unplug the network wire from the second Max Transit. If the mesh works as expected - you should still be able to get to the management web site on the non-wired Max Transit. You can also view the Mesh status on the Status->Mesh / WDS page in the administration web page. The event log on the devices should also show some log entries for âWLAN: MESH Peer (xx:xx:xx:xx:xx:xx) connected (2.4 GHz) IEEE 802.11â.
Make sure the MeshID, Frequency (2.4 or 5Ghz), and passphrase all match between the two devices. Also, make sure the hard-wired Max Transit is powered on and available before you turn on the second (non-wired) Max Transit. I have had better luck with the 2.4Ghz mesh, but data throughput is not really a concern for my use case. To start with, leave the channel and channel width set to Auto - you can make adjustments after you verify that the mesh is able to establish itself properly. I believe that it takes one of the two radios and dedicates it to the Mesh, and uses the other for client connectivity - but how it manages the broadcast channels between the two radios is beyond my comprehension. I am still a noob, but I am learning more all the time.
Remember, they will only ever try to establish the mesh if the path to the gateway is lost. They both start a âreceiverâ (server) listening for connections to the mesh, but neither will try to being the âsenderâ (client) until the path to the gateway is lost.
What is unclear is whether or not you need to use an AP controller to push out the mesh configurations. I wouldnât think that you would, but I have only ever set it up using the AP Controller inside my Balance One. I am sure someone from Peplink will chime in soon and inform us. This is still a relatively new feature, so there may be some lag in documentation updates, etc. Also, since I imagine the first Max Transit actually IS the gateway, that may change the way things work a bit. Also, the âWifi as WANâ probably has some influence to the mesh operation. I can see that there just wouldnât be enough physical radios to support such a configuration - maybe? I really donât know, but it really does expose the complexity these engineers are dealing with to provide such a feature across multiple product lines. Kudos to the engineers doing all the difficult tasks to implement such great features - even for the older product lines - it allows me to get value out of my old APs by extending my modest wired infrastructure.
Good luck in your adventure with the mesh setup - it does work very well and seems very stable and performant (until it isnât), but I have faith that it will be more resilient to interruptions with a few minor firmware tweaks. Currently, I havenât found the proper configurations to prevent clients from connecting to the APs when the mesh is âbrokenâ, but I am trying out the âManagement Unavailable Action - turn off radioâ option currently to try to mitigate the effects on the client devices if/when the mesh breaks. Unfortunately, I can only describe how to set it through an AP Controller based configurationâŚ
@jmjones
Thank you very much!
I am using Max Transit (no mini) devices, so everything should workâŚ
However, I almost suspect that the MAX Transits can only WiFi mesh to AccessPoints (AC One), but not between two MAX Transit devices.
I did exactly as described. Both devices hard wired in one network, both configured the same MeshConfig, âŚ
Both MAX Transit have the latest 8.1.1 firmware.
As soon as I remove the network cable, I can no longer reach the âslaveâ.
Mesh/WDS Page is completely empty and you cant find any info in the logs.
@TK_Liew - can you mesh two Max Transits together? Or do you need an additional non-Max AP to create the mesh?
@jmjones, please refer to my reply below. The answer is applied to all Pepwave routers.
Hope this helps.
Well⌠okay - so we have to to go with devices from Ubiquiti withinin this project.
As mentioned, we need a device with a max width of 10cm and external antenna connectors.
@AC-Max, the design for the Mesh router (MAX Transit here) always accepts the incoming Mesh connections. Hence, both MAX Transits canât communicate via Mesh connection. Do you think this helps?
Transit 1 (WIFI AP) -----> (WIFI WAN) Transit 2
@TK_Liew
I have already thought about this, but i am not sure if this meets our requirements. We will evaluate this in our lab. Thanks!
If an AP was meshed, and you plugged a device into the APâs ethernet port, would that device have a connection?
I have been trying to mesh my Balance one to a Soho MK3 for several days with no success. I have see similar question with this same combination in different forums with less than clear solutions. I have even reset the units back to factory and tried going forward from there. This is what I am trying to do.
(Peplink Balance One - 8.1.3 build 5172) connected over the WiFi to my Soho MK3 with the same build FW.
I have** **configured the Wireless Mesh on both to be HomeMesh , 5Ghz, with the same shared key. But nothing will connect.
The question I have is what does the SOHO MK3 use for a WAN in this case? Since there is nothing upstream WLAN connection. Do I need to do something special here to give it something to connect to or should it automatically connect via the SSID HomeMesh? I do have some VLANs. Do I need to change something on the VLAN to allow the configuration of the SOHO?
Below are both device settings. Any suggestions?
How many AP Ones can be meshed serially back to an AP controller?
I.e. AP Controller â AP One (1) â AP One (2) â ⌠â AP One (x)
