Traffic not passing through the route it supposed to

Issues related to configuring your network
Post Reply
Ajderev
Posts: 2
Joined: 2019/01/21 21:54:29

Traffic not passing through the route it supposed to

Post by Ajderev » 2019/01/21 22:03:58

Hello ALL

From today my centos 7 traffic is not passing through the router it is supposed to.
It is a virtual server. Since today if I try to use 192.168.1.254 as a default gate it sends it to 192.168.1.1
See below example with 8.8.8.8

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 100 0 0 ens192
8.8.8.8 192.168.1.254 255.255.255.255 UGH 0 0 0 ens192
10.1.0.0 192.168.1.1 255.255.0.0 UG 1 0 0 ens192
10.150.0.0 192.168.1.1 255.255.0.0 UG 1 0 0 ens192
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 ens192
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
# ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.296 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.342 ms
^C
--- 192.168.1.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.296/0.319/0.342/0.023 ms
# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.253 ms 0.161 ms 0.154 ms
2 10.1.3.1 (10.1.3.1) 3.695 ms 4.299 ms 6.406 ms
3 10.150.254.251 (10.150.254.251) 22.049 ms 21.990 ms 21.930 ms
4 * * *
5 * * *

It seems to be working for inbound connections. I have publicly accessible service which accessible but if I try to access Internet it is not working bouse it routes the traffic through 192.168.1.1 with is no for Internet access, so only connections initiated by the server to the Internet have this issue.

I will appreciate if someone has an idea what the issue may be and how to solve it.

Ajderev
Posts: 2
Joined: 2019/01/21 21:54:29

Re: Traffic not passing through the route it supposed to

Post by Ajderev » 2019/01/21 22:25:12

I just found the issue.

The virtual interfaces in the VLAN for both routers somehow had the same MAC address.

Post Reply