bughz/3proxy
1
0
Fork 0
mirror of https://github.com/3proxy/3proxy.git synced 2026-08-26 09:55:48 +08:00
Code Issues Actions 10 Packages Projects Releases Wiki Activity

Update HTML documentation from man pages

Browse Source
This commit is contained in:
github-actions[bot] 2026-08-25 16:08:21 +00:00
parent cb9effab9b
commit e78c1d2c07
1 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/html/man5/3proxy.cfg.5.html
View File

@ -824,14 +824,19 @@ argument, with 0.0.0.0 as the address, for example <b>parent
be asked to pick the port itself (Linux be asked to pick the port itself (Linux
<b>IP_LOCAL_PORT_RANGE</b>) it does, otherwise a port is <b>IP_LOCAL_PORT_RANGE</b>) it does, otherwise a port is
picked at random from the range and retried if it is already picked at random from the range and retried if it is already
in use, up to ten times. It can be chained with another in use, up to ten times. On Linux the range has to lie
parent type, and the access rule it belongs to decides which within <i>net.ipv4.ip_local_port_range</i>, commonly
requests it applies to, so <b>allow * * * * UDPASSOC</b> 32768-60999: the kernel ignores a range outside it and picks
followed by <b>parent 1000 extport 0.0.0.0 40000-40100</b> an ordinary ephemeral port instead. If no port in the range
limits it to UDP associations. The range is applied when the can be bound, an ephemeral port is used rather than failing
outgoing connection is made, so a kept alive connection the connection. It can be chained with another parent type,
carrying several requests uses the rule that matched when it and the access rule it belongs to decides which requests it
was opened. <b><br> applies to, so <b>allow * * * * UDPASSOC</b> followed by
<b>parent 1000 extport 0.0.0.0 40000-40100</b> limits it to
UDP associations. The range is applied when the outgoing
connection is made, so a kept alive connection carrying
several requests uses the rule that matched when it was
opened. <b><br>
intport</b> is the same for sockets bound on the side facing intport</b> is the same for sockets bound on the side facing
the client: the port a UDP association tells the client to the client: the port a UDP association tells the client to
send its datagrams to, and the FTP proxy data connection. send its datagrams to, and the FTP proxy data connection.