2 Answers
- Newest
- Most votes
- Most comments
1
Looking at the route table in the screenshot you shared I see there is an entry for 10.2.0.0/24 with local route (gateway 0.0.0.0).
This is the reason why the instance attempts to directly ARP resolve the 10.2.0.35 IP address instead of sending it through the next-hop gateway.
I'm not sure how that entry got in your route table but one you will get rid of it I expect the problem to be resolved.
0
You meant the following ?
I did the following: route add -net 0.0.0.0 dev eth1 Strangely, the second day I noticed it worked.
thanks a lot !!
answered 19 days ago
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked 9 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 8 months ago