ADSBx Noobie

Discussion in 'Feeding' started by Arcadia_UK, Mar 25, 2022.

  1. Arcadia_UK

    Arcadia_UK New Member

    Good morning,

    I have been uploading data to other feeders for several year but only just installed the ADSBx Image to start a new feeder.

    However, I have a couple of questions if I may, or if you could point me to the appropriate thread that could assist?

    1: As I have installed the ADSBx Image, I am unable to gain SSH access through my Putty application to manually add another feeder, whereas I could before installing this image. Do you know how I can access my Putty app, so that I can input the "sudo" "get" commands please?

    2: Whilst I appreciate that I can see my local feeding traffic. I do like to use VRS (Virtual Radar Server), so that I can continue to use the basestation.db file, mainly for "Flights Count" etc. Now, whilst I can see my ADSB aircraft on the 30005 port. Does anyone know which port it is for the MLAT? As FA uses 30106 with the Basestation Format.

    Thank you for reading.
     
    Geoff Lane likes this.
  2. wiedehopf

    wiedehopf Administrator Staff Member

  3. Arcadia_UK

    Arcadia_UK New Member

    Thanks for your reply.

    Thanks for the Port numbers, 31003 worked perfectly.

    As for the SSH into my Pi. I have set my Pi to a static IP address and so, unless this ADSBx image changes my static IP address on my router, I'll have to check my router for any changes but if I use my FR24 Image SD Card or my FA SD Card, I can access the Putty app no problem. I'm just unable to access it with this ADSBx image, as the Putty app comes up with an algorithm error. Unless of course, the ADSBx image is protecting the SD Card from users accessing the command prompt to add things.

    Here is a screenshot of my Putty Screen when trying to log in with the ADSBx Image.

    Putty Error MSg.jpg

    Thanks again :)
     
    Last edited: Mar 26, 2022
  4. James

    James Guest

    "The Couldn't agree a key exchange algorithm is expected behavior with older version of PuTTy or PuTTy integrated solutions like WInSCP."

    https://www.putty.org/

    The first remedy to try is to download a new version of Putty. It’s not an onerous task: the download is free, the license is permissive, and the file is less than 10 MB in size.

    Since you've used a static IP, you might need to clear PuTTy connections settings and recreate it.
     
    Arcadia_UK likes this.
  5. Arcadia_UK

    Arcadia_UK New Member

    Thank you James,

    I can confirm, that I was using an old (2014) version of Putty. Downloaded an updated x64 one as you suggested and I SSH'd straight in using my static IP.

    Now I have installed my second feeder and all is working well :)

    Thanks again :D
     
  6. wiedehopf

    wiedehopf Administrator Staff Member

  7. Geoff Lane

    Geoff Lane Member

    I'm finding issues with devices on networks now occasionally not being available, sometimes they resolve themselves, sometimes not. In the router I find clearing the ARP cache sometimes works.

    A useful app on a mobile device is FING - it will scan your network for connected devices, particularly useful if you have more than one Access Point. If the device shows up it will show what ports are available. This will at least let you know if ssh port 22 is being broadcast by the device.

    I'm guessing you are using Windows, I seldom use that but do know you can actually install an Ubuntu (linux) command line system. When launched it brings up what appears to be a proper Linux terminal. Only used it a few times so can't comment too much but found it worked fine.

    Geoff