You are here

tools to find nodes

4 posts / 0 new
Last post
AE4ML
AE4ML's picture
tools to find nodes
Good afternoon to all.
I have recently had a problem at a site. This site has three nodes up on the tower about 250ft. all on different frequencies. connected to thier end point nodes. These are backhaul nodes used to interconnect multiple counties. I have one node that gives me a link on the switch but I can't access it.

I started running Nmap against the node 10.0.0.0/8  but after 4 hours I just gave up.

Is there a script out there that will send out a crafted packet and give back an ip address or some other piece of data to identify it? something that can help me identify this node so I can fix it. I have tried a reboot without success. Since this site has multiple nodes all DHCP is off except for one node. Pulling this one node and plugging into my laptop does me no good as I will never get an IP address. 

The only other option here is to climb the tower and that i'm not able to do right now.


Thank you

Mike AE4ML
KG6JEI
Not sure I fully understand
Not sure I fully understand the situation here but for part of it regarding the nodes with DHCP disabled, if you use a power injector at the ground with the reset button (Some injector models have this reset button) after the node fully boots hold for 5 seconds and the DHCP is re-enabled and the password is reset to "hsmm" 

a 15 second hold resets it to "just flashed" state.

All this can be done from the ground.
K5DLQ
K5DLQ's picture
do you have all three node
do you have all three node plugged into a switch to DtDLink them?
If so, you don't need to disable DHCP on them.

1) you could set a static IP on your PC 10.x.x.x.x and connect with a CAT5 cable to see if you can talk to it.
2) if you hold the reset button on the bottom of your PoE adapter for 5 secs, it will re-enable DHCP, reset the password to hsmm, and restart the web server.

 
KA9Q
I'm not sure I understand the

I'm not sure I understand the problem either, but if you're on an Ethernet to which all the nodes are connected, then you only have to dump the olsr routing broadcasts with a tool like tcpdump or wireshark to discover the IP addresses of all the Ubiquiti nodes. I've appended an example, done on Linux.

They'll be on VLAN2 but Linux easily handles vlans; in fact, tcpdump/wireshark seem to just show everything it sees, even if the traffic is tagged.

I think OSX also handles VLANs, but in a slightly different way. I haven't used Windows in well over a decade so I can't speak to it.

karn@maggie:~$ sudo tcpdump -n -i eth0.2 host 10.255.255.255
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0.2, link-type EN10MB (Ethernet), capture size 262144 bytes
14:51:22.659840 IP 10.19.73.183.698 > 10.255.255.255.698: OLSRv4, seq 0x3c49, length 152
14:51:23.330832 IP 10.44.77.5.698 > 10.255.255.255.698: OLSRv4, seq 0xb208, length 356
14:51:23.541860 IP 10.19.73.134.698 > 10.255.255.255.698: OLSRv4, seq 0x1ead, length 1372
14:51:24.562675 IP 10.19.73.183.698 > 10.255.255.255.698: OLSRv4, seq 0x3c4a, length 524
14:51:24.794565 IP 10.19.73.134.698 > 10.255.255.255.698: OLSRv4, seq 0x1eae, length 1392
14:51:25.138467 IP 10.44.77.5.698 > 10.255.255.255.698: OLSRv4, seq 0xb209, length 140
14:51:25.513384 IP 10.19.73.183.698 > 10.255.255.255.698: OLSRv4, seq 0x3c4b, length 1472
14:51:25.546412 IP 10.19.73.134.698 > 10.255.255.255.698: OLSRv4, seq 0x1eaf, length 716
14:51:26.413595 IP 10.19.73.183.698 > 10.255.255.255.698: OLSRv4, seq 0x3c4c, length 404
14:51:26.597715 IP 10.19.73.134.698 > 10.255.255.255.698: OLSRv4, seq 0x1eb0, length 1452
14:51:26.692486 IP 10.44.77.5.698 > 10.255.255.255.698: OLSRv4, seq 0xb20a, length 104
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer