Running a DVMEGA and Beta RC4 release of pi-star - in the web interface I an unable to link any D-Star
resources ie. reflectors or repeaters from the admin screen. However, I am able to link just fine via RF/radio
and I can even use the ircddb app on my iPhone for linking unlinking all work great - just doesn't work from the web
page. there something in the Beta RC4 release 20190324 ?
TIA
Unable to Link Via Web Interface
Unable to Link Via Web Interface
73! de David KG5EIU
Re: Unable to Link Via Web Interface
I'm running Pi-Star 4.0.0-RC3 and dashboard update 20190324, and I'm able to connect just fine using the Admin dashboard's D-Star Link Manager. On the Configuration page, the Controller Software is MMDVMHost, the Controller Mode is Simplex Mode. At least that will tell you that this isn't an issue with Pi-Star 4.0.0-RC3, so you'll need to look elsewhere for what is causing you the problem. You'll need to provide more details to get more help. Try looking at your logs when you're attempting to link via the D-Star Link Manager to get a better idea of what may be going wrong.
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
https://amateurradionotes.com/pi-star.htm
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
https://amateurradionotes.com/pi-star.htm
Re: Unable to Link Via Web Interface
Just wondering if you changed the default remote port for use with the ircddb remote app?
Andrew M1DNS, (Mod)
Andrew M1DNS, (Mod)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Unable to Link Via Web Interface
Hi Andrew and All:
I am having this same problem... I changed the default ircddbgateway remote port from 10022 to something else. I have opened up that port in my firewall (iptables) and I can remote in using the remote app' on my phone and link / unlink, etc. So I know that my firewall settings are good.
However, I cannot link / unlink using the Admin page on the Pi-Star dashboard. I see an authentication error in the ircddbgateway log file.... what do I need to do to correct this?
Thanks,
Ramesh.
VA3UV, WA3UV, G4PNQ
I am having this same problem... I changed the default ircddbgateway remote port from 10022 to something else. I have opened up that port in my firewall (iptables) and I can remote in using the remote app' on my phone and link / unlink, etc. So I know that my firewall settings are good.
However, I cannot link / unlink using the Admin page on the Pi-Star dashboard. I see an authentication error in the ircddbgateway log file.... what do I need to do to correct this?
Thanks,
Ramesh.
VA3UV, WA3UV, G4PNQ
Re: Unable to Link Via Web Interface
From a command line, typeand verify that the values returned are correct.
Code: Select all
grep remote /etc/ircddbgateway
Re: Unable to Link Via Web Interface
remoteEnabled=1
remotePassword=*********
remotePort=<my_port_number>
remotePassword=*********
remotePort=<my_port_number>
Re: Unable to Link Via Web Interface
Hi Again...
Suspecting that the dashboard may be still trying to communicate on port 10022, I used tcpdump to monitor port 10022:
pi-star@va3pmo(rw):pi-star$ sudo tcpdump -i lo udp port 10022 -vv -x
tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes
13:35:43.312067 IP (tos 0x0, ttl 64, id 12774, offset 0, flags [DF], proto UDP (17), length 31)
localhost.49782 > localhost.10022: [bad udp cksum 0xfe1e -> 0x7def!] UDP, length 3
0x0000: 4500 001f 31e6 4000 4011 0ae6 7f00 0001
0x0010: 7f00 0001 c276 2726 000b fe1e 4c49 4e
13:35:43.412451 IP (tos 0x0, ttl 64, id 12776, offset 0, flags [DF], proto UDP (17), length 31)
localhost.49782 > localhost.10022: [bad udp cksum 0xfe1e -> 0x7def!] UDP, length 3
0x0000: 4500 001f 31e8 4000 4011 0ae4 7f00 0001
0x0010: 7f00 0001 c276 2726 000b fe1e 4c49 4e
Changed the port # to my new port # and nothing... no activity.
So the webpage seems to be either hard-coded to use port 10022 or is not reading / updating the port #.
Thoughts?
Ramesh.
Suspecting that the dashboard may be still trying to communicate on port 10022, I used tcpdump to monitor port 10022:
pi-star@va3pmo(rw):pi-star$ sudo tcpdump -i lo udp port 10022 -vv -x
tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes
13:35:43.312067 IP (tos 0x0, ttl 64, id 12774, offset 0, flags [DF], proto UDP (17), length 31)
localhost.49782 > localhost.10022: [bad udp cksum 0xfe1e -> 0x7def!] UDP, length 3
0x0000: 4500 001f 31e6 4000 4011 0ae6 7f00 0001
0x0010: 7f00 0001 c276 2726 000b fe1e 4c49 4e
13:35:43.412451 IP (tos 0x0, ttl 64, id 12776, offset 0, flags [DF], proto UDP (17), length 31)
localhost.49782 > localhost.10022: [bad udp cksum 0xfe1e -> 0x7def!] UDP, length 3
0x0000: 4500 001f 31e8 4000 4011 0ae4 7f00 0001
0x0010: 7f00 0001 c276 2726 000b fe1e 4c49 4e
Changed the port # to my new port # and nothing... no activity.
So the webpage seems to be either hard-coded to use port 10022 or is not reading / updating the port #.
Thoughts?
Ramesh.
Re: Unable to Link Via Web Interface
Solved it!!
The default remote password needed to be changed in the D-STAR section under the 'Configuration' tab (I had previously changed the password in the /etc/ircddbgateway file, along with the port #).
Clearly changing the parameters in the /etc/ircddbgateway file alone were not 'read' by the web utility, which was still using the old password along with the old port #.
Now since I changed the password via the web utility, it updated the /etc/ircddbgateway file, overwriting my dplus login callsign.....maybe something else too... need to review and validate.
Cheers,
Ramesh.
VA3UV, WA3UV, G4PNQ
The default remote password needed to be changed in the D-STAR section under the 'Configuration' tab (I had previously changed the password in the /etc/ircddbgateway file, along with the port #).
Clearly changing the parameters in the /etc/ircddbgateway file alone were not 'read' by the web utility, which was still using the old password along with the old port #.
Now since I changed the password via the web utility, it updated the /etc/ircddbgateway file, overwriting my dplus login callsign.....maybe something else too... need to review and validate.
Cheers,
Ramesh.
VA3UV, WA3UV, G4PNQ
Re: Unable to Link Via Web Interface
The main config page will update the file used by the remote control app that the dashboard uses to change reflectors, since you cant change the port in the main config page, nothing is able to change that other than editing the file
Once you edit that by hand to match up the port, you should be good again.
Code: Select all
/root/.Remote Control
- NL13716
- Posts: 2
- Joined: Mon Feb 10, 2020 3:16 am
- Location: Bergen op Zoom, The Netherlands
- Contact:
Re: Unable to Link Via Web Interface
In my case the IP address was 127.0.0.1, port was OK because I never changed it.MW0MWZ wrote: ↑Mon May 20, 2019 5:45 pm The main config page will update the file used by the remote control app that the dashboard uses to change reflectors, since you cant change the port in the main config page, nothing is able to change that other than editing the file
Once you edit that by hand to match up the port, you should be good again.Code: Select all
/root/.Remote Control
I changed it to the IP of my Pi which solved it.