XG 135 Bridge LAN to Wifi

I also experienced this issue on an XG85W.  I was forced to choose "separate zone" then choose the LAN zone. I would consider this a workaround, but when talking with Sophos technical support, they considered this to be a resolution.  From what I can tell, they are not treating this as a bug and are not working on a fix for it.

I also have an XG210 at a different location which is using the "bridge to lan" option successfully.  So I don't know why it works on one appliance but not on another.  The appliances are running the same firmware and using the same model of wireless AP.  The only difference that I can find is the hardware model of the appliance.

You will not see the bridge under Network > Interfaces.

If the Bridge to AP LAN is working on one model and not on another double check the configuration (you can share them) or open a ticket with Support.

Regards

I tested on XG105 LAN to wifi bridge is working( builtin wifi) but

not working on XG 135 ( Access point).

Is sophos support wifi to LAN bridge on XG135( AP wifi to lan)?

Of course, it is supported. At home, I have an AP 10 with XG SW home version.

I worked with technical support on my issue, they couldn't explain why the "bridge to lan" option worked on one model but not on another.  On my wireless model XG, we had to use "separate zone" and then choose LAN zone.  Technical support considered this to be a solution, I consider it a workaround.  

This is another example of how something in Sophos and XG are not working as expected. This is absolutely a workaround.

sachingurung, can you explain and take care of what ZaneDonaldson reported here?

Thanks

This is another example of how something in Sophos and XG are not working as expected. This is absolutely a workaround.

sachingurung, can you explain and take care of what ZaneDonaldson reported here?

Thanks

 I received following solution from level 2 engineer and its Work

"The process for bridging AP to LAN is slightly different for XGs with Built in APs compared to external APs. With Built in APs, you will see the Interface there to create the bridge but for External APs you do not. When you create a SSID and set that to be "Bridge to AP LAN" it's essentially bridging the AP to everything that is connected to that Port in the backend.

So, if you have your APs hooked up to the XG to a switch that led into the LAN port (Port1). When you create a SSID and set it to be Bridge to AP it will bridge that AP to everything else that is also connected to that LAN port. So, if you try this and connect to the SSID in question you should be able to access all the resources that are on the port that these APs are connected to"

On old 15.x & 16.x SFOS xg105w & xg115w's I had been manually creating a bridge interface in the network interfaces screen when it was necessary to bridge a SSID to the local network.  This worked and clients on that ssid would then get their ip's from a local windows dhcp server rather than the sophos dhcp used by the non-bridged ssid's.  Is the info in this article still the correct approach to bridging one of the wifi ssid's on XG115w_XN03_SFOS 17.1.1 MR-1 with only the integrated wifi?   Sophos XG Firewall: How to bridge the internal wireless card to LAN -

"One of the new features introduced in Sophos Firewall version 16.05 MR7 is to simplify the wireless and the LAN networks bridging.  Go to Wireless > Wireless Networks and create a Bridge to AP LAN network.
The intelligence is behind this selection which creates automatically and transparently the bridge interface and the associated firewall rules." 

After adding a "bridge to ap lan"ssid on this one it looks like an unbound network interface associated with the ssid is automatically created with no ip configured.  Should that interface be left as is in order for bridging to function or is it expected that you still must set it to a zone and configure it with an ip?