SSLVPN 5.2.9

[Carl_Wallmark]

Heads up!

Seems like the old bug which breaks SSLVPN on interfaces other than WAN1 is back in this release.

Had it working perfectly on 5.2.8 then upgraded to 5.2.9 and it stops working. After some testing I was able to get it to work on WAN1 but no other interface.

Downgraded to 5.2.8 and it started to work again.

[Ralph1973]

Hello, what unit are  you using?

Regards,

Ralph

[Carl_Wallmark]

Hi Ralph,

200D and 100D is the ones I tested.

[JohnLuo_FTNT]

Thanks for your feedback. We will add it into release notes.

[Carl_Wallmark]

We will add it into release notes.

I guess this is confirmed then ?

[Carl_Wallmark]

Confirmed:

Bug ID 287871

Administrative HTTPS and SSLVPN access using second WAN interface does not work after upgrade to 5.2.9.

[Ed1]

What happens if you aggregate the two WAN interfaces? Is the bug still there?

[Toshi_Esumi]

We experienced this when it was introduced first time, and read this thread. Now I'm wondering this problem happens because we didn't (didn't have to) originally specify the incoming interface of SSL VPN quite some time ago then it broke when the new firmware is looking for that part of config, which doesn't exist in the config. I think this because it doesn't happen to IPSec VPNs where we always bind them to a specific interface. 

[nwillia09]

We also just experienced this after getting a replacement 200D that came with 5.2.9. The SSL VPN web & tunnel mode works only on WAN2. I have attempted to unset the source-interface from the authorization rules as indicated in other forums, however that has not made any difference at all. Has anyone found a workaround besides changing firmware?

[maryzhang_FTNT]

Thanks for your feedback. There is no workaround. The issue is fixed with 5.2.10. Please upgrade your device to 5.2.10.