BR-150 Bridge is Routing not Bridging

[UndecidedMiddle]

I am implementing an all-new HPE/Aruba Central network. As we are waiting for the fiber to be installed, we are relying on our backup cellular through the BR-150. The facility in question is under construction, so I need to use IPSEC to PtP tunnel back to our existing Meraki gateway. The BR is using our static public IP instead of bridging it to the 9114 gateway. This is causing tunnel issues as the HPE gateway doesn't have the IP, only a private IP address pushed via DHCP from the BR-150. How do I get the BR-150 to bridge, not route?

[support_s]

Hello,

Thank you for posting! HPE Networking forum has moved to Airheads Community. For HPE Aruba Networking product queries, request you to visit and post your query here.

You can refer to this link for more details.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[zayanhani]

Hey i ran into something similar when setting up a BR-150 in a temporary site. By default it tends to route instead of bridge, especially when using cellular connections. Have you checked the operating mode settings in the management interface? There should be a way to toggle between 'Router' and 'Bridge' mode but depending on firmware, that option might be hidden or limited when using certain WAN interfaces like cellular.

Also, sometimes bridging is not fully supported over LTE, so even in 'bridge mode', you might still end up with NAT behavior. Maybe try assigning the public IP directly to the HPE gateway (if your provider allows passthrough) or see if the BR-150 supports DMZ passthrough?

Would love to hear if anyone got true bridge mode working over cellular with the BR-150!

[UndecidedMiddle]

I hear you. It sounds like you're in the same place I am. What frustrates me the most is the lack of decent documentation for the BR-150. 

Also, the device is barely visible in Aruba Central and there's no ability to configure it in any way.

I grant that it's a relatively new device, but gateway support didn't even know what it was, let alone how to help. Now I'm sitting in another queue while they find someone who knows anything for it.

I will get back to you when I know more so hopefully it'll help fix your issue, but HPE/Aruba support is not moving with any haste.