Controllerless Networks

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Still not fully clear what you try to do:

• Do you want the AP to be connected to the (backbone) networks and have a wired or wireless client connect to the AP and then bridged to the backbone network?
• Do you want the AP to be part of a mesh with other APs and then have a wired client connect to one of the wired ports and use the mesh as connection to the network?
• Do you want the AP to be a WLAN client to another WLAN and then use the AP as a wireless bridge to connect a wired client to a wireless network?

Can you draw an image and share what you are trying to do and make the explanation a bit more clear, before we go into configuration options?

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Thanks for the replies thus far. I'm on the road now, so can't do a diagram until later. Let me try and clarify. 

IAP1 is connected to my router. 

IAP2 is wirelessly linked to IAP1. 

I want to use eth0 to connect my PC back to the network by wire. 

I assume that configuring the port for bridging would accomplish that, but the port is only live during boot of IAP2 and then dies. Disconnects. No juice. 

If I reset IAP2 and wire it back to the router, it recognizes IAP1 as the master and pulls the firmware/config as needed. So eth0 is working. 

I may have something misunderstood or incorrectly configured. 

Hopefully that gives some insight. 

Original Message:
Sent: Nov 06, 2023 11:54 AM
From: Herman Robers
Subject: IAP-215 - ETH0 Bridging Not Working

Still not fully clear what you try to do:

• Do you want the AP to be connected to the (backbone) networks and have a wired or wireless client connect to the AP and then bridged to the backbone network?
• Do you want the AP to be part of a mesh with other APs and then have a wired client connect to one of the wired ports and use the mesh as connection to the network?
• Do you want the AP to be a WLAN client to another WLAN and then use the AP as a wireless bridge to connect a wired client to a wireless network?

Can you draw an image and share what you are trying to do and make the explanation a bit more clear, before we go into configuration options?

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.

Original Message:
Sent: Nov 04, 2023 10:21 AM
From: carlos
Subject: IAP-215 - ETH0 Bridging Not Working

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Put both APs on the same network.  Enable mesh on both APs.  Disable E0 Bridging on one of the APs, setting the AP for mesh point operation.  Reboot both APs, making sure to remove the mesh point from the wired network.

Both APs should come up with mesh enabled, one noted as portal and the other as point.  When looking at the VC you should see both APs as operational within the cluster.  At this point you can connect to E0 on the mesh point and should get an IP address from the management/untagged VLAN of the portal AP.

If you want to mess with additional VLANs, tagged or untagged, across the mesh then I'd recommend using E1 on the mesh point as your wired bridging interface as that simplifies the configuration of the wired port profile.

Thanks for the replies thus far. I'm on the road now, so can't do a diagram until later. Let me try and clarify. 

IAP1 is connected to my router. 

IAP2 is wirelessly linked to IAP1. 

I want to use eth0 to connect my PC back to the network by wire. 

I assume that configuring the port for bridging would accomplish that, but the port is only live during boot of IAP2 and then dies. Disconnects. No juice. 

If I reset IAP2 and wire it back to the router, it recognizes IAP1 as the master and pulls the firmware/config as needed. So eth0 is working. 

I may have something misunderstood or incorrectly configured. 

Hopefully that gives some insight. 

Still not fully clear what you try to do:

• Do you want the AP to be connected to the (backbone) networks and have a wired or wireless client connect to the AP and then bridged to the backbone network?
• Do you want the AP to be part of a mesh with other APs and then have a wired client connect to one of the wired ports and use the mesh as connection to the network?
• Do you want the AP to be a WLAN client to another WLAN and then use the AP as a wireless bridge to connect a wired client to a wireless network?

Can you draw an image and share what you are trying to do and make the explanation a bit more clear, before we go into configuration options?

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

That's what I did. Except waiting on the boot up before adding the cable. The cable was plugged in from the start. If I get to a point today that I'm able to remote to a system on the network and screenshot the dashboard, I'll do so and let you see. 

Put both APs on the same network.  Enable mesh on both APs.  Disable E0 Bridging on one of the APs, setting the AP for mesh point operation.  Reboot both APs, making sure to remove the mesh point from the wired network.

Both APs should come up with mesh enabled, one noted as portal and the other as point.  When looking at the VC you should see both APs as operational within the cluster.  At this point you can connect to E0 on the mesh point and should get an IP address from the management/untagged VLAN of the portal AP.

If you want to mess with additional VLANs, tagged or untagged, across the mesh then I'd recommend using E1 on the mesh point as your wired bridging interface as that simplifies the configuration of the wired port profile.

Thanks for the replies thus far. I'm on the road now, so can't do a diagram until later. Let me try and clarify. 

IAP1 is connected to my router. 

IAP2 is wirelessly linked to IAP1. 

