Annotated edit history of
DestinationNetworkUnreachable version 4, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 2 |
PerryLorier |
1 |
[ICMP] reason subcode 0, used with ICMP reason code 3 to explain why a DestinationUnreachable message was sent. |
| 4 |
BenStaz |
2 |
|
| |
|
3 |
If a router cannot forward a packet because it has no routes at all (including no default route) to the destination specified in the packet, then the router must generate a Network Unreachable. |
| 1 |
MattBrown |
4 |
|
| |
|
5 |
It is usally generated by a gateway when it does not have a route for the destination specified in the IP packet that caused the error. |
| 3 |
PerryLorier |
6 |
|
| |
|
7 |
Note a server with a default gateway won't ever issue this message (since it always has a route for packets...). |
| |
|
8 |
|
| |
|
9 |
Reject routes can also solicit this error. I recommend you add the routes below to any machine that is physically on the internet. It'll make any packet that doesn't have a more specific route (via some VPN, or locally connected machine) generate an [ICMP] DestinationNetworkUnreachable message and not just leak random IP's out onto the Internet. |
| |
|
10 |
route add -net 10.0.0.0/8 reject metric 10000 |
| |
|
11 |
route add -net 192.168.0.0/16 reject metric 10000 |
