14 Nov
2021
14 Nov
'21
3:35 p.m.
On Fri, Nov 12, 2021 at 08:25:17PM -0500, Supratim Sanyal wrote:
On 11/12/21 8:22 PM, Paul Koning wrote:
This may be fixed in a later/current version of nml2.
You can see the answer here:
http://akdesign.dyndns.org:8080/map/data??.
??They show as type "unknown" because Linux (at least with the NML
version you're using) does not send a valid reply to the "show executor
characteristics" request -- the node type is missing.
Got it. Neat. Something needs to be done about it. Thanks Paul.
paul
-- On Nov 12, 2021, at 5:52 PM, Supratim Sanyal
<supratim at riseup.net> wrote:
Just out of curiosity - what are FEDACH and FOMFOR telling your scanner?
> On Nov 12, 2021, at 2:46 PM, Paul Koning <paulkoning at comcast.net> wrote:
>
> ???My network scanner is getting very strange responses from
> three different nodes all misbehaving the same way: CAIR,
> MAGPIE, and FARGO.
>
> What I see is:
>
> 1. The connection to object 19 (NICE, the network management
> listener) is accepted, but the version number that is supposed
> to be sent as part of the accept is missing.
>
> 2. When I send a NICE request to the node, I get back a message
> with this content:
>
> <28>Nov 12 20:35:16 dnetd[1688]: Cannot chdir to /nonexistent :
> No such file or directory\n\xff\x00\x00
>
> All three nodes do this. ??Configuration error that just happens
> to exist on all three?
>
> ????paul
>