YSF Reflector ID

Post Reply
User avatar
g8koe
Posts: 146
Joined: Sun Sep 04, 2016 8:33 pm

YSF Reflector ID

Post by g8koe » Wed Jun 13, 2018 8:49 pm

Hi Norbert,
When you do a *D and get "openSPOT connected to YSF Reflector" could the ID number be included to identify the connected reflector.
Example "openSPOT connected to YSF Reflector 99603"
99603 HUBNet
This would be helpful on our repeater as more than one profile are connected to a YSF reflector.
We are using the openSPOT on our C4FM repeater GB7IS and it works flawless.

73's
Martin
G8KOE

EdAtlanta
Posts: 37
Joined: Wed Dec 21, 2016 12:49 pm

Re: YSF Reflector ID

Post by EdAtlanta » Mon Aug 06, 2018 1:40 pm

I agree with this request. It would be nice.
Ed
KM4STL
3101156

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3936
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF Reflector ID

Post by HA2NON » Mon Aug 06, 2018 2:42 pm

The YSFreflector protocol / server application does not have a message to query the connected server's ID. The ID is only generated by the YSFReflector Registry, which is a website.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

EdAtlanta
Posts: 37
Joined: Wed Dec 21, 2016 12:49 pm

Re: YSF Reflector ID

Post by EdAtlanta » Wed Aug 08, 2018 9:12 am

Now we know. Thank you for the info.
Ed
KM4STL
3101156

yo2loj
Posts: 26
Joined: Mon May 08, 2017 9:40 am

Re: YSF Reflector ID

Post by yo2loj » Sun Sep 30, 2018 11:40 am

Actually it has.
A "YSFS" message (4 bytes) sent to a reflector will trigger the return of a 42 bytes status response holding the reflector ID, the reflector name, its description and the number of currently connected users:

Code: Select all

YSFS<5bytes_ref_id><16bytes_name><14bytes_description><3bytes_user_count>
All data is in ASCII...
The status request is honored even if not connected to that specific reflector, this is how the registry server checks for reflectors to be on line. The numeric reflector ID is also generated locally on the reflector, by a hash function on the reflector name.

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3936
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF Reflector ID

Post by HA2NON » Mon Oct 01, 2018 6:45 am

Thank you for the info!
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

N0RUA
Posts: 16
Joined: Fri Feb 10, 2017 2:08 am

Re: YSF Reflector ID

Post by N0RUA » Fri Mar 01, 2019 10:29 pm

On a related note, the HTTP API GET /status.cgi returns the first few portions of the IP address of the YSF reflector, instead of the full name.

For example, when I'm connected to "US MNWis 21493 / Hamoperator", status.cgi returns the string "167.99...." for the "connected_to" field -- it would be much more useful to return the full name, rather than just a portion of the IP address.

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3936
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF Reflector ID

Post by HA2NON » Sat Mar 02, 2019 9:04 am

That's intentional. You can get the currently connected server's IP address by querying the YSFReflector connector settings.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

N0RUA
Posts: 16
Joined: Fri Feb 10, 2017 2:08 am

Re: YSF Reflector ID

Post by N0RUA » Sat Mar 02, 2019 5:26 pm

HA2NON wrote:
Sat Mar 02, 2019 9:04 am
That's intentional. You can get the currently connected server's IP address by querying the YSFReflector connector settings.
Is that the "server_host" field? What about the name? Would it be possible for you to expose the reflector name, or is there some other place I could look that up?

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3936
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF Reflector ID

Post by HA2NON » Mon Mar 04, 2019 10:21 am

Yes, the server_host field. The openSPOT1 does not handle YSFReflector names.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

Post Reply