You are not logged in.
After installing docker, I found that the ssh connection to the server would time out. I guess it might be because of a conflict between the docker network segment and the server. I successfully modified the docker network segment through /etc/docker/daemon.json, but still could not connect successfully
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 20:88:10:5e:04:25 brd ff:ff:ff:ff:ff:ff
inet 172.23.160.212/17 brd 172.23.255.255 scope global dynamic noprefixroute enp2s0
valid_lft 86318sec preferred_lft 86318sec
inet6 2403:ac00:2383:de:2288:10ff:fe5e:425/128 scope global dynamic noprefixroute
valid_lft 2591921sec preferred_lft 604721sec
inet6 fe80::679d:abdd:c3ea:f8d4/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:5e:61:7f:a6 brd ff:ff:ff:ff:ff:ff
inet 10.16.0.1/12 brd 10.31.255.255 scope global docker0
valid_lft forever preferred_lft forever
4: br-8c625480d70e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:84:8a:e0:74 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global br-8c625480d70e
valid_lft forever preferred_lft forever
inet6 fe80::42:84ff:fe8a:e074/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
Has anyone encountered a similar situation? Does this br-xxx network segment also need to be modified?
Offline
docker occupies in 172.18.* now - did you reboot? Was your real network segment always 172.23.160.0/17
What's the output of "ip r" and what's the source IP/segment?
Can you ping the client from the server?
Offline