All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 35 posts ]  Go to page Previous  1, 2
Author Message
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Tue May 02, 2017 10:46 am 
Offline
FlightAware Member
jimcander - FlightAware user avatar

Joined: Mon Jan 23, 2006 5:00 pm
Posts: 1156
Location: KALB
Hey Oliver -

Any word on converting MAC based installations to ID based installations?

Jim


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Wed May 17, 2017 1:18 pm 
Offline
Ljungskile - FlightAware user avatar

Joined: Tue Mar 08, 2016 1:10 am
Posts: 3
obj wrote:
If you have an existing site this does not affect you - existing sites will continue to be identified by MAC address at the moment.


I have changed hardware on my site, I would like to keep the old site ID, Im using the same image (different SD-card, but I have made sure it has the old sites ID now)

Could you please remove site 43294 and make sure that site 19882 identifies by ID instead of MAC?

Edit:
I didnt want to loose my "longest streak" (from the first day I started with this) on 19882, so I did as GeorgLichtblau and many others, i spoofed the MAC from the old Pi. But I still hope to be able to identify 19882 by ID instead of MAC in the future. It would make it easier when changing out hardware.


Last edited by Ljungskile on Wed May 17, 2017 3:39 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Wed May 17, 2017 2:41 pm 
Offline
GeorgLichtblau - FlightAware user avatar

Joined: Thu Nov 26, 2015 12:28 pm
Posts: 42
Location: Austria
I've changed hardware at one of my receivers (registered before the feeder-id) today...

As I wanted to keep my old stats I changed the mac-address to the old one and fiddling around for two hours with just creating new feeder-ids :)

So the quick and very, very dirty hack to get it to work by just using the mac-address was:

rm /var/cache/piaware/feeder_id
touch /var/cache/piaware/feeder_id
chmod 000 /var/cache/piaware/feeder_id

As said... very, very dirty.. but it works :)


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Wed May 17, 2017 6:24 pm 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3463
That will break in the near future.


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Wed May 17, 2017 8:23 pm 
Offline
FlightAware Member
abcd567 - FlightAware user avatar

Joined: Sat Feb 15, 2014 3:08 am
Posts: 1980
Location: Toronto CYYZ
The Piaware of a new Pi with new image obtains a new feeder-id immediately at FIRST BOOT, if:

(1) Mac address spoof was not done BEFORE FIRST BOOT
OR
(2) Mac address spoof was done, but it did not work due to line break in file cmdline.txt

The trouble free way to spoof mac address is to do it BEFORE FIRST BOOT of the newly written image, and to ensure there is no line break in file cmdline.txt.

After writing the image, and while the microSD card is still in card reader of Laptop/Desktop, click on the drive letter of microSD card. This will open the /boot folder (the only folder visible in laptop/desktop). Then open the file cmdline.txt using Wordpad (do not use Notepad, as it creates a line break in the file when it is saved, and because of line break, the mac spoof does not work).
This file has only one line. At the end of this line, add (without line break) following and save file.

smsc95xx.macaddr=xx:xx:xx:xx:xx:xx
(replace xx:xx:xx:xx:xx:xx by mac address of old Pi)

Now take out card from laptop/desktop, plugin into Pi and do the FIRST BOOT.

If a line break was introduced, then even if you edit file cmdline.txt in nano editor in SSH console and remove the line break, Piaware by that time has already obtained a new 128 bit site identifier, and you will be faced with problem of getting rid of it.


To enable SSH, you will also need to create a new file SSH in /boot folder BEFORE FIRST BOOT, while the microSD card is still in card reader of laptop/desktop.


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Sat May 27, 2017 4:16 pm 
Offline
alleyoopie - FlightAware user avatar

Joined: Mon Feb 20, 2017 4:36 pm
Posts: 11
A couple of weeks ago, I made a complete set (Pi/dongle/antenna) as a test for a friend so initially I registered it as a second feeder under my own account.
My friend has now decided to keep the set and continue as an independant feeder, how do I proceed to convert my second feeder into an independant one? (it's already the version with a unique identifier)


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Sat May 27, 2017 4:36 pm 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3463
alleyoopie wrote:
A couple of weeks ago, I made a complete set (Pi/dongle/antenna) as a test for a friend so initially I registered it as a second feeder under my own account.
My friend has now decided to keep the set and continue as an independant feeder, how do I proceed to convert my second feeder into an independant one? (it's already the version with a unique identifier)

If you stop piaware, remove /var/cache/piaware/feeder_id, and restart piaware, then it will create a new site when it logs in and your friend can claim that site for themselves.


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Sun May 28, 2017 5:58 am 
Offline
alleyoopie - FlightAware user avatar

Joined: Mon Feb 20, 2017 4:36 pm
Posts: 11
obj wrote:
If you stop piaware, remove /var/cache/piaware/feeder_id, and restart piaware, then it will create a new site when it logs in and your friend can claim that site for themselves.


Unfortunately the same feeder_id is created the moment I restart piaware, this is what I do:
sudo systemctl stop piaware
piaware-status (to check that piaware has been stopped)
sudo rm feeder_id (when in the /var/cache folder)
ls (to check the file has gone)
sudo systemctl restart piaware
piaware-status (to check that piaware has been started again)

I also tried to reboot the pi (sudo reboot) just after having deleted the feeder_id but alas, to no avail...


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Sun May 28, 2017 9:46 am 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3463
alleyoopie wrote:
sudo rm feeder_id (when in the /var/cache folder)

Wrong directory.

edit: I looked at the logs and your piaware is providing the same feeder ID as configured data. That means either you configured it explicitly in piaware-config.txt or you've done something to make /var/cache/piaware/feeder_id unwriteable by piaware (piaware treats both cases the same - as a configured feeder ID that it can't update)


Top
 Profile  
 
 Post subject: Re: Changes to how new PiAware feeders are identified
PostPosted: Sun May 28, 2017 10:57 am 
Offline
alleyoopie - FlightAware user avatar

Joined: Mon Feb 20, 2017 4:36 pm
Posts: 11
Your hint does ring a bell. Originally I configured the Pi at my home but at my friends place it kept rebooting because the AC adapter that he used couldn't deliver enough current. Once this was solved I had to reimage the Pi due to a crashed µSD-card but this created a third account which I solved by including the original ID in the config file. I guess the problem will be solved by removing this entry and going through the same procedure as mentioned above.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 35 posts ]  Go to page Previous  1, 2

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: k6rtm 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: