Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 20468 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Creating VLAN on different zone than LAN - BUG

lferrara

This morning I created additional zone on my XG at home, then I was trying to create VLAN on this zone. After clicking apply, nothing happens with no error.

Created another zone and attempt to create an additional VLAN, same issue.

So I created the VLAN on LAN zone then I moved the VLAN to the desired zone.


Where is the limitation? No error messages?

Thanks,

Luk



This thread was automatically locked due to age.
Parents
  • 0

    Hi Luk
    Good spot, thanks for raising this.
    I've reproduced the same symptoms here. I'll do some further investigation into this and let you know the outcome
    Greg

  • 0 in reply to GregH
    Thank you Greg.
    Let us know.
  • 0 in reply to lferrara
    Just a quick update on this. We do already have this logged as a bug and expect this to be fixed in a future update. I don't have a specific version number yet I'm afraid..

    The issue isn't specific to custom zones, but instead occurs when creating a vLAN interface on any zone that doesn't have a remote HTTP/HTTPS device access enabled on it.
    So another workaround for this would be to create the custom zone and enable HTTPS access from it (System > Administration > Device Access). This should allow the vLAN interfaces to be created and may help those that need to create a large number of vLAN interfaces in the short term.

    Greg
Reply
  • 0 in reply to lferrara
    Just a quick update on this. We do already have this logged as a bug and expect this to be fixed in a future update. I don't have a specific version number yet I'm afraid..

    The issue isn't specific to custom zones, but instead occurs when creating a vLAN interface on any zone that doesn't have a remote HTTP/HTTPS device access enabled on it.
    So another workaround for this would be to create the custom zone and enable HTTPS access from it (System > Administration > Device Access). This should allow the vLAN interfaces to be created and may help those that need to create a large number of vLAN interfaces in the short term.

    Greg
Children
Unfiltered HTML