Raspberry Pi (B+, RPi2 & RPi3) - Installation instructions for Raspbian, Dump1090 & Data Feeder

Discussion in 'ADS-B Software' started by ab cd, Jan 28, 2015.

Page 2 of 2
  1. Rueganer91

    Rueganer91 New Member

    of the cache ...
    in the pf client say in the terminal :
    we were unable to locate a configuration file and have entered configuration mode by default . Please visit http:// 192.168.17.8.00:30053

    edit : after 3 hours search and configure its works ... As I have done, I do not know :(
     
    Rueganer91, Dec 10, 2016
    #21
  2. ColinXSD

    ColinXSD New Member

    I have a problem with my Data not feeding to planefinder, my system can have one of two different IP addresses, so if my Pi gets the one that isn't assigned to Planefinder my Data doesn't get out.

    I feed data to other places which don't have this problem, can it be fixed to automatically find the right address like the others?
     
    ColinXSD, Aug 3, 2017
    #22
  3. Lee Armstrong

    Lee Armstrong Administrator Staff Member

    What shows up in the log of the client? We don't lock to an IP.
     
    Lee Armstrong, Aug 4, 2017
    #23
  4. ColinXSD

    ColinXSD New Member

    Where do I find 'the log of the client'?
     
    ColinXSD, Aug 4, 2017
    #24
  5. Lee Armstrong

    Lee Armstrong Administrator Staff Member

    In the web interface under "Log View".

    IMG_2589.PNG
     
    Lee Armstrong, Aug 5, 2017
    #25
  6. ColinXSD

    ColinXSD New Member

    This mornings Log:

    2017-08-05 07:37:13.262047 [-] Successfully sent 86 aircraft updates across 10 packets (11.00KB)
    2017-08-05 07:35:24.984443 [-] Successfully sent 28 aircraft updates across 10 packets (6.00KB)
    2017-08-05 07:34:42.351701 [-] TCP connection established: 192.168.0.33:300052017-08-05
    07:34:42.351092 [-] Client restarted successfully2017-08-05 07:34:42.120407 [-] Restarting due to configuration change
    2017-08-05 07:31:59.335384 [-] Client restarted successfully2017-08-05
    07:31:59.335337 [-] Failed TCP connection to all provided addresses for: 192.168.0.36:300052017-08-05
    07:31:56.441124 [-] Received a restart request, restarting...2017-08-05
    07:31:51.175290 [-] Failed TCP connection to all provided addresses for: 192.168.0.36:300052017-08-05
    07:31:43.15273 [-] Failed TCP connection to all provided addresses for: 192.168.0.36:300052017-08-05
    07:31:34.855385 [-] Failed TCP connection to all provided addresses for: 192.168.0.36:30005

    as you can see it depends what IP address is selected as to whether it connects or not.
    I have to manually change the IP in the setup to match what the Pi is currently using.
     
    ColinXSD, Aug 5, 2017
    #26
  7. Lee Armstrong

    Lee Armstrong Administrator Staff Member

    Looks like you've configured it to a fixed IP and that IP can change with DHCP. If this is installed on that very same Pi change the IP to 127.0.0.1 and it will work even if the IP changes.

    Either that or give it a static reservation in your DHCP scope. If you do this you won't have to hunt around for the IP when you want to access the web interfaces of the client.
     
    Lee Armstrong, Aug 5, 2017
    #27
  8. ColinXSD

    ColinXSD New Member

    Thanks Lee, changing to 127.0.0.1 worked.
    I don't remember setting up a static IP originally, it just seemed to pick the address I was using at the time.

    Colin.
     
    ColinXSD, Aug 5, 2017
    #28
Page 2 of 2

Share This Page