MartyWalter  Freshman Member

Yes, that would be great! It would be very helpful in the client list page to show the voucher information.

Update - Still trying to migrate the customer from the NSG300 to an ATP700. Simply removing the NSG device and adding the ATP device does not work. When you do so, you receive a message 'This site had been used NSG300 on before, so can't be add NSG\NSG100\NSG200 into this site" It does not seem possible to migrate.

Yes, that worked. Seems like a trivial difference but I get it. Thank you

I understand how 1:1 NAT works, but what I cannot do is map public IP at Site 1 to a private IP in site 2.

So once I set this AND I set a firewall rule, the 1:1 nat worked. The next items would be using 1:1 nat within the autovpn. i.e. Site 1 has a static IP from the ISP that I would like to route to a server at Site 2. Is this possible?

Great idea! When administering a network remotely without a remote access pc on site, this would help when customers complain of speed issues. It would also be nice to have the bandwidth speed test ahead of any IDP/AV/CF for true speed tests.

I tried that, the issue was that then the vlan7 dhcp started serving up addresses on the native vlan. 

No, it was the other way around. We worked with ZyXEL HQ to figure out this problem. Turns out there were two issues. 1. Three units would not upgrade FROM 4.39 TO 10.03. We had to manually upgrade those three units. 2. When setting a DHCP option using HEX, it caused a bug to stop the DHCP server. They are working on that…

This is exactly how we have the ATP200 programmed. It does not pass vlan7 or vlan10 from the VPN100 to the network.

Thank you! It's just what I needed.

Anytime I try to add widgets to the custom reporting I get a popup box with an error : Unexpected exception: Direct assignment to the forward side of a many-to-many set is prohibited. Use widgets.set() instead. I have tried to use only one widget and all widgets, I get the same result no matter what I do.

No, the plan was to use google domain’s dynamic dns. They use the dyndns2 protocol. 

Agree with this. As well as in a dhcp request, the default name of the product is what shows up in LLDP Neighbors listings. i.e. A GS1920-24HPv2 shows a System Name as GS1920 when looking up LLDP neighbors. It would be better if it showed the switch name and location.

We were using the old version of NCC which does not have the VLAN type field. After switching to the new version of NCC we were able to select the VLAN type. This should be addressed. 

Is this being considered for a future feature? It would be helpful.