A user guide that is easy to understand

ravichaudhary133 commented 1 year ago

Discussed in https://github.com/Project-Faster/qpep/discussions/44

^{Originally posted by **ravichaudhary133** March 13, 2023} Dear dev, requesting you to please make the instructions to setup server and client a bit more comprehensive as people like me(the beginners) find it difficult to establish a successful connection between server and client even after reading the current readme.txt multiple times.

ravichaudhary133 commented 1 year ago

I would like to share the problem I am facing establishing connection with the server- I have one vps on Oracle cloud where I have hosted the qpep server without making changes to the configuration file, and it starts listening on default ports once I run the command. The client is my PC that is connected to my vsat router via an Ethernet cable. The problem is I am unable to configure the client to handshake with the server. Couldn't derive the 'gateway address', 'port', 'listen address' and 'listen port'. Everytime I use the public IP of server as gateway the windivert diverts the listen address to some unknown IP and couldn't establish connection.

ravichaudhary133 commented 1 year ago

If there is any other active platform where people share the bugs and queries, please let me know. @parvit @bizzbyster any help would be appreciated.

bizzbyster commented 1 year ago

@ravichaudhary133 we are working to respond to these.

ravichaudhary133 commented 1 year ago

@bizzbyster can I DM you on some platform like on telegram or any other platform like it?

bizzbyster commented 1 year ago

Yes jus my GitHub username @gmail.Com.

On Sun, May 21, 2023 at 11:33 AM ravichaudhary133 @.***> wrote:

@bizzbyster https://github.com/bizzbyster can I DM you on some platform?

— Reply to this email directly, view it on GitHub https://github.com/Project-Faster/qpep/issues/54#issuecomment-1556208457, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6RAADKK2S2EKVPE4COS6TXHIYT7ANCNFSM6AAAAAAYJJVXZI . You are receiving this because you were mentioned.Message ID: @.***>

parvit commented 1 year ago

Hi @ravichaudhary133, thanks for your interest in the project.

You are right that the README has fallen behind, I'll update the README with update instructions in the near future.

In the meantime please follow these indications for configuring:

Server (qpep.yml)

listenaddress: local listening address where quic connections are received

if you have an address with a public facing address and a local address (via NAT for example), this needs to be the local address
listenport: local listening port for quic connections

this port needs to be open in the firewall / router for udp traffic
apiport: local port for the api connections

no need to open to the outside network
gateway,port: not necessary for server config

Client (qpep.yml)

listenaddress: local listening address where tcp connections are received

can be 0.0.0.0 for autodetection but in some scenarios its necessary to specify it explicitly (can be overriden via the menu in the tray app)
listenport

local listening port for tcp redirected/proxied connections
apiport

api port for the api connections
gateway

remote (public) address of the qpep server
port

remote (udp) port for qpep server
preferproxy

true/false, allows to prefer using the proxy mechanism first for connecting instead of diverter

If you make a new test, please also attach the qpep-server.log and qpep-client.log files generated.

ravichaudhary133 commented 1 year ago

Thank you for the response @parvit. Now, when i try to make connection with the server, error 401 emerges on the client side. Here the the necessary logs and config files.

qpepconfigserver.txt qpep-serverlog.txt qpepclientconfig.txt qpepclientlog.txt

parvit commented 1 year ago

Are you using the client on linux? It has not been adapted to the redirection improvements so in the meantime the client only works on windows currently.

Il giorno gio 25 mag 2023 alle ore 16:36 ravichaudhary133 < @.***> ha scritto:

Thank you for the response @parvit https://github.com/parvit. Now, when i try to make connection with the server, error 401 emerges on the client side. Here the the necessary logs and config files.

qpepconfigserver.txt https://github.com/Project-Faster/qpep/files/11566001/qpepconfigserver.txt qpep-serverlog.txt https://github.com/Project-Faster/qpep/files/11566041/qpep-serverlog.txt

— Reply to this email directly, view it on GitHub https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563023000, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGJD4ELYOP4BU4OPESAMPLXH5U53ANCNFSM6AAAAAAYJJVXZI . You are receiving this because you were mentioned.Message ID: @.***>

--

Vittorio Parrella Software Developer

@.*** Naples, Italy

ravichaudhary133 commented 1 year ago

Okay then, i used windows machine as client and i think the connection was established successfully but the icon tray always shows connecting. Initially the client logs were suggestive of successful transfer of data between client and server but later the connections timed out. Here are the logs- qpep-client.log

parvit commented 1 year ago

It seems it is trying to connect to the 9443 port with quic, is that correct?

Il giorno gio 25 mag 2023 alle ore 20:40 ravichaudhary133 < @.***> ha scritto:

Okay then, i used windows machine as client and i think the connection was established successfully but the icon tray always shows connecting. Initially the client logs were suggestive of successful transfer of data between client and server but later the connections timed out. Here are the logs- qpep-client.log https://github.com/Project-Faster/qpep/files/11568109/qpep-client.log

— Reply to this email directly, view it on GitHub https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563326871, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGJD4DMMC5C4UETZDBPZVTXH6RSLANCNFSM6AAAAAAYJJVXZI . You are receiving this because you were mentioned.Message ID: @.***>

