Brie Gordon
I'm Brie, a 22 year-old graduate of Slippery Rock University's Computer Science department. My interests include Linux (generally and Ubuntu), networking, BSD-style operating systems including my own, BrieSD, translating English-Spanish-English for open source projects and LAMP configuration. Aside from that, I enjoy photography, making short films and soccer.
Posterous is one of my favorite new(ish) web sites!
brie@briegordon.com
Search
Tags
- comcast (3)
- advanced (2)
- custom (2)
- customization (2)
- google (2)
- ISP (2)
- linux (2)
- network (2)
- network latency (2)
- posterous (2)
- View all 92 tags
- programming (2)
- python (2)
- Apache (1)
- auth (1)
- backbone (1)
- backgrounds (1)
- backup (1)
- bash (1)
- bash script (1)
- bin (1)
- brainstorm (1)
- calculator (1)
- capacity (1)
- client (1)
- collatz (1)
- collatz conjecture (1)
- compliant (1)
- contract (1)
- core (1)
- crawl (1)
- crawler (1)
- cron (1)
- css (1)
- customer service (1)
- default (1)
- dropbox (1)
- email (1)
- favicon (1)
- fios (1)
- folder (1)
- friends (1)
- gmail (1)
- googlebot (1)
- google wave (1)
- grep (1)
- host (1)
- hosting (1)
- image (1)
- imgur (1)
- interview (1)
- invites (1)
- IP (1)
- latency (1)
- logs (1)
- lonely (1)
- mailing lists (1)
- math (1)
- mathematics (1)
- newbie (1)
- NIX (1)
- open source (1)
- packet (1)
- packet loss (1)
- php (1)
- ping (1)
- provider (1)
- python development (1)
- reality (1)
- reddit (1)
- RFC (1)
- rfc822 (1)
- robots (1)
- robots.txt (1)
- routing (1)
- rsync (1)
- sales tax (1)
- script (1)
- security (1)
- SEO (1)
- server (1)
- ssh (1)
- technician (1)
- throttling (1)
- tweet (1)
- twitter (1)
- ubuntu (1)
- unix (1)
- verizon (1)
- virtue (1)
- wave (1)
- web (1)
- windows7 (1)
December 11th, 9:32pm
2 comments
ISP Trouble? For best results, do this first.
Occasionally, I experience some network latency and packet loss through my ISP, Comcast. When this happens, I let them know about it - and you should, too.
Before you do that, though, there are some things that you should do, as dumb as they may sound. They *will* help you get through to your ISP. Reboot your computer. Reboot your router. Reboot your modem. (For the last two, unplugging the power cable should suffice; don't forget to plug it back in.)Finally, you should gather some data to give them. I like to do this by setting up some pings to places in different geographical locations. I've written a script (tested on Linux and FreeBSD) to get this ping party started. FreeBSD users may have to change the interpreter to #!/usr/local/bin/bash first. Here is the script:#!/bin/bash#### uhoh #### ISP Trouble Script #
# Author: Brie A. Gordon
# brie@unixsysadmin.org
# I run this when I'm having trouble with Comcast. # Replace the line below with the IP of your router.
gnome-terminal -e "ping 10.100.1.1" -t "router" &# Located in Pittsburgh
gnome-terminal -e "ping cmu.edu" -t "pgh" & # My ISP
gnome-terminal -e "ping comcast.com" -t "ISP" &# Located in Australia
gnome-terminal -e "ping news.com.au" -t "australia" & # Located in California
gnome-terminal -e "ping dreamhost.com" -t "california" &#Located in Germany
gnome-terminal -e "ping joker.com" -t "germany" &
Filed under
bash
bash script
comcast
ISP
latency
linux
network
network latency
packet
packet loss
script
unix
Posted 7 months ago
2 Comments