I want to use eth0 to connect my PC back to the network by wire. 

I assume that configuring the port for bridging would accomplish that, but the port is only live during boot of IAP2 and then dies. Disconnects. No juice. 

If I reset IAP2 and wire it back to the router, it recognizes IAP1 as the master and pulls the firmware/config as needed. So eth0 is working. 

I may have something misunderstood or incorrectly configured. 

Hopefully that gives some insight. 

Still not fully clear what you try to do:

• Do you want the AP to be connected to the (backbone) networks and have a wired or wireless client connect to the AP and then bridged to the backbone network?
• Do you want the AP to be part of a mesh with other APs and then have a wired client connect to one of the wired ports and use the mesh as connection to the network?
• Do you want the AP to be a WLAN client to another WLAN and then use the AP as a wireless bridge to connect a wired client to a wireless network?

Can you draw an image and share what you are trying to do and make the explanation a bit more clear, before we go into configuration options?

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

Original Message:
Sent: Nov 06, 2023 12:21 PM
From: chulcher
Subject: IAP-215 - ETH0 Bridging Not Working

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Nov 04, 2023 10:21 AM
From: carlos
Subject: IAP-215 - ETH0 Bridging Not Working

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Alright. Created a new one but maybe incorrectly configured?

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

That "Admin status" set to "Down" is going to cause you a bunch of problems.  Also set as "uplink", should be "downlink".  I'd recommend operating in "Access" mode, with the VLAN set to 1 (assuming that you've not modified the VLAN settings anywhere else) to at least get operational.  Having the client IP assignment set to VC managed is calling for the AP to utilize magic VLAN functionality rather than dumping the client into the untagged VLAN.

Alright. Created a new one but maybe incorrectly configured?

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Current settings that I think might actually be working. Going to reboot all devices and verify. If this works fine - just need to sort the SSL certificate for captive portal.

That "Admin status" set to "Down" is going to cause you a bunch of problems.  Also set as "uplink", should be "downlink".  I'd recommend operating in "Access" mode, with the VLAN set to 1 (assuming that you've not modified the VLAN settings anywhere else) to at least get operational.  Having the client IP assignment set to VC managed is calling for the AP to utilize magic VLAN functionality rather than dumping the client into the untagged VLAN.

Alright. Created a new one but maybe incorrectly configured?

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Thanks to Herman Robers and chulcher for all of the help in getting this working. From here I'll play around with the various settings and see what I can do. I guess it would be a similar process with another AP that has eth0 and eth1, but I'd be assigning the bridge to eth1 instead. 

My question though - my router does support VLAN tagging - would the settings here have worked if it was a regular switch/router with no VLAN tagging?

I'm up and working now so there's no real urgency anymore.

Many thanks again!

Current settings that I think might actually be working. Going to reboot all devices and verify. If this works fine - just need to sort the SSL certificate for captive portal.

That "Admin status" set to "Down" is going to cause you a bunch of problems.  Also set as "uplink", should be "downlink".  I'd recommend operating in "Access" mode, with the VLAN set to 1 (assuming that you've not modified the VLAN settings anywhere else) to at least get operational.  Having the client IP assignment set to VC managed is calling for the AP to utilize magic VLAN functionality rather than dumping the client into the untagged VLAN.

Alright. Created a new one but maybe incorrectly configured?

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

E0 must be in downlink mode (bridging enabled), like you've already done, for a mesh enabled AP to operate as a point.  You can use E1 rather than E0 for bridged connections, but the AP, by default, determines mesh operation mode from the E0 state.

Thanks to Herman Robers and chulcher for all of the help in getting this working. From here I'll play around with the various settings and see what I can do. I guess it would be a similar process with another AP that has eth0 and eth1, but I'd be assigning the bridge to eth1 instead. 

My question though - my router does support VLAN tagging - would the settings here have worked if it was a regular switch/router with no VLAN tagging?

I'm up and working now so there's no real urgency anymore.

Many thanks again!

Current settings that I think might actually be working. Going to reboot all devices and verify. If this works fine - just need to sort the SSL certificate for captive portal.

That "Admin status" set to "Down" is going to cause you a bunch of problems.  Also set as "uplink", should be "downlink".  I'd recommend operating in "Access" mode, with the VLAN set to 1 (assuming that you've not modified the VLAN settings anywhere else) to at least get operational.  Having the client IP assignment set to VC managed is calling for the AP to utilize magic VLAN functionality rather than dumping the client into the untagged VLAN.

Alright. Created a new one but maybe incorrectly configured?

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance. 

Many thanks for all the info and insight so far @chulcher. Will be getting some other equipment for testing later on. The main feature that made me look at Aruba was the built in captive portal. Just need to work on the certificate and changing out my router for added testing and it'll be good.

