Commit ae5da89a authored by Eric Tune's avatar Eric Tune

Correct scratch guide re: bridge and iptables

Replace "eth0" with "cbr0" in "ip add" command, as reported by github user @kjvalencik. Update iptables command to match changes in #13348.
parent 284039c9
...@@ -476,7 +476,7 @@ because of how this is used later. ...@@ -476,7 +476,7 @@ because of how this is used later.
1. Set appropriate MTU 1. Set appropriate MTU
- `ip link set dev cbr0 mtu 1460` (NOTE: the actual value of MTU will depend on your network environment) - `ip link set dev cbr0 mtu 1460` (NOTE: the actual value of MTU will depend on your network environment)
1. Add the clusters network to the bridge (docker will go on other side of bridge). 1. Add the clusters network to the bridge (docker will go on other side of bridge).
- e.g. `ip addr add $NODE_X_BRIDGE_ADDR dev eth0` - e.g. `ip addr add $NODE_X_BRIDGE_ADDR dev cbr0`
1. Turn it on 1. Turn it on
- e.g. `ip link set dev cbr0 up` - e.g. `ip link set dev cbr0 up`
...@@ -485,7 +485,7 @@ other, then you may need to do masquerading just for destination IPs outside ...@@ -485,7 +485,7 @@ other, then you may need to do masquerading just for destination IPs outside
the cluster network. For example: the cluster network. For example:
```sh ```sh
iptables -w -t nat -A POSTROUTING -o eth0 -j MASQUERADE \! -d ${CLUSTER_SUBNET} iptables -t nat -A POSTROUTING ! -d ${CLUSTER_SUBNET} -m addrtype ! --dst-type LOCAL -j MASQUERADE
``` ```
This will rewrite the source address from This will rewrite the source address from
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment