I recently removed my repeater from a remote site, and updated the firmware on the Due 1.0 to the latest MMDVM FW. I also replaced the Raspberry Pi with a new 3B+ and a fresh SD Card. I am running the latest Pi-Star Beta version on it.
I access the Pi by going through a second Raspberry Pi at the location. Just using Chrome on the remote Pi. Usually this is not an issue using the local IP address on the repeater. I have the repeater connected using a Cat5 cable directly to a Microtik router in the shack. Has always worked well for the last two years. However, upon me redeploying the repeater, I can no longer access the dashboard, because I cannot find the IP address of the repeater. I know I should have did this before leaving the site, but everything appeared to work. The repeater does appear to be connected to the internet because my Brandmeister dashboard is showing a green icon, and I can hear traffic on BM on the repeater. I am using dmap on the remote Pi and it is not finding the IP address of the repeater (Pi Star.) I have done this before, and works great. But now it does not. Does anyone have any suggestions? Does this mabye have to do with the version of Pi Star or the new Pi? I am trying to do this remotely so I do not have to bother anyone to go back out to the site again.
Forgot to mention, everything worked as expected on my home network. I could see and access the Pi with no problem. It does not appear that anything has changed on the remote site network either.
Thanks, Oren K5LPD
Cannot see Pi (IP) on network, has connection to BM
Re: Cannot see Pi (IP) on network, has connection to BM
Your router -- if fairly modem -- should present the Pi-Star node as a local /name/. Try some variation of pi-star or pi-star.local (Windows doesn't use the .local it seems), if those don't work, maybe pistar or pistar.local (you didn't change the host name at some time, did you? Mine is actually pi-star-3b as I planned to add a second unit and didn't want conflicts during initial set-up).
If that doesn't work, your router should have some admin pages -- one of them should show you what clients are connected and what the IP of said client is. From my Uverse router:
(The "Action" column is to allow for fixing the IP permanently, rather than relying upon DHCP random issue)
If that doesn't work, your router should have some admin pages -- one of them should show you what clients are connected and what the IP of said client is. From my Uverse router:
Code: Select all
IP Allocation
IPv4 Address / Name MAC Address Status Allocation Action
192.168.1.68 / EPSONF4EF32 00:26:ab:f4:ef:32 on DHCP Allocation
192.168.1.65 / DIRECTV-HR54-C94828D7 18:16:c9:48:28:d9 on DHCP Allocation
192.168.1.83 / unknown28c68efb9d7b 28:c6:8e:fb:9d:7b off DHCP Allocation
192.168.1.70 / Galaxy-S9 8c:45:00:6d:1a:4c on DHCP Allocation
192.168.1.79 / pi-star-3b b8:27:eb:4b:0b:d5 on DHCP Allocation
192.168.1.252 / microdiversity b8:27:eb:ce:b1:eb on DHCP Allocation
192.168.1.66 / ElusiveUnicorn b8:ca:3a:79:0c:36 on DHCP Allocation
192.168.1.84 / HP7C548D c4:65:16:7c:54:8d on DHCP Allocation --
AF6VN
Dennis L Bieber