Best Of
Re: Flex 500 H - import DHCP list
Hello @kaktusus,
So far, we do not have a converter tool to convert from USG FLEX 200 to USG FLEX 500H.
I'd like to check with you for more information about your request.
Please check your PM box.
Thanks.
Ivan
Re: Flex 500 H - import DHCP list
You cannot upload a configuration file named startup-config.conf, please adjust the configuration file name and upload again, then apply it afterwards.
Re: Migrating from USG210 to FLEX500H
Due to the differences in port quantity and other related specifications, the Configuration Converter is only capable of converting configurations from same level of Firewalls, which means it only convert configuration from the USG FLEX 200 to the USG FLEX 200H, not USG FLEX 500H.
Re: NebulaFlex Switch GS1920 Series - V5.00 Patch 0 Firmware Release
No not really, we normally use local date/time only for both logs and files on the site I'm working now. For us it is not really necessary to have "DST" in the date string.
But, other sites that operate more globally, UTC is usually the standard for logs and files, so the whole (UTC +xx.xx DST) string can be omitted.
So here are some suggestions that might be interesting to look at:
- tickbox for individual objects like file-names, config-files to use local date/time or UTC only.
- tickbox for individual objects like file-names, config-files if the DST flag has to be mentioned or not.
- tickbox to omit the time offset string.
- Option to use the local Time standard abbreviation (CET, CEST in W-Europe for example) instead of the abbreviation DST.
In a different post for the Wireless LAN devices, I've already mentioned that the date string used in every object (logs, file names etc) should be a user definable format - not every site uses the US format.

Re: NAS 326 change disks
You must unmount the filesystem (/dev/md2, I suppose), but not stop it. If you stop it, the md device is gone, and only /dev/sda3 is left. But that doesn't contain a filesystem.
Then run e2fsck on /dev/md2.

Voice VLAN on Nebula.
ackground: Voice VLAN is a feature that separates voice and data traffic on a network, ensuring optimal performance for voice communication. This is particularly important for VoIP (Voice over Internet Protocol) systems. In this guide, we will walk you through the steps to configure Voice VLAN on a Nebula switch.
Topology and Scenario: We will configure Voice VLAN on a Nebula switch within a business environment that uses VoIP phones. The goal is to ensure that voice traffic is prioritized and segregated from data traffic for better call quality.
Steps:
- Log in to the Nebula control center using your account credentials.
- Navigate to Switch > Configure > Switch settings.
- Scroll down and find Voice VLAN, start to assign the VLAN ID also the OUI of the IP phone MAC vendor.
- Next, go to Switch > Configure > Switch ports.
- Change the port type to Access and change the VLAN type to "Voice VLAN".
Note: Ensure that the connected VoIP phones are configured to tag their traffic with the Voice VLAN ID. This setting is typically found in the phone's network configuration.
By following these steps, you can successfully configure Voice VLAN on your Nebula switch, enhancing the performance and quality of your VoIP communications.
Application patrol: "Media Streaming" and google app
Re: VPN with Snapdragon ARM
Hi @JoseHSB,
What's your ARM PC's OS? Windows? If so, have you tried the Windows VPN script?
Update: Windows ARM version should be able to use the Windows VPN script to create the VPN profile.
Re: Create simple VLAN config between GS1200 and GS1900
Hi @Momro,
Your configurations are correct. In addition, the switch-connected ports can be VLAN 1 untagged members since the PVID is 1 by default. (I assume "No PVID configured" means the PVID is 1 as default) In my experience, I will not change to a tagged member, although it also works.
Re: Create simple VLAN config between GS1200 and GS1900
hello @Momro
PVID specifies the native VLAN (untagged VLAN) for a Port, so all your Ports that use VLAN1 need to have PVID set to VLAN1 no matter if it is a trunk or access Port.
Only Port 24 on GS1900-24 and Port 1 on GS1200-5 need VLAN10 tagged.
You should be fine with everything else.
