Why, when installing an additional ip 10.0.0.233, the node is available, packets are sent, but there is no answer (Gateway default 192.168.0.1)?

Question

linux

[[email protected] ~]# tcpdump -np icmp
09:58:11.495982 IP 10.0.0.233 > 216.58.214.238: ICMP echo request, id 5940, seq 1, length 64
09:58:12.495906 IP 10.0.0.233 > 216.58.214.238: ICMP echo request, id 5940, seq 2, length 64
09:58:13.495984 IP 10.0.0.233 > 216.58.214.238: ICMP echo request, id 5940, seq 3, length 64
09:58:14.496363 IP 10.0.0.233 > 216.58.214.238: ICMP echo request, id 5940, seq 4, length 64
09:58:15.496502 IP 10.0.0.233 > 216.58.214.238: ICMP echo request, id 5940, seq 5, length 64

checked with ping -I 10.0.0.233 google.com
Mask 255.255.255.0 . Is it because different address ranges (01.0.0.0-126.0.0.0 and 192.0.0.0-222.0.0.0)? Explain, please

Answer 1

The subnet mask has nothing to do with it. Where should the gateway respond to requests from the 10.0.0.0/24 network? Of course, along its default route, which looks like it looks into the provider's network.
Add a static route on the gateway to return 10.0.0.0/24 packets back to the local network. Well, you need to check the firewall rules.
What is the reason to hang two gray addresses from different spaces and go to the Internet with them?

Answer 2

the mask is wrong, the gateway is wrong
10--233 just doesn't know where to forward those packets