Frequently Asked Questions#

The logout button doesn’t work.

The logout function may not behave consistently across all web browsers. For example, some browsers (such as Firefox) may cache authentication credentials and automatically log the user in again after logout. In such cases, the saved credentials may need to be manually cleared.

Parts of the webinterface are in the wrong language.

Some elements of the web interface are automatically localized by the web browser. This may affect number formatting (e.g., decimal separators) and some browser-generated error messages (e.g., “value out of range”).

How can the integrity of a firmware update be checked?

The device automatically rejects firmware updates that were tampered with. It does this by checking the uploaded image against the provided signature and a pre-shared public key. Using OpenSSL, it is possible to run this authenticity check on any computer. The check requires that the public key (.pub) is obtained from a trusted source:

# Example with authentic firmware
user@computer ~ $ openssl dgst -sha512 \
    -signature Firmware.sig \
    -verify Firmware.pub \
    Firmware.zip
Verified OK

# Example with manipulated firmware
user@computer ~ $ openssl dgst -sha512 \
    -signature Firmware.sig \
    -verify Firmware.pub \
    Firmware.zip
Verification failure
What are the supported time zones?

All current time zones defined in the IANA time zone database version 2025a are supported.

Abidjan, Accra, Addis_Ababa, Algiers, Asmara, Asmera, Bamako, Bangui, Banjul, Bissau, Blantyre, Brazzaville, Bujumbura, Cairo, Casablanca, Ceuta, Conakry, Dakar, Dar_es_Salaam, Djibouti, Douala, El_Aaiun, Freetown, Gaborone, Harare, Johannesburg, Juba, Kampala, Khartoum, Kigali, Kinshasa, Lagos, Libreville, Lome, Luanda, Lubumbashi, Lusaka, Malabo, Maputo, Maseru, Mbabane, Mogadishu, Monrovia, Nairobi, Ndjamena, Niamey, Nouakchott, Ouagadougou, Porto-Novo, Sao_Tome, Timbuktu, Tripoli, Tunis, Windhoek, Adak, Anchorage, Anguilla, Antigua, Araguaina, Argentina/Buenos_Aires, Argentina/Catamarca, Argentina/ComodRivadavia, Argentina/Cordoba, Argentina/Jujuy, Argentina/La_Rioja, Argentina/Mendoza, Argentina/Rio_Gallegos, Argentina/Salta, Argentina/San_Juan, Argentina/San_Luis, Argentina/Tucuman, Argentina/Ushuaia, Aruba, Asuncion, Atikokan, Atka, Bahia, Bahia_Banderas, Barbados, Belem, Belize, Blanc-Sablon, Boa_Vista, Bogota, Boise, Buenos_Aires, Cambridge_Bay, Campo_Grande, Cancun, Caracas, Catamarca, Cayenne, Cayman, Chicago, Chihuahua, Ciudad_Juarez, Coral_Harbour, Cordoba, Costa_Rica, Creston, Cuiaba, Curacao, Danmarkshavn, Dawson, Dawson_Creek, Denver, Detroit, Dominica, Edmonton, Eirunepe, El_Salvador, Ensenada, Fort_Nelson, Fort_Wayne, Fortaleza, Glace_Bay, Godthab, Goose_Bay, Grand_Turk, Grenada, Guadeloupe, Guatemala, Guayaquil, Guyana, Halifax, Havana, Hermosillo, Indiana/Indianapolis, Indiana/Knox, Indiana/Marengo, Indiana/Petersburg, Indiana/Tell_City, Indiana/Vevay, Indiana/Vincennes, Indiana/Winamac, Indianapolis, Inuvik, Iqaluit, Jamaica, Jujuy, Juneau, Kentucky/Louisville, Kentucky/Monticello, Knox_IN, Kralendijk, La_Paz, Lima, Los_Angeles, Louisville, Lower_Princes, Maceio, Managua, Manaus, Marigot, Martinique, Matamoros, Mazatlan, Mendoza, Menominee, Merida, Metlakatla, Mexico_City, Miquelon, Moncton, Monterrey, Montevideo, Montreal, Montserrat, Nassau, New_York, Nipigon, Nome, Noronha, North_Dakota/Beulah, North_Dakota/Center, North_Dakota/New_Salem, Nuuk, Ojinaga, Panama, Pangnirtung, Paramaribo, Phoenix, Port-au-Prince, Port_of_Spain, Porto_Acre, Porto_Velho, Puerto_Rico, Punta_Arenas, Rainy_River, Rankin_Inlet, Recife, Regina, Resolute, Rio_Branco, Rosario, Santa_Isabel, Santarem, Santiago, Santo_Domingo, Sao_Paulo, Scoresbysund, Shiprock, Sitka, St_Barthelemy, St_Johns, St_Kitts, St_Lucia, St_Thomas, St_Vincent, Swift_Current, Tegucigalpa, Thule, Thunder_Bay, Tijuana, Toronto, Tortola, Vancouver, Virgin, Whitehorse, Winnipeg, Yakutat, Yellowknife, Casey, Davis, DumontDUrville, Macquarie, Mawson, McMurdo, Palmer, Rothera, South_Pole, Syowa, Troll, Vostok, Longyearbyen, Aden, Almaty, Amman, Anadyr, Aqtau, Aqtobe, Ashgabat, Ashkhabad, Atyrau, Baghdad, Bahrain, Baku, Bangkok, Barnaul, Beirut, Bishkek, Brunei, Calcutta, Chita, Choibalsan, Chongqing, Chungking, Colombo, Dacca, Damascus, Dhaka, Dili, Dubai, Dushanbe, Famagusta, Gaza, Harbin, Hebron, Ho_Chi_Minh, Hong_Kong, Hovd, Irkutsk, Istanbul, Jakarta, Jayapura, Jerusalem, Kabul, Kamchatka, Karachi, Kashgar, Kathmandu, Katmandu, Khandyga, Kolkata, Krasnoyarsk, Kuala_Lumpur, Kuching, Kuwait, Macao, Macau, Magadan, Makassar, Manila, Muscat, Nicosia, Novokuznetsk, Novosibirsk, Omsk, Oral, Phnom_Penh, Pontianak, Pyongyang, Qatar, Qostanay, Qyzylorda, Rangoon, Riyadh, Saigon, Sakhalin, Samarkand, Seoul, Shanghai, Singapore, Srednekolymsk, Taipei, Tashkent, Tbilisi, Tehran, Tel_Aviv, Thimbu, Thimphu, Tokyo, Tomsk, Ujung_Pandang, Ulaanbaatar, Ulan_Bator, Urumqi, Ust-Nera, Vientiane, Vladivostok, Yakutsk, Yangon, Yekaterinburg, Yerevan, Azores, Bermuda, Canary, Cape_Verde, Faeroe, Faroe, Jan_Mayen, Madeira, Reykjavik, South_Georgia, St_Helena, Stanley, ACT, Adelaide, Brisbane, Broken_Hill, Canberra, Currie, Darwin, Eucla, Hobart, LHI, Lindeman, Lord_Howe, Melbourne, NSW, North, Perth, Queensland, South, Sydney, Tasmania, Victoria, West, Yancowinna, Acre, DeNoronha, East, Atlantic, Central, Eastern, Mountain, Newfoundland, Pacific, Saskatchewan, Yukon, Chile/Continental, Chile/EasterIsland, Greenwich, UCT, UTC, Universal, Zulu, Amsterdam, Andorra, Astrakhan, Athens, Belfast, Belgrade, Berlin, Bratislava, Brussels, Bucharest, Budapest, Busingen, Chisinau, Copenhagen, Dublin, Gibraltar, Guernsey, Helsinki, Isle_of_Man, Jersey, Kaliningrad, Kiev, Kirov, Kyiv, Lisbon, Ljubljana, London, Luxembourg, Madrid, Malta, Mariehamn, Minsk, Monaco, Moscow, Oslo, Paris, Podgorica, Prague, Riga, Rome, Samara, San_Marino, Sarajevo, Saratov, Simferopol, Skopje, Sofia, Stockholm, Tallinn, Tirane, Tiraspol, Ulyanovsk, Uzhgorod, Vaduz, Vatican, Vienna, Vilnius, Volgograd, Warsaw, Zagreb, Zaporozhye, Zurich, Antananarivo, Chagos, Christmas, Cocos, Comoro, Kerguelen, Mahe, Maldives, Mauritius, Mayotte, Reunion, Mexico/BajaNorte, Mexico/BajaSur, Mexico/General, Apia, Auckland, Bougainville, Chatham, Chuuk, Easter, Efate, Enderbury, Fakaofo, Fiji, Funafuti, Galapagos, Gambier, Guadalcanal, Guam, Honolulu, Johnston, Kanton, Kiritimati, Kosrae, Kwajalein, Majuro, Marquesas, Midway, Nauru, Niue, Norfolk, Noumea, Pago_Pago, Palau, Pitcairn, Pohnpei, Ponape, Port_Moresby, Rarotonga, Saipan, Samoa, Tahiti, Tarawa, Tongatapu, Truk, Wake, Wallis, Yap, Alaska, Aleutian, Arizona, US/Central, East-Indiana, US/Eastern, Hawaii, Indiana-Starke, Michigan, CET, CST6CDT, Cuba, EET, EST, EST5EDT, Egypt, Eire, Factory, GB, GB-Eire, GMT, GMT+0, GMT-0, GMT0, HST, Hongkong, Iceland, Iran, Israel, Japan, Libya, MET, MST, MST7MDT, NZ, NZ-CHAT, Navajo, PRC, PST8PDT, Poland, Portugal, ROC, ROK, Turkey, W-SU, WET
Is it possible to access the device’s API without the webinterface?

