My named feed is not my feed

Discussion in 'Feeding' started by janrinok, Feb 22, 2018.

  1. janrinok

    janrinok Member

    James,

    I wonder if you can help me please. The feed that I requested Lezardrieux_Alpha is now in the list as being on 51155, but it appears to be a feed from the Chicago area. My own feed (from NW France) is still still connected to port zCons-51155, and has been since Sunday evening non-stop. I suspect the person whose feed is actually being displayed with my name will also want to have this resolved. Many thanks.
     
  2. sierra november

    sierra november New Member

    Hi James,

    identical issue here: I do see my station "edtf-01" in the coverage chart (with active coverage info), but selecting my receiver on the customglobal-map does not bring up an single aircraft.
    I am feeding with bin/nc feed.adsbexchange.com 51280

    Thanks
     
  3. janrinok

    janrinok Member

    sierra november
    If you open up the map to show the entire world, can you see where the feed is actually coming from? I found mine in the Chicago area.
     
  4. janrinok

    janrinok Member

    James
    Quote "Ok let me figure it out. There are so many people connecting to the ports and not putting in a request - there is currently no traffic on it. If you connect and stay connected. I'll try to figure out who's also trying to connect."

    I might be able to explain what has happened. Prior to the maintenance period on 17/19 Feb, several of us had requested that our feeds on custom ports be named and allocated to us on the requested ports. During the maintenance we were all, understandably, disconnected. After the site came back on line we tried to reconnect to our previous ports but discovered that someone else had already jumped onto the feeds that we had requested, again quite understandably because all ports were free. So the requests for action that you had were now incorrect as the feeds on them were not the ones that were there before maintenance. We had to then search for alternative ports and resubmit a second request for custom port allocation. It is quite possible that the same will occur again for any unactioned port requests during future maintenance periods.

    Hopefully this will explain the cause of the confusion. I tried to leave this explanation on your own thread along with my request for assistance, but the limit of 420 characters would not permit it. Thanks for your efforts in trying to sort this out.
     
  5. James

    James Guest

    I went through all the requests and there were only 3 overlapping requests in the form. But what's happening is people are connecting and not making a request for the port - or they aren't checking to see if there is a feed on it already.



    EDTF-01 is for sure assigned in the config to port 51280 - if that's you in the area of the map then awesome! If not let me know.

    Screenshot_2018-02-24_02-00-19.png
     
  6. James

    James Guest


    51155 is just mislabeled. I corrected it and it will get updated then the config is updated again.

    Screenshot_2018-02-24_02-03-46.png
     
  7. James

    James Guest

    Not to mention there are probably 30 requests where people are feeding to ports outside the range we have configured. or they request a port but don't provide a lat and long .... or a name ...

    51666 51717 51999 52106 51331 51 328 51301 51320 51300

    https://www.adsbexchange.com/how-to-feed/custom-feed-how-to/

    Pi Feeder Port Range: Starting with 51001 and up to 51299

    VRS Port Range: Starting with 53001 and up to 53299


    I think I've got all the valid ones done and ready for the next update.
     
  8. janrinok

    janrinok Member

    I will wait for the update and see what happens. Thanks again.