Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor text improvements #17

Merged
merged 1 commit into from
Jan 6, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ the response packets to the default route (internet). To work around
we deploy a custom routing table, which forces the return traffic to
be routed to loopback.

1) if traffic is forwarded to lo interface (127.0.0.1 / ::1 for exemple)
1) If traffic is forwarded to the "lo" interface (127.0.0.1 / ::1 for example):

# 1. Route packets from lo address and lo interface to table 100
ip -4 rule add from 127.0.0.1/8 iif lo table 100
Expand All @@ -88,12 +88,13 @@ be routed to loopback.
ip route add local 0.0.0.0/0 dev lo table 100
ip -6 route add local ::/0 dev lo table 100

2) if traffic is forwarded to any other interface
2) Or, if traffic is forwarded to any other interface:

# 1. Check if you have a default route for ipv4 / ipv6
# if you don't have any default route response will be dropped before #4 & #5

# 2. Enable route_localnet on your default interface
# substitute "eth0" in the path below, if needed
echo 1 > /proc/sys/net/ipv4/conf/eth0/route_localnet

# 3. Save conntrack CONNMARK on packets sent with MARK 123.
Expand All @@ -118,7 +119,7 @@ Development
-----------


git clone https://github.com/xxx/mmproxy.git
git clone https://github.com/cloudflare/mmproxy.git
cd mmproxy
git submodule update --init
make
Expand Down