redsocks icon indicating copy to clipboard operation
redsocks copied to clipboard

Broken pipe and dropping client messages in the log file

Open animer3009 opened this issue 3 years ago • 2 comments

I am getting this messages in the log file. What does it mean and how to solve it?

1647970994.602918 info redsocks.c:444 redsplice_write_cb(...) [192.168.8.134:58287->216.151.180.254:8080]: splice(to client): Broken pipe
1647970994.603068 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:58287->216.151.180.254:8080]: dropping client (R/W), relay (R/W), idle 0.000216s
1647970994.604036 info redsocks.c:444 redsplice_write_cb(...) [192.168.8.134:58290->64.18.148.2:8080]: splice(to client): Broken pipe
1647970994.604430 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:58290->64.18.148.2:8080]: dropping client (-/W), relay (R/W), idle 0.000484s
1647970994.614544 info redsocks.c:444 redsplice_write_cb(...) [192.168.8.134:58288->24.29.97.13:8080]: splice(to client): Broken pipe
1647970994.614693 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:58288->24.29.97.13:8080]: dropping client (-/W), relay (R/W), idle 0.000212s
1647970994.615226 info redsocks.c:444 redsplice_write_cb(...) [192.168.8.134:58292->216.151.180.254:8080]: splice(to client): Broken pipe
1647970994.615364 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:58292->216.151.180.254:8080]: dropping client (-/W), relay (R/W), idle 0.000191s
1647970994.615936 info redsocks.c:444 redsplice_write_cb(...) [192.168.8.134:58289->209.254.101.138:8080]: splice(to client): Broken pipe
1647970994.616086 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:58289->209.254.101.138:8080]: dropping client (-/W), relay (R/W), idle 0.000255s

When I set splice = false, than I am getting this messages:

1647971533.862176 info redsocks.c:839 redsocks_event_error(...) [192.168.8.134:59195->205.185.216.42:443]: client error, code EVBUFFER_READ|0|0|EVBUFFER_ERROR|0|0x0: Connection reset by peer
1647971533.882441 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:59195->205.185.216.42:443]: dropping client (R/-), relay (-/W), idle 0.020295s
1647971533.883127 info redsocks.c:839 redsocks_event_error(...) [192.168.8.134:59148->68.67.160.75:443]: client error, code EVBUFFER_READ|0|0|EVBUFFER_ERROR|0|0x0: Connection reset by peer
1647971533.883408 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:59148->68.67.160.75:443]: dropping client (R/-), relay (-/W), idle 0.000184s
1647971533.884049 info redsocks.c:839 redsocks_event_error(...) [192.168.8.134:59150->68.67.160.75:443]: client error, code EVBUFFER_READ|0|0|EVBUFFER_ERROR|0|0x0: Connection reset by peer
1647971533.884348 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:59150->68.67.160.75:443]: dropping client (R/-), relay (-/W), idle 0.000335s
1647971533.884871 info redsocks.c:671 redsocks_drop_client(...) [192.168.8.134:59189->199.38.167.128:443]: connection closed
1647971533.885376 info redsocks.c:839 redsocks_event_error(...) [192.168.8.134:59183->209.197.3.19:443]: client error, code EVBUFFER_READ|0|0|EVBUFFER_ERROR|0|0x0: Connection reset by peer
1647971533.885506 info redsocks.c:689 redsocks_drop_client(...) [192.168.8.134:59183->209.197.3.19:443]: dropping client (R/-), relay (-/W), idle 0.000173s

My config is:

base {
    log_info = on;
    log = "file:/var/log/redsocks_proxy.log";
    daemon = on;
    redirector = iptables;

    redsocks_conn_max = 10000;
}

redsocks {
    // Use iptables to redirect traffic here
    local_ip = 0.0.0.0;
    local_port = 12345;

    // Remote proxy info
    ip = 192.168.220.82;                                    
    port = 55555;        
    type = socks5;      
                  
} 

animer3009 avatar Mar 22 '22 17:03 animer3009

1648365860.844289 info redsocks.c:514 redsplice_read_cb(...) [192.168.1.134:50968->38.117.158.3:8080]: splice(from client): Connection reset by peer
1648365860.844469 info redsocks.c:689 redsocks_drop_client(...) [192.168.1.134:50968->38.117.158.3:8080]: dropping client (R/W), relay (R/W), idle 0.000247s
1648365860.845038 info redsocks.c:514 redsplice_read_cb(...) [192.168.1.134:50966->38.117.158.3:8080]: splice(from client): Connection reset by peer
1648365860.845213 info redsocks.c:689 redsocks_drop_client(...) [192.168.1.134:50966->38.117.158.3:8080]: dropping client (R/W), relay (R/W), idle 0.000218s
1648365860.845787 info redsocks.c:514 redsplice_read_cb(...) [192.168.1.134:50965->38.117.158.3:8080]: splice(from client): Connection reset by peer
1648365860.845937 info redsocks.c:689 redsocks_drop_client(...) [192.168.1.134:50965->38.117.158.3:8080]: dropping client (R/W), relay (R/W), idle 0.000200s
1648365860.846351 info redsocks.c:514 redsplice_read_cb(...) [192.168.1.134:50970->38.117.158.3:8080]: splice(from client): Connection reset by peer
1648365860.846475 info redsocks.c:689 redsocks_drop_client(...) [192.168.1.134:50970->38.117.158.3:8080]: dropping client (R/W), relay (R/W), idle 0.000132s
1648365860.846927 info redsocks.c:514 redsplice_read_cb(...) [192.168.1.134:50969->38.117.158.3:8080]: splice(from client): Connection reset by peer
1648365860.847054 info redsocks.c:689 redsocks_drop_client(...) [192.168.1.134:50969->38.117.158.3:8080]: dropping client (R/W), relay (R/W), idle 0.000206s

animer3009 avatar Mar 27 '22 07:03 animer3009

If I remember correctly, those are boring "transactional" messages showing the start and the end of each proxified connection, something like access.log for a webserver. IIRC, log_info = off will hide those messages:

https://github.com/darkk/redsocks/blob/19b822e345f6a291f6cff6b168f1cfdfeeb2cd7d/redsocks.conf.example#L5-L6

darkk avatar Mar 27 '22 11:03 darkk