ping --vlan=xxx error

[returntrip]

Is it happening due to some misconfiguration in my config or is it expected somehow??

22:06:04 [Scheduler] run for IPNEIGH: YES
22:06:04 [Plugin utils] ---------------------------------------------
22:06:04 [Plugin utils]  display_name :  IP Neigh
22:06:04 [Plugins] Executing: python3 /app/front/plugins/ipneigh/ipneigh.py
22:06:05 [Plugins] Output: [plugin_helper] reading config file
22:06:05 [IPNEIGH] In script
22:06:05 [IPNEIGH] SCAN_SUBNETS value: ['--localnet', '<ip>/24 --interface=enp0s31f6 --vlan=101']
22:06:05 [IPNEIGH] Interfaces value: "enp0s31f6 --vlan=101"
22:06:05 [IPNEIGH] Pinging on interface: "enp0s31f6 --vlan=101"
ping: unrecognized option: vlan=101
BusyBox v1.37.0 (2025-11-21 22:40:56 UTC) multi-call binary.

Usage: ping [OPTIONS] HOST

Send ICMP ECHO_REQUESTs to HOST

	-4,-6		Force IP or IPv6 name resolution
	-c CNT		Send only CNT pings
	-s SIZE		Send SIZE data bytes in packets (default 56)
	-i SECS		Interval
	-A		Ping as soon as reply is received
	-t TTL		Set TTL
	-I IFACE/IP	Source interface or IP address
	-W SEC		Seconds to wait for the first response (default 10)
			(after all -c CNT packets are sent)
	-w SEC		Seconds until ping exits (default:infinite)
			(can exit earlier with -c CNT)
	-q		Quiet, only display output at start/finish
	-p HEXBYTE	Payload pattern

[jokob-sk]

Looks like a bug. This should be available/fixed in the next release.
It would be great if you could test the ghcr.io/netalertx/netalertx-dev-unsafe Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

👉 If I don’t receive confirmation that this works, I may revert the changes to avoid introducing bugs.

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j

[returntrip]

I backed up my settings/db and I tried ghcr.io/netalertx/netalertx-dev-unsafe:sha-f9b413d

Built on: 31/05/2026, 00:52:47 | Version: dev-20260530-225215

First I got this but maybe it is expected. have not checked the link tbh.

DataTables warning: table id=NEWDEV_devCustomProps_table - Cannot reinitialise DataTable. For more information about this error, please see http://datatables.net/tn/3

For the actual issue, still there:

ping: unrecognized option: vlan=101
BusyBox v1.37.0 (2025-11-21 22:40:56 UTC) multi-call binary.

Usage: ping [OPTIONS] HOST

Send ICMP ECHO_REQUESTs to HOST

[jokob-sk]

Thanks for testing.

The DataTables warning is probably unrelated to the ICMP issue. It's a frontend warning about a table being initialized twice and shouldn't affect scanning.

For the ICMP problem, the important part is:

ping: unrecognized option: vlan=101

That suggests --vlan=101 is still being passed to a ping/fping command somewhere. The code in this build should strip both --interface= and --vlan= from the subnet definition before it is used, so I wouldn't expect that argument to reach ping at all.

Could you please check the ICMP plugin log and post the lines containing:

[ICMP] SCAN_SUBNETS value:
[ICMP] Parsed subnets:
[ICMP] Parsed interfaces:

as well as a few lines before and after the ping error?

That will tell me whether the parsing code is actually running and what values it is producing. Based on the error, either the build isn't running the code I expect, or there's another path where SCAN_SUBNETS is being used without first removing the VLAN/interface parameters.

Thanks for testing this again - the additional logs should help narrow it down quickly. Please also make sure you are running the latest netalertx-dev-unsafe image: ghcr.io/netalertx/netalertx-dev-unsafe (not netalertx-dev as the code is not yet merged into the main branch)

[returntrip]

I went through the plugins and see that the ICMP plugin is disabled

The error seems to come from here:
06:45:33
[IPNEIGH] Pinging on interface: "enp0s31f6 --vlan=101"
ping: unrecognized option: vlan=101
BusyBox v1.37.0 (2025-11-21 22:40:56 UTC) multi-call binary.

[jokob-sk]

Thanks for the additional error message. This should be fixed now - can you pull the latest netalertx-dev-unsafe and try again?

[returntrip]

Yep, the error is not in the logs now. Thanks!

OT, can INTRNT plugin use DOT/DOH for "Internet IP discover"? In my setup I allow only secure DNS to port 853 and DNS resolution towards port 53 is disabled on the FW.

[jokob-sk]

Great, thanks for the update. Please open a separate issue or discussion for unrelated queries as it's easier to track for me and other users.