-
Notifications
You must be signed in to change notification settings - Fork 2
/
user.ruleset.EXAMPLE-DOCKER
67 lines (58 loc) · 1.85 KB
/
user.ruleset.EXAMPLE-DOCKER
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
#
# Docker Chain/Rules (WIP)
#
# In this scenario, I'm considering containers in their own bridges,
# with previous known IP ranges. Internet interface name is `eth0`.
#
# In docker-compose.yml, you can use something like that:
# networks:
# default:
# driver: bridge
# ipam:
# config:
# - subnet: 192.168.10.0/24
# services:
# myapp:
# networks:
# default:
# ipv4_address: 192.168.10.100
#
# In the example I'm using 192.168.0.0/16, so all 192.168.X will be
# considered as from containers(Note 16 CIDR not 24).
#
# You have to enable Forwarding on your kernel:
#
# Change provided sysctl.conf file:
# net.ipv4.ip_forward=1
#
# Docker NAT Chain/Rules
table inet docker {
chain prerouting {
type nat hook prerouting priority -100; policy accept;
# Jump to Docker NAT rule
fib daddr type local jump docker;
}
# We use u-user-output, so all unite rules will be respected
chain u-user-output {
# Jump to Docker NAT rule
fib daddr type local jump docker;
}
# We use u-user-forward, so all unite rules will be respected
chain u-user-forward {
# Forward traffic between containers
ip saddr 192.168.0.0/16 ip daddr 192.168.0.0/16 accept
}
chain postrouting {
type nat hook postrouting priority 100; policy accept;
# Masquerade Docker containers to the internet
ip saddr 192.168.0.0/16 oifname "eth0" masquerade
}
chain output {
type nat hook output priority -100; policy accept;
fib daddr type local jump docker
}
chain docker {
# NAT from some external IP 1.1.1.1, port 1234 to the container on 192.168.10.100, port 4321:
meta l4proto tcp ip daddr 1.1.1.1 tcp dport 1234 dnat to 192.168.10.100:4321
}
}