Announcement

Collapse
No announcement yet.

FR24 Link disconnected and nothing is uploaded. PlanePlotter and Plane Finder work OK

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Just as an update, the below better shows the error that I am experiencing. Clearly, Port 8099 (UDP) is blocked by the staff free wifi at my former employment.

    Is there a workaround here? For example, redirect to another port?

    As Plane Finder and PlanePlotter are working fine, it is strange that FR24 feeding is proving so problematic on this occassion.


    Thabks,
    Ian

    2019-10-05 08:16:03 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:16:03 | [feed][n]connecting
    2019-10-05 08:17:50 | [time][i]Synchronizing time via NTP
    2019-10-05 08:17:53 | [time][i]Time synchronized correctly, offset +0.0001 seconds, drift 0.0000 seconds/minute
    2019-10-05 08:18:32 | [feed][e]Could not connect!
    2019-10-05 08:18:32 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:18:32 | [feed][n]waiting 8 seconds
    2019-10-05 08:18:40 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:18:40 | [feed][n]connecting
    2019-10-05 08:21:10 | [feed][e]Could not connect!
    2019-10-05 08:21:10 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:21:10 | [feed][n]waiting 8 seconds
    2019-10-05 08:21:18 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:21:18 | [feed][n]connecting
    2019-10-05 08:23:48 | [feed][e]Could not connect!
    2019-10-05 08:23:48 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:23:48 | [feed][n]waiting 5 seconds
    2019-10-05 08:23:53 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:23:53 | [feed][n]connecting
    2019-10-05 08:25:21 | [stats][e]Cached feed_id=25232 for network T
    2019-10-05 08:25:21 | [stats][i]sent 16 bytes
    2019-10-05 08:26:23 | [feed][e]Could not connect!
    2019-10-05 08:26:23 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:26:23 | [feed][n]waiting 7 seconds
    2019-10-05 08:26:30 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:26:30 | [feed][n]connecting
    2019-10-05 08:27:53 | [time][i]Synchronizing time via NTP
    2019-10-05 08:27:56 | [time][i]Time synchronized correctly, offset +0.0001 seconds, drift -0.0000 seconds/minute
    2019-10-05 08:29:01 | [feed][e]Could not connect!
    2019-10-05 08:29:01 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:29:01 | [feed][n]waiting 6 seconds
    2019-10-05 08:29:07 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:29:07 | [feed][n]connecting
    2019-10-05 08:31:37 | [feed][e]Could not connect!
    2019-10-05 08:31:37 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:31:37 | [feed][n]waiting 5 seconds
    2019-10-05 08:31:42 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:31:42 | [feed][n]connecting
    2019-10-05 08:34:12 | [feed][e]Could not connect!
    2019-10-05 08:34:12 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:34:12 | [feed][n]waiting 8 seconds
    2019-10-05 08:34:20 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:34:20 | [feed][n]connecting
    2019-10-05 08:35:22 | [stats][e]Cached feed_id=25232 for network T
    2019-10-05 08:35:22 | [stats][i]sent 16 bytes
    2019-10-05 08:36:50 | [feed][e]Could not connect!
    2019-10-05 08:36:50 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:36:50 | [feed][n]waiting 9 seconds
    2019-10-05 08:36:59 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:36:59 | [feed][n]connecting
    2019-10-05 08:37:56 | [time][i]Synchronizing time via NTP
    2019-10-05 08:37:58 | [time][i]Time synchronized correctly, offset +0.0001 seconds, drift 0.0000 seconds/minute
    2019-10-05 08:39:30 | [feed][e]Could not connect!
    2019-10-05 08:39:30 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:39:30 | [feed][n]waiting 7 seconds
    2019-10-05 08:39:37 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:39:37 | [feed][n]connecting
    2019-10-05 08:42:08 | [feed][e]Could not connect!
    2019-10-05 08:42:08 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:42:08 | [feed][n]waiting 9 seconds
    2019-10-05 08:42:17 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:42:17 | [feed][n]connecting
    2019-10-05 08:44:47 | [feed][e]Could not connect!
    2019-10-05 08:44:47 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:44:47 | [feed][n]waiting 5 seconds
    2019-10-05 08:44:52 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:44:52 | [feed][n]connecting
    2019-10-05 08:45:22 | [stats][e]Cached feed_id=25232 for network T
    2019-10-05 08:45:22 | [stats][i]sent 16 bytes
    2019-10-05 08:47:23 | [feed][e]Could not connect!
    2019-10-05 08:47:23 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:47:23 | [feed][n]waiting 5 seconds
    2019-10-05 08:47:28 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:47:28 | [feed][n]connecting
    2019-10-05 08:47:58 | [time][i]Synchronizing time via NTP
    2019-10-05 08:48:00 | [time][i]Time synchronized correctly, offset -0.0000 seconds, drift -0.0000 seconds/minute
    2019-10-05 08:49:59 | [feed][e]Could not connect!
    2019-10-05 08:49:59 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:49:59 | [feed][n]waiting 5 seconds
    2019-10-05 08:50:04 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:50:04 | [feed][n]connecting
    2019-10-05 08:52:34 | [feed][e]Could not connect!
    2019-10-05 08:52:34 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:52:34 | [feed][n]waiting 7 seconds
    2019-10-05 08:52:41 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:52:41 | [feed][n]connecting
    2019-10-05 08:55:12 | [feed][e]Could not connect!
    2019-10-05 08:55:12 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:55:12 | [feed][n]waiting 9 seconds
    2019-10-05 08:55:21 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:55:21 | [feed][n]connecting
    2019-10-05 08:55:22 | [stats][e]Cached feed_id=25232 for network T
    2019-10-05 08:55:22 | [stats][i]sent 16 bytes
    2019-10-05 08:57:52 | [feed][e]Could not connect!
    2019-10-05 08:57:52 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 08:57:52 | [feed][n]waiting 7 seconds
    2019-10-05 08:57:59 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 08:57:59 | [feed][n]connecting
    2019-10-05 08:58:00 | [time][i]Synchronizing time via NTP
    2019-10-05 08:58:02 | [time][i]Time synchronized correctly, offset -0.0005 seconds, drift -0.0000 seconds/minute
    2019-10-05 09:00:29 | [feed][e]Could not connect!
    2019-10-05 09:00:29 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 09:00:29 | [feed][n]waiting 6 seconds
    2019-10-05 09:00:35 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 09:00:35 | [feed][n]connecting
    2019-10-05 09:03:05 | [feed][e]Could not connect!
    2019-10-05 09:03:05 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-05 09:03:05 | [feed][n]waiting 6 seconds
    2019-10-05 09:03:11 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-05 09:03:11 | [feed][n]connecting

    Comment


    • #17
      You could make a TCP stream of the raw beast data to another machine and then run fr24feed there.
      It seems outbound TCP connections are not a problem.

      So if the other machine you want to feed from is behind a router, you'll have to forward port 30004.
      On the other machine you run any dump1090 you want an configure it net-only.
      Then if the outside IP address of the router is changing you need a dyndns address.

      On the machine in the restricted network you run the data redirection.
      You could use the redirection-only install of combine1090: https://github.com/wiedehopf/combine...direction-only

      TARGET would be the outside IP address of the router or the dyndns address you have plus port 30004 which you have forwarded.

      Change sources to only be 127.0.0.1
      Ports you only want 30005

      After having that all configured you can install fr24feed on the other machine and feed from there.


      Pretty sure FR24 has no provisions for feeding in this case.
      The use-http is the only option i know and i'm not sure if it has any effect anymore.
      If you want to hear from FR24 you'll have to open a ticket, they don't seem to care about this forum.

      Comment


      • #18
        Hi Wiedehopf,

        Thank you for all of your help so far. It is really apreciated. Actually, I already raised a ticket with FR24, but this forum has been far more informative so far.

        So, I am reasonably IT literate, but a bit of a newbie to Linux (Ubuntu 18.04 on the 32-bit Toughbooks and also a single Rp3 running here at home.

        Therefore, please may I ask for a little more detailed info on your suggested TCP stream of raw data? This intertests me greatly, but I need to learn a little bit more first.

        So, current set-up is Dump1090 Mutability feeding Plane Finder and FR24 installed through the ADS-B Receiver Project (Joe Prochazka). I am however familiar with reinstalling the settings file / co-ordinates individually for all three. I then also feed PlanePlotter through virtual Windows (using Wine).

        Can I therefore redirect only the FR24 feed to TCP stream of raw data, or does this come from within Dump1090 Mutability? If the latter, can I still directly feed Plane Finder and PlanePlotter (the latter through Wine) directly from source, or is it "all or nothing"?

        Would I need the redirection-only install of combine1090: https://github.com/wiedehopf/combine...direction-only, which i am guessing that you wrote? Or is that an option of choice? Would it replace or run alongside the existing Dump1090 Mutability from ADS-B Receiver Project?

        I can set up another identical CF-18 Toughbook (with Ubuntu 18.04) at home and run 24/7 as the "other machine". Logically, I could feed all three from said machine, with the raw data from the Gatwick one. My home environment is reasonable quick Wifi (through Virgin Media) and I already feed all three from my home set-up (roof aerial) through the RPi, so would need to ensure that the "other machine" did not create conflicts there. (I think that this might possibly occur with PlanePlotter if more than one installation is running from the same IP address).

        Sorry if I ask any stupid questions above. Your continued help much apreciated.

        Ian

        Comment


        • #19
          The stream of data is just a copy of all messages received by dump1090, you can continue running the other feeders as is.

          The redirection-only install won't do anything except run socat to forward the data. (maybe forward is a better word then redirect)

          On the additional machine at your home you'll need to configure dump1090 with the --net-only parameter, otherwise it won't run without a dongle.
          I'm not familiar with dump1090-mutability and how to configure it though.

          Here is an instruction on how to install dump1090-fa: https://github.com/wiedehopf/adsb-wi...ng-dump1090-fa
          That configuration i'm very familiar with.
          Oh i guess you need to compile it, that's why you are using the script.
          Gotta do a script that compiles and installs dump1090-fa for such cases, the adsb-receiver project is just so unflexible and added to that not that well maintained. (still a nice tool)
          You can compile it like explained here: https://github.com/wiedehopf/adsb-wi...fa-from-source

          The just replace "--device-index 0" with "--net-only" in the configuration file /etc/default/dump1090-fa
          That will have it running in net-only mode.
          Set up fr24feed to use beast-tcp as receiver from 127.0.0.1 on port 30005.
          (as described in the Installing dump1090-fa explanation)


          Note for a message rate of around 1500 messages per second, the datastream will use around 25 KByte/s of bandwidth.
          That usually isn't a problem though.
          Last edited by wiedehopf; 2019-10-05, 11:26.

          Comment


          • #20
            Thank you again for the detailed reply.

            So it looks like I will need Dump1090-fa rather than -Mutability on my Gatwick machine, then to install Combine1090. I am assuming that to install Combine1090 alongside Dump1090--Mutability will simply not work.

            I checked out the dump1090-mutability configuration file on an identical Toughbook at home and noted:

            # If set to "none", dump1090 will be started in --net-only mode
            DEVICE=""


            Therefore, changing this to DEVICE="none" would achieve the required result for the “other machine” which will be running at home???


            Cheers, Ian

            Comment


            • #21
              The data redirection will need to be on the machine with the source data.
              The redirection part doesn't care which program it's talking to.

              Yeah, that should be enough to use --net-only mode.
              No need for dump1090-fa in that case if you don't want to use it.

              I'm not sure if the adsb receiver project is working anymore for that as the github for dump1090-mutability was recently changed.
              Anyway i've already outlined how to use dump1090-fa.

              Comment


              • #22
                Thanks again.

                I just tried to install Data Redirection Only (as I read that the full Combine1090 installation requires Dump1090-fa) and I am getting the following error message:

                av6@Aerovision10:~$ sudo bash -c "$(wget -O - https://raw.githubusercontent.com/wiedehopf/combine1090/master/redirect-only.sh)"
                --2019-10-05 18:50:37-- https://raw.githubusercontent.com/wi...direct-only.sh
                Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 199.232.56.133
                Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|199.232.56.133|:443... connected.
                HTTP request sent, awaiting response... 404 Not Found
                2019-10-05 18:50:37 ERROR 404: Not Found.

                Comment


                • #23
                  Try again

                  Seems i forgot to add that file which i already had locally.

                  Comment


                  • #24
                    Thanks. Now installed.

                    Please confirm TARGET should be home IP address, or specific "other machine" IP address, e.g. 82.6.239.44:30004 or 192.168.0.202:30004? Also, why 30004, not 30005? Many thanks again.

                    Ian

                    Comment


                    • #25
                      30004 is the port for incoming data.
                      30005 is the port for outgoing data.

                      the target IP address needs to be reachable from the machine which has the actual receiver/antenna.
                      192.168.0.202 is a local address and can't be reached from the internet.
                      That's why i said public IP address and port forwarding.

                      Comment


                      • #26
                        Thanks.

                        What (if anything) st the bottom of the file will need altering (seeing as I am not using Dump1090-fa at either source or target)?

                        #options for dump1090-fa where all the data goes
                        RECEIVER_OPTIONS="--net-only"
                        DECODER_OPTIONS="--max-range 360"
                        NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 0.2 --net-ri-port 29001 --net-ro-port 29002 --net-sbs-port 29003 --$
                        JSON_OPTIONS="--json-location-accuracy 1"

                        Comment


                        • #27
                          Those options don't have any effect when using it redirect-only.

                          Those are just configuration options for running a second instance of dump1090-fa.
                          But as i said that's not used in your case.

                          Comment


                          • #28
                            Thanks. I think the home end is now working fine. However, at source end I cannot see combine1090 when I run TOP.

                            At home, this is now to FR24 output:

                            Flightradar24 Feeder/Decoder
                            Linux/generic/i686/1.0.18-5
                            Updated: 09:10:18 GMT+0100 (British Summer Time)
                            FR24 Link: Connected via UDP
                            FR24 Radar Code: T-EGKK139
                            Aircraft Tracked (ModeS & ADS-B): 0
                            Aircraft Uploaded: N/A
                            Receiver: beast-tcp, Connected
                            MLAT running: N/A
                            Actions:


                            At my source end I have the following (my home external IP address is "X'ed" out):

                            # Append the IP addresses of the feeders you want to combine in the next line:
                            SOURCES= 127.0.0.1 or SOURCES=127.0.0.1 - is this correct and is a space needed or not needed after the "=" sign?

                            # which ports to collect beast data from (for piaware/dump1090-fa this is 30005 for ADS-B and 30105 for MLAT)
                            PORTS= 30005 or PORTS=30005 - is this correct and is a space needed or not needed after the "=" sign?

                            #where the data shall go, for display under /combine1090 leave it as is.
                            TARGET=XX.X.XXX.XX:30004 or TARGET= XX.X.XXX.XX:30004 - is this correct and is a space needed or not needed after the "=" sign?

                            I assume that I do not need to uncomment the bit below?
                            # for the IP addresses in SOURCES all PORTS are used
                            # If your sources have the beast data on different ports, you can use CUSTOM to configure hostort combinations instead.
                            # uncomment and add IP addresses with ports for redirection
                            #CUSTOM=127.0.0.1:29005 127.0.0.1:29999


                            Finally, I am not convinced that "sudo systemctl restart combine1090" is having any effect. Is there any way to check please (other than in "TOP"?

                            Thank you again,
                            Ian

                            Comment


                            • #29
                              Another question. Do I need to "Port Forward" (on my home router) port 30004 (or 30005) to the computer (192.168.0.108) at home that is receiving the Dump1090 data?

                              Ian

                              Comment


                              • #30
                                The output from the source machine upon command av6@Aerovision6:~$ sudo systemctl status combine1090

                                ● combine1090.service - combine1090 - redirect beast data
                                Loaded: loaded (/lib/systemd/system/combine1090.service; enabled; vendor preset: enabled)
                                Active: active (running) since Sun 2019-10-06 10:59:11 BST; 1min 50s ago
                                Docs: https://github.com/wiedehopf/combine1090
                                Main PID: 14953 (combine1090.sh)
                                Tasks: 5 (limit: 3513)
                                CGroup: /system.slice/combine1090.service
                                ├─14953 /bin/bash /usr/local/bin/combine1090.sh
                                ├─14956 /bin/bash /usr/local/bin/combine1090.sh
                                ├─14957 /bin/bash /usr/local/bin/combine1090.sh
                                ├─14958 sleep 1024
                                └─14959 socat -d -u TCP:127.0.0.1:30005,keepalive,keepidle=30,keepintv l=30,keepcnt=2,connect-timeout=30,retry=2,interval=15 TCP:XX.X

                                Oct 06 10:59:11 Aerovision6 systemd[1]: Started combine1090 - redirect beast data.
                                Oct 06 10:59:11 Aerovision6 combine1090.sh[14953]: Starting data redirection with socat for combine1090: Sun 6 Oct 10:59:11 BST 2019
                                Oct 06 10:59:11 Aerovision6 combine1090.sh[14953]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004


                                Ian

                                Comment

                                Working...
                                X