Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ICMP scan vs host status #934

Closed
3 of 7 tasks
kris969 opened this issue Jan 5, 2025 · 14 comments
Closed
3 of 7 tasks

ICMP scan vs host status #934

kris969 opened this issue Jan 5, 2025 · 14 comments
Labels
bug 🐛 Something isn't working next release/in dev image🚀 This is coming in the next release or was already released if the issue is Closed.

Comments

@kris969
Copy link

kris969 commented Jan 5, 2025

Is there an existing issue for this?

The issue occurs in the following browsers. Select at least 2.

  • Firefox
  • Chrome
  • Edge
  • Safari (unsupported) - PRs welcome
  • N/A - This is an issue with the backend

Current Behavior

I have an Internet box not directly placed on my LAN, cause I have a router between the two. I want to have a check on this box gateway so I create a "new device" giving a dummy MAC address and the right fix IP address. I added the ICMP scan and was expected this box gateway status to be actualized based on ICMP result.

The ICMP result if ok for this device, as visible on this screen copy:
SC 2025-01-05 10-17-31

But the device status isn't actualized, as visible on this screen copy:
SC 2025-01-05 19-54-39
The source plugin used for updates is normally set (as for the switch with ARPSCAN) but nothing is visible when only using ICMP plugin.

I'm sure it's not a NetAlertX issue, but rather a misunderstanding on my side on how to used it ;(
So thanks a lot to guide me to have the expected behavior ;)

Expected Behavior

Expecting a host status with static IP Address to be actualized based on ICMP result.

Steps To Reproduce

No response

app.conf

No response

docker-compose.yml

No response

What branch are you running?

Production

app.log

No response

Debug enabled

  • I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.
@kris969 kris969 added the bug 🐛 Something isn't working label Jan 5, 2025
@jokob-sk
Copy link
Owner

jokob-sk commented Jan 5, 2025

Hi @kris969 ,

Thanks for the report.

This should be fixed in the next release. ICMP schedule execution:

image

It would be great if you could test this. Can you please switch to the netalertx-dev docker image (backup everything at first or, ideally spin up a separate container with a separate db and config), in about 15 minutes (or after the last action finishes) from now?

Thanks in advance,
j

@jokob-sk jokob-sk added the next release/in dev image🚀 This is coming in the next release or was already released if the issue is Closed. label Jan 5, 2025
@kris969
Copy link
Author

kris969 commented Jan 6, 2025

hi jokob-sk,

After testing on my side, I confirm ICMP result is considered and reported to status as well on the NetAlertX node instance, that's great:
Capture d’écran du 2025-01-06 13-53-14

The status is also reported to the NetAlertX hub instance:
image

As visible on screenshots, there are remaining issues:

  • Source Plugin is not set on first line, it should be ICMP in this case, if I understand.
  • Sync Node is not set on the first line, it should be the same value than for the other lines.

Approximately, do you know when you plan to publish next release?

Thanks
Having a good day ;)

@jokob-sk
Copy link
Owner

jokob-sk commented Jan 6, 2025 via email

@kris969
Copy link
Author

kris969 commented Jan 7, 2025

hi jokob-sk,

In this case, automatically discovering isn't possible because this device freebox and the NetAlertX node instance aren't in the same subnet.

As a workaround, I have manually created the freebox device given a dummy ARP and the good IP. My expectation was to have status updated by ICMP plugin and it works :
Capture d’écran du 2025-01-07 08-42-45

Afterward, because it is not automatically done, it was possible to manually edit the Sync Node using multi-edit :
Capture d’écran du 2025-01-07 09-05-04

but NetAlertX node is not available for editing! maybe it's impossible for you to give access to it for real reason?

At the NetAlertX hub level, I first clear all the devices, then wait for SYNC update. I got all devices back, but concerning specific freebox device the Sync Node field value was not reported.
image

have you an explanation and/or a workaround on this?

Thanks ;)

@jokob-sk
Copy link
Owner

jokob-sk commented Jan 7, 2025

Hi @kris969 - I think that's resolved by this latest commit: 0cc87e3

You can test this in the dev image

@kris969
Copy link
Author

kris969 commented Jan 7, 2025

hi jokob-sk,

First of all, is there a usable environment variable to place in docker_compose to have db reset at startup, this for testing purpose only?
I have seen this information somewhere in the documentation, but I can't locate it again.
Thanks to guide me on this ;)

@kris969
Copy link
Author

kris969 commented Jan 7, 2025

hi jokob-sk,

After testing on Version: 13:52:47 - Dev, I can confirm you, the Sync Node value is now reported with SYNC plugin at NetAlertX hub level:
SC 2025-01-07 13-48-37

Is it normal the Source Plugin field is still empty at node level?

Thanks ;)

@jokob-sk
Copy link
Owner

jokob-sk commented Jan 7, 2025

Hi @kris969 ,

For available env variables, please check this doc: https://github.com/jokob-sk/NetAlertX/tree/main/dockerfiles#docker-environment-variables

The Source plugin population needs to be implemented by the plugin. Which plugin is it that is supplying this device? I can double check if it's implemented on the plugin itself.

Thanks,
j

@jokob-sk
Copy link
Owner

jokob-sk commented Jan 8, 2025

Closing -> Releasing

@jokob-sk jokob-sk closed this as completed Jan 8, 2025
@kris969
Copy link
Author

kris969 commented Jan 8, 2025

hi jokob-sk,

Concerning your remaining question: Which plugin is it that is supplying this device?

This device was supplying by myself, using the image function.
For sure in that case it can't be populated by plugin, but maybe the "New Device" code could populate the Source Plugin field with a value to have a stored info on how the device was coming from.

Have a good day ;)

@jokob-sk
Copy link
Owner

jokob-sk commented Jan 8, 2025 via email

@kris969
Copy link
Author

kris969 commented Jan 8, 2025

Why not, or something like "Manual" or "Users setting"...

@jokob-sk
Copy link
Owner

jokob-sk commented Jan 8, 2025

Hi,

DUMMY will be inserted in the next version forward when creating a device this way:
image

@kris969
Copy link
Author

kris969 commented Jan 8, 2025

hi jokob-sk,

Great!

Thanks ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working next release/in dev image🚀 This is coming in the next release or was already released if the issue is Closed.
Projects
None yet
Development

No branches or pull requests

2 participants