background
Another inaccessible event
Analysis
First of all, refer to this kind of questions Troubleshooting: foreign consumer XXX access service YYY from registry zzz use Dubbo version 2.5.3, please check register access list (whitelist / blacklist)
It's not the same thing to find out~
It can be seen from the error reporting above that an abnormal ip is found [192.168.122.1]
And our ip is 12 / 13 network segment, so where does this 122 network segment come from???
Interesting
I still remember that I wrote about the environment of multiple network cards the other day dubbo multi network card
Let's consider whether the network environment has changed
ifconfig enp0s29u1u1u5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 169.254.95.120 netmask 255.255.255.0 broadcast 169.254.95.255 inet6 fe80::40f2:e9ff:fed5:1704 prefixlen 64 scopeid 0x20<link> ether 42:f2:e9:d5:17:04 txqueuelen 1000 (Ethernet) RX packets 4520292 bytes 357928180 (341.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4302246 bytes 412991075 (393.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp11s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.13.128 netmask 255.255.255.0 broadcast 192.168.13.255 inet6 fe80::9123:a7e2:7f1f:5f12 prefixlen 64 scopeid 0x20<link> ether 40:f2:e9:d5:17:02 txqueuelen 1000 (Ethernet) RX packets 1401038615 bytes 1284272900666 (1.1 TiB) RX errors 0 dropped 94542 overruns 0 frame 0 TX packets 1167969749 bytes 643782468645 (599.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xc1a80000-c1aa0000 enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 40:f2:e9:d5:17:01 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 memory 0xc1b80000-c1ba0000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 6793920 bytes 32362453500 (30.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6793920 bytes 32362453500 (30.1 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:00:38:71 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
An abnormal virbr0 appears? ]
The ip address of virbr0 is just 192.168.122.1, so we can judge that the most likely reason is the wrong gateway.
So what the hell is virbr0?
After installing Xen or KVM in CentOS 7.3, you will find that there is an additional virtual network interface called virbr0 in the network interface, and a private address will be automatically obtained.
This is because libvirt is generated after the libvirt service is installed and enabled. Libvirt generates a virtual network switch (virbr0) on the server host. All virtual machines (guests) on the host are connected through this virbr0. By default, virbr0 uses NAT mode (IP Masquerade), so in this case, the guest can access the external through host.
Solve
Let's close this network card
ifconfig virbr0 down brctl delbr virbr0
All OK!