search

g4klx / YSFClients

System Fusion network servers; a gateway and a parrot.
GNU General Public License v2.0
83 stars 95 forks source link

GB Leeds UK #118

Open 2E0LXY opened 6 years ago

2E0LXY commented 6 years ago

Hi. I’ve installed YSFReflector on a Pi3+ on Raspbian Created account and added the details at https://register.ysfreflector.de/ Port forward done for 80 and 42000 Dashboard at http://xxx.sn.mynetname.net

Pinged reflector... "Your Reflector has been pinged! Following results: No reply from xxx.sn.mynetname.net:42000 Try to wake it up! No reply from xxx.sn.mynetname.net:42000 YSFReflector xxx.sn.mynetname.net:42000 updated! "

Still showing offline.

Please help.

ChrisK9EQ commented 5 years ago

You have a MikroTik router that is improperly configured. These routers have serious security issues in their default state. Port 80 is showing the admin port. THIS SHOULD NEVER HAPPEN. You need to fix this NOW and assume your router has been compromised. (99% probability) Suggest using a different port for your dashboard.

You will need to forward your incoming YSF port (probably 42000) to the YSFReflector computer. Best to use via MAC address.

Make sure you have enabled your reflector at register.ysfreflector.de. It may take a while for pinged reflector to wake up.

Suggest this issue be closed.

kb0isw commented 5 years ago

I just installed a YSF reflector using a Raspberry Pi 3B+ and am having the same exact problem, but I'm using a Netgear router. I have mapped port 42000 to the YSFReflector computer, but it still refuses to wake up.

da13ba commented 5 years ago

I am also having the same problem. It was up for a day and working, but now it will not wake up and it is showing offline.

SA7SVR commented 5 years ago

I have the same problem! Your Reflector has been pinged!

Following results:

No reply from xxxxx.ddns.net:42000 Try to wake it up! No reply from xxxxx.ddns.net:42000 YSFReflector xxxxx.ddns.net:42000 updated!

ChrisK9EQ commented 5 years ago

I believe this is a problem with ysfreflector.de. I have observed the problem as well with my YSF reflectors running in a high-bandwidth commercial hosting facility. I've played with a number of changes to the YSF Reflector code and have never been able to resolve the issue from the reflector end.

I suggest closing this issue. If it's still a problem, contact ysfreflector.de. 73, Chris, K9EQ

mslade1969 commented 4 years ago

What I found with my router, was that uPnP applications had been using forwarded ports and one of these was 42000. I changed my config to use 39000 which is out of range of the uPnP and now register.ysfreflector.de can ping it.

I've got other issues, but, at least it's pinging now.

73, Mark M0CUK

K9JTV commented 3 years ago

I just configured my first YSF Reflector on a Pi 3 B + and am having the same problems as listed above. I too found that my router's UPnP was forwarding port 42000 for use by my Wires-x monitor that is not hosted on my Pi. I changed the port to an unused one, added it to Port forwarding in my router, and changed the port in my YSFReflector.ini to match the router config, then updated my reflector info with YSFReflector Registration. Still no ping reply and my reflector is showing as offline. My Router is a Calix 844G-1, with fiber coming into it. Any suggestions would be appreciated.