bughz/glider
1
0
Fork 0
mirror of https://github.com/nadoo/glider.git synced 2025-02-23 17:35:40 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

doc: correct mistakes in README file

Browse Source
This commit is contained in:
nadoo 2017-09-03 01:18:01 +08:00
parent e34b787ea5
commit efb1029793
3 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -22,14 +22,14 @@ Forward(upstream proxy server):
- Http proxy
- SS proxy
DNS Forwarding Server(udp2tcp)
DNS Forwarding Server(udp2tcp):
- Listen on UDP and forward dns requests to remote dns server in TCP via forwarders
- Specify different upstream dns server based on destinations(in rule file)
- Tunnel mode: forward to a fixed upstream dns server
- Add resolved IPs to proxy rules
- Add resolved IPs to ipset
Ipset Management
Ipset Management:
- Add ip/cidrs from rule files on startup
- Add resolved ips for domains from rule files by dns forwarding server

4
config/examples/8.transparent_proxy_with_dnsmasq/README.md
View File

@ -38,6 +38,6 @@ iptables -t nat -I OUTPUT -p tcp -m set --match-set myset dst -j REDIRECT --to-p
#### When client requests network, the whole process:
1. all dns requests for domain example1.com will be forward to glider(:5353) by dnsmasq
2. glider will forward dns requests to 8.8.8.8:53 in tcp via forwarders
3. the resolved ip address will be add to ipset "myset" by dnsmasq
4. all tcp requests to example1.com will be redirect to glider(:1081)
3. the resolved ip address will be added to ipset "myset" by dnsmasq
4. all tcp requests to example1.com will be redirect to glider(:1081) by iptables
5. glider then forward requests to example1.com via forwarders

9
config/examples/9.transparent_proxy_without_dnsmasq/README.md
View File

@ -72,18 +72,17 @@ iptables -t nat -I OUTPUT -p tcp -m set --match-set glider dst -j REDIRECT --to-
```
#### Client DNS settings
use the linux server'ip as your dns server
use the linux server's ip as your dns server
#### When client requesting to access http://example1.com(in office.rule), the whole process:
- dns resolving:
#### When client requesting to access http://example1.com (in office.rule), the whole process:
- Dns resolving:
1. client sends a udp dns request to linux server, and glider will receive the request(as it listen on default dns port :53)
2. upstream dns server choice: glider will lookup it's rule config and find out the dns server to use for this domain(matched "example1.com" in office.rule, so 208.67.222.222:53 will be choosen)
3. glider uses the forwarder in office.rule to ask 208.67.222.222:53 for the resolve answers
4. glider updates it's office rule config, add the resolved ip address to it
5. glider adds the resolved ip into ipset "glider", and return the dns answer to client
- destination accessing:
- Destination accessing:
1. client sends http request to the resolved ip of example1.com
2. linux gateway server will get the request
3. iptabes matches the ip in ipset "glider" and redirect this request to :1081(glider)
4. glider finds the ip in office rule, and then choose a forwarder in office.rule to complete the request