All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: Changes to how new PiAware feeders are identified
PostPosted: Mon Mar 20, 2017 8:42 am 
Online
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3205
Brand new PiAware feeders (from new hardware that has never been seen previously by FlightAware) are now being identified by a unique feeder ID stored by PiAware, rather than by hardware MAC addresses.

If you have an existing site this does not affect you - existing sites will continue to be identified by MAC address at the moment.

For new sites (running PiAware 3.3.0 or newer), a feeder ID will be assigned when the feeder first connects, and will be stored by PiAware on the sdcard. Subsequent connections will use that feeder ID to identify the site. The main consequence of this is that if you re-image the sdcard or otherwise remove the feeder ID, then subsequently the feeder will look like a brand new feeder and will create a new site.

If you want to retain the same feeder-to-site association when re-imaging, so that the existing site continues to be used, then you can explicitly configure the feeder ID to use. This is a somewhat manual process at the moment:

  • Find the feeder ID that you want to use. You can find this either as the "Site identifier" on the site page at https://flightaware.com/adsb/stats/user/yourusername, or from the PiAware logs in /var/log/piaware.log on your existing install. The identifier looks like a series of dash-separated hex digits: 12345678-1234-1234-1234-123456789abc.
  • Configure the feeder ID on the new system: piaware-config feeder-id 12345678-1234-1234-1234-123456789abc
  • Restart piaware: sudo systemctl restart piaware

This also works when replacing hardware (if it is just a Pi replacement, you can just move the existing sdcard over and the feeder ID will be retained)

Existing sites can't be moved like this - yet. We plan to migrate existing sites to the new scheme in the future, but that's not quite there yet.


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Mon Mar 20, 2017 3:42 pm 
Offline
FlightAware Member
tdrane - FlightAware user avatar

Joined: Thu Jan 08, 2015 7:28 am
Posts: 95
This is certainly a welcome change. Playing MAC roulette has been a pain since I've upgraded Pi's twice over the last two years and I'm about to do it again.

I hope the new identifier is stored in a simple text file on the boot volume so that one can keep it stored on a PC and copy it easily to the SD Card when necessary.

Thanks for all the good work.

TD


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Mon Mar 20, 2017 4:25 pm 
Online
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3205
tdrane wrote:
I hope the new identifier is stored in a simple text file on the boot volume so that one can keep it stored on a PC and copy it easily to the SD Card when necessary.

It's not in /boot but it is just a simple text file: /var/cache/piaware/feeder_id
You can set the feeder-id config option in /boot/piaware-config.txt though.


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Mon Mar 20, 2017 5:22 pm 
Offline
deanoz - FlightAware user avatar

Joined: Mon Mar 20, 2017 4:16 pm
Posts: 2
Ah, well this is annoying, had me scraching my head for ages trying to work this out.

I just swapped my SD card to another Pi and got the new identifier ID (used same wifi dongle) noticed it had created new site (new long ID), i was confused so have now put back to my old Pi with wifi dongle and still got new Id. Ive tried deleting the file you mentioned and also forcing back to macaddress but no luck.

I dont want to lose my old stats and i dont want 2x sites as they are the same, is there a way to reconfigure this to keep as one site with or without new ID

Thanks for any ideas.
Dean

EDIT: Old Site: 37789. New Site: 39711


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Mon Mar 20, 2017 8:30 pm 
Online
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3205
You triggered a corner case by swapping hardware and then trying to go back to a MAC-address-based site. I fixed it by hand this time.

(edit: this case should work a bit more smoothly now; migration of an old site to new hardware won't prevent using the old site on old hardware)


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Tue Mar 21, 2017 4:26 pm 
Offline
deanoz - FlightAware user avatar

Joined: Mon Mar 20, 2017 4:16 pm
Posts: 2
obj wrote:
You triggered a corner case by swapping hardware and then trying to go back to a MAC-address-based site. I fixed it by hand this time.

(edit: this case should work a bit more smoothly now; migration of an old site to new hardware won't prevent using the old site on old hardware)


Thanks obj for fixing that for me, very much appreciated for the quick response.

Im going to do some digging in other posts to see how to delete that site ID now its not needed.

Thanks
Dean


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: obj and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to: