Date: Wed, 28 Jun 1995 17:34:35 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: rsnow@legend.txdirect.net (Rob Snow) Cc: davidg@Root.COM, jbeukema@hk.super.net, hackers@freebsd.org Subject: Re: packet forwarding Message-ID: <199506280804.RAA20077@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.BSF.3.91.950629020541.408A-100000@oasis> from "Rob Snow" at Jun 29, 95 02:14:40 am
next in thread | previous in thread | raw e-mail | index | archive | help
Rob Snow stands accused of saying: > > Perhaps I'm missing something, but why would your ISP send packets for > > 10.x.x.x back to you? The "10" net is supposed to be local-only. > > #define PPP ppp machine with lp0 to LOST and tun0 to ISP > starts at 204.57.120.200 and gets reassigned to > 204.57.120.[50-100]. ifconfig lp0 inet PPP LOST > > #define LOST 204.57.120.201 with ifconfig lp0 inet LOST PPP > > #define ISP 204.57.120.3 Ok; I'll rephrase the question: why would your ISP send packets back to you for any host other than the one that's connected? Have you arranged with them for a route to be added every time you get a new IP address assigned? > LOST can NEVER ping/rlogin to ISP. How about you look at your modem lights and tell us whether the ping packets are going out, and whether they come back. I have an interesting story for you : genesis:~>traceroute 204.57.120.201 traceroute to 204.57.120.201 (204.57.120.201), 30 hops max, 40 byte packets 1 thebarton.net.adelaide.edu.au (129.127.96.87) 7.340 ms 3.544 ms 3.457 ms 2 pancho.adelaide.edu.au (129.127.92.86) 4.993 ms 3.555 ms 4.818 ms 3 sa.gw.au (129.127.12.1) 4.942 ms 4.328 ms 3.945 ms 4 national-sa.gw.au (139.130.40.1) 20.775 ms 23.580 ms 20.046 ms 5 usa.gw.au (139.130.240.2) 23.285 ms 25.028 ms 19.323 ms 6 border4-hssi1-0.SanFrancisco.mci.net (204.70.35.5) 288.579 ms 203.096 ms 198.989 ms 7 core-fddi-1.SanFrancisco.mci.net (204.70.3.161) 205.590 ms 201.714 ms 207 .041 ms 8 core-hssi-2.LosAngeles.mci.net (204.70.1.41) 213.136 ms 325.821 ms 413.63 2 ms 9 core-hssi-2.Houston.mci.net (204.70.1.33) 236.785 ms 249.729 ms 266.177 m s 10 border4-fddi0-0.Houston.mci.net (204.70.3.99) 238.812 ms 247.084 ms 240.2 73 ms 11 kblcom.Houston.mci.net (204.70.39.58) 254.885 ms 248.636 ms 240.165 ms 12 s12-cust.fibrcom.net (204.57.64.10) 255.286 ms 256.203 ms 255.440 ms 13 * s12-cust.fibrcom.net (204.57.64.10) 547.994 ms !H 253.274 ms !H genesis:~>traceroute 204.57.120.3 traceroute to 204.57.120.3 (204.57.120.3), 30 hops max, 40 byte packets 1 thebarton.net.adelaide.edu.au (129.127.96.87) 7.002 ms 3.493 ms 4.056 ms 2 pancho.adelaide.edu.au (129.127.92.86) 5.212 ms 6.165 ms 4.286 ms 3 sa.gw.au (129.127.12.1) 4.235 ms 4.218 ms 4.806 ms 4 national-sa.gw.au (139.130.40.1) 42.745 ms 26.573 ms 28.499 ms 5 usa.gw.au (139.130.240.2) 19.643 ms 18.720 ms 19.601 ms 6 border4-hssi1-0.SanFrancisco.mci.net (204.70.35.5) 210.667 ms 203.208 ms 205.689 ms 7 core-fddi-1.SanFrancisco.mci.net (204.70.3.161) 219.924 ms 207.232 ms 208 .312 ms 8 * core-hssi-2.LosAngeles.mci.net (204.70.1.41) 214.211 ms 221.210 ms 9 core-hssi-2.Houston.mci.net (204.70.1.33) 239.825 ms 252.157 ms 251.542 m s 10 border4-fddi0-0.Houston.mci.net (204.70.3.99) 237.784 ms 235.791 ms 236.0 65 ms 11 kblcom.Houston.mci.net (204.70.39.58) 258.455 ms 258.609 ms 250.428 ms 12 s12-cust.fibrcom.net (204.57.64.10) 257.253 ms 291.199 ms 255.267 ms 13 sat-rot1.txdirect.net (204.57.120.3) 251.562 ms 312.534 ms 256.176 ms Now, if you can read these, it tells us that your ISP isn't propagating a route to your system, and in fact, they don't even have a route to that half of their class C. > Rob Snow Blame where blame is due. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506280804.RAA20077>