4 ms·
> 172.16-172.31 are particularly frequently unused haha, I wish. We decided to use them two decades ago exactly because we thought they were less frequently us
by ATsch 7y ago
> 172.16-172.31 are particularly frequently unused
haha, I wish. We decided to use them two decades ago exactly because we thought they were less frequently used, but then a decade later docker comes along and uses exactly that as a default NAT subnet. So we get multiple tickets about that a week.
- saurik 7y agoWhat kind of issues is this causing you / your users?
- ATsch 7y agoWell, the complaint usually goes like this: "we recently set up service x, and it seems to be working fine. However, when we try to connect from the campus wifi, or a certain department, the service does not respond". What happens is the server gets a request from a private IP within the range assigned to docker0, and then the container replies, but because the IP is believed to be local, linux correctly tries to find something attached to the docker0 interface with that IP and fails.