this post was submitted on 27 Jul 2024
7 points (88.9% liked)
Network Engineering
586 readers
1 users here now
All things enterprise network engineering, design, and architecture.
Rules
- No low effort posts
- No home networking topics
- No memes
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I believe so, yes. The routing table should result in the PC sending the response via the direct route, as opposed to via the defGW. I'm not 100% sure, though. There could be some "default" behavior of using the same nic as the one the packet was received on, stemming from the original 192.168.2.0/24 destination.
I recently tested this using wireshark. When I run packet capture on nic1 of dstPC I see ping request packets coming, but no response packets leaving the interface. On nic2 I don't see any packets leaving either. So kind of stumped what is happening. It seems the computer just drops the response packet and it never makes it till any nic. But still don't have a good explanation of WHY the packet gets dropped.
Probably rp filtering.
https://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.kernel.rpf.html