The device can be fully configured and monitored through its RESTCONF API. This is the same API used by the web interface and allows for easy integration into automation scripts and network management systems.

All API requests require HTTP Basic Authentication with a valid user account. When using a self-signed certificate, you may need to use an option like --insecure with tools like curl to bypass certificate validation (do not use this option in production!).

Example: Reading Settings and Status

# Request the NTP configuration and state from the device:
user@computer ~ $ curl -X GET -u "admin:password" \
    "https://192.168.0.39/restconf/data/network-slave-clock-common:ntp"

// Example Response
{
  "network-slave-clock-common:ntp": {
    "enable": true,
    "server1": "ntp.mobatime.com",
    "server2": "ntp-public.mobatime.com",
    "server3": "pool.ntp.org",
    "server4": "pool.ntp.org",
    "synchronized": true,
    "drift": "-0.283",
    "accuracy": "0.005249",
    "stratum": 3
  }
}

Example: Changing Configuration Parameters

# Send a PATCH request with a JSON payload containing the parameters you wish to change.
user@computer ~ $ curl -X PATCH -u "admin:password" \
  -H "Content-Type: application/yang-data+json" \
  -d '{"network-slave-clock-common:ntp": {"enable": false}}' \
  "https://192.168.0.39/restconf/data/network-slave-clock-common:ntp"

