Ability to turn off ircddbgateway

[K2IE]

In a previous feature request post, I mentioned that I am running two pi-star nodes, with ircddbgateway and the D-Star "C" module on one node and the "B" module on the other. All my attempts to prevent ircddbgateway from running on the "B" box have been in vain, as something always ends up to keep starrting it up despite disabling services, tmers, etc.

What would be very useful is an explicit binary switch on the dashboard that would decide whether to run ircddbgateway or not.

If not practical, at least a sure-fire recipe on how to prevent it from running would be appreciated.

So far, I tried disabling the ircddbgateway.timer service and the pistar-watchdog.service but something (perhaps an update) restarted the watchdog service anyway and it in turn restarted the ircddbgateway! Great if you want reliability, not so great if you don't want a service to run.

Thanks.

[K2IE]

For those interested, here is a workaround that I implemented:

systemctl disable ircddbgateway.timer
systemctl mask ircddbgateway.service

While it does not prevent the watchdog from restarting the service, the service now points to /dev/null. It would be more convenient to have a dashboard button.

73

[G4AON]

I'm not sure why running two Pi-Star access points should be a problem with the ircddb gateway. I use two myself.

I run one with a DVAP dongle on 2m and another with an MMDVM board on 70cms. I access them via their IP address, which is xxx.3 for one and xxx.2 for the other. I use ircddb remote on my iPhone to switch D-Star reflectors, picking whichever one I want via the IP address in the setup on the iPhone app.

[M1DNS]

I'm not sure why running two Pi-Star access points should be a problem with the ircddb gateway. I use two myself.

I run one with a DVAP dongle on 2m and another with an MMDVM board on 70cms. I access them via their IP address, which is xxx.3 for one and xxx.2 for the other. I use ircddb remote on my iPhone to switch D-Star reflectors, picking whichever one I want via the IP address in the setup on the iPhone app.

Brobably not the best way to run. Having two ircddbgateway instances running the same callsign logging into the same server.

With the above...
He's running a specific use case. Two instances, C & B modules running into one ircddbgateway. (And, not the way you are running in having two seperate installs each using their seperate ircddbgateway. (Which is Not advised))
He wants to stop the 2nd install of ircddbgateway from running.

Andrew M1DNS, (Mod)

[VA3UV]

Hi Guys:

Similar to K2DLS, while I have tried to get 2 instances of dstarrepeater to play nice on one Pi, I thought I'd try running my 2nd instance on a completely different Pi.

So my stepup is:

Pi #1 (192.168.1.136) running ircddbgateway & dstarrepeater (Module B)

Pi #2 (192.168.1.100) ircddbgateway disabled, dstarrepeater running (Module C).

Of course, I want my Pi #2 to communiate with ircddbgateway on Pi #1.

Here are the pertinent sections from my config:


ircddbgateway on Pi #1

repeaterCall2=VE3RSD
repeaterBand2=C
repeaterType2=0
repeaterAddress2=192.168.1.100
repeaterPort2=20012


dstarrepeater on Pi #2:

gatewayAddress=192.168.1.136
gatewayPort=20010
localAddress=127.0.0.1 <=== Tried spec'ing 192.168.1.136 here but dstarrepeater will not even start
localPort=20012
networkName=
modemType=DV-RPTR V1


With the above config, I am getting the following error in the dstarrepeater log file:

E: 2019-05-05 11:40:08: Error returned from sendto (port: 20012), err: 22
E: 2019-05-05 11:41:09: Error returned from sendto (port: 20012), err: 22


Any ideas?

Thanks,

Ramesh.
VA3UV / WA3UV / G4PNQ

[K2IE]

Ramesh:

I compared your config to mine and you are configured properly as far as I can tell, with the following caveats:

I am running RC4.
My node that talks to the remote ircddbgateway is using MMDVM rather than dstarrepeater.

So the next thing to look at is firewall rules between the two hosts.

On Pi#2:

iptables -A INPUT -p udp -s Pi#1 --sport 20010 -d Pi#2 --dport 20012 -j ACCEPT
iptables -A OUTPUT -p udp -s Pi#2 --sport 20012 -d Pi#1 --dport 20010 -j ACCEPT

On Pi#1:

iptables -A INPUT -p udp -s Pi#2 --sport 20012 -d Pi#1 --dport 20010 -j ACCEPT
iptables -A OUTPUT -p udp -s Pi#1 --sport 20010 -d Pi#2 --dport 20012 -j ACCEPT

Give that a try.

73

[M1DNS]

You beat me to it Dan. I was also going to suggest Ramesh looks at the ip tables, the firewall is most probably to blame in its not allowing for the other instance. I ran into the same allowing my repeater install and another gateway install to work this same way.

Andrew M1DNS, (Mod)

[VA3UV]

Hi Andrew and Dan:

Thanks for your replies. I applied the iptables rules on the two respective Pi's. I am no longer seeing the error on Pi #2 (192.168.1.100). However, on Pi # 1 (192.168.1.136), when I tail the ircddbgateway log file, I am not seeing my RF activity appear there.

I have tried altering the 'mode' parameter on Pi #2 (where I am just running dstarrepeater for my C module). This is a simplex radio. I have tried mode =0 as well as 2.


So on Pi #2 (192.168.1.100) - my dstarrepeater config is:

callsign=VE3RSD C
gateway=VE3RSD G
mode=0
ack=1
restriction=0
rpt1Validation=1
dtmfBlanking=1
errorReply=1
gatewayAddress=192.168.1.136
gatewayPort=20010
localAddress=192.168.1.100
localPort=20012
networkName=
modemType=DV-RPTR V1


On Pi #1 (192.168.1.136), my ircddbgateway config is:

band1_1=1
band1_2=0
band1_3=0
repeaterCall2=VE3RSD
repeaterBand2=C
repeaterType2=0
repeaterAddress2=192.168.1.100
repeaterPort2=20012



Hopefully, I'm one step closer!

Thanks,

Ramesh.

[VA3UV]

Hi Guys:

Solved it!!!

With the tip about the iptables change... I had to edit the ircddbgateway config on Pi #1 to listen on 192.168.1.136 rather than 127.0.0.1

Finally, got two modules working!

Thank you!

Ramesh.

[VA3UV]

Hi Dan:

I had to power recycle my Pi and found that the new iptables rules had to be re-applied.

iptables-save did not seem to 'save' them. Where in the Pi-Star distro' are the iptables saved and restored on boot-up?

Thanks!

Ramesh.