Skip to content
This repository has been archived by the owner on May 2, 2022. It is now read-only.
This repository has been archived by the owner on May 2, 2022. It is now read-only.

wlx interface timeout, https not available, socks error  #88

Open
@sircotra

Description

@sircotra

Hi,
I'm testing dispatch-proxy with Xubuntu 16.04.5 LTS on my pc with "eno1" and "wlx..." interfaces.
I have three problem:

1 - the wlx interface doing nothing and blocking the entire process. I'm using firefox with 127.0.0.2 8081 on proxy (only http proxy). Output:
dispatch start -H 127.0.0.2 -p 8081 --debug --http
HTTP server started on 127.0.0.2:8081
Dispatching to addresses 192.168.1.154@1, 192.168.2.152@1
request [49c52e] http://www.pubbliaccesso.gov.it/logo/elenco.php
dispatch [49c52e] 192.168.1.154
end [49c52e] clientRequest
response [49c52e] 200
request [83d6de] http://www.pubbliaccesso.gov.it/layout/stili/logo.css
dispatch [83d6de] 192.168.2.152
end [83d6de] clientRequest

... after long time
error [83d6de] clientRequest
Error: connect ETIMEDOUT 93.147.186.151:80
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1063:14)

The wlx interface works because I use it daily.

2 - the https connections are not available with single or both connections. Firefox with full proxy protocols configuration:
Browser: https://www.google.it Secure connection failed

3 - error socks
Unsupported SOCKS version: 71

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions