RED WLAN of RED15w not showing

It will likely not a bug, instead a wrong configuration. 

See: docs.sophos.com/.../index.html

well, i configured it exactly like the video told me to and the tunnel works (Standard/unified, DHCP Running)

Do i need to add a Firewall rule of any kind, i cant find a written configuration for Wifi anywhere, also on the manuals page the RED15w is missing? If i look at the RED configuration, as soon as its about 3G/5G/WLAN it routes you back to the same article...

"

All traffic from a separate zone network is sent to Sophos Firewall using the Virtual Extensible LAN (VXLAN) protocol. The packets will be encrypted while crossing the RED tunnel. The separate zone networks are connected to each other in Sophos Firewall. You must configure Sophos Firewall to allow traffic for the AWE (Astaro Wireless Extension) client and VXLAN (RFC 7348) for the RED interface.

AWE client is a client daemon, which runs on access points and REDs with wireless support. It registers access points on Sophos Firewall."

id be happy to configure a FW Rule if someone would point out what port the AWE is using.

So if the access point is not showing, you could look into this: https://support.sophos.com/support/s/article/KB-000036133?language=en_US

the request is coming in - packet capture shows incoming ARP/NDP Request to 1.2.3.4 and the Firewall main IP from the REDw IP

i also see a DHCP request form 0.0.0.0 to 255.255.255.255 on Port 67&68

Any reason, the firewall is not responding on DHCP requests? You could look into this in more detail on the CLI: Check the drop packet capture: https://support.sophos.com/support/s/article/KB-000036858?language=en_US

Do you have a DHCP server for this RED as well? 

i have the default DHCP on LAN, Gateway IP is 192.168.20.200 (Range 192.168.20.1-192.168.20.199), i have an addl. DHCP for the RED, IP is 192.168.20.230 (Range 192.168.20.231-192.168.20.239)

Can you show us a screenshot of your network interface page? 

That is the issue. You cannot do the same network subnet on two different interfaces. This will result in network problems like you experience. RED is a cable. It is like plugging in the same subnet into the firewall, this causes the linux kernel to mess up. 

You need to configure a different subnet range (.21) or something. 

Or you could bridge Port1 and your RED into one network by creating a Network bridge. This would resolve this issue as well, because you will have one bridge with both interfaces and one IP. 

That is the issue. You cannot do the same network subnet on two different interfaces. This will result in network problems like you experience. RED is a cable. It is like plugging in the same subnet into the firewall, this causes the linux kernel to mess up. 

You need to configure a different subnet range (.21) or something. 

Or you could bridge Port1 and your RED into one network by creating a Network bridge. This would resolve this issue as well, because you will have one bridge with both interfaces and one IP. 

it works, thank you!