1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Current VRS idiots that are banned

Discussion in 'Feeding' started by James, Mar 5, 2019.

  1. James

    James Administrator Staff Member

    ADSBx will not longer accept new VRS feeds as of June 1st 2019.

    Examples of things that VRS feeds commonly do:

    Running VRS on a Pi, instead of sending data sending direct from dump1090, using VRS to send it. This is bad and doesn't make sense at all. Usually results in IP ban when VRS crashes out.

    Running VRS with poor configuration. This results in permanent and immediate IP ban, no questions asked.

    Sending Basestation data to compressed VRS feed port. Immediate IP Ban. CompressedVRS, it was repeated multiple times in the instructions. Results in IP Ban.


    Here's a short list of the repeat offenders.

    acl bad_loops src 83.80.169.164
    acl bad_loops src 205.123.139.71
    acl bad_loops src 72.51.113.221
    acl bad_feeders_VRS src 24.98.165.212
    acl bad_feeders_VRS src 213.222.23.236
    acl bad_feeders_VRS src 97.123.34.51
    acl bad_feeders_VRS src 188.206.68.0
    acl bad_feeders_VRS src 205.123.139.71
    acl bad_feeders_VRS src 83.82.125.89
    acl bad_feeders_VRS src 109.152.191.163
    acl bad_feeders_VRS src 72.22.151.64
    acl bad_feeders_VRS src 90.248.152.216
    acl bad_feeders_VRS src 69.159.164.9


    # TURDS with BAD LAT/LON
    acl bad_feeders_VRS src 96.93.149.101
    acl bad_feeders_VRS src 24.202.248.194
    acl bad_feeders_VRS src 72.51.113.221

    # TURDS SENDING BASESTATION
    acl bad_basestation_ip src 94.214.219.75
    acl bad_basestation_ip src 67.0.86.205
    acl bad_basestation_ip src 5.138.58.164
    acl bad_basestation_ip src 98.163.100.245
    acl bad_basestation_ip src 188.207.115.242
    acl bad_basestation_ip src 75.161.5.150
    acl bad_basestation_ip src 73.87.97.118
    acl bad_basestation_ip src 173.93.103.56
    acl bad_basestation_ip src 88.65.73.73
    acl bad_basestation_ip src 50.5.60.80
    acl bad_basestation_ip src 199.115.114.75
    acl bad_basestation_ip src 178.4.74.35
    acl bad_basestation_ip src 188.206.64.15
    acl bad_basestation_ip src 95.149.160.222
    acl bad_basestation_ip src 82.2.230.135
    acl bad_basestation_ip src 67.0.56.165
    acl bad_basestation_ip src 2.24.175.119
    acl bad_basestation_ip src 2.203.120.117
    acl bad_basestation_ip src 172.106.12.212
    acl bad_basestation_ip src 62.133.103.96
    acl bad_basestation_ip src 176.252.138.190
     
    Last edited: Mar 17, 2019
    andykeck and Freqman like this.
  2. Geoff Lane

    Geoff Lane Member

    As it appears to annoy you so much I am surprised you have offered it.

    Geffers
     
  3. James

    James Administrator Staff Member

    It's not that it annoys me and maybe we will reconsider, but I spend hours every week with a high percentage of VRS feeds sending bad data.

    I know people are going to take it personally, but there are a multitude of reasons not to feed with VRS.
     
    Last edited: Mar 17, 2019
  4. jdubner

    jdubner New Member

    Not taking it personally and I'm not a Windows fanboy, but what are some of those reasons? I've been feeding ADSB-X and two others with VRS on Windows for years.

    [​IMG]

    Other than VRS, what choice do I have for Windows? I can understand the lack of love for Windows among the illuminati but a) my dedicated 24/7 Windows PC is paid for and works and b) my feeds have not given anyone any trouble as far as I can tell.

    Incidentally, FlightRadar24 sent me an email yesterday with the subject "Deactivation of Windows feeds". In part it states "... in about a week's time, we will remove FR24 Windows feeding software from "Share your data https://www.flightradar24.com/share-your-data" page."

    I made their job easier by deactivating my FR24 feed the same day.

    --
    Joe
    My last track
     
  5. MDA

    MDA Administrator Staff Member

    This thread is about feeding from VRS with wrong data format. Instead of VRS you can use dump1090 for Win and mlat-client for Win (links to download on forum, I can repost here).
    But please install first NTP service on your PC https://www.meinbergglobal.com/download/ntp/windows/ntp-4.2.8p13-win32-setup.exe
     
  6. jdubner

    jdubner New Member

    Yes, posting a link to the MLAT client for Windows would be helpful. I was unable to spot it as a "sticky" (or otherwise) on this forum but I don't visit the forum often so am not very familiar.

    As for the NTP service you linked to (windows/ntp-4.2.8p13-win32-setup.exe), how is this better than the NTP service that is installed with Windows-7 X64? (Perhaps that was generic advice for a different version of Windows.)
     
  7. MDA

    MDA Administrator Staff Member

  8. James

    James Administrator Staff Member

    VRS has issues, a lot of it is user error related.

    Sending the VRS format timestamps are usually wrong due to multiple factors.
    Data can be delayed by minutes or hours, since VRS fills the TCP buffer in sequence.
    Configuration and location issues. VRS will ignore the lat, lon of aircraft if the VRS program is setup incorrectly. I have no idea why dev would do something like that, "interesting" design choices.

    We're also finding that the raw data from dump1090 can be more useful.

    Dan and I will send you a Pi all setup if you want to use it.

    James
     
    Last edited: Mar 27, 2019
  9. jdubner

    jdubner New Member

    I'm beginning to suspect this may be at least a partial cause of the "Out-of-order position reports" problem I reported a few months ago.
    That is very generous of you but I will respectfully decline. My location is not special and I'd rather ADSB-X use its limited resources to install a feed in a location where it is badly needed (e.g. just about anywhere in the USA on 978 MHz). Besides, I'm lazy <g> -- if I keep my Windows PC receiver running I would have to build and install a new collinear antenna for the receiver on the Pi.

    Here's what I'll try to do: I'll see if I can use the Windows version of DUMP1090 with Mode-S mixer to provide a Beast, avr, or avrmlat feed independent of VRS (while still using VRS for my own purposes).

    UPDATE: I was able to do what I said in the last paragraph (above). Do I need a new port assignment in the 51xxx block for Beast format instead of my current 53077 for VRS?
    --
    Joe
     
    Last edited: Mar 26, 2019
  10. MDA

    MDA Administrator Staff Member

    If you want custom port find one free in range 51xxx and claim it.
    Did you try mlat client for windows?

    Marcin
     
  11. Paulg

    Paulg Member

    @James I assume this problem only relate to ADSB data via VRS, I currently sending Satellite data (Inmarsat 3F5) from Jaero via VRS, is this still Ok? I'll stop it if you want me to as vrs is not doing anything else
     
  12. James

    James Administrator Staff Member

    Yes only related to ADS-B data on port 41000 for VRS.

    The sat data is useful for us. There's someone working on getting pacific ocean working this month or next.
     
    Rubiconic likes this.
  13. jdubner

    jdubner New Member

    Done
    No. Not going to do that.
     
  14. MDA

    MDA Administrator Staff Member

    Thanks for feeding.