StevieG  Freshman Member

I think PeterUK is right, the setting to block other static IP assigned devices, if not listed in the IP/MAC (DHCP) binding table is to enable the setting: "Enable IP/MAC Binding and DHCP Enforcement" found within the on-premise configuration. I am unsure if this setting is available in Nebula as I can only see settings…

Due to you putting a static IP on the device, then it will bypass the DHCP server/ignore the IP you reserved on that address and just try and use the IP you have given it. This will then cause conflicts on the network as both devices will try and use the given IP address. If you are going to give devices a static IP…

Hi @RDVasil Did you ever get this resolved. I am experiencing the same issue on a new branch site I am trying to setup. Struggling to find an answer. Would be grateful for any pointers.

Alexandrian In my case when I posted this question I was concerned the NSG100 would not pick up/be assigned the correct WAN IP address but it did with leaving the device on DHCP assigned. As long as your ISP is pushing out the correct static IP address you should be fine to leave it on this setting. In saying this, I still…

Chris Thanks for confirming this for me. Steve

Thanks to both Alfonso and RUnglaube for your responses. As you are allowed more licences with the NSG firewalls than the SSL VPN on USG firewalls along with the added security I will be looking into providing an NSG solution for my client.

Thanks Nebula _Freda for the update.

We have now deployed the system into a live environment and found that the captive portal was sometimes working and other times it didn't. We were experiencing different results with using different browsers and devices so therefore we decided to remove this feature at the moment and only protect with the WAP2 password. We…