Cant connect to my XLX941 reflector

[n2ajo]

Apologize if this has been asked before. I have done some searching on this forum but can't find anything. I installed a XLX reflector following n5amd scripts. The reflector shown a green thumb up that I take to mean it is working. When I attempt to connect to XLX941 using my Pi-Star applications, the status on the dashboard shows not linked. Yet I can connect to XLX940 (not my reflector) and Pi-star connects. So, I must be missing something along the way. I have tried DCS, XRF and REF 941 with no luck.

73
Art N2AJO

[n2ajo]

I have all of the listed ports forwarded from my router to my server including 4004. My host table shows my public IP and 4004. I then input 4004 udp and tcp input/output on my rpi server. I did a netstat -lptn and 4004 doesn't appear. I then did a iptables -L and 4004 appears on both input and output. Still I can't connect to XLX941 using Pi-Star although the reflector shows it is up. Should I add all these other ports to the iptables on the rpi server?

Ports Forwarded in router
UDP 1000-10002
UDP 30001
UPD 30051
UDP 10100-10199
UDP 42000
UDP 20001
UDP 62030
TCP 80/443
TCP/UDP 4004

[n2ajo]

Hello

Yes the xlxhost file is shown as you stated

are you trying to add the XLX server to a RPi that is already running Pi-Star? Or are you running 2 seperate RPi's?? One with Pi-Star and one with the Raspberry Pi OS.

2 separate PIs. 1- with Pi-star image installed running PI-Star ; 2- RPI image with XLX reflector installed.

I have engaged the developer and he was of little help. Now probably for a dumb question. Can you run Pi-star as a reflector? If so, could you point me to where I can get up to speed.
Apologize for taking up so much of your time.

73
art N2AJO

[AF6VN]

4004 isn't a port number.

Technically, it IS -- commonly assigned to something called "pxc-roid" (for which I can not find information, other than a few port numbers to either side also have "pxc-..." assignments). Port numbers run from 0 to 65535.

Granted, it is likely not a Pi-Star related port number

[M1DNS]

In this instance 4004 is referencing the D module.

Server IP address: module D.

XLX DSTAR modules A through Z
Are referenced for connection in DMR mode as (tg) 4001 through 4026.

4004 = Module D



Sent via smoke signals from my SM-G935F M1DNS (Admin)

[W3KIT]

I have all of the listed ports forwarded from my router to my server including 4004. My host table shows my public IP and 4004. I then input 4004 udp and tcp input/output on my rpi server. I did a netstat -lptn and 4004 doesn't appear. I then did a iptables -L and 4004 appears on both input and output. Still I can't connect to XLX941 using Pi-Star although the reflector shows it is up. Should I add all these other ports to the iptables on the rpi server?

Ports Forwarded in router
UDP 1000-10002
UDP 30001
UPD 30051
UDP 10100-10199
UDP 42000
UDP 20001
UDP 62030
TCP 80/443
TCP/UDP 4004

I would check your log and see if you have an error opening those ports. Often your xlxd service will come on faster than network service.

Make xlxd service sleep for 30 or so sec before it starts after boot, let the network service finish their things first.

I can't connect to xlx941 using DMR and using your IP address to 4004 (module D) either because your xlx server port 62030 could not be reached from the outside world.

Good luck, Kit

[W3KIT]

Often your xlxd service will come on faster than network service.

Make xlxd service sleep for 30 or so sec before it starts after boot, let the network service finish their things first.

The associated service that requires a network should have After=network.target declared.

Agreed,

Although even require or after I often got an error opening socket on port UDP##### on fresh boot for some reason.

Until I added 45 sec sleep in xlxd.sh I never saw the issue again.

The bottom line is log files needs to be checked and see if there is any clue.

So this is not really a pi-star issue . But I hope he get that fixed somehow.

Good luck, Kit