Example: Executing Commands

# Commands (RPCs) are executed by sending a POST request to the operations endpoint.
# Reboot the device
user@computer ~ $ curl -X POST -u "admin:password" \
  "https://192.168.0.39/restconf/operations/network-slave-clock-common:reboot"

# Change the admin password
user@computer ~ $ curl -X POST -u "admin:password" \
  -H "Content-Type: application/yang-data+json" \
  -d '{"network-slave-clock-common:input": {"password": "my_new_password"}}' \
  "https://192.168.0.39/restconf/operations/network-slave-clock-common:set-own-password"
How does the IPv4 prefix work? How can I set the IPv4 network mask?

The prefix notation is fully equivalent to classical network masks. See the following table for details:

Class

Prefix

Network mask

Usable hosts per subnet

-

/1

128.0.0.0

2,147,483,646

-

/2

192.0.0.0

1,073,741,822

-

/3

224.0.0.0

536,870,910

-

/4

240.0.0.0

268,435,454

-

/5

248.0.0.0

134,217,726

-

/6

252.0.0.0

67,108,862

-

/7

254.0.0.0

33,554,430

A

/8

255.0.0.0

16,777,214

A

/9

255.128.0.0

8,388,606

A

/10

255.192.0.0

4,194,302

A

/11

255.224.0.0

