Administrative notice, office relocation from the second floor to the fifteenth floor – a standard, routine desk move.
Design Sense
Migration
Closing up shop, packing everything away, a familiar route, a new workstation – adjusting computer cabling, finding a comfortable posture to start working. (ÒωÓױ)! – Connecting the network cable, the servers frequently used by the team were inaccessible. I tried switching to wireless networking, and access was normal again.
Initially, I thought it was a problem with the server’s IP address range settings. The wired network at the new workstation wasn’t included in the firewall configuration list. After contacting IT colleagues to adjust it, the issue was resolved. This IP address range wasn’t just for one server; when trying to access other servers, they were all functioning normally. Gradually, I began to feel confused? Let professional people handle professional matters – eventually, the operations department colleague identified that this server had docker deployed, and the default network of the docker0 service conflicted with the wired network configuration of the office, causing data packets sent to it to not receive responses and being routed to the docker service.
Other servers didn’t have the docker service deployed, so only this one was affected. I frequently used it, and occasionally used containers to deploy some testing services – I never expected to encounter such a scenario. Later, thinking about it in detail, since the entire group was located within the same office building, IT colleagues divided IP address ranges using addresses starting with 172, which wasn’t unusual.
docker0
# vim /etc/docker/daemon.json
{
"bip":"172.200.0.1/24"
}
Restart the service and switch to the new network; the server recovers normal access.