New YSFGateway pushed out...

Help with YSF / Fusion issues
Post Reply
User avatar
MW0MWZ
Site Admin
Posts: 1074
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

New YSFGateway pushed out...

Post by MW0MWZ » Thu Jan 24, 2019 7:47 pm

This version has fixes for:

Paging of searched YSF/FCS rooms (page down was not always working right)
Better Handling of Upper case host entries (most of you will want to make sure "UPPERCASE Hostfiles" are enabled in the Yaesu System Fusion section of the config page.

We did have our own version of the Upper Case fix already, but thanks to Jonathan (G4KLX) for pushing a fix into the gateway to handle it natively.
I've asked Andy (CA6JAU) to add similar code to his YSF2xxx modes too, those will also need it.
Andy

73 de MW0MWZ
http://pistar.uk

AC8OB
Posts: 25
Joined: Thu Nov 01, 2018 2:28 am

Re: New YSFGateway pushed out...

Post by AC8OB » Thu Jan 31, 2019 2:50 am

Not sure if related to this but YSF00009 - Local Parrot is no longer available from the YSF Startup Host dropdown list.
Nick - G4IRX - MB6IRX - AC8OB
IO92JV - EN70VN

User avatar
MW0MWZ
Site Admin
Posts: 1074
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New YSFGateway pushed out...

Post by MW0MWZ » Thu Jan 31, 2019 8:47 pm

I'm in the process of sorting out the host files, this is part of the work on YSFGateway and YSF2xxx modes.

I've just put parrot back into the config page, its actually hard coded to 00001 in YSFGateway, so that is now matched up on the dashboard too.
Andy

73 de MW0MWZ
http://pistar.uk

AC8OB
Posts: 25
Joined: Thu Nov 01, 2018 2:28 am

Re: New YSFGateway pushed out...

Post by AC8OB » Thu Jan 31, 2019 10:13 pm

Thanks for the updates Andy.

Maybe I'm misunderstanding how the Parrots work. I thought YSF00001 (Parrot) was somewhere externally hosted but YSF00009 (Local Parrot) was a locally hosted YSFParrot. It's the latter one I can't see in the dropdown.
Nick - G4IRX - MB6IRX - AC8OB
IO92JV - EN70VN

User avatar
MW0MWZ
Site Admin
Posts: 1074
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New YSFGateway pushed out...

Post by MW0MWZ » Fri Feb 01, 2019 12:44 am

That is how I had it in the host files - however, the YSFGateway has the YSF00001 listed internally as the local one, so I am making sure we follow that.
I also cleaned up the Pi-Star hostiles to make the YF2xxx modes match exactly.
Andy

73 de MW0MWZ
http://pistar.uk

AC8OB
Posts: 25
Joined: Thu Nov 01, 2018 2:28 am

Re: New YSFGateway pushed out...

Post by AC8OB » Tue Feb 05, 2019 12:28 am

On my installs I'm seeing YSF0001 as

Code: Select all

00001;Parrot;Parrot;c4fm.ysfreflector.de;42020;000;http://
which is also listed on https://register.ysfreflector.de/ - so the parrot goes out over the network (verified with tcpdump)

If I change to

Code: Select all

00001;Parrot;Parrot;127.0.0.1;42012;000;http://
then it works correctly with the local parrot.

Not related but I also noticed that the ss command doesn't work correctly in this distro - If I run ss -lun to look for udp sockets it doesn't show any. Had to take step back to netstat -na4 to confirm the YSFparrot was actually listening.
Nick - G4IRX - MB6IRX - AC8OB
IO92JV - EN70VN

User avatar
MW0MWZ
Site Admin
Posts: 1074
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New YSFGateway pushed out...

Post by MW0MWZ » Tue Feb 05, 2019 5:04 pm

Well this raises some interesting points - "Parrot" does not has to 00001 using the hashing method used to get the YSF reflector number from the name, so I do wonder how exactly that happened, anyway - so I can manually add a parrot back in, (thats what I had before), I can also re-write the network parrot to a new address so that 00001 is the on-board parrot.

Peronally I want the 00001 to be the local parrot since this follows the software design, so I would rather move the network parrot.
Who knows how many other YSF2xxx gateways we could end up with, so I still think 00009 is a reasonable choice.
Andy

73 de MW0MWZ
http://pistar.uk

Post Reply