help me configering simple socks4 proxy.

[tazihad]

in redsocks I used this as simple socks4 proxy. just gave ip and port. But too much confused with redsocks2 config. what could be the alternative for socks4 proxy?

base {
 log_debug = on;
 log_info = on;
 log = "stderr";
 daemon = off;
 redirector = iptables;
}

redsocks {
    local_ip = 127.0.0.1;
    local_port = 12345;

    ip = 103.82.11.233; // your custom socks4 ip
    port = 4153;          // your custom socks4 port
    type = socks4;
    // known types: socks4, socks5, http-connect, http-relay

    // login = username;
    // password = password;
}

[semigodking]

The example config is in repo. ''' redsocks { /* `bind' defaults to 127.0.0.1:0 for security reasons, * use 0.0.0.0 if you want to listen on every interface. * `bind' are used as ip:port to redirect to. */ bind = "127.0.0.1:12345"; // listen() queue length. Default value is SOMAXCONN and it should be // good enough for most of us. // listenq = 128; // SOMAXCONN equals 128 on my Linux box. // `max_accept_backoff` is a delay to retry `accept()` after accept // failure (e.g. due to lack of file descriptors). It's measured in // milliseconds and maximal value is 65535. `min_accept_backoff` is // used as initial backoff value and as a damper for `accept() after // close()` logic. // min_accept_backoff = 100; // max_accept_backoff = 60000; // `relay` is IP address and port of proxy-server. Domain name is not // supported yet. // Can be: // [IPv6Address]:port // [IPv6Address] // IPv6Address // IPv4Address:port // IPv4Address // If no port is given, 0 is used. Usually, a valid port is required. relay = "127.0.0.1:1080"; // known types: socks4, socks5, http-connect, http-relay // New types: direct, shadowsocks, https-connect // For type direct: // if `relay` is not specified, connections will be forwarded to // original destinations. // if `relay` is filled with valid IP address, connections will be // forwarded to IP address defined in `relay`. It is useful when you // just want to forward connections to a specific IP address without // transparent proxy. E.g. forward IPv4:port to IPv6:port. type = socks5; // Specify interface for outgoing connections. // This is useful when you have multiple connections to // internet or when you have VPN connections. // interface = tun0; // Change this parameter to 1 if you want auto proxy feature. // When autoproxy is set to non-zero, the connection to target // will be made directly first. If direct connection to target // fails for timeout/connection refuse, redsocks will try to // connect to target via the proxy. autoproxy = 0; // timeout is meaningful when 'autoproxy' is non-zero. // It specified timeout value when trying to connect to destination // directly. Default is 10 seconds. When it is set to 0, default // timeout value will be used. timeout = 10; // login = "foobar";// field 'login' is reused as encryption // method of shadowsocks // password = "baz"; } ''' Zihad ***@***.***> 于 2022年10月19日周三 01:39写道：

…

in redsocks I used this as simple socks4 proxy. just gave ip and port. But too much confused with redsocks2 config. what could be the alternative for socks4 proxy? base { log_debug = on; log_info = on; log = "stderr"; daemon = off; redirector = iptables; } redsocks { local_ip = 127.0.0.1; local_port = 12345; ip = 103.82.11.233; // your custom socks4 ip port = 4153; // your custom socks4 port type = socks4; // known types: socks4, socks5, http-connect, http-relay // login = username; // password = password; } — Reply to this email directly, view it on GitHub <#180>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAP2XD3O44AF4PKOZBFFDB3WD3ODZANCNFSM6AAAAAARIKIXOE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>