Pi-Star Destination Unreachable.

General support for the Pi-Star System
Post Reply
w1get
Posts: 6
Joined: Tue Sep 07, 2021 1:50 am

Pi-Star Destination Unreachable.

Post by w1get »

Trying to connect pi-star to a XLX reflector on the same network for Dstar and DMR.

however when I try to connect, the PI-star is blocking the reflector.

10.100.1.7 is my xlx reflector
10.100.1.80 is the pi-star.

Code: Select all

sudo tshark -f "icmp or port 30051"
1 0.000000000   10.100.1.7 → 10.100.1.80  ICMP 81 Destination unreachable (Port unreachable)
2 0.000014979   10.100.1.7 → 10.100.1.80  ICMP 81 Destination unreachable (Port unreachable)
3 8.226725044   10.100.1.7 → 10.100.1.80  ICMP 81 Destination unreachable (Port unreachable)
4 8.226741179   10.100.1.7 → 10.100.1.80  ICMP 81 Destination unreachable (Port unreachable)
w1get
Posts: 6
Joined: Tue Sep 07, 2021 1:50 am

Re: Pi-Star Destination Unreachable.

Post by w1get »

Anyone know why I cannot connect my pi-star to my xlx reflector on the same network? Has anyone else done this before??
AF6VN
Posts: 821
Joined: Fri Jul 20, 2018 1:15 am

Re: Pi-Star Destination Unreachable.

Post by AF6VN »

First thing I'd look at is firewalls on either side, or in the router (you don't state if you are using WiFi on both sides, or cabled to router)

Many WiFi routers are often configured to only pass traffic from LAN to WAN and back, and block LAN<>LAN traffic -- a configuration useful for public WiFi access points as it gives some sense of privacy between random users. Mine, OTOH, has separate "HOME" and "GUEST" SSIDs (with associated passwords), where Guest can be configure for "Internet Only" or "Internet and LAN".

After checking the router, I'd check the firewalls on each computer. It is possible to have firewalls configured to pass Internet, but for some reason block LAN traffic.

What does traceroute/tracert show?

As an example -- my small (cabled) web-server (presuming the dynamic DNS works and ATT doesn't block it from outside) box can ping my (WiFi) Pi-Star box. BUT the Pi-Star can't ping back...

microdiversity (server) on cable to router

Code: Select all

md_admin@microdiversity:~$ ping pi-star-3b
PING pi-star-3b.attlocal.net (192.168.1.79) 56(84) bytes of data.
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=1 ttl=64 time=6.24 ms
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=2 ttl=64 time=6.12 ms
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=3 ttl=64 time=5.55 ms
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=4 ttl=64 time=5.66 ms
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=5 ttl=64 time=5.49 ms
^C
--- pi-star-3b.attlocal.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 10ms
rtt min/avg/max/mdev = 5.492/5.814/6.241/0.307 ms
md_admin@microdiversity:~$
md_admin@microdiversity:~$ traceroute pi-star-3b
traceroute to pi-star-3b (192.168.1.79), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
<SNIP REST>
Pi-Star node on WiFi

Code: Select all

pi-star@pi-star-3b(ro):~$ ping microdiversity
PING microdiversity.attlocal.net (192.168.1.252) 56(84) bytes of data.
^C
--- microdiversity.attlocal.net ping statistics ---
27 packets transmitted, 0 received, 100% packet loss, time 85ms

pi-star@pi-star-3b(ro):~$
pi-star@pi-star-3b(ro):~$ traceroute microdiversity
traceroute to microdiversity (192.168.1.252), 30 hops max, 60 byte packets
send: Operation not permitted
pi-star@pi-star-3b(ro):~$ sudo traceroute microdiversity
traceroute to microdiversity (192.168.1.252), 30 hops max, 60 byte packets
send: Operation not permitted

--
AF6VN
Dennis L Bieber
NQ4T
Posts: 51
Joined: Mon Aug 06, 2018 11:48 pm

Re: Pi-Star Destination Unreachable.

Post by NQ4T »

w1get wrote: Sat Sep 18, 2021 11:22 pm
however when I try to connect, the PI-star is blocking the reflector.
Pi-Star isn't "blocking" the connection. As stated, it shouldn't care what it's outbound is going to, as long as it can reach it. For whatever reasons...those two network devices are unable to talk. Maybe they're not actually on the same network despite being on the same subnet; you may have something funky with your network wiring where there's a "disconnect" between two segments of your network.

If they're physically plugged up to the same switch...or you know there's no other routers/gateway/network equipment that could be "breaking" the connection between networks; I'd start checking firewall settings.

That said...I did do this during some initial testing of xlxd back when I ran a reflector; Pi-Star had no problems connecting to it.
AF6VN wrote: Tue Sep 21, 2021 3:36 pm BUT the Pi-Star can't ping back...
traceroute != ping. All my stuff can ping each other, even across a network gateway to the storage network. (Synology lives on 10.1.1.0/24 @ 10.1.1.2 on an entirely separate LAN. 192.168.1.253 is also 10.1.1.1 and acts as a gateway between the two). But I'm pretty sure whatever the ICMP message type used for tracert is blocked in Pi-Star's firewall, where as ICMP PING is not.

Code: Select all

dewdude@synology:~$ sudo ping -c 5 192.168.1.10
Password:
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=62 time=1.69 ms
64 bytes from 192.168.1.10: icmp_seq=2 ttl=62 time=1.23 ms
64 bytes from 192.168.1.10: icmp_seq=3 ttl=62 time=1.74 ms
64 bytes from 192.168.1.10: icmp_seq=4 ttl=62 time=1.25 ms
64 bytes from 192.168.1.10: icmp_seq=5 ttl=62 time=1.28 ms

--- 192.168.1.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.230/1.441/1.740/0.229 ms

dewdude@synology:~$ sudo traceroute 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 60 byte packets
 1  10.1.1.1 (10.1.1.1)  0.374 ms  0.328 ms  0.295 ms
 2  * * *
 3  * * *
 4  * * *
 5  * ^C

dewdude@synology:~$ sudo traceroute 192.168.1.1
traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets
 1  10.1.1.1 (10.1.1.1)  0.399 ms  0.345 ms  0.316 ms
 2  192.168.1.1 (192.168.1.1)  0.818 ms *  0.932 ms

dewdude@synology:~$ sudo traceroute 192.168.1.253
traceroute to 192.168.1.253 (192.168.1.253), 30 hops max, 60 byte packets
 1  192.168.1.253 (192.168.1.253)  0.415 ms  0.368 ms  0.340 ms

dewdude@synology:~$ sudo traceroute 192.168.1.254
traceroute to 192.168.1.254 (192.168.1.254), 30 hops max, 60 byte packets
 1  10.1.1.1 (10.1.1.1)  0.347 ms  0.289 ms  0.258 ms
 2  192.168.1.254 (192.168.1.254)  1.894 ms  2.016 ms  1.997 ms
Post Reply