# ICMP redirect received from 10.0.0.1 for destination 192.168.1.100

- **ID:** `networking/icmp-redirect-received`
- **Domain:** networking
- **Category:** network_error
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

A router sent an ICMP redirect message indicating a better route exists for a destination, often due to suboptimal routing configuration or asymmetric routing paths.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Linux kernel 6.1 | active | — | — |
| FreeBSD 13.2 | active | — | — |
| Cisco IOS 15.9 | active | — | — |

## Workarounds

1. **Accept the redirect and update routing table: route add -net 192.168.1.0/24 gw 10.0.0.2 dev eth0** (90% success)
   ```
   Accept the redirect and update routing table: route add -net 192.168.1.0/24 gw 10.0.0.2 dev eth0
   ```
2. **Disable redirects only on the specific interface: sysctl -w net.ipv4.conf.eth0.accept_redirects=0** (95% success)
   ```
   Disable redirects only on the specific interface: sysctl -w net.ipv4.conf.eth0.accept_redirects=0
   ```

## Dead Ends

- **** — Disabling ICMP redirect processing globally (net.ipv4.conf.all.accept_redirects=0) may break legitimate routing updates and cause packet loss. (75% fail)
- **** — Ignoring the redirect without updating routing tables can lead to persistent suboptimal paths and increased latency. (80% fail)