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

Unused POSTROUTING rules #12632

Open
itatabitovski opened this issue Apr 22, 2015 · 4 comments
Open

Unused POSTROUTING rules #12632

itatabitovski opened this issue Apr 22, 2015 · 4 comments

Comments

@itatabitovski
Copy link

I've noticed that except the first rule none of the other rules are used. Are they needed for some corner case or they can be removed?

Chain POSTROUTING (policy ACCEPT 1313K packets, 79M bytes)
num   pkts bytes target     prot opt in     out     source               destination         
1    1195K   76M MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0           
2        0     0 MASQUERADE  tcp  --  *      *       172.17.0.3           172.17.0.3           tcp dpt:9115
3        0     0 MASQUERADE  tcp  --  *      *       172.17.0.6           172.17.0.6           tcp dpt:443
4        0     0 MASQUERADE  tcp  --  *      *       172.17.0.13          172.17.0.13          tcp dpt:80
5        0     0 MASQUERADE  tcp  --  *      *       172.17.0.14          172.17.0.14          tcp dpt:9200
6        0     0 MASQUERADE  tcp  --  *      *       172.17.0.16          172.17.0.16          tcp dpt:8080
7        0     0 MASQUERADE  tcp  --  *      *       172.17.0.17          172.17.0.17          tcp dpt:9116
8        0     0 MASQUERADE  tcp  --  *      *       172.17.0.14          172.17.0.14          tcp dpt:9300
9        0     0 MASQUERADE  tcp  --  *      *       172.17.0.21          172.17.0.21          tcp dpt:9103
10       0     0 MASQUERADE  tcp  --  *      *       172.17.0.22          172.17.0.22          tcp dpt:80
11       0     0 MASQUERADE  tcp  --  *      *       172.17.0.24          172.17.0.24          tcp dpt:3000
12       0     0 MASQUERADE  tcp  --  *      *       172.17.0.35          172.17.0.35          tcp dpt:9200
13       0     0 MASQUERADE  tcp  --  *      *       172.17.0.35          172.17.0.35          tcp dpt:9200
14       0     0 MASQUERADE  tcp  --  *      *       172.17.0.35          172.17.0.35          tcp dpt:9300
15       0     0 MASQUERADE  tcp  --  *      *       172.17.0.35          172.17.0.35          tcp dpt:9300
16       0     0 MASQUERADE  tcp  --  *      *       172.17.0.40          172.17.0.40          tcp dpt:80
17       0     0 MASQUERADE  tcp  --  *      *       172.17.0.41          172.17.0.41          tcp dpt:9110
18       0     0 MASQUERADE  tcp  --  *      *       172.17.0.43          172.17.0.43          tcp dpt:80
19       0     0 MASQUERADE  tcp  --  *      *       172.17.0.49          172.17.0.49          tcp dpt:80
20       0     0 MASQUERADE  tcp  --  *      *       172.17.0.51          172.17.0.51          tcp dpt:9200
21       0     0 MASQUERADE  tcp  --  *      *       172.17.0.51          172.17.0.51          tcp dpt:9300
22       0     0 MASQUERADE  tcp  --  *      *       172.17.0.54          172.17.0.54          tcp dpt:80
@LK4D4
Copy link
Contributor

LK4D4 commented Sep 13, 2016

ping @mavenugo @mrjana @aboch
Can you pls answer this question?

@aboch
Copy link
Contributor

aboch commented Oct 31, 2016

@itatabitovski
I see those rules are hit when docker is started with --userland-proxy=false and you try to access the service's published port on the host or bridge interface address from inside the container .

@itatabitovski
Copy link
Author

itatabitovski commented Oct 31, 2016

@aboch thanks, I've never run docker with --userland-proxy=false. Maybe these rules should not be created by default?

@aboch
Copy link
Contributor

aboch commented Oct 31, 2016

agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants