Hmmmm. Wayne,
I put in an external wireless card and pinged.
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_req=1 ttl=64 time=1.88 ms
64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=1.62 ms
64 bytes from 192.168.1.254: icmp_req=3 ttl=64 time=1.64 ms
64 bytes from 192.168.1.254: icmp_req=4 ttl=64 time=1.66 ms
64 bytes from 192.168.1.254: icmp_req=5 ttl=64 time=1.57 ms
64 bytes from 192.168.1.254: icmp_req=6 ttl=64 time=1.60 ms
64 bytes from 192.168.1.254: icmp_req=7 ttl=64 time=1.58 ms
64 bytes from 192.168.1.254: icmp_req=8 ttl=64 time=1.56 ms
64 bytes from 192.168.1.254: icmp_req=9 ttl=64 time=1.58 ms
64 bytes from 192.168.1.254: icmp_req=10 ttl=64 time=1.83 ms
64 bytes from 192.168.1.254: icmp_req=11 ttl=64 time=2.30 ms
64 bytes from 192.168.1.254: icmp_req=12 ttl=64 time=1.54 ms
^C
--- 192.168.1.254 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11017ms
rtt min/avg/max/mdev = 1.546/1.701/2.300/0.207 ms
Then when I try and connect to post results. I can't connect. With external wireless card that works on every other computer in the house. I get traceroute results as follows -
traceroute
http://www.yahoo.comtraceroute to
http://www.yahoo.com (209.191.122.70), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I haven't a clue what's happening! The other wireless card I used at first disappeared. But this one I'm using had worked once before. (Thanks for the ctrl-c, by the way) I think what makes this more complicated is that THIS computer has three differences from the rest of the computers in the house that work on the modem. #1 - runs Mint 12 (The rest run Mint 9) #2 - Has n-band wireless card (the rest have b or g) #3 - Uses Chrome (the rest use Firefox). On this computer I've tried using Epiphany with the same result so I don't think it's the browser.