On Wed, Feb 13, 2002 at 04:30:05PM -0800, Cy Schubert - CITS Open Systems Group wrote: > In message <03f401c1b4bb$7f97bfa0$34f820c0@ix1x1000>, "Michael Meltzer" > writes: > > I try it out tonight, head good things about it already, ThankYou. > > > > For what is worth, it seems the problem he is really a > > routing table issue, it seem that on FreeBSD-stable (without the code) if > > you where trying to ping 127.0.0.2 (which is not defined) the message goes > > out the default route, which is a bad thing :-) but by adding "route > > add -net 127.0.0.0 127.0.0.1 255.0.0.0" which cleaned > > this up nicely and BTW is how most interfaces handle unknow local networks > > hosts > > :-) I am sure that thier is a problem doing this (never seen local host > > route the address 127.* space, :-) but ..... > > With UNIX there are a dozen ways to solve any problem. Here is > solution #2. > > /sbin/route add -net 127.0.0.0 -netmask 255.0.0.0 -iface lo0 -blackhole > Perhaps you don't realize that this fixes only the half of the problem. The other half is the source address in -net 127:
ping -S 127.1 1.2.3.4 telnet -s 127.1 1.2.3.4 The routing doesn't solve this, and firewall is optional. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
