DHCP Relay over Routing-Based IPsec in SFOS 19 not workin

Yes - Route Based VPN does not support DHCP Relay.

You can use RED site to Site or Ipsec Policy based. 

No I can't...  IPSEC policy based does not work with OSPF
No I can't...  RED can't do... in fact RED can't do anything...

There is technical reason why people do thing the way they do.  Sophos XG support "routed based", Sophos XG support dhcp-relay;  dhcp-relay across xfrm interface should just work as it should.

If that box was open, I probably fixed that code myself, but unfortunatly it is not the case.  So I am here for someone to fix a feature that is advertised but does not work.

Sophos: Just fix that damn thing...  That has been reported more than 2 years ago...

Why cant RED resolve this one? If the peer is a UTM/SFOS appliance, it can perfectly resolve this scenario. 

Not cross platform...

That is correct, but you did not reflect this in your initial answer. 

You should talk to your Sales Engineer to talk about some possibilities to resolve this. 

SFOS advertise dhcp-relay

SFOS advertise routed-based ipsec

It's a bug fix, not a feature request.

I know that sales people don't care about that because they already label the box with "dhcp-relay" and "routed based ipsec" and that's all they care and now push dev. team for more label to put on the box, but that just bad...  Business driven by sales people deliver crapy product.

bug fix should be top priority, i will fill a bug report and hope for some result...

As it is documented to be a known limitation, it is not a Bug report, instead a limitation, which can be lifted. docs.sophos.com/.../index.html

cool, when bug are documented they become a "limitation".  problem solved...

that the path to allot of feature on a broken product.

roger, out...

Actually If there is a not implemented feature, it is a limitation, which is documented and you cannot configure it.

A Bug would mean, you can configure it and it does not work. 

This is actually on the roadmap to implement this feature in a future release. Feel free to talk to your local sales to get more insights to share. 

Actually If there is a not implemented feature, it is a limitation, which is documented and you cannot configure it.

A Bug would mean, you can configure it and it does not work. 

This is actually on the roadmap to implement this feature in a future release. Feel free to talk to your local sales to get more insights to share. 

So by your definition it is a bug then...

you can set up a site-2-site routed-based VPN.
you can set up a dhcp-relay that listen on a local interface and you can put the remote dhcpserver (VPN reachable, pignable from the router) in the dhcp-relay config.  You can apply/save that, no warning, no error

it just doesn't work... bug...