Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 4 subscribers
  • Views 4251 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MESH networking - 2.4GHz and 5GHz question

Amodin

UTM 9.711, with two APX120s.  These two APs are set up in a MESH.

My question is this - I have my APs set up for my regular WIFI as 2.4 and 5GHz, but the MESH is only at 2.4 GHz.  If I only change the MESH to 5GHz (because we have to pick one or the other), does ONLY the MESH network operate at 5GHz, and leave the WIFI network able to operate at both?  Or will it force the WIFI network that the MESH connects to one or the other?

I am trying to make this MESH network operate better.  I really don't have much in the way of obstructions between the two AP, but there is about 100ft distance that I need to get across, and the connection is really spotty.

I am also getting weird Wireless log entries: coming from the remote MESH AP.  (BTW, both APs are showing on the UTM as a root device and the remote won't change):

2022:05:21-15:04:18 P310062TCCHQB8C kernel: [ 9416.462969] [wifi0] FWLOG: [222677] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x365d5, 0x362d7, 0x3e8 )
2022:05:21-15:04:19 P310062TCCHQB8C kernel: [ 9417.462460] [wifi0] FWLOG: [223017] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:04:26 P310062TCCHQB8C kernel: [ 9424.261068] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:05:21-15:04:26 P310062TCCHQB8C kernel: [ 9424.458844] [wifi0] FWLOG: [230441] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x38429, 0x381b7, 0x3e8 )
2022:05:21-15:04:27 P310062TCCHQB8C kernel: [ 9425.458336] [wifi0] FWLOG: [231465] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x38829, 0x387e5, 0x3e8 )
2022:05:21-15:04:30 P310062TCCHQB8C kernel: [ 9428.456794] [wifi0] FWLOG: [234428] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x393bc, 0x39361, 0x3e8 )
2022:05:21-15:04:30 P310062TCCHQB8C kernel: [ 9428.456841] [wifi0] FWLOG: [234768] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:04:31 P310062TCCHQB8C kernel: [ 9429.456326] [wifi0] FWLOG: [235792] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x39910, 0x39658, 0x3e8 )
2022:05:21-15:04:32 P310062TCCHQB8C kernel: [ 9430.455810] [wifi0] FWLOG: [236237] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:04:34 P310062TCCHQB8C kernel: [ 9432.454828] [wifi0] FWLOG: [239044] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x3a5c4, 0x39ec0, 0x3e8 )
2022:05:21-15:04:35 P310062TCCHQB8C kernel: [ 9433.454252] [wifi0] FWLOG: [239279] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:04:38 P310062TCCHQB8C kernel: [ 9436.452697] [wifi0] FWLOG: [242821] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x3b485, 0x3b472, 0x3e8 )
2022:05:21-15:04:39 P310062TCCHQB8C kernel: [ 9437.452303] [wifi0] FWLOG: [243845] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x3b885, 0x3b64a, 0x3e8 )
2022:05:21-15:04:39 P310062TCCHQB8C kernel: [ 9437.452352] [wifi0] FWLOG: [244210] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:04:52 P310062TCCHQB8C kernel: [ 9450.445861] [wifi0] FWLOG: [257300] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x3ed14, 0x3eadc, 0x3e8 )
2022:05:21-15:04:53 P310062TCCHQB8C kernel: [ 9451.445345] [wifi0] FWLOG: [258324] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x3f114, 0x3ee46, 0x3e8 )
2022:05:21-15:04:54 P310062TCCHQB8C kernel: [ 9452.444875] [wifi0] FWLOG: [259319] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:04:59 P310062TCCHQB8C kernel: [ 9457.110033] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:05:21-15:05:08 P310062TCCHQB8C kernel: [ 9465.716447] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:05:21-15:05:14 P310062TCCHQB8C pdog[707]: src/process.c:241/timer_timeout_cb: process aweclient is dead for 100 seconds
2022:05:21-15:05:16 P310062TCCHQB8C kernel: [ 9474.434302] [wifi0] FWLOG: [281641] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x44c29, 0x4443f, 0x3e8 )
2022:05:21-15:05:17 P310062TCCHQB8C kernel: [ 9475.433807] [wifi0] FWLOG: [282665] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x45029, 0x44fc6, 0x3e8 )
2022:05:21-15:05:17 P310062TCCHQB8C kernel: [ 9475.433856] [wifi0] FWLOG: [282715] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:05:21 P310062TCCHQB8C kernel: [ 9479.432232] [wifi0] FWLOG: [286782] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x4603e, 0x45fbb, 0x3e8 )
2022:05:21-15:05:21 P310062TCCHQB8C kernel: [ 9479.432282] [wifi0] FWLOG: [287227] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:05:23 P310062TCCHQB8C kernel: [ 9481.431694] [wifi0] FWLOG: [289300] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x46a14, 0x46829, 0x3e8 )
2022:05:21-15:05:23 P310062TCCHQB8C kernel: [ 9481.431743] [wifi0] FWLOG: [289325] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:05:34 P310062TCCHQB8C kernel: [ 9492.426704] [wifi0] FWLOG: [300107] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x4944b, 0x49406, 0x3e8 )
2022:05:21-15:05:34 P310062TCCHQB8C kernel: [ 9492.426753] [wifi0] FWLOG: [300342] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:05:21-15:05:35 P310062TCCHQB8C kernel: [ 9493.426102] [wifi0] FWLOG: [301366] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x49936, 0x49651, 0x3e8 )
2022:05:21-15:05:35 P310062TCCHQB8C kernel: [ 9493.426150] [wifi0] FWLOG: [301391] VDEV_MGR_BCN_IN_SYNC ( 0x2 )