I noticed some other things that I may want assistance with, but I should probably start new threads for that. I noticed the device supports l2tp - but the settings there are different from what's in SoftEther VPN Server. But as I said - maybe a different thread if I can't figure it out.

Thanks again!

E0 must be in downlink mode (bridging enabled), like you've already done, for a mesh enabled AP to operate as a point.  You can use E1 rather than E0 for bridged connections, but the AP, by default, determines mesh operation mode from the E0 state.

Thanks to Herman Robers and chulcher for all of the help in getting this working. From here I'll play around with the various settings and see what I can do. I guess it would be a similar process with another AP that has eth0 and eth1, but I'd be assigning the bridge to eth1 instead. 

My question though - my router does support VLAN tagging - would the settings here have worked if it was a regular switch/router with no VLAN tagging?

I'm up and working now so there's no real urgency anymore.

Many thanks again!

Current settings that I think might actually be working. Going to reboot all devices and verify. If this works fine - just need to sort the SSL certificate for captive portal.

That "Admin status" set to "Down" is going to cause you a bunch of problems.  Also set as "uplink", should be "downlink".  I'd recommend operating in "Access" mode, with the VLAN set to 1 (assuming that you've not modified the VLAN settings anywhere else) to at least get operational.  Having the client IP assignment set to VC managed is calling for the AP to utilize magic VLAN functionality rather than dumping the client into the untagged VLAN.

Alright. Created a new one but maybe incorrectly configured?

Ah, next step then is to create a new wired port profile (aka wired network configuration) and apply that to E0. Since that configuration is done at the cluster level, this can be slightly confusing as you're doing this change for all APs.  Fortunately, any AP operating E0 as an uplink ignore most of the configuration settings in the wired port profile applied to E0 and will just continue to operate normally.  For the mesh point, whatever you configure will be applied on the downlink port...including the "Admin status" which may be set to "down".

Literally stopped home for 10 minutes before moving on to the next location - did a quick thing on a VM and exported with some areas blurred out. Quick and dirty with ClipChamp. But you can see the two IAPs in the list I think. 

I did the reboot of both with the settings as told before - still shows IAP2 port as not connected once it boots up.

Not sure what else to try. I have 3 IAPs in total - I swap them around and it's the same thing. Once I enable bridge on eth0 - it is live during boot but not once it's fully booted.

The devices are IAP-215s so there's only console and eth0 - no eth1 unfortunately. heading back on the road again. Will monitor for replies and do what I can remotely.

OK. Got it. 

So my point (IAP2) has bridging enabled, but the eth0 is dead after booting. 

eth0 is live during boot but not getting an IP. 

Will try rebooting both and then only connect the cable after confirming the point (IAP2) is up. 

Let me know if there's any info or screenshots you'd like to see and I'll post it as soon as I'm able. 

Portal is the mesh AP that has a wired uplink.  Point is a mesh AP that uses a mesh wireless connection for an uplink.

Portal remains connected to the wired network, point is the remote AP that has E0 bridging disabled.

Thanks for that. Not clear on the terminology and difference between point and portal. 

Assuming from your description that point means the IAP gets the IP from the router directly over wire. Portal then means it gets the IP from the router via the primary/master IAP wirelessly, and the eth0 port should provide network connectivity back to the router. 

If those assumptions are correct, then it's not happening that way. It works fine as a point, works fine as a portal for wireless, but the eth0 does not function. 

To note here, E0 bridging is telling the AP whether or not that port is to be used as an uplink (toggle enabled) and part of the uplink bond, or as a downlink (toggle disabled).

When mesh is enabled and E0 bridging is disabled, the AP will operate as a mesh point.  If E0 bridging is instead enabled, the AP will be default operate as a mesh portal.

Hi all. Hopefully someone can tell me what I'm missing. Purchased some used IAP-215 units for testing to get into the Aruba hardware. Everything seems to work seamlessly - takes a bit of getting accustomed to - but working fine so far. Here's the device infos.

Name                :Aruba Operating System Software
Type                :215
Build Time          :2023-10-29 03:31:29 PDT (build 88342) by jenkins
Version             :8.6.0.23

As the title suggests, I'm not getting ETH0 to work as a bridge. The port obviously works as I'm able to get the devices on the network and upgraded/configured, but after booting up it just doesn't work as a bridge. Unless I either misunderstood or something is off with the configuration. 

The intention is to use the remote AP as a connection by cable (over ETH0) back to the network. So....bridge. The port comes up at boot - shows on the PC it's connected to - but then seems to get disabled.

Watching the port from the console shows that it SHOULD be up.

You can see where it says twice that "enet0 bridging is enabled" - but it's really not working. If I reset the devices then the go back to working fine on LAN, but they just won't work bridged for some reason. Any help is appreciated. Thanks in advance.