Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry pi4B set up, the program runs but does not open the port #244

Open
gaoben opened this issue Jan 29, 2021 · 12 comments
Open

Raspberry pi4B set up, the program runs but does not open the port #244

gaoben opened this issue Jan 29, 2021 · 12 comments

Comments

@gaoben
Copy link

gaoben commented Jan 29, 2021

Pi4b
run ps ax | grep YSFReflector
pi@pi-4b:~ $ ps ax | grep YSFReflector

395 ? Ss 0:00 ./YSFReflector /etc/YSFReflector.ini
1505 pts/1 S+ 0:00 grep --color=auto YSFReflector

after looking at the ports, it is found that port 42000 is not running

@gaoben
Copy link
Author

gaoben commented Jan 29, 2021

M: 2021-01-29 00:01:36.264 No repeaters/gateways linked
M: 2021-01-29 00:02:01.321 Adding TEST F (52.163.250.190:38691)
M: 2021-01-29 00:03:01.336 Removing TEST F (248.34.75.0:38691) disappeared
M: 2021-01-29 00:03:36.304 No repeaters/gateways linked
M: 2021-01-29 00:05:36.343 No repeaters/gateways linked
M: 2021-01-29 00:06:49.028 Adding TEST F (52.163.250.190:38691)
M: 2021-01-29 00:07:36.379 Currently linked repeaters/gateways:
M: 2021-01-29 00:07:36.379 TEST F: 216.161.250.190:38691 47/60
M: 2021-01-29 00:07:49.038 Removing TEST F (248.34.75.0:38691) disappeared
M: 2021-01-29 00:09:36.409 No repeaters/gateways linked
M: 2021-01-29 00:11:36.452 No repeaters/gateways linked
M: 2021-01-29 00:11:40.175 Adding TEST F (52.163.250.190:38691)
M: 2021-01-29 00:12:40.186 Removing TEST F (248.34.75.0:38691) disappeared
M: 2021-01-29 00:13:36.493 No repeaters/gateways linked
M: 2021-01-29 00:15:36.518 No repeaters/gateways linked
M: 2021-01-29 00:17:36.563 No repeaters/gateways linked
M: 2021-01-29 00:19:36.593 No repeaters/gateways linked
M: 2021-01-29 00:21:36.640 No repeaters/gateways linked
M: 2021-01-29 00:23:36.668 No repeaters/gateways linked
M: 2021-01-29 00:25:36.704 No repeaters/gateways linked

@dg9vh
Copy link
Contributor

dg9vh commented Jan 29, 2021

How did you check the port open? Locking at the log-sequence you presenting, all is ok so far... The reflector is running and accepting connections, so it is listening on port 42000 udp.

@gaoben
Copy link
Author

gaoben commented Jan 29, 2021

How did you check the port open? Locking at the log-sequence you presenting, all is ok so far... The reflector is running and accepting connections, so it is listening on port 42000 udp.

I connect to the port through the port forwarding function of the router, and other ports that scan and forward are open.
But YSFReflector port is not open.
Through pi-star to connect my YSFReflector and TX, there is no signal coming from the YSFReflector dashboard.
And about 1 minute later, pi-star will show that it is disconnected~
In order to eliminate the problem of port forwarding. I set the DMZ, and the fault is still the same

@dg9vh
Copy link
Contributor

dg9vh commented Jan 29, 2021

You can test your reflector with following little script:

#!/bin/bash
echo -n "YSFGATEWAY" | nc -u $1 $2 -w 2 && echo
echo -n "YSFS" | nc -u $1 $2 -w 2 && echo

If you name it ysfping.sh you could call it with:
./ysfping.sh

For example:
./ysfping.sh c4fm.ysfreflector.de 42000

it gives you following answer if all is running:

./ysfping.sh c4fm.ysfreflector.de 42000

YSFS62829DE Germany YSF262 BM263 014

So similar answer would be delivered by your reflector, if running.

UDP-Ports are not easy to scan.

@gaoben
Copy link
Author

gaoben commented Jan 29, 2021

sudo ./ysfping.sh gaoben.iok.la 8624
YSFS47747CN-Daqing-C4 DQ-C4FM-BG2EFX000

looks it's OK
bug pi-star will show that it is disconnected ,And can't forward the signal
You can visit my dashboard to see

http://gaoben.iok.la:8626/C4FM/

@dg9vh
Copy link
Contributor

dg9vh commented Jan 29, 2021

As you can see on your dashboard, the reflector is working fine best... it must be a problem with your pi-star-setup or your local network...

I can connect to the reflector, my transmission is listed in the dashboard...

image

73 de Kim

@gaoben
Copy link
Author

gaoben commented Jan 29, 2021

As you can see on your dashboard, the reflector is working fine best... it must be a problem with your pi-star-setup or your local network...

I can connect to the reflector, my transmission is listed in the dashboard...

image

73 de Kim

OK, thank you. I'll let my friend test it
Is it possible that my local pi-star device can't be connected to the reflector set up in the same LAN

@gaoben
Copy link
Author

gaoben commented Jan 29, 2021

As you can see on your dashboard, the reflector is working fine best... it must be a problem with your pi-star-setup or your local network...

I can connect to the reflector, my transmission is listed in the dashboard...

image

73 de Kim

Do need to set INI file parameters separately for reflectors installed by SH script

Prevent log file from being too large

@dg9vh
Copy link
Contributor

dg9vh commented Jan 29, 2021

You can use the new feature by switching off rotating the logs by the reflector and add the logfile to system's logrotate-configuration.

@gaoben
Copy link
Author

gaoben commented Jan 29, 2021

You can use the new feature by switching off rotating the logs by the reflector and add the logfile to system's logrotate-configuration.

My friend test with pi-star
TX, but it didn't work
There is no information about him on the dashboard

@gaoben
Copy link
Author

gaoben commented Jan 30, 2021

You can use the new feature by switching off rotating the logs by the reflector and add the logfile to system's logrotate-configuration.

Do youTX pass pistar?
My friend is connected through pistar, and my reflector can't launch
The fault is still automatic disconnection after connection

@AndyTaylorTweet
Copy link
Contributor

Your problem is not at all related to YSFGateway, its the port you chose to run your relflector on;
Pi-Star has an on-board firewall, "8624" is not on the allowed list. Suggest you run the reflector on the stock port number 42000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants