This feature is available in all current routers, is it not? I have used it with Netgear, Linksys, and TP-Link now.
It may not be enabled the exact same way. In my case, it was a one time ‘link’ between MAC and IP addresses.
I cannot find where i said “It is not”.
I only said that this is working for me and for many others as standard way to get a fixed IP on LAN devices
Oh boy, I did not mean that. Forgive me, please. I’ll recant.
1 Like
@lockon1 I sincerely apologize and completely understand your frustrations.
Our engineers have been focused on other things since the 3.8.0 release, but we will try to get 3.8.1 out as soon as possible.
1 Like
No worries, for such things my memory is very short term 
I’d welcome some advice on how to upgrade to 3.80 on one of my Pis. It currently has Jessie as the OS and with a Piaware 3.70 image. It’s all working fine so should I just leave it alone? I have tried to upgrade by using the online Receiver configure option but it doesn’t work. I think it is probably time to upgrade to either Stretch or Buster and then upgrade to 3.80. What is the best way to do this?
-
Start from scratch and burn everything onto a new card, or
-
Can I upgrade onto the current card using Putty?
Any suggestions, advice, appropriate links would be much appreciated for a non-technical person
Many thanks
It doesn’t work for piaware sd-card.
Even for Raspbian it’s not recommended.
1 Like
Thanks…so I guess the only option is to start with a new card?
Always the best and fastest option, unless one wants to get deeper into software.
1 Like
Thank you so much for this!! This was driving me bonkers.
1 Like
Sorry, I’m not “techie” at all. I’m running Piaware 3.7.2. If I’m understanding things here, there is an issue with 3.8.0.
Do I need to upgrade?
Will I loose my feed to Flightradar 24?
Should I wait for 3.8.1?
PS - Flightaware, I really don’t like the lay out of your “forums”.
3.8.1 is expected in a couple of weeks or so, so I’d be inclined to hang on for that and then review your options. 3.8.0 is based on Debian Buster Lite and caused a little interoperability issue for some people upgrading in a particular way from 3.7.2, and it also has a couple of bugs which are more edge cases than anything. No big deal and worth upgrading for the fixes from 3.7.2. Someone else may be able to help with the FR24 question.
Thank you.
Yes, if anyone knows if upgrading will knock my FR24 feed offline would be appreciate. I had lots of difficulty getting the feed to FR24 started.
Instead of upgrading 3.7.2 to 3.8.1, better write 3.8.1 image to a spare microSD card, slip-out old microSD card and slip-in the spare microSD card. See configuration steps here:
Howto : Piaware SD card image 3.8.0 Quickstart Guide
Using a spare microSD card for fresh install has advantage that in case of any problem with fresh install, you can replace new card by old card and your system will be up again.
On new card you should make a fresh install of FR24 feeder. I don’t foresee any problem in doing so. I have done it innumerable number of times.
First note down your FR24 feeder key either from file /etc/fr24feed.ini in existing install, or by logging in to your Fr24 account, and go to stats page, and find it there.
Next install fr24feed by the bash script. When you reach settings stage, do NOT use setting receiver="dvbt". Use receiver=Beast (TCP) and host 127.0.0.1:30005
I am feedeing several sites and updated it without losing anything.
But i did not use the full Piaware image as i am using Raspberry Buster
Thanks everyone. See all those steps scare me big time. It was a battle for me setting this stuff in the first place.
Can someone please remind me of where to find steps to install FR24 feed after getting the Flightaware feed all squared away.
It’s been so long, I can’t remember anything but the scares from my frustration.
@abcd567 has some helpful information. I assume this is still valid.
Most of howto are not simple or outdated.
Tonight I will write piaware image to a spare microSD card, then install FR24, note all steps and post procedure for FR24 in simplest form possible.
Note for piaware: By default the Piaware image behaves as dump1090-fa only. If you dont want dump978-fa, there is nothing to do more than adding ssh, wifi, and feeder key.
Piaware installation
On a spare microSD card install piaware as per QuickStart Guide linked below.
Follow steps 1 to 4 only and disregard rest of steps.
Howto : Piaware SD card image 3.8.0 Quickstart Guide
FR24 installation
1 - Retrieve your existing fr24 key
Go to page https://www.flightradar24.com and login to your account
After login, go to your stats page. On stats page you will find your fr24 key. Copy the key and paste in Notepad and save the Notepad.
See screenshots below.
Screenshot 1 of 2
Screenshot 2 of 2
Install fr24feed
Give following command
sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"
The above command will run installation for some time, then automatically start signup process. The signup process will halt and ask for email address.
Case 1:
If you do not have a fr24 sharing key, or want a brand new key, continue inputting your email and other details. A new key will be generated and saved in file /etc/fr24feed.ini. FR24 will also send this key to you by email for your records.
Case 2:
If you already have a key, then do not enter any details. Instead break the siugnup process by pressing Ctrl and C keys together. This will result in display of ^C and command prompt "pi@piaware:~ $". Please see screenshot below.
Configure FR24
Give following command
sudo nano /etc/fr24feed.ini
Above command will open the config file. It will have following text
bs=yes
raw=yes
mlat="yes"
mlat-without-gps="yes"
(1) Delete all above lines by:
- bring cursor to the top line
- keep pressed Ctrl key and repeatedly press K key till the file becomes blank.
(2) Copy paste following in this file (replace "xxxxxxxxxxxxxxx" by the key you have copied from your stats page).
receiver="beast-tcp"
fr24key="xxxxxxxxxxxxxxx"
host="127.0.0.1:30005"
bs="no"
raw="no"
logmode="1"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"
(3) Save file (Ctrl+o) and Close (Ctrl+x).
(4) Restart FR24 feeder
sudo systemctl restart fr24feed
(5) Check status:
fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2020-03-14 06:15:24.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-CYYZ9.
[ ok ] FR24 Tracked AC: 1.
[ ok ] Receiver: connected (4 MSGS/0 SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 1.
(6) Check status in browser on following address:
ip-of-pi:8754
And that is all, enjoy!
NOTE
If you want a new key at any time after installation, you can signup again by following command. Complete signup and obtain a new key, which will automatically be saved in config file /etc/fr24feed.ini as well as sent to you by email.
sudo fr24feed --signup
CAUTION:
Never use FR24 setting receiver="dvbt".
This setting will install dump1090-mutability ver 1.14, which will conflict/compete for dongle with dump1090-fa, and result in a mess
2 Likes
Thanks for that very clear guide, I will try that shortly. I’ve got a FR24 account and was resigned to working out the cleanest process from scratch myself at some point as a future mini project. This gives a good starting point. I have a question about it. In the fr24feed.ini config you have
mlat="yes"
mlat-without-gps="yes"
What does this actually mean in terms of using dump1090-fa port 30005 to feed FR24? I understand what MLAT is and how it works. I know that FlightAware does not allow its own MLAT calculations from PiAware port 30105 to be resent back out to commercial services such as FR24, only for hobby VRS use.
So what are those FR24 MLAT settings actually doing? Does FR24 also calculate positions via MLAT on its own servers from the ADS-B and Mode S data we send it? If so, does it install its own equivalent of fa-mlat-client and return the info to a waiting port on dump1090-fa (analogous to port 30104)? And if it does, why do we need it anyway, since we already have FlightAware’s MLAT calculations for our own use?
Perhaps admins can move this guide and response to its own new topic, as it’s a bit buried here in this PiAware announce thread.