A cross-platform programmable network tool.
❤️ Shiliew - A network app designed for those who value their time
bash <(curl https://bash.ooo/nami.sh)
nami install brook
brook server -l :9999 -p hello
You may want to use
brook link
to customize some parameters
- About App Mode on macOS
- How to install Brook on Windows
- How to install Brook on Linux
- How to install Brook on OpenWrt
brook dnsserver, dohserver, dnsserveroverbrook, server, wsserver, wssserver, quicserver can use script to do more complex thing. brook will pass different global variables to the script at different times, and the script only needs to assign the processing result to the global variable out
Script can do more:
- There are examples for dns server
- In the
script: in_dnsquery
step, script can do more, read more below
Script can do more:
- There are examples for server
- In the
script: in_address
step, script can do more, read more below
variable | type | command | timing | description | out type |
---|---|---|---|---|---|
in_dnsservers | map | dnsserver/dnsserveroverbrook/dohserver/server/wsserver/wssserver/quicserver | When just running | Predefine multiple dns servers, and then programmatically specify which one to use | map |
in_dohservers | map | dnsserver/dnsserveroverbrook/dohserver/server/wsserver/wssserver/quicserver | When just running | Predefine multiple doh servers, and then programmatically specify which one to use | map |
in_brooklinks | map | server/wsserver/wssserver/quicserver | When just running | Predefine multiple brook links, and then programmatically specify which one to use | map |
in_dnsquery | map | dnsserver/dnsserveroverbrook/dohserver | When a DNS query occurs | Script can decide how to handle this request | map |
in_address | map | server/wsserver/wssserver/quicserver | When the Server connects the proxied address | Script can decide how to handle this request | map |
Key | Type | Description | Example |
---|---|---|---|
_ | bool | meaningless | true |
out
, ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
... | ... | ... | ... |
custom name | string | dns server | 8.8.8.8:53 |
... | ... | ... | ... |
Key | Type | Description | Example |
---|---|---|---|
_ | bool | meaningless | true |
out
, ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
... | ... | ... | ... |
custom name | string | dohserver | https://dns.quad9.net/dns-query?address=9.9.9.9%3A443 |
... | ... | ... | ... |
Key | Type | Description | Example |
---|---|---|---|
_ | bool | meaningless | true |
out
, ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
... | ... | ... | ... |
custom name | string | brook link | brook://... |
... | ... | ... | ... |
Key | Type | Description | Example |
---|---|---|---|
fromipaddress | string | client address which send this request | 1.2.3.4:5 |
domain | string | domain name | google.com |
type | string | query type | A |
... | ... | ... | ... |
tag_key | string | --tag specifies the key value | tag_value |
... | ... | ... | ... |
out
, if it is error
type will be recorded in the log. Ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
block | bool | Whether Block, default false |
false |
ip | string | Specify IP directly, only valid when type is A /AAAA |
1.2.3.4 |
dnsserverkey | string | Use the dnsserver specified by key to resolve | custom name |
dohserverkey | string | Use the dohserver specified by key to resolve | custom name |
Key | Type | Description | Example |
---|---|---|---|
network | string | tcp or udp |
tcp |
fromipaddress | string | client address which send this request | 1.2.3.4:5 |
ipaddress | string | ip address to be proxied | 1.2.3.4:443 |
domainaddress | string | domain address to be proxied | google.com:443 |
user | string | user ID, only available when used with --userAPI | 9 |
... | ... | ... | ... |
tag_key | string | --tag specifies the key value | tag_value |
... | ... | ... | ... |
out
, if it is error
type will be recorded in the log. Ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
block | bool | Whether Block, default false |
false |
address | string | Rewrite destination to an address | 1.2.3.4 |
ipaddressfromdnsserverkey | string | If the destination is domain address, use the dnsserver specified by key to resolve | custom name |
ipaddressfromdnsserverkey | string | If the destination is domain address, use the dohserver specified by key to resolve | custom name |
aoraaaa | string | Must be used with ipaddressfromdnsserverkey or ipaddressfromdnsserverkey. Valid value is A /AAAA |
A |
speedlimit | int | Set a rate limit for this request, for example 1000000 means 1000 kb/s |
1000000 |
brooklinkkey | string | Use the brook link specified by key to proxy | custom name |
dialwith | string | If your server has multiple IPs or network interfaces, you can specify the IP or network interface name to initiate this request | 192.168.1.2 or 2606:4700:3030::ac43:a86a or en1 |
Before discussing the GUI client, let's first talk about the command line client brook
. As we know, after you have deployed the server, you can use the command line client brook
to create a local socks5 proxy or http proxy on your machine, and then configure it in your system proxy settings or in your browser to use this proxy. However:
- Not all apps will use this proxy, whether they use it is up to the app itself.
- Generally, all UDP protocols will not go through this proxy, such as http3.
For the specifics of socks5 and http proxy, you can read this article.
The GUI client does not use socks5 and http proxy mode, so there is no issue with some software not using the system proxy. Instead, it uses a virtual network card to take over the entire system's network, including UDP-based http3. Moreover, Brook allows us to control network requests programmatically, so it is necessary to have basic knowledge of network requests. Brook GUI will pass different global variables to the script at different times, and the script only needs to assign the processing result to the global variable out
Note: When we talk about addresses, we mean addresses that include the port number, such as a domain address:
google.com:443
, or an IP address:8.8.8.8:53
- When an app requests a domain address, such as
google.com:443
- It will first perform a DNS resolution, which means that the app will send a network request to the system-configured DNS, such as
8.8.8.8:53
, to inquire about the IP ofgoogle.com
- The system DNS will return the IP of
google.com
, such as1.2.3.4
, to the app - The app will combine the IP and port into an IP address, such as:
1.2.3.4:443
- The app makes a network request to this IP address
1.2.3.4:443
- The app receives the response data
In the above process, the app actually makes two network requests: one to the IP address 8.8.8.8:53
and another to the IP address 1.2.3.4:443
. In other words, the domain name is essentially an alias for the IP, and must obtain the domain's IP to establish a connection.
Brook has a Fake DNS feature default, which can parse the domain name out of the query requests that an app sends to the system DNS UDP 53 and decide how to respond to the app.
- When an app requests a domain name address, such as
google.com:443
- A DNS resolution will be performed first. That is, the app will send a network request to the system-configured DNS, such as
8.8.8.8:53
, to inquire about the IP ofgoogle.com
- The Brook client detects that an app is sending a network request to
8.8.8.8:53
. This will trigger thein_dnsquery
variable, carrying information such asdomain
- The Brook client returns a fake IP to the app, such as
240.0.0.1
- The app combines the IP and port into an IP address, such as:
240.0.0.1:443
- The app makes a network request to the IP address
240.0.0.1:443
- The Brook client detects that an app is sending a network request to
240.0.0.1:443
, discovers that this is a fake IP, and will convert the fake IP address back to the domain addressgoogle.com:443
. This will trigger thein_address
variable, carrying information such asdomainaddress
- The Brook client sends
google.com:443
to the Brook Server - The Brook Server first requests its own DNS to resolve the domain name to find out the IP of
google.com
, such as receiving1.2.3.4
- The Brook Server combines the IP and port into an IP address, such as:
1.2.3.4:443
- The Brook Server sends a network request to
1.2.3.4:443
and returns the data to the Brook client - The Brook client then returns the data to the app
- The app receives the response data
However, if the following situations occur, the domain name will not/cannot be parsed, meaning that the Brook client will not/cannot know what the domain name is and will treat it as a normal request sent to an IP address. To avoid the ineffectiveness of Fake DNS, please refer to this article:
- Fake DNS not enabled: in this case, the Brook client will not attempt to parse the domain name from the request sent to the system DNS and will treat it as a normal request sent to an IP address.
- Even with Fake DNS enabled, but the app uses the system's secure DNS or the app's own secure DNS: in this case, the Brook client cannot parse the domain name from the request sent to the secure DNS and will treat it as a normal request sent to an IP address.
Script can do more:
- In the
script: in_dnsquery
step, script can do more, read more below - In the
script: in_address
step, script can do more, read more below
variable | type | condition | timing | description | out type |
---|---|---|---|---|---|
in_brooklinks | map | / | Before connecting | Predefine multiple brook links, and then programmatically specify which one to connect to | map |
in_dnsquery | map | FakeDNS: On | When a DNS query occurs | Script can decide how to handle this request | map |
in_address | map | / | When connecting to an address | Script can decide how to handle this request | map |
in_httprequest | map | / | When an HTTP(S) request comes in | Script can decide how to handle this request | map |
in_httprequest,in_httpresponse | map | / | when an HTTP(S) response comes in | Script can decide how to handle this response | map |
Key | Type | Description | Example |
---|---|---|---|
_ | bool | meaningless | true |
out
, ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
... | ... | ... | ... |
custom name | string | brook link | brook://... |
... | ... | ... | ... |
Key | Type | Description | Example |
---|---|---|---|
domain | string | domain name | google.com |
type | string | query type | A |
appid | string | macOS App Mode: this is app id; Linux and Windows: this is app path; OpenWrt: this is IP address of client device. Note: In some operating systems, the app may initiate DNS queries through the system app. | com.google.Chrome.helper |
out
, if it is error
type will be recorded in the log. Ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
block | bool | Whether Block, default false |
false |
ip | string | Ignore fake DNS, specify IP directly, only valid when type is A /AAAA |
1.2.3.4 |
system | bool | Ignore fake DNS, resolve by System DNS over brook, default false |
false |
bypass | bool | Ignore fake DNS, resolve by Bypass DNS, default false |
false |
brooklinkkey | string | When need to connect the Server, instead, perfer connect to the Server specified by the key in_brooklinks | custom name |
Key | Type | Description | Example |
---|---|---|---|
network | string | Network type, the value tcp /udp |
tcp |
ipaddress | string | IP type address. There is only one of ipaddress and domainaddress. Note that there is no relationship between these two | 1.2.3.4:443 |
domainaddress | string | Domain type address, because of FakeDNS we can get the domain name address here | google.com:443 |
appid | string | macOS App Mode: this is app id; Linux and Windows: this is app path; OpenWrt: this is IP address of client device | com.google.Chrome.helper |
out
, if it is error
type will be recorded in the log. Ignored if not of type map
Key | Type | Description | Example |
---|---|---|---|
block | bool | Whether Block, default false |
false |
ipaddress | string | Rewrite destination to an ip address | 1.2.3.4:443 |
ipaddressfrombypassdns | string | Use Bypass DNS to obtain A or AAAA IP and rewrite the destination, only valid when domainaddress exists, the value A /AAAA |
A |
bypass | bool | Bypass, default false . If true and domainaddress exists, then ipaddress or ipaddressfrombypassdns must be specified |
false |
mitm | bool | Whether to perform MITM, default false . Only valid when network is tcp . Need to install CA, see below |
false |
mitmprotocol | string | MITM protocol needs to be specified explicitly, the value is http /https |
https |
mitmcertdomain | string | The MITM certificate domain name, which is taken from domainaddress by default. If ipaddress exists and mitm is true and mitmprotocol is https then must be must be specified explicitly |
example.com |
mitmwithbody | bool | Whether to manipulate the http body, default false . will read the body of the request and response into the memory and interact with the script. iOS 50M total memory limit may kill process |
false |
mitmautohandlecompress | bool | Whether to automatically decompress the http body when interacting with the script, default false . Usually need set this to true |
false |
mitmclienttimeout | int | Timeout for MITM talk to server, second, default 0 | 0 |
mitmserverreadtimeout | int | Timeout for MITM read from client, second, default 0 | 0 |
mitmserverwritetimeout | int | Timeout for MITM write to client, second, default 0 | 0 |
brooklinkkey | string | When need to connect the Server,instead, connect to the Server specified by the key in_brooklinks | custom name |
Key | Type | Description | Example |
---|---|---|---|
URL | string | URL | https://example.com/hello |
Method | string | HTTP method | GET |
Body | bytes | HTTP request body | / |
... | string | other fields are HTTP headers | / |
out
, must be set to an unmodified or modified request or a response
Key | Type | Description | Example |
---|---|---|---|
StatusCode | int | HTTP status code | 200 |
Body | bytes | HTTP response body | / |
... | string | other fields are HTTP headers | / |
out
, must be set to an unmodified or modified response
In Brook GUI, scripts are abstracted into Modules. There are already some modules, and there is no magic, it just automatically combine _header.tengo and _footer.tengo, so you only need to write the module itself.
modules = append(modules, {
// If you want to predefine multiple brook links, and then programmatically specify which one to connect to, then define `brooklinks` key a function
brooklinks: func(m) {
// Please refer to the example in `brooklinks.tengo`
},
// If you want to intercept and handle a DNS query, then define `dnsquery` key a function, `m` is the `in_dnsquery`
dnsquery: func(m) {
// Please refer to the example in `block_aaaa.tengo`
},
// If you want to intercept and handle an address, then define `address` key a function, `m` is the `in_address`
address: func(m) {
// Please refer to the example in `block_google_secure_dns.tengo`
},
// If you want to intercept and handle a http request, then define `httprequest` key a function, `request` is the `in_httprequest`
httprequest: func(request) {
// Please refer to the example in `ios_app_downgrade.tengo` or `redirect_google_cn.tengo`
},
// If you want to intercept and handle a http response, then define `httpresponse` key a function, `request` is the `in_httprequest`, `response` is the `in_httpresponse`
httpresponse: func(request, response) {
// Please refer to the example in `response_sample.tengo`
}
})
https://github.com/txthinking/ipio
ipio uses the same script as the GUI. If you are using ipio, you can manually combine multiple modules into a complete script in the following way. For example:
cat _header.tengo > my.tengo
cat block_google_secure_dns.tengo >> my.tengo
cat block_aaaa.tengo >> my.tengo
cat _footer.tengo >> my.tengo
https://www.txthinking.com/talks/articles/brook-openwrt-en.article
openwrt uses the same script as the GUI. If you are using openwrt, you can manually combine multiple modules into a complete script in the following way. For example:
cat _header.tengo > my.tengo
cat block_google_secure_dns.tengo >> my.tengo
cat block_aaaa.tengo >> my.tengo
cat _footer.tengo >> my.tengo
If you are writing complex scripts, the GUI may not be convenient for debugging. It is recommended to use ipio on desktop to debug with fmt.println
https://txthinking.github.io/ca/ca.pem
OS | How |
---|---|
iOS | https://www.youtube.com/watch?v=HSGPC2vpDGk |
Android | Android has user CA and system CA, must be installed in the system CA after ROOT |
macOS | nami install mad ca.txthinking , sudo mad install --ca ~/.nami/bin/ca.pem |
Windows | nami install mad ca.txthinking , Admin: mad install --ca ~/.nami/bin/ca.pem |
Some software may not read the system CA,you can use
curl --cacert ~/.nami/bin/ca.pem
to debug
Brook's stance on IPv6 is positive, if your server or local environment doesn't have an IPv6 stack, read this article.
- After adding your Server to the Brook client
- If your Server uses a domain and has not specified an IP address via
brook link --address
, then Brook client will attempt to resolve the domain's IP using local DNS, preferring AAAA record. For example:- domain.com:9999
- ws://domain.com:9999
- wss://domain.com:9999
- quic://domain.com:9999
- Connectivity check: Go to the Server details page and click
Connectivity Check
. If it works sometimes but not others, this indicates instability. - After connected
- Brook will change your system DNS to the System DNS configured in Brook (by default Google's DNS). In very rare cases, this change may be ignored on Windows, you can confirm this in the system settings.
- Test IPv4 TCP: Use
Test IPv4 TCP
for testing; this test has hardcoded the IP address, so does not trigger DNS resolution. - Test IPv4 UDP: Use
Test IPv4 UDP
for testing; this test has hardcoded the IP address, so does not trigger DNS resolution. - Test IPv6 TCP: Use
Test IPv6 TCP
for testing; this test has hardcoded the IP address, so does not trigger DNS resolution. - Test IPv6 UDP: Use
Test IPv6 UDP
for testing; this test has hardcoded the IP address, so does not trigger DNS resolution. - Test TCP and UDP: Use the
Echo Client
for testing. If the echo server entered is a domain address, it will trigger DNS resolution. - Ensure the effectiveness of Fake DNS: Fake DNS is essential to do something with a domain or domain address. Generally, enable the
Block Google Secure DNS
module is sufficient. For other cases, refer to this article. - If your local or Server does not support IPv6: Refer to this article.
- macOS App Mode: Refer to this article.
- Windows:
- The client can pass the tests without any special configuration on a brand-new, genuine Windows 11.
- Be aware that the Windows system time is often incorrect.
- Do not have other similar network software installed; they can cause conflicting network settings in the system.
- Try restarting the computer.
- Windows Defender may ask for permission to connect to the network or present other issues.
- System DNS may need to be set to 8.8.8.8 and/or 2001:4860:4860::8888
- Android:
- The client can pass the tests without any special configuration on the official Google ROM.
- Different ROMs may have made different modifications to the system.
- Permission for background running might require separate settings.
- System DNS may need to be set to 8.8.8.8 and/or 2001:4860:4860::8888
- Bypass traffic such as China, usually requires the following modules to be activated:
Block Google Secure DNS
Bypass Geo
Bypass Apple
: To prevent issues receiving Apple message notifications.Bypass China domain
orBypass China domain A
: The former usesBypass DNS
to obtain the IP, thenBypass Geo
or other modules decide whether to bypass; the latter bypasses directly after obtaining the IP withBypass DNS
using A records. The latter is needed if your local does not support IPv6.- If you are a Shiliew user, some modules are enabled by default, which is usually sufficient.
- Search GitHub issues
- Read the blog
- Read the documentation
- Submit new issue
- Seek help in the group
I think just reading this one page is enough: Tengo Language Syntax
Library
-
text: regular expressions, string conversion, and manipulation
-
math: mathematical constants and functions
-
times: time-related functions
-
rand: random functions
-
fmt: formatting functions
-
json: JSON functions
-
enum: Enumeration functions
-
hex: hex encoding and decoding functions
-
base64: base64 encoding and decoding functions
-
brook
: brook moduleConstants * os: string, linux/darwin/windows/ios/android Functions * splithostport(address string) => map/error: splits a network address of the form "host:port" to { "host": "xxx", "port": "xxx" } * country(ip string) => string/error: get country code from ip * cidrcontainsip(cidr string, ip string) => bool/error: reports whether the network includes ip * parseurl(url string) => map/error: parses a raw url into a map, keys: scheme/host/path/rawpath/rawquery * parsequery(query string) => map/error: parses a raw query into a kv map * map2query(kv map) => string/error: convert map{string:string} into a query string * bytes2ints(b bytes) => array/error: convert bytes into [int] * ints2bytes(ints array) => bytes/error: convert [int] into bytes * bytescompare(a bytes, b bytes) => int/error: returns an integer comparing two bytes lexicographically. The result will be 0 if a == b, -1 if a < b, and +1 if a > b * bytescontains(b bytes, sub bytes) => bool/error: reports whether sub is within b * byteshasprefix(s bytes, prefix bytes) => bool/error: tests whether the bytes s begins with prefix * byteshassuffix(s bytes, suffix bytes) => bool/error: tests whether the bytes s ends with suffix * bytesindex(s bytes, sep bytes) => int/error: returns the index of the first instance of sep in s, or -1 if sep is not present in s * byteslastindex(s bytes, sep bytes) => int/error: returns the index of the last instance of sep in s, or -1 if sep is not present in s * bytesreplace(s bytes, old bytes, new bytes, n int) => bytes/error: returns a copy of the s with the first n non-overlapping instances of old replaced by new. If n < 0, there is no limit on the number of replacements * pathescape(s string) => string/error: escapes the string so it can be safely placed inside a URL path segment, replacing special characters (including /) with %XX sequences as needed * pathunescape(s string) => string/error: does the inverse transformation of pathescape * queryescape(s string) => string/error: escapes the string so it can be safely placed inside a URL query * queryunescape(s string) => string/error: does the inverse transformation of queryescape * hexdecode(s string) => bytes/error: returns the bytes represented by the hexadecimal string s * hexencode(s string) => string/error: returns the hexadecimal encoding of src
Each subcommand
has a --example
, such as:
brook server --example
CLI | Description |
---|---|
nami | A clean and tidy decentralized package manager |
joker | Joker can turn process into daemon. Zero-Configuration |
nico | Nico can work with brook wsserver together |
z | z - process manager |
ipio | Proxy all traffic just one line command |
mad | Generate root CA and derivative certificate for any domains and any IPs |
hancock | Manage multiple remote servers and execute commands remotely |
sshexec | A command-line tool to execute remote command through ssh |
bash | Many one-click scripts |
docker | docker run txthinking/brook |
Resources | Description |
---|---|
Protocol | Brook Protocol |
Blog | Some articles you should read |
YouTube | Some videos you should watch |
Telegram | Ask questions here |
Announce | All news you should care |
GitHub | Other useful repos |
Socks5 Configurator | If you prefer CLI brook client |
IPvBar | See domain, IP and country in browser |
TxThinking SSH | A SSH Terminal |
brook-store | A Brook User System |
TxThinking | Everything |
Brook - A cross-platform programmable network tool
Brook
brook --help
Usage:
Brook [GLOBAL OPTIONS] command [COMMAND OPTIONS] [ARGUMENTS...]
-
--cliToken="": The CLI Token of your Brook Plus or Brook Business account, get it from https://www.txthinking.com/brook.html
-
--clientHKDFInfo="": client HKDF info, most time you don't need to change this, if changed, all and each brook links in client side must be same (default: "brook")
-
--log="": Works with server, wsserver, wssserver, quicserver, dnsserver, dohserver, dnsserveroverbrook. A valid value is file path. If you want to debug SOCKS5 lib, set env SOCKS5_DEBUG=true
-
--pid="": A file path used to store pid. Send SIGUSR1 to me to reset the --log or --userLog file on unix system
-
--script="": [Brook Plus or Brook Business]. Works with server, wsserver, wssserver, quicserver, dnsserver, dohserver, dnsserveroverbrook. https://, http:// or /path/to/file.tengo. Get details at https://brook.app
-
--scriptUpdateInterval="": Works with --script. The interval (s) to re-fetch script. The default is 0, which means only fetch once on startup (default: 0)
-
--serverHKDFInfo="": server HKDF info, most time you don't need to change this, if changed, all and each brook links in client side must be same (default: "brook")
-
--tag="": Works with --log, --userAPI, --userLog, --script. Tag can be used to the process, will be append into log or userLog, such as: 'key1:value1'. And all tags will also be appended as query parameters one by one to the userAPI
-
--userAPI="": [Brook Business]. Works with server, wsserver, wssserver, quicserver. When you build your own user system, Brook Server will send GET request to your userAPI to check if token is valid, for example: https://your-api-server.com/a_unpredictable_path. Yes, it is recommended to add an unpredictable path to your https API, of course, you can also use the http api for internal network communication. The request format is https://your-api-server.com/a_unpredictable_path?token=xxx. When the response is 200, the body should be the user's unique identifier, such as user ID; all other status codes are considered to represent an illegitimate user, and in these cases, the body should be a string describing the error. For more information, please read https://github.com/txthinking/brook/blob/master/protocol/user.md
-
--userAPIRateLimit="": Works with --userAPI. Limit the request rate per token to the user API by Brook Server, this will reduce the load on the user API. This is especially important when users have expired, and the userAPIValidCacheTime will not cache the requests, resulting in continuous requests to the user API. The default is 0, which means no limitation. For example, setting it to 1 means the rate is limited to 1 request per token per second. The phrase 'per token' means that each token has its own rate limiter, and they do not interfere with each other (default: 1)
-
--userAPIValidCacheTime="": Works with --userAPI. Once a token is checked and valid, the userAPI will not be requested to validate again for a certain period (s). A reasonable value must be set, otherwise it will affect the performance of each incoming connection (default: 3600)
-
--userLog="": Works with --userAPI. Log, traffic and more. A valid value is file path. Send SIGUSR1 to me to reset the log file on unix system. Mutually exclusive with the --log parameter.
-
--version, -v: print the version
Start a brook server that supports tcp and udp
-
--example: Show a minimal example of usage
-
--listen, -l="": Listen address, like: ':9999'
-
--password, -p="": Server password
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Start a brook client that supports tcp and udp. It can open a socks5 proxy, [src <-> socks5 <-> $ brook client <-> $ brook server <-> dst]
-
--example: Show a minimal example of usage
-
--http="": Where to listen for HTTP proxy connections
-
--link="": brook link, you can get it via $ brook link. The wssserver and password parameters will be ignored
-
--password, -p="": Brook server password
-
--server, -s="": Brook server address, like: 1.2.3.4:9999
-
--socks5="": Where to listen for SOCKS5 connections (default: 127.0.0.1:1080)
-
--socks5ServerIP="": Only if your socks5 server IP is different from listen IP
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Start a brook wsserver that supports tcp and udp. It opens a standard http server and a websocket server
-
--example: Show a minimal example of usage
-
--listen, -l="": Listen address, like: ':80'
-
--password, -p="": Server password
-
--path="": URL path (default: /ws)
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
-
--xForwardedFor: Replace the from field in --log, note that this may be forged
Start a brook wsclient that supports tcp and udp. It can open a socks5 proxy, [src <-> socks5 <-> $ brook wsclient <-> $ brook wsserver <-> dst]
-
--example: Show a minimal example of usage
-
--http="": Where to listen for HTTP proxy connections
-
--link="": brook link, you can get it via $ brook link. The wssserver and password parameters will be ignored
-
--password, -p="": Brook wsserver password
-
--socks5="": Where to listen for SOCKS5 connections (default: 127.0.0.1:1080)
-
--socks5ServerIP="": Only if your socks5 server IP is different from listen IP
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
-
--wsserver, -s="": Brook wsserver address, like: ws://1.2.3.4:80, if no path then /ws will be used. Do not omit the port under any circumstances
Start a brook wssserver that supports tcp and udp. It opens a standard https server and a websocket server
-
--cert="": The cert file absolute path for the domain, such as /path/to/cert.pem. If cert or certkey is empty, a certificate will be issued automatically
-
--certkey="": The cert key file absolute path for the domain, such as /path/to/certkey.pem. If cert or certkey is empty, a certificate will be issued automatically
-
--domainaddress="": Such as: domain.com:443. If you choose to automatically issue certificates, the domain must have been resolved to the server IP and 80 port also will be used
-
--example: Show a minimal example of usage
-
--password, -p="": Server password
-
--path="": URL path (default: /ws)
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Start a brook wssclient that supports tcp and udp. It can open a socks5 proxy, [src <-> socks5 <-> $ brook wssclient <-> $ brook wssserver <-> dst]
-
--example: Show a minimal example of usage
-
--http="": Where to listen for HTTP proxy connections
-
--link="": brook link, you can get it via $ brook link. The wssserver and password parameters will be ignored
-
--password, -p="": Brook wssserver password
-
--socks5="": Where to listen for SOCKS5 connections (default: 127.0.0.1:1080)
-
--socks5ServerIP="": Only if your socks5 server IP is different from listen IP
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
-
--wssserver, -s="": Brook wssserver address, like: wss://google.com:443, if no path then /ws will be used. Do not omit the port under any circumstances
Start a brook quicserver that supports tcp and udp.
-
--cert="": The cert file absolute path for the domain, such as /path/to/cert.pem. If cert or certkey is empty, a certificate will be issued automatically
-
--certkey="": The cert key file absolute path for the domain, such as /path/to/certkey.pem. If cert or certkey is empty, a certificate will be issued automatically
-
--domainaddress="": Such as: domain.com:443. If you choose to automatically issue certificates, the domain must have been resolved to the server IP and 80 port also will be used
-
--example: Show a minimal example of usage
-
--password, -p="": Server password
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Start a brook quicclient that supports tcp and udp. It can open a socks5 proxy, [src <-> socks5 <-> $ brook quicclient <-> $ brook quicserver <-> dst]
-
--example: Show a minimal example of usage
-
--http="": Where to listen for HTTP proxy connections
-
--link="": brook link, you can get it via $ brook link. The wssserver and password parameters will be ignored
-
--socks5="": Where to listen for SOCKS5 connections (default: 127.0.0.1:1080)
-
--socks5ServerIP="": Only if your socks5 server IP is different from listen IP
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Relay network traffic over brook, which supports TCP and UDP. Accessing [from address] is equal to accessing [to address], [src <-> from address <-> $ brook server/wsserver/wssserver/quicserver <-> to address]
-
--example: Show a minimal example of usage
-
--from, -f, -l="": Listen address: like ':9999'
-
--link="": brook link, you can get it via $ brook link. The server and password parameters will be ignored
-
--password, -p="": Password
-
--server, -s="": brook server or brook wsserver or brook wssserver or brook quicserver, like: 1.2.3.4:9999, ws://1.2.3.4:9999, wss://domain:443/ws, quic://domain.com:443
-
--tcpTimeout="": time (s) (default: 0)
-
--to, -t="": Address which relay to, like: 1.2.3.4:9999
-
--udpTimeout="": time (s) (default: 0)
Run a dns server over brook, which supports TCP and UDP, [src <-> $ brook dnserversoverbrook <-> $ brook server/wsserver/wssserver/quicserver <-> dns]
-
--dns="": Forward to DNS server (default: 8.8.8.8:53)
-
--example: Show a minimal example of usage
-
--link="": brook link, you can get it via $ brook link. The server and password parameters will be ignored
-
--listen, -l="": Listen address, like: 127.0.0.1:53
-
--password, -p="": Password
-
--server, -s="": brook server or brook wsserver or brook wssserver or brook quicserver, like: 1.2.3.4:9999, ws://1.2.3.4:9999, wss://domain.com:443/ws, quic://domain.com:443
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Run a client and connect with a brook link, which supports TCP and UDP. It can start a socks5 proxy, [src <-> socks5 <-> $ brook connect <-> $ brook server/wsserver/wssserver/quicserver <-> dst]
-
--example: Show a minimal example of usage
-
--http="": Where to listen for HTTP proxy connections
-
--link, -l="": brook link, you can get it via $ brook link
-
--socks5="": Where to listen for SOCKS5 connections (default: 127.0.0.1:1080)
-
--socks5ServerIP="": Only if your socks5 server IP is different from listen IP
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Generate a brook link
-
--address="": When server is brook wsserver or brook wssserver or brook quicserver, specify address instead of resolving addresses from host, such as 1.2.3.4:443
-
--ca="": When server is brook wssserver or brook quicserver, specify ca for untrusted cert, such as /path/to/ca.pem
-
--clientHKDFInfo="": client HKDF info, most time you don't need to change this, read brook protocol if you don't know what this is
-
--example: Show a minimal example of usage
-
--fragment="": When server is brook wssserver, split the ClientHello into multiple fragments and then send them one by one with delays (millisecond). The format is min_length:max_length:min_delay:max_delay, cannot be zero, such as 50:100:10:50
-
--insecure: When server is brook wssserver or brook quicserver, client do not verify the server's certificate chain and host name
-
--name="": Give this server a name
-
--password, -p="": Password
-
--server, -s="": Support brook server, brook wsserver, brook wssserver, socks5 server, brook quicserver. Like: 1.2.3.4:9999, ws://1.2.3.4:9999, wss://google.com:443/ws, socks5://1.2.3.4:1080, quic://google.com:443
-
--serverHKDFInfo="": server HKDF info, most time you don't need to change this, read brook protocol if you don't know what this is
-
--tlsfingerprint="": When server is brook wssserver, select tls fingerprint, value can be: chrome
-
--token="": A token represents a user's identity. A string encoded in hexadecimal. Server needs to have --userAPI enabled
-
--udpoverstream: When server is brook quicserver, UDP over Stream. Under normal circumstances, you need this parameter because the max datagram size for QUIC is very small
-
--udpovertcp: When server is brook server, UDP over TCP
-
--username, -u="": Username, when server is socks5 server
Run a standalone relay, which supports TCP and UDP. Accessing [from address] is equal to accessing [to address], [src <-> from address <-> to address]
-
--example: Show a minimal example of usage
-
--from, -f, -l="": Listen address: like ':9999'
-
--tcpTimeout="": time (s) (default: 0)
-
--to, -t="": Address which relay to, like: 1.2.3.4:9999
-
--udpTimeout="": time (s) (default: 0)
Run a standalone dns server
-
--dns="": DNS server which forward to. Such as 8.8.8.8:53 or https://dns.google/dns-query?address=8.8.8.8%3A443, the address is required (default: 8.8.8.8:53)
-
--example: Show a minimal example of usage
-
--listen, -l="": Listen address, like: 127.0.0.1:53
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Send a dns query
-
--dns, -s="": DNS server, such as 8.8.8.8:53 (default: 8.8.8.8:53)
-
--domain, -d="": Domain
-
--example: Show a minimal example of usage
-
--short: Short for A/AAAA
-
--type, -t="": Type, such as A (default: A)
Run a standalone doh server
-
--cert="": The cert file absolute path for the domain, such as /path/to/cert.pem. If cert or certkey is empty, a certificate will be issued automatically
-
--certkey="": The cert key file absolute path for the domain, such as /path/to/certkey.pem. If cert or certkey is empty, a certificate will be issued automatically
-
--dns="": DNS server which forward to. Such as 8.8.8.8:53 or https://dns.google/dns-query?address=8.8.8.8%3A443, the address is required (default: 8.8.8.8:53)
-
--domainaddress="": Such as: domain.com:443, if you want to create a https server. If you choose to automatically issue certificates, the domain must have been resolved to the server IP and 80 port also will be used
-
--example: Show a minimal example of usage
-
--listen="": listen address, if you want to create a http server behind nico
-
--path="": URL path (default: /dns-query)
-
--tcpTimeout="": time (s) (default: 0)
-
--udpTimeout="": time (s) (default: 0)
Send a dns query
-
--doh, -s="": DOH server, the address is required (default: https://dns.quad9.net/dns-query?address=9.9.9.9%3A443)
-
--domain, -d="": Domain
-
--example: Show a minimal example of usage
-
--short: Short for A/AAAA
-
--type, -t="": Type, such as A (default: A)
Run a standalone dhcp server. IPv4 only. Other running dhcp servers need to be stopped.
-
--cache="": Cache file, local absolute file path, default is $HOME/.brook.dhcpserver
-
--count="": IP range from the start, which you want to assign to clients (default: 0)
-
--dnsserver="": The dns server which you want to assign to clients, such as: 192.168.1.1 or 8.8.8.8
-
--example: Show a minimal example of usage
-
--gateway="": The router gateway which you want to assign to clients, such as: 192.168.1.1
-
--interface="": Select interface on multi interface device. Linux only
-
--netmask="": Subnet netmask which you want to assign to clients (default: 255.255.255.0)
-
--serverip="": DHCP server IP, the IP of the this machine, you shoud set a static IP to this machine before doing this, such as: 192.168.1.10
-
--start="": Start IP which you want to assign to clients, such as: 192.168.1.100
Run a standalone standard socks5 server, which supports TCP and UDP
-
--example: Show a minimal example of usage
-
--limitUDP: The server MAY use this information to limit access to the UDP association. This usually causes connection failures in a NAT environment, where most clients are.
-
--listen, -l="": Socks5 server listen address, like: :1080 or 1.2.3.4:1080
-
--password="": Password, optional
-
--socks5ServerIP="": Only if your socks5 server IP is different from listen IP
-
--tcpTimeout="": Connection deadline time (s) (default: 0)
-
--udpTimeout="": Connection deadline time (s) (default: 0)
-
--username="": User name, optional
Convert a socks5 proxy to a http proxy, [src <-> listen address(http proxy) <-> socks5 address <-> dst]
-
--example: Show a minimal example of usage
-
--listen, -l="": HTTP proxy which will be create: like: 127.0.0.1:8010
-
--socks5, -s="": Socks5 server address, like: 127.0.0.1:1080
-
--socks5password="": Socks5 password, optional
-
--socks5username="": Socks5 username, optional
-
--tcpTimeout="": Connection tcp timeout (s) (default: 0)
Test a socks5 server to see if it works properly
-
--dns="": A DNS Server to connect to and send TCP DNS query to test TCP, and UDP DNS query to test UDP. (default: 8.8.8.8:53)
-
--example: Show a minimal example of usage
-
--password, -p="": Socks5 password
-
--socks5, -s="": Like: 127.0.0.1:1080
-
--username, -u="": Socks5 username
Test UDP and TCP of a brook server/wsserver/wssserver/quicserver connection.
-
--dns="": A DNS Server to connect to and send TCP DNS query to test TCP, and UDP DNS query to test UDP. (default: 8.8.8.8:53)
-
--example: Show a minimal example of usage
-
--link, -l="": brook link. Get it via $ brook link
Echo server, echo UDP and TCP address of routes
-
--example: Show a minimal example of usage
-
--listen, -l="": Listen address, like: ':7777'
Connect to echoserver, echo UDP and TCP address of routes
-
--example: Show a minimal example of usage
-
--server, -s="": Echo server address, such as 1.2.3.4:7777
-
--times="": Times of interactions (default: 0)
Get country of IP
-
--example: Show a minimal example of usage
-
--ip="": 1.1.1.1
Generate shell completions
-
--example: Show a minimal example of usage
-
--file, -f="": Write to file (default: brook_autocomplete)
Generate markdown page
-
--example: Show a minimal example of usage
-
--file, -f="": Write to file, default print to stdout
Generate man.1 page
-
--example: Show a minimal example of usage
-
--file, -f="": Write to file, default print to stdout. You should put to /path/to/man/man1/brook.1 on linux or /usr/local/share/man/man1/brook.1 on macos
Shows a list of commands or help for one command