No MLAT connection

Discussion in 'Feeding' started by Rubiconic, Jan 30, 2020.

  1. Rubiconic

    Rubiconic New Member

    My MLAT connection is down again since around 7 hours ago - and adsbexchange-mlat.service is up and running on my Pi.

    I checks the logs:

    Connection to feed.adsbexchange.com:31090 failed: [Errno -3] Temporary failure in name resolution

    DNS problem in my end?!
    Lost MLAT connection seems maybe to correlate with my ADSB router rebooting (on internet provider's initiative).

    Feeder connection is comming up after router reboot, though:

    Data incoming from: 195.192.xxx.xxx
    Route: beast_front Port: 51251
    Backend: beast_back
    Connected: merge-3-1
    Age: 7h34m
     
    Last edited: Feb 8, 2020
  2. wiedehopf

    wiedehopf Administrator Staff Member

    Seems like a DNS problem indeed.

    I don't know what the mlat-client does differently that it wouldn't work.
    Anyhow i'd personally just use a work-around:

    sudo nano /etc/default/adsbexchange

    Change the MLAT_SERVER line so it reads like this:

    MLATSERVER="167.114.60.74:31090"


    Alternatively you could follow this guide to not use the DNS server advertised by your router:
    https://pimylifeup.com/raspberry-pi-dns-settings/

    Which Raspbian image are you using?
    Updating it might help.
     
  3. James

    James Guest

    that's DNS indeed.
     
  4. Rubiconic

    Rubiconic New Member

    I have just changed feed.adsbexchange.com to IP 167.114.60.74 via sudo nano /etc/default/adsbexchange.
    Let's see if that fixes the problem.

    I'm on Buster Lite and up to date - kernel version 4.19.97
     
  5. wiedehopf

    wiedehopf Administrator Staff Member

    You'll need to restart the mlat-client as well:

    sudo systemctl restart adsbexchange-mlat