Ping reply packet received on wrong interface

I have created a vlan 'eth1.10' with untagged port and it has ip A.B.C.D . when i perform

root@OpenWrt:~# ping 8.8.8.8 -I eth1.10
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:~# 

however , when i performed this

root@OpenWrt:~# ping 8.8.8.8 -I A.B.C.D -c 5
PING 8.8.8.8 (8.8.8.8) from A.B.C.D: 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=117 time=2.543 ms
64 bytes from 8.8.8.8: seq=1 ttl=117 time=2.256 ms
64 bytes from 8.8.8.8: seq=2 ttl=117 time=2.709 ms
64 bytes from 8.8.8.8: seq=3 ttl=117 time=2.270 ms
64 bytes from 8.8.8.8: seq=4 ttl=117 time=2.280 ms

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.256/2.411/2.709 ms
root@OpenWrt:~# 

I have no idea whats going on. please help me with this problem

Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have

ip -4 addr ; ip -4 ro li tab all ; ip -4 ru;

ip -4 addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
9: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet 172.16.1.13/22 brd 172.16.3.255 scope global eth0
       valid_lft forever preferred_lft forever
10: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet 192.168.0.1/24 brd 192.168.0.255 scope global eth1
       valid_lft forever preferred_lft forever
13: eth1.10@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    inet A.B.C.D/24 brd A.B.C.255 scope global eth1.10
       valid_lft forever preferred_lft forever

ip -4 ro li tab all

default via 172.16.0.254 dev eth0  metric 10 
default via A.B.C.1 dev eth1.10  proto static  metric 50 
A.B.C.0/24 dev eth1.10  proto static  scope link  metric 50 
172.16.0.0/22 dev eth0  proto kernel  scope link  src 172.16.1.13 
192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.1 
broadcast A.B.C.0 dev eth1.10  table local  proto kernel  scope link  src A.B.C.D 
local A.B.C.D dev eth1.10  table local  proto kernel  scope host  src A.B.C.D 
broadcast A.B.C.255 dev eth1.10  table local  proto kernel  scope link  src A.B.C.D 
broadcast 127.0.0.0 dev lo  table local  proto kernel  scope link  src 127.0.0.1 
local 127.0.0.0/8 dev lo  table local  proto kernel  scope host  src 127.0.0.1 
local 127.0.0.1 dev lo  table local  proto kernel  scope host  src 127.0.0.1 
broadcast 127.255.255.255 dev lo  table local  proto kernel  scope link  src 127.0.0.1 
broadcast 172.16.0.0 dev eth0  table local  proto kernel  scope link  src 172.16.1.13 
local 172.16.1.13 dev eth0  table local  proto kernel  scope host  src 172.16.1.13 
broadcast 172.16.3.255 dev eth0  table local  proto kernel  scope link  src 172.16.1.13 
broadcast 192.168.0.0 dev eth1  table local  proto kernel  scope link  src 192.168.0.1 
local 192.168.0.1 dev eth1  table local  proto kernel  scope host  src 192.168.0.1 
broadcast 192.168.0.255 dev eth1  table local  proto kernel  scope link  src 192.168.0.1

ip -4 ru

0:      from all lookup 128 
1:      from all lookup local 
32766:  from all lookup main 
32767:  from all lookup default 

C.D.Enomaly?

ip route show table 128
172.16.0.254 metric 10 
A.B.C.1 metric 50 

i did this in accordance to mwan3.

output

root@OpenWrt:~# ip route show table 128
root@OpenWrt:~# 
1 Like

yup... this one is probably too complex for me... sorry was just thinking aloud...