--

Vittorio Parrella Software Developer

@.*** Naples, Italy

ravichaudhary133 commented 1 year ago

Yes, this is what is there in server config.

On Fri, May 26, 2023, 01:35 Vittorio Parrella @.***> wrote:

It seems it is trying to connect to the 9443 port with quic, is that correct?

Il giorno gio 25 mag 2023 alle ore 20:40 ravichaudhary133 < @.***> ha scritto:

Okay then, i used windows machine as client and i think the connection was established successfully but the icon tray always shows connecting. Initially the client logs were suggestive of successful transfer of data between client and server but later the connections timed out. Here are the logs- qpep-client.log https://github.com/Project-Faster/qpep/files/11568109/qpep-client.log

— Reply to this email directly, view it on GitHub < https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563326871>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AWGJD4DMMC5C4UETZDBPZVTXH6RSLANCNFSM6AAAAAAYJJVXZI

. You are receiving this because you were mentioned.Message ID: @.***>

--

Vittorio Parrella Software Developer

@.*** Naples, Italy

— Reply to this email directly, view it on GitHub https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563443485, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2VLFWTZGLTBUBLAIAYKYTXH63QZANCNFSM6AAAAAAYJJVXZI . You are receiving this because you were mentioned.Message ID: @.***>

parvit commented 1 year ago

Can you send the client config ? thanks

Il giorno ven 26 mag 2023 alle ore 04:42 ravichaudhary133 < @.***> ha scritto:

Yes, this is what is there in server config.

On Fri, May 26, 2023, 01:35 Vittorio Parrella @.***> wrote:

It seems it is trying to connect to the 9443 port with quic, is that correct?

Il giorno gio 25 mag 2023 alle ore 20:40 ravichaudhary133 < @.***> ha scritto:

Okay then, i used windows machine as client and i think the connection was established successfully but the icon tray always shows connecting. Initially the client logs were suggestive of successful transfer of data between client and server but later the connections timed out. Here are the logs- qpep-client.log <https://github.com/Project-Faster/qpep/files/11568109/qpep-client.log

— Reply to this email directly, view it on GitHub < https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563326871 , or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AWGJD4DMMC5C4UETZDBPZVTXH6RSLANCNFSM6AAAAAAYJJVXZI

. You are receiving this because you were mentioned.Message ID: @.***>

--

Vittorio Parrella Software Developer

@.*** Naples, Italy

— Reply to this email directly, view it on GitHub < https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563443485>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AL2VLFWTZGLTBUBLAIAYKYTXH63QZANCNFSM6AAAAAAYJJVXZI

. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/Project-Faster/qpep/issues/54#issuecomment-1563740477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGJD4DDGDX5PPQ2IZ3LMCLXIAKATANCNFSM6AAAAAAYJJVXZI . You are receiving this because you were mentioned.Message ID: @.***>

--

Vittorio Parrella Software Developer

@.*** Naples, Italy

ravichaudhary133 commented 1 year ago

Here it is- ack: 10 ackdelay: 25 congestion: 4 decimatetime: 100 maxtries: 10 gateway: 144...* port: 9443 apiport: 444 listen address: 192.168.1.126 listenport: 5443 multistream: true verbose: false preferproxy: false varackdelay: 0 threads: 4

ravichaudhary133 commented 1 year ago

The client log says - Failed to Open QUIC Session: timeout: no recent network activity

Does gateway in server config plays any role. Also @parvit are you able to establish connection with my qpep server with IP address as their in log files attached above and port as 123 and api 444. Really annoyed to see it not working

ravichaudhary133 commented 1 year ago

Btw, when I try to check for open ports on my server through third part port scanner, I can only reach port 444 as open and the qpep server port always stay closed.

ravichaudhary133 commented 1 year ago

Okay, it seems that my isp firewall is blocking connection with the server.

Can i redirect the traffic of qpep through another tunnel like udp2raw. I use udp2raw tunnel to bypass the crappy firewall by faking my udp traffic from wireguard as icmp requests. Otherwise, it spoofs all the udp/tcp traffic and blocks intermittently.

ravichaudhary133 commented 1 year ago

Okay, it seems that my isp firewall is blocking connection with the server.

Can i redirect the traffic of qpep through another tunnel like udp2raw. I use udp2raw tunnel to bypass the crappy firewall by faking my udp traffic from wireguard as icmp requests. Otherwise, it spoofs all the udp/tcp traffic and blocks intermittently.

parvit commented 1 year ago

Okay, it seems that my isp firewall is blocking connection with the server.

Can i redirect the traffic of qpep through another tunnel like udp2raw. I use udp2raw tunnel to bypass the crappy firewall by faking my udp traffic from wireguard as icmp requests. Otherwise, it spoofs all the udp/tcp traffic and blocks intermittently.

Sorry but i have never used the tool you mention and don't know if it would work.

parvit commented 1 week ago

Release 0.5 now contains an updated configuration and a pdf user manual to explain in detail the operation and configuration of qpep.

Release v0.5.0

Project-Faster / qpep