Devices with the same IP

[lncommunications]

The addition of scan subnet facility is great! ...but I have a slight problem, all our networks use the same subnet internally 192.168.3.0/24.

When I VPN into a network remotely and scan the subnet it discovers all the devices and they are all manageable which is fantastic!

When I connect to another seperate remote network, the devices that were discovered and saved previously are then replace by the current network due to devices having the same IP addresses.

Is there currently a way of saving seperate network details on the same subnet per network? if not can there be?

Thanks greatly.

[UBNT-Thomas]

Currently devices need to have a unique IP to be managed. That is already recognized as a problem for NAT setups and will be addressed in short order. I'm working on it right now, folks that volunteer to test a patch please let me know.

If you use scan and then switch between subnets via VPN, the originally found batch of devices cannot be connected anyways. What are you planning to use AirControl for? If you want to monitor the units, you need to assign permanent addresses/ports instead of rotating the VPN connection.

In your case, after you did the VPN trick to locate the devices connect them and at that time override IP address and SSH port with permanent settings (expand details through check box in connect dialog).

Once the issue mentioned above is fixed, you will also be able to just list the devices with duplicate IP (the MAC address found during scan is the real identifier).

[lncommunications]

That sounds great Thomas, ill try the patch if you want to send it over (mboswell at lncomms.co.uk)

At the moment we dont permenantly monitor the systems via AirControl 24/7 we only use it when we need to. I suppose things will change in the future with enhancements on our networks but for now logging in via VPN is the quickest and easiest solution for us, which definately works but as I say when I log onto another network it overwrites the the previous.

MAC address identifier sounds good!