Re: how to generate a host/network unreachable

Robert Forsman (thoth@cis.ufl.edu)
Wed, 05 Jun 1996 14:24:57 EDT

jeffm@iglou.com (Jeff Mcadams) ,in message <m0uRMac-000s8TC@iglou.com>, wrote:

> If the destination network is running a routing protocol which is
> capable of advertising that the eventual destination doesn't exist (ie
> BGP4) then, yeah, you're going to get a Host Unreachable as well...if
> things are statically routed though....its unlikely that you will get a
> host unreachable (unless someone went in and blew away the static routes
> when they found out the destination was unreachable...which is unlikely)
> and you'll get the ping-pong.

Unlikely, I'll grant that. But I SHOULD be getting such messages. I'm
getting normative here and noone seems to care.

"All I wanted was a goddamn pepsi"

I want to prevent this:

slack:16 $ traceroute 207.100.2.7
traceroute to 207.100.2.7 (207.100.2.7), 30 hops max, 40 byte packets
1 grad1-n71.ortge.ufl.edu (128.227.71.1) 2 ms 2 ms 1 ms
2 cse-wfl-001-n020.core.ufl.edu (128.227.20.1) 17 ms 5 ms 4 ms
3 cse-wfl-001-n254.core.ufl.edu (128.227.254.2) 17 ms 6 ms 7 ms
4 ssrb-cis-f30-b252.nerdc.ufl.edu (128.227.252.10) 8 ms 14 ms 13 ms
5 jacksonvil-cr1.bbnplanet.net (192.221.6.13) 63 ms 18 ms 11 ms
6 atlanta3-cr2.bbnplanet.net (192.221.48.1) 191 ms 171 ms 286 ms
7 192.221.42.100 (192.221.42.100) 112 ms 77 ms 94 ms
8 borderx1-hssi2-0.Atlanta.mci.net (204.70.86.101) 116 ms 128 ms 150 ms
9 * core2-fddi-0.Atlanta.mci.net (204.70.86.49) 152 ms 251 ms
10 core3.Washington.mci.net (204.70.4.29) 265 ms * *
11 206.157.77.26 (206.157.77.26) 113 ms 132 ms 145 ms
12 Fddi0/0.CR1.DCA1.Alter.Net (137.39.33.130) 148 ms 136 ms *
13 101.Hssi4/0.GW1.ATL1.Alter.Net (137.39.30.26) 128 ms 129 ms 110 ms
14 * 137.39.37.67 (137.39.37.67) 132 ms 157 ms
15 * 137.39.140.22 (137.39.140.22) 94 ms 137 ms
16 137.39.140.22 (137.39.140.22) 153 ms 95 ms 122 ms
17 icix-rtr44.icix.net (206.72.129.44) 152 ms 220 ms *
18 icix-uunet.icix.net (206.72.129.1) 111 ms 173 ms 134 ms
19 icix-uunet.icix.net (206.72.129.1) 297 ms 211 ms 204 ms
20 icix-rtr44.icix.net (206.72.129.44) 237 ms 220 ms 166 ms
21 icix-uunet.icix.net (206.72.129.1) 195 ms * 186 ms
22 icix-uunet.icix.net (206.72.129.1) 164 ms 648 ms 168 ms
23 icix-rtr44.icix.net (206.72.129.44) 263 ms 220 ms 568 ms
24 icix-uunet.icix.net (206.72.129.1) 274 ms 328 ms 228 ms
25 * * icix-uunet.icix.net (206.72.129.1) 274 ms
26 icix-rtr44.icix.net (206.72.129.44) 346 ms 296 ms 268 ms
27 * icix-uunet.icix.net (206.72.129.1) 487 ms 226 ms
28 icix-uunet.icix.net (206.72.129.1) 901 ms 293 ms 341 ms
29 icix-rtr44.icix.net (206.72.129.44) 792 ms * *
30 icix-uunet.icix.net (206.72.129.1) 265 ms 318 ms 398 ms
slack:17 $

I don't care if no one will ever traceroute to that host. I'm anal
retentive and I want to make icix-rtr44.icix.net (a Livingston
firewall/router) return a network unreachable ICMP packet. This is a
multiple choice question:

a) You can't do that with Livingston gear
b) ComOS release x.y will let you do that with the following syntax:
____________________

The first few c & d answers were OK, but I've had enough non-answers that
I'm making an RFE.

> add nondefault 207.200.0.0/22
> add nondefault 207.200.4.0/23

(when there's no static route for an address in the above-mentioned ranges,
return a network unreachable ICMP packet)