Device with two IPs

[maghuro]

I wonder what happens if you kill networkmap --bootwait

Nothing

adminRT-AC86U/tmp/home/root kill networkmap --bootwait kill: invalid number 'networkmap' kill: invalid number '--bootwait'

 

[maghuro]

Mmm. I think a lot of these NAS systems goose their appeal with the ability to run other apps in jails, in VMs, and so on. Running plex server in a FreeNAS jail I can't pick an adapter, but I can configure a vnet with a full network stack that pulls its own IP address. So this single adapter for the box actually has 3 (at one time four) IP addresses that all appear separate in the router's GUI.

I bind the adaptor manually, but as I only have one, it's the same to be on auto.

The problem is, like I said, I haven't had this problem before factory reset the router...
That's the strange thing that's going me nuts

 

[ColinTaylor]

Nothing

adminRT-AC86U/tmp/home/root kill networkmap --bootwait kill: invalid number 'networkmap' kill: invalid number '--bootwait'

I think the actual command would be something like this:

killall networkmap

 

[maghuro]

I think the actual command would be something like this:

killall networkmap

Wow that solved it right away, the phantom IP disappeared!!
Do I have to Kill Everytime I reboot the router?

Thanks

 

[Jack Yaz]

Wow that solved it right away, the phantom IP disappeared!!
Do I have to Kill Everytime I reboot the router?

Thanks

Does networkmap come back? This has given me an idea re. YazFi...

ps | grep networkmap

 

[ColinTaylor]

Does networkmap come back? This has given me an idea re. YazFi...

ps | grep networkmap

That's what I was wondering. It looks like the watchdog should restart it. In which case it could be killed once at startup in services-start.

 

[Jack Yaz]

That's what I was wondering. It looks like the watchdog should restart it. In which case it could be killed once at startup in services-start.

and in YazFi's case, whenever it applies the settings. Maybe this will finally end the "why do i see the 'wrong' IP in the WebUI" saga!

EDIT: I've done a quick test, it did come back but without --bootwait . Not sure if that's significant...

EDIT2: Grumble, older entries still stick around in ARP even if I kill network map and flush the ip neigh tables

 

[maghuro]

and in YazFi's case, whenever it applies the settings. Maybe this will finally end the "why do i see the 'wrong' IP in the WebUI" saga!

EDIT: I've done a quick test, it did come back but without --bootwait . Not sure if that's significant...

EDIT2: Grumble, older entries still stick around in ARP even if I kill network map and flush the ip neigh tables

My old entries disappeared...
Edit: well, regarding that qnap phantom IP, it disappeared. Don't know about everything else.
Which ideia did you have?

adminRT-AC86U/tmp/home/root ps | grep networkmap                       5696 admin     5432 S    grep networkmap                                 24978 admin     8360 S    networkmap

 

[Jack Yaz]

My old entries disappeared...
Edit: well, regarding that qnap phantom IP, it disappeared. Don't know about everything else.
Which ideia did you have?

adminRT-AC86U/tmp/home/root ps | grep networkmap                       5696 admin     5432 S    grep networkmap                                 24978 admin     8360 S    networkmap

https://github.com/jackyaz/YazFi/pull/66

 

[ColinTaylor]

https://github.com/jackyaz/YazFi/pull/66

Just wondering whether a "service restart_networkmap" might be more proper rather than relying on watchdog to restart it. On the other hand maybe there needs to be a suitable delay before it's restarted to give enough time to clear out any entries. If it's the later then it might be hit or miss as to whether it's effective or not depending on the variable time it takes for watchdog to kick in.

 

[Jack Yaz]

Just wondering whether a "service restart_networkmap" might be more proper rather than relying on watchdog to restart it. On the other hand maybe there needs to be a suitable delay before it's restarted to give enough time to clear out any entries. If it's the later then it might be hit or miss as to whether it's effective or not depending on the variable time it takes for watchdog to kick in.

i didn't realise it was one of the services. i wonder if a stop command, sleep 5-10 and start would be sufficient?

EDIT: hm, despite being a service, issuing service stop_networkmap doesn't seem to kill the process on my 86U

 

[ColinTaylor]

EDIT: hm, despite being a service, issuing service stop_networkmap doesn't seem to kill the process on my 86U

Looks like that service is only present if complied with RTCONFIG_DISABLE_NETWORKMAP. So unless the following returns a hit I guess it isn't present.

nvram show | grep networkmap_enable

 

[Jack Yaz]

Looks like that service is only present if complied with RTCONFIG_DISABLE_NETWORKMAP. So unless the following returns a hit I guess it isn't present.

nvram show | grep networkmap_enable

I have no nvram matching that. killall it is?

 

[RMerlin]

EDIT: I've done a quick test, it did come back but without --bootwait . Not sure if that's significant...

Bootwait is something I implemented and was picked up by Asus at some point. There was an issue where networkmap may start scanning too soon at boot time, causing it to fail. Bootwait is only used when network is started at boot time, telling it to wait a certain amount of time before starting its scan.

 

[Jack Yaz]

Bootwait is something I implemented and was picked up by Asus at some point. There was an issue where networkmap may start scanning too soon at boot time, causing it to fail. Bootwait is only used when network is started at boot time, telling it to wait a certain amount of time before starting its scan.

OK that makes sense!