Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: discover_waps: false is not ignoring access points
(Oliver Gorwits)
2. Re: discover_waps: false is not ignoring access points
(Koen Dooms)
--- Begin Message ---
Hi Koen
Just to understand ... the access points are already discovered and known
to Netdisco as devices but you don't want arpnip or macsuck on them? Or you
don't want daily re-discovery on them?
The discover_waps setting applies to the initial discovery only. It is used
when the access point is seen as a neighbor over LLDP/CDP and then Netdisco
knows whether to queue a discover job for the new IP, or not.
So, if you are talking about macsuck and arpnip then I guess they are
already discovered? You can delete them, and then discover_waps would work,
or else you need to use devices_no setting and add the IPs or another type
of field like the vendor or model in an access control list (devices_no
applies to discover and macsuck and arpnip).
(Depending on your answer, maybe we need an additional field like is_wap or
is_phone on the device itself, rather than only the remote LLDP data.)
regards
Oliver
On Mon, 21 Aug 2023 at 11:56, Koen Dooms <drhn...@gmail.com> wrote:
> Not sure why, but setting discover_waps: false doesn't seem to prevent
> Arpnip or Macsuck on acces points. Although processed in an instance
> according to the job queue, I guess they should not be going thru the queue.
>
> Any hints on troubleshooting?
>
> --
> mvg,
> Koen
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Oliver,
Thanks again.
Totally makes sence.
The APs were indeed already discovered before I changed the discover_waps
to false.
Will delete the APs and see what happens.
Regards,
Koen
On Mon, 21 Aug 2023, 17:41 Oliver Gorwits, <oli...@cpan.org> wrote:
> Hi Koen
>
> Just to understand ... the access points are already discovered and known
> to Netdisco as devices but you don't want arpnip or macsuck on them? Or you
> don't want daily re-discovery on them?
>
> The discover_waps setting applies to the initial discovery only. It is
> used when the access point is seen as a neighbor over LLDP/CDP and then
> Netdisco knows whether to queue a discover job for the new IP, or not.
>
> So, if you are talking about macsuck and arpnip then I guess they are
> already discovered? You can delete them, and then discover_waps would work,
> or else you need to use devices_no setting and add the IPs or another type
> of field like the vendor or model in an access control list (devices_no
> applies to discover and macsuck and arpnip).
>
> (Depending on your answer, maybe we need an additional field like is_wap
> or is_phone on the device itself, rather than only the remote LLDP data.)
>
> regards
> Oliver
>
> On Mon, 21 Aug 2023 at 11:56, Koen Dooms <drhn...@gmail.com> wrote:
>
>> Not sure why, but setting discover_waps: false doesn't seem to prevent
>> Arpnip or Macsuck on acces points. Although processed in an instance
>> according to the job queue, I guess they should not be going thru the queue.
>>
>> Any hints on troubleshooting?
>>
>> --
>> mvg,
>> Koen
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
>
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
