Windows feeder discontinued 7-May-19

[Aries]

Well, FR24 - thank you!
You buried yourself.

I gave you feed during the last 5 years 24/7.
How much you earned on advertising broadcasting data from such as I enthusiasts who gave you the data for free and only occasionally using the privileges of a business account. Not enough for you?
Instead of fixing the customer under win decided to go the other way? Good luck!

I have an unaffected Raspberry PI that I could set up to broadcast to you. But at the moment there is no time, nor what is most important - desire, as you put a large community in front of the fact - we do not need you anymore.
You have forgotten the basis that this resource has generated in the first place the community, a large part of which You just left behind.
Moreover, none of the users of win did not keep the machine 27/7 only for broadcasting on FR24, and used the resources in parallel and for other tasks, I doubt that all rush to move to other platforms at the expense of other interests.
I perfectly understand, that I only a drop in sea and my opinion little whom interested in, but it has the right on existence.
Maybe someday I will be angry because of this attitude (and I'm not quite a young man and there is not teenage hormones), I calm down and I will be broadcast on a different platform or hardware, possible I got one of these, but again, dramatically fell off the desire.
Russia. T-UUDD3, T-UUMO31
Thank You and good Luck!

[mlat21]

I've received the notification about deactivation on 7 may.
Thank You FR24!

[YSCB8]

Aww bugger them then. I'm going back to RTL190. It's got better range anyway.

[federbear]

It is funny. I use Linux but it writes about windows feeder

[T-CYBN3]

Not everyone.

That never happens to me.
Mine has worked fine for years without issue.

I certainly will not be changing to any other systems, so it's goodbye for me.

I am not sure of the real reason for FR24 to discontinue Windows feed, but one reason seems to be there: whenever Windows10 updates, it replaces dvb-t's custom driver "zadig" by Microsoft's generic driver, forcing users to reinstall "zadig" after updates of Win10.

[Stealth]

Many thanks for that... but its extra effort, and theres a principal here !

I felt and still feel the same. However, I looked at what use I made of FR24 overall and which was my preferred mobile app. My criteria was that it would not cost me anything to switch, but a bit of effort (and self-education) was acceptable. Neither Oracle VM or a linux image cost anything and if I had hindsight, its a fairly quick and simple process.

So basically nothing has changed on my Windows set up, same people get feeds, just FR24 feeder sitting on the VM. The linux installation may also be useful for other things in the future.

[abcd567]

...and theres a principal here !

Well, in this case your stand is right !

[Rooster]

Dont be frustrated.
You can still feed from Windows computer without "investing" a single penny in other kit.
Please see Post #1 and Post #2 of this thread:

Feed options for depreciated windows feeder

.

Many thanks for that... but its extra effort, and theres a principal here !

[abcd567]

After years of feeding from PC, this is a right kick in the teeth

I shall not be "investing" in other kit... so im voting with my feet.

Dont be frustrated.
You can still feed from Windows computer without "investing" a single penny in other kit.
Please see Post #1 and Post #2 of this thread:

Feed options for depreciated windows feeder

.

[Rooster]

After years of feeding from PC, this is a right kick in the teeth

I shall not be "investing" in other kit... so im voting with my feet.

[Oblivian]

Links have been removed.

Sent from my EML-L09 using Tapatalk

[FlyingAnt]

Because on 20th March Khan stated in the original post that the Share Your Data was foing to be withdrawn in about seven days time and it wasnt...very disappointing about the lack of further information being given by Flight Radar.

[wiedehopf]

- disabled DHCP and changed RasPi to a fixed IP address
- a script is running every five minutes pinging the router
- when ping fails network services will be restarted

Well with a static IP restarting dhcpcd shouldn't be necessary but if your solution works that's just fine

I'm curious did you have to change /etc/fstab?
Looked at the pi24 image but i don't know where that readonly mounting of / comes from.

[esom]

reading wiedehopf's valuable suggestions, we have implemented following solution:
- enabled SD card write
- disabled DHCP and changed RasPi to a fixed IP address
- a script is running every five minutes pinging the router
- when ping fails network services will be restarted

I will continue observing
Thanks a lot for the support

[wiedehopf]

He will pass by today and help me by writing a script to automatically restart the device every 6 hours, which I hope will solve the problem temporarily until I find the real cause. By the way what was the cause of your random Wifi disconnection?

I'm not quite sure what the reason was but my problem is gone now.

But restarting every 6 hours is a little crude and i already have a better script written for myself, you can use it like this:
(the mount line is just to make sure that the sd-card isn't read-only)

sudo mount -o remount ,rw /
sudo nano /root/.pingfail.bash

Copy and paste the following:

#!/bin/bash
ROUTER="192.168.2.1"
exec &>>/var/log/pingfail
sleep 30
if ! [[ -a /tmp/pingfailed ]] && ! ping $ROUTER -c5 >/dev/null
then
	echo "Restarting dhcpcd; could not reach $ROUTER"
	systemctl restart dhcpcd
	date
	touch /tmp/pingfailed
	sleep 300
	rm /tmp/pingfailed
fi

On the second line change the Ip-address after ROUTER to your routers IP address.
(The script will be run every minute and when it can't reach that IP address of the router it will restart dhcpcd which manages network connections on Raspbian)
(You should probably test if you can ping that IP address otherwise it will restart networking every 5 minutes)

Ctrl-o and enter to save, Ctrl-x to exit.

sudo crontab -e

choose nano if asked
with arrow keys go all the way down and press enter to make a new line
paste the following:

*   *   *   *   *     /bin/bash /root/.pingfail.bash

Ctrl-o and enter to save, Ctrl-x to exit.


Now you should be all set and have a nice workaround that restarts the relevant network stuff when the connection is interrupted.

You could try to update to the latest firmware / software if you want:

sudo mount -o remount ,rw /
sudo apt update
sudo apt dist-upgrade
sudo apt install rpi-update
sudo rpi-update
(type y for yes :) )
sudo reboot