[SATLUG] Ping with 75%+ packet loss!

Tony Beauregard tonybeau at cajunbro.com
Thu Aug 29 00:20:03 CDT 2002


The problem may be something like not having identd running (you don't
need to have this running).

Basically, set a firewall rule to reject (specifically) port 113.  The
reject on port 113 should allow for a immediate connection and you will
stop losing those packets.  

Hopefully this helps.  (Thank Sparky for this one if it does.)

Tony

On Mon, 2002-08-26 at 18:11, Jeff Edmonson wrote:
> 
> 
> > > > More on this ODD case...
> > > > If I ping the IP address instead of the name, I get ZER0% packet loss.
> > >Seems
> > > > like I'm having a DNS issue here.
> >
> > >what does your /etc/resolv.conf look like?
> >
> > search cox.net sd.cox.net
> > nameserver 68.6.16.30
> > nameserver 68.2.16.30
> > nameserver 68.1.17.5
> > All ping-able at ZERO% loss!
> 
> 
> what happens when you ping cox.net instead of the ip address?
> 
> 
> 
> 
> _______________________________________________
> Satlug mailing list
> Satlug at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug





More information about the Satlug mailing list