I have been running two pi-star repeaters here for a while now and they are generally satisfactory except for DCS which has never worked right on either machine. This goes for XLX too, where the connection made is a DCS connection. It seems to connect but then I get the connected message every two minutes or so with a corresponding log entry like this
M: 2020-06-07 22:21:46: DCS link to DCS006 F has failed (poll inactivity)
M: 2020-06-07 22:21:46: DCS link to DCS006 F has failed, relinking
M: 2020-06-07 22:21:46: Unknown incoming DCS poll from DCS006 F
M: 2020-06-07 22:21:46: DCS ACK message received from DCS006 F
M: 2020-06-07 22:21:46: DCS link to DCS006 F established
I have dcsEnabled=1 in the gateway, is there something else needed?
Ken
KE2N
the DCS poll
Re: the DCS poll
Prob. Similar issue to one mentioned here a while back between original DCS reflectors and the newer XLX. When XLX came about there was an agreement that none would use original DCS reflector no's.
To prevent conflicts of connection.
If there's an original dcs006 running the various sources in ircddbgateway will be pulling that address and not the newer XLX. If dcs006 is now using XLX it's original entry should of been requested to be removed from xreflector by it's owner.
If there are two running, original DCS and a newer XLX then the original will be the priority.
You can force the install into using whatever connection you want by entering the DCS reflector no and its ip add. into the DCShosts.txt file found in root.
If it is an old vs New situation as seen several times before it needs to be resolved by/ between the owner(s)
Sent from my SM-G935F using Tapatalk
To prevent conflicts of connection.
If there's an original dcs006 running the various sources in ircddbgateway will be pulling that address and not the newer XLX. If dcs006 is now using XLX it's original entry should of been requested to be removed from xreflector by it's owner.
If there are two running, original DCS and a newer XLX then the original will be the priority.
You can force the install into using whatever connection you want by entering the DCS reflector no and its ip add. into the DCShosts.txt file found in root.
If it is an old vs New situation as seen several times before it needs to be resolved by/ between the owner(s)
Sent from my SM-G935F using Tapatalk
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: the DCS poll
Wow - there must be a lot of these, if that is the cause, I am surprised I am the only one posting about it.
DCS006 and XLX006 have different addresses. When i ask for XLX I get DCS instead and that is a different IP. And I get those poll errors.
Let's pick a different reflector.
If I select XLX287 (66.42.109.165) then pi-star actually makes a DCS connection (also on address 44.42.109.165). So here they have the same IP. Now I get a different error. Nothing about polling It keeps announcing the XLX connection.
M: 2020-06-08 15:38:26.977 D-Star link status set to "Linking to XLX287 A "
M: 2020-06-08 15:38:27.059 D-Star link status set to "Linked to XLX287 A "
M: 2020-06-08 15:38:28.988 D-Star, received network header from W4BRM /INFO to CQCQCQ via XLX287 A
M: 2020-06-08 15:38:34.972 D-Star, received network end of transmission, 6.0 seconds, 0% packet loss, BER: 0.0%
If I connect to the DCS it only announces once.
So: when I try an XLX connection I get a DCS connection. If the IP's are the same I get one type of error and if the IP's are different, I get a different kind of error. In any case I get an error using XLX.
I should mention this is with version 3.4.17 (the latest version available for the nano pi)
The newer version I see has some parameters you can set for XLX that are not present in the older version. Maybe that is the answer. Just don't use XLX with 3.4.17.
Ken
DCS006 and XLX006 have different addresses. When i ask for XLX I get DCS instead and that is a different IP. And I get those poll errors.
Let's pick a different reflector.
If I select XLX287 (66.42.109.165) then pi-star actually makes a DCS connection (also on address 44.42.109.165). So here they have the same IP. Now I get a different error. Nothing about polling It keeps announcing the XLX connection.
M: 2020-06-08 15:38:26.977 D-Star link status set to "Linking to XLX287 A "
M: 2020-06-08 15:38:27.059 D-Star link status set to "Linked to XLX287 A "
M: 2020-06-08 15:38:28.988 D-Star, received network header from W4BRM /INFO to CQCQCQ via XLX287 A
M: 2020-06-08 15:38:34.972 D-Star, received network end of transmission, 6.0 seconds, 0% packet loss, BER: 0.0%
If I connect to the DCS it only announces once.
So: when I try an XLX connection I get a DCS connection. If the IP's are the same I get one type of error and if the IP's are different, I get a different kind of error. In any case I get an error using XLX.
I should mention this is with version 3.4.17 (the latest version available for the nano pi)
The newer version I see has some parameters you can set for XLX that are not present in the older version. Maybe that is the answer. Just don't use XLX with 3.4.17.
Ken