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

  • wiedehopf
    replied
    Just in case you want a improved local map on your home relay:
    https://github.com/wiedehopf/tar1090#tar1090

    Or some graphs:
    https://github.com/wiedehopf/graphs1090#graphs1090

    Leave a comment:


  • Aerovision
    replied
    Wiedehopf, I have now sorted out Dyndns - something totally new to me! Combine1090 still working perfectly.

    Ian

    Leave a comment:


  • Aerovision
    replied
    Thanl you again for your help and patience!

    Leave a comment:


  • wiedehopf
    replied
    There is no reason not to use port 80, unless you want to run a webserver on your home IP address

    And here you can see why it's useless to block all those other ports.
    Sophisticated malware will try using port 80 to "phone home" anyway.

    Anyway pseudo security is big these days. Better apply some snake oil to protect from $stuff.
    I guess it can help against some stuff, but still, it's stupid

    Glad you got it working!
    Last edited by wiedehopf; 2019-10-06, 22:10.

    Leave a comment:


  • Aerovision
    replied
    OK, we are getting somewhere with Port 80.

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


    Assume that I can't use Port 80 longterm, so we need to find a suitable port I guess?

    Cheers,
    Ian

    Leave a comment:


  • Aerovision
    replied
    Does this look right?

    # Service Name External Start Port Internal Start Port Internal IP address

    2 LGW D1090 80 30004 192.168.1.208


    I am using a Netgear Nighthawk R8000 router and my Virgin Media Superhub as a modem.

    Leave a comment:


  • Aerovision
    replied
    av6@Aerovision8:~$ sudo netstat -tl | grep 30004
    [sudo] password for av6:
    tcp 0 0 0.0.0.0:30004 0.0.0.0:* LISTEN
    tcp6 0 0 [::]:30004 [::]:* LISTEN

    I used to have a Windows 7 Toughbook at my former office, that only sucessfully uploaded to PlanePlotter. I used to port onto it with TeamViewer, but now use Any Desk, which is better IMO. Never had a problem.

    I have converted several old Toughbooks (all 32-bit) to Linux because FR24 no longer takes Windows data and Plane Finder now only accepts data from 64-bit Windows machines. But, I am very much learning Linux as i go along......

    The fact that the Linux machine at Gatwick worked fine for all three when tested at home, then fine for PlanePlotter and Plane Finder when at Gatwick does suggest a firewall issue with certain ports. I will work on trying the 80 port test.

    Thanks again,
    Ian

    Leave a comment:


  • wiedehopf
    replied
    No, some routers allow one port that's coming in to be redirected to another port on the machine behind the router.

    Your interface allows that as well.
    External port 80
    Internal port 30004

    Then on the source machine change the TARGET in the combine1090 configuration to port 80 (address:80)
    also restart combine1090 of course after changing that.

    This should circumvent possible port restrictions the source machine has.
    I'm confused though, how are you even connecting to the source machine if it's behind their firewall?


    Just for confirmation, let's check on the target machine
    sudo netstat -tl | grep 30004
    Last edited by wiedehopf; 2019-10-06, 16:42.

    Leave a comment:


  • Aerovision
    replied
    av6@Aerovision8:~$ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp6s2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:0b:97:a3:90:71 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.208/24 brd 192.168.1.255 scope global dynamic noprefixroute enp6s2
    valid_lft 55767sec preferred_lft 55767sec
    inet6 fe80::f3f7:da78:e6b5:dec8/64 scope link noprefixroute
    valid_lft forever preferred_lft forever
    3: wlp6s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:16:6f:ae:7b:5d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.108/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp6s3
    valid_lft 84270sec preferred_lft 84270sec
    inet6 fe80::947a:5ba1:546c:2e7a/64 scope link noprefixroute
    valid_lft forever preferred_lft forever
    inet6 fe80::fe5c:4425:6d06:be55/64 scope link dadfailed tentative noprefixroute
    valid_lft forever preferred_lft forever


    Port_Forwarding.jpg

    And, just checking, use combine1090 to forward port 80 to 30004 on target machine???


    Thanks.

    Leave a comment:


  • wiedehopf
    replied
    Can you show me a screenshot of the port forwarding?

    If you can forward port 80 on the router to port 30004 on the target machine, that might help.
    (wherever your source machine is might be really paranoid and stupid about port controls, but port 80 usually works because hey, you can't browse without it)
    With that forward you'd have to accordingly change TARGET to match the new port.

    And the output of
    ip a
    on the target machine.

    Also are you sure you are using the internet facing IP of your router as a TARGET?
    Last edited by wiedehopf; 2019-10-06, 15:46.

    Leave a comment:


  • Aerovision
    replied
    Thanks. Yes, aware that IP will change. I have not yet looked into dyndns. I wanted to suceed with proof of concept first.

    Port forwarding changed to TCP. Still no difference.

    Check of pgrep -a dump1090 on target machine produced:
    av6@Aerovision8:~$ pgrep -a dump1090
    7247 /usr/bin/dump1090-mutability --net-only --ppm 0 --fix --lat 51.14508 --lon -000.16533 --max-range 300 --net-ri-port 30001 --net-ro-port 30002 --net-bi-port 30004,30104 --net-bo-port 30005 --net-sbs-port 30003 --net-heartbeat 60 --net-ro-size 500 --net-ro-interval 1 --net-buffer 2 --stats-every 3600 --write-json /run/dump1090-mutability --write-json-every 1 --json-location-accuracy 1 --quiet


    Thanks,
    Ian

    Leave a comment:


  • wiedehopf
    replied
    You are aware the Home IP will change?

    That's why i wrote you should use dyndns.

    beast input port looks correct.
    maybe check like this if it's actually running on the target machine.
    pgrep -a dump1090

    As for the forwarding, it's TCP. Do you have it forwarded to the target machine?

    The source machine is indicating it can't connect to the target.
    It may be that they are limiting TCP outbound ports as well.
    Not sure which ports the other feeders use.

    But my guess is that you haven't quite setup the forwarding correctly or the IP is wrong.
    Last edited by wiedehopf; 2019-10-06, 12:57.

    Leave a comment:


  • Aerovision
    replied
    One other point to check. Home network port forwarding of port 30004 - TCP & UDP, just UDP or just TCP? I opted for TCP & UDP.

    Ian

    Leave a comment:


  • Aerovision
    replied
    Thanks Wiedehopf. I am somewhat new to Linux, so please be gentle with me. I am fasinated by this, but I have to take one step at a time. In no way was I suggesting that your supplied data was not correct.

    Port 30004 is now port forwarded to 192.168.1.208 on my home network.

    Not sure exactly where "30004" should be within the dump1090 configuration. However, is the following correct?:

    # Port to listen on for Beast-format input connections. 0 disables.
    BEAST_INPUT_PORT="30004,30104"



    Result of sudo journalctl --no-pager -u combine1090 on source computer:
    av6@Aerovision6:~$ sudo journalctl --no-pager -u combine1090
    -- Logs begin at Tue 2019-04-16 17:51:36 BST, end at Sun 2019-10-06 12:57:36 BST. --
    Oct 06 07:55:32 Aerovision6 systemd[1]: Started combine1090 - redirect beast data.
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: Starting data redirection with socat for combine1090: Sun 6 Oct 07:55:33 BST 2019
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: 127.0.0.1:29004
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: 2019/10/06 07:55:33 socat[13473] E write(6, 0x1cf8e90, 510): Connection refused
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: Lost Connection: SOURCE: 127.0.0.1:30005 TARGET: 127.0.0.1:29004
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: Redirecting: SOURCE: 127.0.0.1:30105 TARGET: 127.0.0.1:29004
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: 2019/10/06 07:55:33 socat[13478] E read(5, 0x1c66e90, 8192): Connection refused
    Oct 06 07:55:33 Aerovision6 combine1090.sh[13467]: Lost Connection: SOURCE: 127.0.0.1:30105 TARGET: 127.0.0.1:29004

    Oct 06 12:54:17 Aerovision6 combine1090.sh[8283]: 2019/10/06 12:54:17 socat[8562] E connecting to AF=2 XX.X.XXX.XX:30004: Connection timed out
    Oct 06 12:54:17 Aerovision6 combine1090.sh[8283]: Lost Connection: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:54:36 Aerovision6 combine1090.sh[8283]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:56:36 Aerovision6 combine1090.sh[8283]: 2019/10/06 12:56:36 socat[8575] E connecting to AF=2 XX.X.XXX.XX:30004: Connection timed out
    Oct 06 12:56:36 Aerovision6 combine1090.sh[8283]: Lost Connection: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:57:01 Aerovision6 combine1090.sh[8283]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004

    Results of sudo systemctl status combine1090 on source computer:
    av6@Aerovision6:~$ sudo systemctl status combine1090
    [sudo] password for av6:
    ● 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 12:21:43 BST; 31min ago
    Docs: https://github.com/wiedehopf/combine1090
    Main PID: 8283 (combine1090.sh)
    Tasks: 5 (limit: 3513)
    CGroup: /system.slice/combine1090.service
    ├─8283 /bin/bash /usr/local/bin/combine1090.sh
    ├─8286 /bin/bash /usr/local/bin/combine1090.sh
    ├─8287 /bin/bash /usr/local/bin/combine1090.sh
    ├─8372 sleep 1024
    └─8562 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 12:45:10 Aerovision6 combine1090.sh[8283]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:47:10 Aerovision6 combine1090.sh[8283]: 2019/10/06 12:47:10 socat[8396] E connecting to AF=2 XX.X.XXX.XX:30004: Connection timed out
    Oct 06 12:47:10 Aerovision6 combine1090.sh[8283]: Lost Connection: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:47:32 Aerovision6 combine1090.sh[8283]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:49:32 Aerovision6 combine1090.sh[8283]: 2019/10/06 12:49:32 socat[8402] E connecting to AF=2 XX.X.XXX.XX:30004: Connection timed out
    Oct 06 12:49:32 Aerovision6 combine1090.sh[8283]: Lost Connection: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:49:56 Aerovision6 combine1090.sh[8283]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:51:56 Aerovision6 combine1090.sh[8283]: 2019/10/06 12:51:56 socat[8418] E connecting to AF=2 XX.X.XXX.XX:30004: Connection timed out
    Oct 06 12:51:56 Aerovision6 combine1090.sh[8283]: Lost Connection: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004
    Oct 06 12:52:17 Aerovision6 combine1090.sh[8283]: Redirecting: SOURCE: 127.0.0.1:30005 TARGET: XX.X.XXX.XX:30004



    Again, thank you for your assistance.
    Ian

    Leave a comment:


  • wiedehopf
    replied
    Check the log:

    sudo journalctl --no-pager -u combine1090

    The spaces you mentioned are irrelevant, i wouldn't supply a default configuration that doesn't work.


    And yes of course you need to forward the port 30004, that's what i already wrote.
    What's not clear about that?
    The source computer connects to your home router IP, that router needs to know what to with the connection coming in on 30004.
    So you forward that connections on that port to the computer that wants the data.

    Maybe check the target computer dump1090 configuration for 30004, if that's enabled there.

    Leave a comment:

Working...
X