Menu

#8 First proxy in chain drops connection if name cannot be resolved

open
nobody
None
5
2019-01-16
2017-07-20
SimonM
No

I have a proxy chain with two hosts. Connecting all the way through using the IP address of the destination host works fine. If I use the hostname instead of IP to connect, and the hostname can't be reolved by the first proxy in the chain, then the connection is dropped at the first proxy and is not passed through to the second.
Is there some way I can configure the first proxy to pass the request through even though the name cannot be resolved?
I do not have any direct hosts configured on either proxy.

Discussion

  • Robert Simac

    Robert Simac - 2017-08-12

    Wow, the jsocks is still being used... It has been a while since last time I (or probably anyone) looked into this code... can you please post some logs or error messages being displayed at or around the time the 'connection is dropped at the 1st proxy'... I just need something to narrow down the code section to look into... Thanks.

     
  • Richard Morales

    Richard Morales - 2019-01-07

    Wow, the jsocks is still being used... It has been a while since last time I (or probably anyone) looked into this code... can you please post some logs or error messages being displayed at or around the time the 'connection is dropped at the 1st proxy'... I just need something to narrow down the code section to look into... Thanks.

     
  • Richard Morales

    Richard Morales - 2019-01-10

    505702

     
  • SimonM

    SimonM - 2019-01-11

    Hi Richard thankyou for looking into this - below is a log to stdout from the first proxy host showing two connections, the first is using IP address as destination and second is using a name - the name is not resolveable on the first proxy host, but it is resolvableon the second.
    I'm using SSH with connect-proxy proxyCmd to initiate the connection.

     ~/socks/bin $ ./SOCKS.sh
    Loading properties
    Reading file socks.properties
    Setting iddle timeout to 600000 ms.
    Setting accept timeout to 60000 ms.
    Setting udp timeout to 600000 ms.
    Adding Proxy:pita.redacted.com:1080  Version 5
    Adding Proxy:pita.redacted.com:1080  Version 5
    Using Ident Authentication scheme:
    Range:localhost; redacted.com.
    Users:Everybody is permitted.
    
    Starting SOCKS Proxy on:0.0.0.0:1080
    Accepted from:lxatomic02.redacted.com:57066
    Request version:5       Command: CONNECT
    IP:/203.22.7.7  Port:22
    Accepted from:lxatomic02.redacted.com:57160
    Aborting operation
    Main thread(client->remote)stopped.
    
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.