Forgotten IP

[ninedd]

I've been expiramenting with WAR's and the Mesh routing and I've mixed up the IP's of one of the WAR board. Is there any way to...

1) Discover or find the IP number?
2) Reset the WAR board to defaults, so that the IP is 192.168.1.1 again?

I've tried setting my netmast to 255.255.0.0 and pinging all the common 192.168.x.x addresses I'd have probably used... 0.1, 1.1, 1.2, 1.254, 2.1, 2.2, 2.3, 2.254, 3.1, 3.2, 3.3 etc and no reply. I've obviously set it to something other, or I made a typo and it's something stupid like 192.168.12.54

[tog]

I hope Lonnie has a better answer, but as far as I know the WAR2s have no way to reset them to factory defaults in case of a lost IP address or password so you have to be careful.

Keep in mind when you are searching for its IP address if its netmask is 255.255.255.0 and its IP is for example 192.168.12.5, you will have to be 192.168.12.x/255.255.255.0 yourself in order to communicate with it.

If you set yourself to 192.168.0.2/255.255.0.0 and tried to communicate with 192.168.12.5/255.255.255.0, it would not be able to talk back to you at 192.168.0.2 (except through a gateway) so you would not get a response.

For your search, you could set up a shell script in Linux or BSD where you can change your IP address/netmask instantly so you can write a script that changes to 192.168.1.2 and scans 192.168.1.0/24 and then changes your NIC to 192.168.2.2 and scans 192.168.2.0/24 and so on. I'd put a short sleep and an arp -da and route flush in there in between changes of IP address to be safe.

[lonnie]

You will need access to a Linux system so that you can ping the broadcast IP.

ping -b 192.168.1.0 will reply with all units in the subnet.

Also, clear your arp table and reboot the unit, then check your arp table for new announcements.

Did you have anything on the wireless? You can always set another unit up with ESSID and IP and get in through it.

If it is a 4 port simply connect a serial cable and reset to factory.

[ninedd]

OK, thanx, I got it. I was (stupidly) setting my netmast to a class B and thinking that would allow me to ping around, but like tog said, if the board is set to a /24, then it can't respond back to me off it's netmask. Duh! The board was actually on 255.255.255.252, so I had to get the laptop's NIC to the next IP to get it. :)

Masking tape and a pen from now on...

[tog]

Wow netmask 255.255.255.252, glad you had a really good exact idea of what IP it was on. You never would have found it otherwise.

[ninedd]

Wow netmask 255.255.255.252, glad you had a really good exact idea of what IP it was on. You never would have found it otherwise.Yes, these were just on the bench and wired together for testing, so I was using links like 192.168.4.1/30 and 192.168.4.2/30, so a .252 was all that I needed. However, yes, when I shuffled the boards on the bench, it did make it tricky to find out what IP was set in what board!

As I just mentioned in the Mesh thread, I'm now doing two things differently. I'm A) marking things with masking tape and a pen, and B) doing a /24 so that I can more easily ping around and find it. When I'm in production, I'll doa /30 for the PtP links, but on the bench, a /24 is fine.