Timeline for One IP is not reachable unless creating a dummy route
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 22, 2023 at 9:06 | comment | added | Peregrino69 | ... I'm sorry for that, you're right, I embarrassingly SSHd into wrong RasPi running DietPi to check the routing table... | |
| Mar 22, 2023 at 8:48 | comment | added | Skippy | @Peregrino69, those routes were there since the first boot of my RPi. I tried to remove that one but completely lost the connection with my RPi, had to plug a screen and keyboard to recover. | |
| Mar 22, 2023 at 8:48 | comment | added | Skippy | @user1686, when ping is failing : host is in arp cache (and show as REACHABLE), arping is working, the mac in tshark is the mac in the arp cache. Even after succesful arping, ping is still failing. | |
| Mar 21, 2023 at 10:04 | comment | added | Skippy | Although not technically a dummy, it appears to be functionally useless since it should have been automatically routed through existing routes. The gateway appears to be rejecting it, so I will discontinue my workaround and monitor the network for the inevitable issues. I will keep you informed. | |
| Mar 21, 2023 at 9:43 | comment | added | grawity_u1686 |
It's not a dummy route; it's a functional route that makes the packets take a different path. Does the device show up in your client host's ARP cache (ip -4 n) after the failed ping attempts? Does it respond to arping? Does your packet capture show the correct "destination MAC" for the failed ping attempts?
|
|
| S Mar 21, 2023 at 9:25 | review | First questions | |||
| Mar 21, 2023 at 9:32 | |||||
| S Mar 21, 2023 at 9:25 | history | asked | Skippy | CC BY-SA 4.0 |