Joined: 18 Mar 2014 Posts: 12837 Location: Netherlands
Posted: Sun Sep 20, 2020 7:28 Post subject:
Answer from BS:
Quote:
it disables if wshaper is on, and also if you have multiple outgoing networks with nat. the reason is simple. sfe doesnt work then anymore
and produces routing errors. observed it with own tests. it only works with a single nat local network.
Well I still have some questions left, on Broadcom it does not seem to disable, and also when I leave the VAP as bridged and then create a bridge br1 (which has its own subnet and dhcp server) and add the VAP to this bridge (effectively having the same situation) SFE seems to stay on (please try this).
I will ask BS about this, also about his testing, in the past we had problems with SFE, it was not working with Policy Based Routing and/or stops UDP forwarding but those were all resolved by @Quarkysg (the author of SFE aka fast classifier) so maybe this problem is also resolved already?
Well I still have some questions left, on Broadcom it does not seem to disable, and also when I leave the VAP as bridged and then create a bridge br1 (which has its own subnet and dhcp server) and add the VAP to this bridge (effectively having the same situation) SFE seems to stay on (please try this).
Thanks for confirming, according to BS, SFE does not support support multiple ingoing/outgoing interfaces
So if you have SFE on and multipele interfaces (you can escape the automatic disabling by making a bridge (br1) or on broadcom automatic disabling does not seem to work) and you have strange routing problems (like hiccups etc.) then disable SFE.
What do you mean by this? Can you provide a more detailed info?
I have two VAP and I cannot enable SFE, I am also using policy based routing which was mentioned before (I think by you).