2,097,150

A

/12

255.240.0.0

1,048,574

A

/13

255.248.0.0

524,286

A

/14

255.252.0.0

262,142

A

/15

255.254.0.0

131,070

B

/16

255.255.0.0

65,534

B

/17

255.255.128.0

32,766

B

/18

255.255.192.0

16,382

B

/19

255.255.224.0

8,190

B

/20

255.255.240.0

4,094

B

/21

255.255.248.0

2,046

B

/22

255.255.252.0

1,022

B

/23

255.255.254.0

510

C

/24

255.255.255.0

254

C

/25

255.255.255.128

126

C

/26

255.255.255.192

62

C

/27

255.255.255.224

30

C

/28

255.255.255.240

14

C

/29

255.255.255.248

6

C

/30

255.255.255.252

2

C

/31

255.255.255.254

0
How to set a link-local IP address on Windows?

If the device is being provisioned on a network without a DHCP server, a link-local IP address is required. On Windows systems, a link-local address is assigned automatically. If connectivity issues occur, follow the steps below to eliminate common configuration problems:

  1. Enable DHCP on the network interface.
    Since no DHCP server is present, the interface will automatically assign itself a link-local address.

  2. Reconnect the network cable.
    Disconnect and reconnect the Ethernet cable to ensure the interface initializes with the updated settings.

  3. Disable other network interfaces.
    Temporarily disable WLAN and any additional LAN interfaces. This prevents routing conflicts when multiple interfaces have link-local addresses.

  4. Verify the IP address assignment.
    Open a command prompt and run ipconfig. Confirm that the interface has an address in the link-local range:

    • IPv4: 169.254.x.x

    • IPv6: fe80::…

C:\Users\...> ipconfig
...
Ethernet adapter:
...
Link-local IPv6 Address . . . . . : fe80::dfb4:...    <--- IPv6 link-local address
Autoconfiguration IPv4 Address. . : 169.254.95.33     <--- IPv4 link-local address
Subnet Mask . . . . . . . . . . . : 255.255.0.0
...
The device does not appear in Windows Explorer

The device announces itself using SSDP / UPnP. It will only appear in Windows Explorer if the following conditions are met:

  1. The device and the computer can communicate (compatible network configuration).

  2. Windows Network Discovery is enabled and active on the relevant network interface.

If the device is not displayed, follow these troubleshooting steps:

  1. Verify IP configuration.
    Ensure the Windows computer has an IP address in the same subnet as the device. If no DHCP server is available, a link-local address is required for initial discovery.

  2. Disconnect other network interfaces.
    Temporarily disable WLAN and any additional LAN connections to avoid routing conflicts.

  3. Disable special network settings.
    Temporarily turn off non-default settings such as metered connection, data limits, or additional authentication mechanisms.

  4. Enable Network Discovery.
    Check the current network profile type (Public, Private, or Domain) and enable Network Discovery for that specific profile.

  5. Check firewall settings.
    Ensure that firewall rules are not blocking incoming or outgoing SSDP or UPnP traffic. Allow the required communication if necessary (for example “Network Discovery (SSDP-In)”).

Are there any command-line tools that can detect the device?

Yes. Many tools are either pre-installed on your system or available as free downloads that can detect the device.

Example: SSDP Discovery in Windows PowerShell

PS C:\Users\user> $ssdpFinder = New-Object -ComObject 'UPnP.UPnPDeviceFinder'
PS C:\Users\user> $ssdpFinder.FindByType('upnp:rootdevice', 0)
...
FriendlyName     : NCC-V2-VB-6A-50-C6-5C-88-BB
PresentationURL  : http://10.97.101.8/
ManufacturerName : Mobatime
...

Example: SSDP Discovery on Linux

user@computer ~ $ ssdp-scan
+ NCC-V2-VB-6A-50-C6-5C-88-BB               http://10.97.101.8/
+ NCC-V2-82-3B-56-C6-53-A6                  http://10.97.101.14/
...