Well, this is odd.
My airport is working fine, but everytime I connect my ethernet cable, it kills my internet. I just get a continuos white page, with waiting for Google at the bottom (or whatever website I try) Kills it instantly, within a second I would say.
Ethernet is getting good IP address from router, and is using the same DNS as Airport.
I've tried the usuals including:
Power cycle everything,
Turn off airport while trying the ethernet,
new Location,
Different User account,
Tried URL address and IP address,
Different Browsers,
From Terminal: dscacheutil -flushcache
Used Different computer, works fine
reset PRAM
Whats odd, is that I cant even log into my router. Also, even though I cant reach these websites, I can ping them. Trace route does show an interesting problem where I dont seem to get out of my ISP's servers.
Also, under network utility->info, I seem to have an unusually high Recv Errors. Recv Packets:396, Recv Errors:349
I ran tcpdump -n -i en0 port 53 from terminal and got this:
Any help would be massively appreciated.
My airport is working fine, but everytime I connect my ethernet cable, it kills my internet. I just get a continuos white page, with waiting for Google at the bottom (or whatever website I try) Kills it instantly, within a second I would say.
Ethernet is getting good IP address from router, and is using the same DNS as Airport.
I've tried the usuals including:
Power cycle everything,
Turn off airport while trying the ethernet,
new Location,
Different User account,
Tried URL address and IP address,
Different Browsers,
From Terminal: dscacheutil -flushcache
Used Different computer, works fine
reset PRAM
Whats odd, is that I cant even log into my router. Also, even though I cant reach these websites, I can ping them. Trace route does show an interesting problem where I dont seem to get out of my ISP's servers.
Code:
traceroute: Warning: www.google.com has multiple addresses; using 203.217.23.29
traceroute to www.l.google.com (203.217.23.29), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.026 ms 0.660 ms 0.568 ms
2 * nexthop.qld.iinet.net.au (203.55.228.88) 17.727 ms 17.392 ms
3 gi1-2.bne-pipe-bdr2.iinet.net.au (203.215.8.14) 20.766 ms 21.761 ms *
4 * po1.bne-pipe-bdr1.iinet.net.au (203.215.20.144) 84.378 ms 31.651 ms
5 gi1-0-4.syd-ult-core1.iinet.net.au (203.215.20.100) 30.342 ms * 31.713 ms
6 te1-4.syd-ult-bdr1.iinet.net.au (203.215.20.31) 30.363 ms * 40.002 ms
7 te1-2.syd-ult-bdr2.iinet.net.au (203.215.20.147) 30.349 ms 30.414 ms *
8 gi0-28.syd-ult-hsa1.iinet.net.au (203.215.16.67) 31.115 ms * 30.417 ms
9 * * *
I ran tcpdump -n -i en0 port 53 from terminal and got this:
Code:
tcpdump: WARNING: en0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes
03:27:50.029469 IP 192.168.0.2.56449 > 192.168.0.1.53: 1831+ PTR? 2.0.168.192.in-addr.arpa. (42)
03:27:50.115771 IP 192.168.0.1.53 > 192.168.0.2.56449: 1831 NXDomain 0/0/0 (42)
03:27:52.940554 IP 192.168.0.2.63408 > 192.168.0.1.53: 349+ A? slogin.oscar.aol.com. (38)
03:27:53.041436 IP 192.168.0.2.65506 > 192.168.0.1.53: 32196+ AAAA? slogin.oscar.aol.com. (38)
03:27:53.303032 IP 192.168.0.1.53 > 192.168.0.2.65506: 32196 1/0/0 CNAME slogin.gslogin.oscar.aol.com. (67)
03:27:53.391666 IP 192.168.0.2.54255 > 192.168.0.1.53: 56895+ A? slogin.gslogin.oscar.aol.com. (46)
03:27:53.491742 IP 192.168.0.2.50145 > 192.168.0.1.53: 24092+ AAAA? slogin.gslogin.oscar.aol.com. (46)
03:27:53.708753 IP 192.168.0.1.53 > 192.168.0.2.50145: 24092 0/0/0 (46)
03:27:54.192362 IP 192.168.0.2.63671 > 192.168.0.1.53: 56241+ PTR? 1.97.168.192.in-addr.arpa. (43)
03:27:54.492418 IP 192.168.0.2.54255 > 192.168.0.1.53: 56895+ A? slogin.gslogin.oscar.aol.com. (46)
03:27:54.535936 IP 192.168.0.1.53 > 192.168.0.2.54255: 56895 1/0/0 A 64.12.202.117 (62)
03:27:55.194160 IP 192.168.0.2.63671 > 192.168.0.1.53: 56241+ PTR? 1.97.168.192.in-addr.arpa. (43)
03:27:55.212982 IP 192.168.0.1.53 > 192.168.0.2.63671: 56241 NXDomain 0/0/0 (43)
03:27:55.216081 IP 192.168.0.2.51649 > 192.168.0.1.53: 18145+ PTR? 1.203.168.192.in-addr.arpa. (44)
03:27:56.218021 IP 192.168.0.2.51649 > 192.168.0.1.53: 18145+ PTR? 1.203.168.192.in-addr.arpa. (44)
03:27:56.237634 IP 192.168.0.1.53 > 192.168.0.2.51649: 18145 NXDomain 0/0/0 (44)
03:28:18.740472 IP 192.168.0.2.52057 > 192.168.0.1.53: 4653+ A? www.guardian.co.uk. (36)
03:28:19.742866 IP 192.168.0.2.52057 > 192.168.0.1.53: 4653+ A? www.guardian.co.uk. (36)
03:28:22.748700 IP 192.168.0.2.52057 > 192.168.0.1.53: 4653+ A? www.guardian.co.uk. (36)
03:28:22.769395 IP 192.168.0.1.53 > 192.168.0.2.52057: 4653 1/0/0 A 77.91.249.30 (52)
03:28:54.230828 IP 192.168.0.2.54275 > 192.168.0.1.53: 42061+ A? gmail-imap.l.google.com. (41)
Any help would be massively appreciated.