1. Forum
  2. FidoNet
  3. Z2REGION25

  • BAd connects from some one

    From Vincent Coen@2:250/1 to All on Sat Apr 6 23:28:57 2024
    Hello All!

    I keep seeing bad connects with Error BO etc then it fails. Here is my log content for it :

    + 06-Apr-2024 23:30:14 mbcico[323284] Incoming IBN/TCP connection from 69.162.124.235
    + 06-Apr-2024 23:30:14 mbcico[323284] GeoIP location: United States, US NA
    + 06-Apr-2024 23:30:14 mbcico[323284] Start inbound Binkp session
    + 06-Apr-2024 23:30:14 mbcico[323284] Binkp: start session
    ! 06-Apr-2024 23:30:14 mbcico[323284] tty_read: error flag
    - 06-Apr-2024 23:30:14 mbcico[323284] Binkp: tty_status with b0
    ? 06-Apr-2024 23:30:14 mbcico[323284] Binkp: TCP rcv error, tty status: Error
    ! 06-Apr-2024 23:30:14 mbcico[323284] Binkp: error waiting for remote info
    ! 06-Apr-2024 23:30:14 mbcico[323284] Binkp: session handshake failed
    + 06-Apr-2024 23:30:14 mbcico[323284] Binkp: session finished, rc=121
    + 06-Apr-2024 23:30:16 mbcico[323284] Incoming call failed (rc=121)
    + 06-Apr-2024 23:30:16 mbcico[323284] Terminated with error 121
    + 06-Apr-2024 23:30:16 mbcico[323284] Connected 2.00s
    06-Apr-2024 23:30:16 mbcico[323284] MBCICO finished in 2.00s


    and just did a whois on it and get :

    NetRange: 69.162.64.0 - 69.162.127.255
    CIDR: 69.162.64.0/18
    NetName: LIMESTONE-NETWORKS
    NetHandle: NET-69-162-64-0-1
    Parent: NET69 (NET-69-0-0-0-0)
    NetType: Direct Allocation
    OriginAS: AS46475
    Organization: Limestone Networks, Inc. (LIMES-2)
    RegDate: 2008-06-27
    Updated: 2024-01-08
    Comment: https://www.limestonenetworks.com/
    Comment: Geofeed https://geofeed.limestonenetworks.com/geofeed.csv
    Ref: https://rdap.arin.net/registry/ip/69.162.64.0


    OrgName: Limestone Networks, Inc.
    OrgId: LIMES-2
    Address: 400 S. Akard Street
    Address: Suite 200
    City: Dallas
    StateProv: TX
    PostalCode: 75202
    Country: US
    RegDate: 2007-12-04
    Updated: 2017-01-28
    Comment: http://limestonenetworks.com/
    Ref: https://rdap.arin.net/registry/entity/LIMES-2

    ReferralServer: rwhois://rwhois.limestonenetworks.com:4321

    OrgAbuseHandle: ABUSE1804-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-214-586-0555
    OrgAbuseEmail: abuse@limestonenetworks.com
    OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE1804-ARIN

    OrgTechHandle: NOC2791-ARIN
    OrgTechName: Network Operations Center
    OrgTechPhone: +1-214-586-0555
    OrgTechEmail: noc@limestonenetworks.com
    OrgTechRef: https://rdap.arin.net/registry/entity/NOC2791-ARIN

    RTechHandle: NOC2791-ARIN
    RTechName: Network Operations Center
    RTechPhone: +1-214-586-0555
    RTechEmail: noc@limestonenetworks.com
    RTechRef: https://rdap.arin.net/registry/entity/NOC2791-ARIN

    RNOCHandle: NOC2791-ARIN
    RNOCName: Network Operations Center
    RNOCPhone: +1-214-586-0555
    RNOCEmail: noc@limestonenetworks.com
    RNOCRef: https://rdap.arin.net/registry/entity/NOC2791-ARIN

    RAbuseHandle: ABUSE1804-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-214-586-0555
    RAbuseEmail: abuse@limestonenetworks.com
    RAbuseRef: https://rdap.arin.net/registry/entity/ABUSE1804-ARIN


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/resources/registry/whois/tou/
    #
    # If you see inaccuracies in the results, please report at
    # https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
    #
    # Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
    #



    Found a referral to rwhois.limestonenetworks.com:4321.

    %rwhois V-1.5:003fff:00 rwhois.limestonenetworks.com (by Network Solutions, Inc.
    V-1.5.9.5)
    network:Class-Name:network
    network:ID:LSN-BLK-69.162.64.0/18
    network:Auth-Area:69.162.64.0/18
    network:Network-Name:LSN-69.162.64.0/18
    network:IP-Network:69.162.124.224/28
    network:IP-Network-Block:69.162.124.224 - 69.162.124.239 network:Organization-Name:Uptime Robot Service Provider Ltd. network:Organization-City:Sliema
    network:Organization-State:OT
    network:Organization-Zip:SLM1640
    network:Organization-Country:MT network:Tech-Contact;I:abuse@limestonenetworks.com network:Admin-Contact;I:abuse@limestonenetworks.com network:Updated-By:admin@limestonenetworks.com

    network:Class-Name:network
    network:ID:LSN-BLK-69.162.64.0/18
    network:Auth-Area:69.162.64.0/18
    network:Network-Name:LSN-69.162.64.0/18
    network:IP-Network:69.162.64.0/18
    network:IP-Network-Block:69.162.64.0 - 69.162.127.255 network:Organization;I:Limestone Networks network:Tech-Contact;I:ipadmin@limestonenetworks.com network:Admin-Contact;I:admin@limestonenetworks.com
    network:Created:20080129
    network:Updated:20080129
    network:Updated-By:admin@limestonenetworks.com

    %referral rwhois://root.rwhois.net:4321/auth-area=.
    %ok

    Is it you ?


    If so please fix it.


    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.8.6/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Keyop to Vincent Coen on Sun Apr 7 23:16:21 2024
    Re: BAd connects from some one
    By: Vincent Coen to All on Sat Apr 06 2024 23:28:57

    Hello All!

    I keep seeing bad connects with Error BO etc then it fails. Here is my log content for it :

    That IP is used by UptimeRobot.com

    So either you or someone else using that service to report when your BINKP service is up or down.

    If its not you, you could complain to uptimerobot.com that you don't want it checking your server.

    If you block that IP, then uptimerobot.com is likely to use one of the many other IP's it has available.

    K
  • From Vincent Coen@2:250/1 to Keyop on Mon Apr 8 11:57:17 2024
    Hello Keyop!

    Sunday April 07 2024 23:16, you wrote to me:

    Re: BAd connects from some one
    By: Vincent Coen to All on Sat Apr 06 2024 23:28:57

    Hello All!

    I keep seeing bad connects with Error BO etc then it fails. Here is
    my log content for it :

    That IP is used by UptimeRobot.com

    So either you or someone else using that service to report when your
    BINKP service is up or down.

    If its not you, you could complain to uptimerobot.com that you don't
    want it checking your server.

    If you block that IP, then uptimerobot.com is likely to use one of the
    many other IP's it has available.

    Thanks for the explain, and NO I do not use BinkP or similar.

    It is bad enough for robots to connect via the web interface and scroll through
    my system despite using robot excludes but I am some what amazed that some are doing it with the fido interface as well - total dicks not stopping it when they get perm. errors.

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.8.6/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)