Unable to access dashboard for several weeks, or connect to DStar Reflectors

General support for the Pi-Star System
W5PB
Posts: 15
Joined: Mon Sep 16, 2019 1:02 am

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by W5PB » Wed Oct 09, 2019 6:39 pm

AF6VN - I really appreciate you sticking with trying to help me. Clearly there's a learning curve for me. I'm assuming Win 10 has a way of doing ping and Trace route? I tried doing it from the command line and powershell but it didn't work.

AF6VN
Posts: 273
Joined: Fri Jul 20, 2018 1:15 am

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by AF6VN » Thu Oct 10, 2019 2:05 pm

Code: Select all

Microsoft Windows [Version 10.0.18362.388]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Wulfraed>ping pi-star-3b

Pinging pi-star-3b.attlocal.net [192.168.1.79] with 32 bytes of data:
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.79:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 2ms, Average = 2ms

C:\Users\Wulfraed>tracert pi-star-3b

Tracing route to pi-star-3b.attlocal.net [192.168.1.79]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  pi-star-3b.attlocal.net [192.168.1.79]

Trace complete.

C:\Users\Wulfraed>
I just checked the control panel for optional Windows features, but ping/tracert [note spelling] are not something that had to be added. There ARE "simple tcpip services" that are disabled by default, but who needs echo, daytime, etc. https://winintro.ru/features.en/html/3f ... 9500a6.htm

Google searches also state that tracert goes all the way back to Win95.


Hmmm, never knew about Windows pathping before reading https://en.wikipedia.org/wiki/Traceroute

Code: Select all

C:\Users\Wulfraed>pathping pi-star-3b

Tracing route to pi-star-3b.attlocal.net [192.168.1.79]
over a maximum of 30 hops:
  0  ElusiveUnicorn.attlocal.net [192.168.1.66]
  1  pi-star-3b.attlocal.net [192.168.1.79]

Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ElusiveUnicorn.attlocal.net [192.168.1.66]
                                0/ 100 =  0%   |
  1    2ms     0/ 100 =  0%     0/ 100 =  0%  pi-star-3b.attlocal.net [192.168.1.79]

Trace complete.

C:\Users\Wulfraed>
{Note: have to hit <ctrl-c> to get second half of that listing.}

--
AF6VN
Dennis L Bieber

W5PB
Posts: 15
Joined: Mon Sep 16, 2019 1:02 am

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by W5PB » Fri Oct 11, 2019 5:31 pm

So, the control panel seems to be playing nice this morning. I was able to use ping, tracert, and pathping via the windows command line.

Code: Select all

C:\Users\Asus>ping 192.168.0.3

Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time=76ms TTL=64
Reply from 192.168.0.3: bytes=32 time=5ms TTL=64
Reply from 192.168.0.3: bytes=32 time=10ms TTL=64
Reply from 192.168.0.3: bytes=32 time=13ms TTL=64

Ping statistics for 192.168.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 76ms, Average = 26ms

C:\Users\Asus>tracert 192.168.0.3

Tracing route to PI-STAR [192.168.0.3]
over a maximum of 30 hops:

  1    20 ms     9 ms     3 ms  PI-STAR [192.168.0.3]

Trace complete.

C:\Users\Asus>pathping 192.168.0.3

Tracing route to PI-STAR [192.168.0.3]
over a maximum of 30 hops:
  0  LAPTOP-M7J1P23R.tx.rr.com [192.168.0.5]
  1  PI-STAR [192.168.0.3]

Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           LAPTOP-M7J1P23R.tx.rr.com [192.168.0.5]
                                0/ 100 =  0%   |
  1   10ms     0/ 100 =  0%     0/ 100 =  0%  PI-STAR [192.168.0.3]

Trace complete.

C:\Users\Asus>
I can try again when I'm unable to connect to the dashboard and see if I get different results.

Also, possibly related - I noticed I'm having problems connecting to my printer, which is on the same network, when I can't connect to the dashboard, but I tried printing a document just now (when I AM able to connect to the dashboard) and was successful. This seems to be further proof the issue is with my network and not Pi-Star, although finding the root of the problem is still a bit elusive.

User avatar
w7efs
Posts: 308
Joined: Sun Apr 22, 2018 4:26 pm

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by w7efs » Sun Oct 13, 2019 3:24 am

AF6VN wrote:
Thu Oct 10, 2019 2:05 pm
...
Google searches also state that tracert goes all the way back to Win95.
...
That's only because Microsoft has only had a native tcp/IP stack since that excuse for an operating system. Prior to that time, people limiting their own computer usage to Microsoft used tcp/IP implementations such as Banyan Vines or AOL etc.. Unix has had traceroute since the latter mid-1980s, and I've been using it since 1989, as it's an essential network diagnostic tool. Linux since its inception has always had it.

W5PB
Posts: 15
Joined: Mon Sep 16, 2019 1:02 am

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by W5PB » Tue Oct 15, 2019 12:44 am

And again, I am unable to connect to the dashboard or via ssh, yet I am able to link to reflectors with my radio.

Here are the results of my attempts to ping, tracert, pathping and ssh:

Code: Select all

Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Asus>ping 192.168.0.3

Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.5: Destination host unreachable.
Reply from 192.168.0.5: Destination host unreachable.
Reply from 192.168.0.5: Destination host unreachable.
Reply from 192.168.0.5: Destination host unreachable.

Ping statistics for 192.168.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Asus>tracert 192.168.0.3

Tracing route to 192.168.0.3 over a maximum of 30 hops

  1  LAPTOP-M7J1P23R.tx.rr.com [192.168.0.5]  reports: Destination host unreachable.

Trace complete.

C:\Users\Asus>pathping 192.168.0.3

Tracing route to 192.168.0.3 over a maximum of 30 hops

  0  LAPTOP-M7J1P23R.tx.rr.com [192.168.0.5]
  1  LAPTOP-M7J1P23R.tx.rr.com [192.168.0.5]  reports: Destination host unreachable.

Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           LAPTOP-M7J1P23R.tx.rr.com [192.168.0.5]
                              100/ 100 =100%   |
  1  ---     100/ 100 =100%     0/ 100 =  0%  LAPTOP-M7J1P23R [0.0.0.0]

Trace complete.

C:\Users\Asus>ssh 192.168.0.3
ssh: connect to host 192.168.0.3 port 22: Connection timed out

C:\Users\Asus>


AF6VN
Posts: 273
Joined: Fri Jul 20, 2018 1:15 am

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by AF6VN » Tue Oct 15, 2019 2:51 pm

So far everything just emphasizes that you have a problem between the laptop and the router; since changing reflectors via radio means the R-Pi does have a network connection through the router.

Either the router is not doing LAN<>LAN connections for some reason or (since you are using IP # and not name) it does not have that IP # for the R-Pi at the time you attempt the connections (if a DHCP lease expired, maybe it assigned a different number rather than renewing the one it had been using).

--
AF6VN
Dennis L Bieber

W5PB
Posts: 15
Joined: Mon Sep 16, 2019 1:02 am

Re: Unable to access dashboard for several weeks, or connect to DStar Reflectors

Post by W5PB » Wed Oct 16, 2019 1:38 am

I've used the IP address as well as "pi-star" and I get the same results. I can either connect with both or I cannot.

So knowing that it is not a pi star issue the next thing is to figure out where in my router or computer the problem, but I'm stumped. The only thing I've changed in the router setup is the lease settings.

Post Reply