[SATLUG] Ping with 75%+ packet loss!
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.)
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 18.104.22.168
> > nameserver 22.214.171.124
> > nameserver 126.96.36.199
> > 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
More information about the Satlug