I am guessing because the connection between the APs isn't all that great, so I want to move it to 5GHz, as MESH is assigned to 2.4GHZ at the moment.  I prefer to have both 2.4 and 5 for the WIFI network, as some devices are only allowed to work on 2.4, but I have devices on 5GHz as well.



This thread was automatically locked due to age.
Parents
  • +1

    Mesh needs the entire Radio. This means, the APX has only 2 radios to work with. 

    https://support.sophos.com/support/s/article/KB-000037097?language=en_US

    RADIO-0:

    2.4 GHz single band

    RADIO-1:

    5 GHz single band

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Yeah I had read that before setting up the MESH.  I understand that the MESH itself will operate as one or the other. Either that article doesn't answer the questions I have, or I am just too stupid to get it.

    What I am asking is outside of the MESH, I guess that would only operate on the second radio?

    So if my WIFI is set up as both 2.4 and 5GHz, but my MESH is setup as 2.4, does that mean that my WIFI will only use the 5GHz range for other devices?  And, what about the devices on the remote end of the MESH?  Do they operate at only connecting at 5GHz while the MESH itself uses 2.4?

    So:

    (Regular Home WIFI - 2.4 & 5 GHz) <------------(MESH - 5GHz)------------> (Remote devices - 2.4GHz)

    Does this work?

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • +1 in reply to Amodin

    Mesh is not a network, a client can connect to. 

    Mesh is the network to connect a access point to another access point. It will consume one radio. 

    You can decide, if this particular radio is 5 or 2.4. If you pick 2.4 for Mesh, you can use 5 for the client network. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Yeah, I knew that too, it's just facilitating the connection.  I think you answered my question, thanks.

    I have it at 2.4 currently and it's terrible at the moment, so I want to try 5GHz but some of my devices for smart home require a 2.4 connection, so I think I should be okay changing it.  Hopefully, changing it will get rid of whatever this log entries are that I get spammed with in the Wireless Log from the remote APX.

    I still don't understand why both are showing as the root AP in the MESH network.  My understanding from the documentation should show them as two different APs, unless because the APX doesn't require the Root and Remote AP designation it wouldn't matter.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Reply
  • 0 in reply to LuCar Toni

    Yeah, I knew that too, it's just facilitating the connection.  I think you answered my question, thanks.

    I have it at 2.4 currently and it's terrible at the moment, so I want to try 5GHz but some of my devices for smart home require a 2.4 connection, so I think I should be okay changing it.  Hopefully, changing it will get rid of whatever this log entries are that I get spammed with in the Wireless Log from the remote APX.

    I still don't understand why both are showing as the root AP in the MESH network.  My understanding from the documentation should show them as two different APs, unless because the APX doesn't require the Root and Remote AP designation it wouldn't matter.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Children
  • 0 in reply to Amodin

    This is actually patched. Check the Docs again: 

    Note – You don’t need to specify a mesh network role for Sophos APX series access points.

    Which means, the APX does not use Role anymore. It simply shows always Root. 

    You could try to use the firmware of Central Wireless if this can get better results. It is free to use simply create a account and try it. 

    PS: 2.4 GHz is per default a long range band. So if you have a wide range to cover, likely this will be the only solution. 5 GHz will likely not be a good fit.

    __________________________________________________________________________________________________________________

Unfiltered HTML