wysota
10th September 2010, 14:10
NetworqDebugger is a simple tool for software developers that makes it easy to debug networking applications. It provides a proxy that will sit between your software and a remote server and display the conversation between them in GUI.
You can choose from two different modes of operation:
SOCKS5
This is the recommended mode of operation that is compliant with SOCKS5 protocol. Every application that supports SOCKS5 (such as most web browsers) can use it just by activating the proxy setting in the software. It is also easy to use it in case of your own Qt software - just create a network proxy settings object and use it for your application:
QNetworkProxy proxy(QNetworkProxy::Socks5Proxy, "127.0.0.1", 8080));
QNetworkProxy::setApplicationProxy(proxy);
Also remember to make sure the proxy setting for your actual sockets is correct (i.e. set to QNetworkProxy::DefaultProxy which is the default).
Transparent proxy
This is a fallback mechanism if you can't use SOCKS5. In this case instead of connecting to the remote end, your application connects to the proxy and the proxy makes a connection for you to the remote server based on the address you specify in NetworqDebugger. The address can be specified globally for all connections ("Default route") or can be input when the connection is being established ("Ask for route").
For example, if you want to debug your web browser by checking how it communicates with http://www.qtcentre.org webserver, you point your browser to localhost:8080 (or whatever else address you have set for the proxy) and tell the proxy to connect to www.qtcentre.org:80.
The application sits in the system tray and is configurable via a context menu.
If you use NetworqDebugger, be sure to check if your firewall allows connections to the port the proxy listens on.
Current features:
- SOCKS5 mode of operation for TCP client-side connections,
- transparent proxy mode of operation for TCP client-side connections,
- configurable listening address,
- configurable default remote address,
- session management (application 'lives' through logouts under X11).
Compilation:
1. ungzip/untar
2. run qmake
3. run (n)make
Feedback is welcome.
You can choose from two different modes of operation:
SOCKS5
This is the recommended mode of operation that is compliant with SOCKS5 protocol. Every application that supports SOCKS5 (such as most web browsers) can use it just by activating the proxy setting in the software. It is also easy to use it in case of your own Qt software - just create a network proxy settings object and use it for your application:
QNetworkProxy proxy(QNetworkProxy::Socks5Proxy, "127.0.0.1", 8080));
QNetworkProxy::setApplicationProxy(proxy);
Also remember to make sure the proxy setting for your actual sockets is correct (i.e. set to QNetworkProxy::DefaultProxy which is the default).
Transparent proxy
This is a fallback mechanism if you can't use SOCKS5. In this case instead of connecting to the remote end, your application connects to the proxy and the proxy makes a connection for you to the remote server based on the address you specify in NetworqDebugger. The address can be specified globally for all connections ("Default route") or can be input when the connection is being established ("Ask for route").
For example, if you want to debug your web browser by checking how it communicates with http://www.qtcentre.org webserver, you point your browser to localhost:8080 (or whatever else address you have set for the proxy) and tell the proxy to connect to www.qtcentre.org:80.
The application sits in the system tray and is configurable via a context menu.
If you use NetworqDebugger, be sure to check if your firewall allows connections to the port the proxy listens on.
Current features:
- SOCKS5 mode of operation for TCP client-side connections,
- transparent proxy mode of operation for TCP client-side connections,
- configurable listening address,
- configurable default remote address,
- session management (application 'lives' through logouts under X11).
Compilation:
1. ungzip/untar
2. run qmake
3. run (n)make
Feedback is welcome.