Date: Wed, 12 May 2010 06:26:44 +0300 From: Ed Jobs <oloringr@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Odd routing issue... Message-ID: <201005120626.44764.oloringr@gmail.com> In-Reply-To: <4BEA1B88.8050702@wingfoot.org> References: <4BEA1B88.8050702@wingfoot.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4920005.JgmZsTdu4Q Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Wednesday 12 of May 2010 06:07, Glenn Sieb wrote: > I'm getting a route added upon reboot with the hostname of the box, > going to lo0. > It's preventing things like, pinging itself. I can manually delete the > route, but.. where is it being set to begin with?! well, that behaviour is what i would expect. After all, the machine knows t= hat=20 to ping its own ip, it has to use the lo0 interface. It just resolves your ip with the hostname of the machine. So as far as i see, this is the intended behaviour. (You can use netstat -rn to see the actual ip and not hostnames.) If you can't ping localhost, i'd say that the problem lies elsewere.=20 (firewalls probably) You can check with tcpdump to see what happens and your pings don't get a=20 reply. =2D-=20 Real programmers don't document. If it was hard to write, it should be hard= to=20 understand. --nextPart4920005.JgmZsTdu4Q Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAkvqH/QACgkQBPpdVEWKA31j4wCgvSE2N6+8ZbUKOrNczxqRfGfL 6e4AnRQsMcqhWQdkPws+p38SrkyOcMZD =OFp2 -----END PGP SIGNATURE----- --nextPart4920005.JgmZsTdu4Q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005120626.44764.oloringr>