Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Diagnosing connection issue



Bill Bogstad wrote:
>
> Some more ideas:
>
> 1. Maybe pings work because they are small packets.   Maybe something
> is flaky in handling full size packets.  Try specifying packet sizes
> to ping (ping -s).
> 2. Check stats on your network card with "ifconfig" to look for
> errored or dropped packets.  If your home router has a status page
> with similar info check that as well.
>    

> UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:9082 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8245 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:8784118 (8.7 MB)  TX bytes:1287695 (1.2 MB)

It just did it again, this time in Linux.  I was able to telnet to the 
router while it occurred, the connection was successful.  ifconfig info 
is above - taken /after/ the connection resumed.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org