You are here

Home » Forums » General discussion

Finding an owner of a node

6 posts / 0 new
Log in or register to post comments
Last post
Fri, 08/01/2025 - 10:03
#1
WK7G
WK7G's picture
Finding an owner of a node
Is there a way to track back node IP numbers to an owner. I have tried to find the owner of a remote setup with no luck. I believe it belongs to the Search and rescue team but not sure. There is a CPE-710, a router(10.42.41.7), and a camera(10.42.41.6).
Top
Fri, 08/01/2025 - 11:08
K6CCC
K6CCC's picture
Callsign?
Hopefully the node name has a callsign.  That would be a good start.
 
Top
Fri, 08/01/2025 - 11:16
(Reply to #2)
WK7G
WK7G's picture
No Callsign
It's in a forest service owned building. They host Amateur Radio equipment as well as Local Search and Rescue equipment. The Search and Rescue commander is also the local club contact and the ARES coordinator (David Dean-AE7ID). He doesn't answer any messages. I dont think it's active or working. The CPE-710 is missing half of the reflector. I don't want to step on any toes here, but I would like to put some equipment up.
Top
Sat, 08/02/2025 - 09:23
nc8q
nc8q's picture
Finding an owner of a node
"Is there a way to track back node IP numbers to an owner."
Implied: Is there a way to track back node IP numbers to an owner?

Yes, here is a way:
traceroute to 10.194.133.131 (10.194.133.131), 30 hops max, 46 byte packets
 1  mid12.KI5VMF-OKLAHOMA-SUPERNODE (172.30.38.189)  47.502 ms
 2  mid4.KE5YZP-NTX-SUPERNODE (172.30.190.33)  57.819 ms
 3  mid3.KN6PLV-BAM-SUPERNODE (172.30.2.206)  105.328 ms
 4  mid4.K7SWI-BOI-SUPERNODE (172.30.2.183)  143.484 ms
 5  dtdlink.KI0E-HAP-4.local.mesh (10.156.206.18)  149.342 ms
 6  WK7G-MT-hAPAC2-QTH.local.mesh (10.194.133.131)  157.883 ms

Alas:
root@NC8Q-OHIO:~# traceroute -q 1 10.42.41.7
traceroute: can't connect to remote host (10.42.41.7): Invalid argument
root@NC8Q-OHIO:~# traceroute -q 1 10.42.41.6
traceroute: can't connect to remote host (10.42.41.6): Invalid argument
root@NC8Q-OHIO:~# 

73, Chuck
 
Top
Sun, 08/03/2025 - 12:15
WK7G
WK7G's picture
Chuck
I did a traceroute for both nodes but it ended with no results. I would guess they are not active.
Thanks
Top
Sun, 08/03/2025 - 17:36
(Reply to #5)
nc8q
nc8q's picture
I would guess they are not active.
I would guess your workstation does not have a link path to the device.
Did you run the traceroute from an AREDN device displaying a link to the NOCALL device?

73, Chuck
 
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer