Mac OS X, (and Probably) *nix Question

Oct 28 21:32:04 The-Abyss mDNSResponder: Repeated transitions for interface en1 (192.168.0.101); delaying packets by 5 seconds
Oct 28 21:33:03 The-Abyss mDNSResponder: Repeated transitions for interface en1 (192.168.0.101); delaying packets by 5 seconds


What do those log entries mean, exactly?

In case you haven't guessed, I'm having browsing problems.

 

Generic (Class C) IP's.

Hmmm, are you on a switch/router?

Shouldn't this be under the NETWORKING forum? (Just kidding! )

 

Actually, yes, ROFL.

Yeah, its a generic IP, Im using a Dlink router.

I may* have found a cure...after several channel changes. Maybe the neighbor bought a new 2.4ghz phone.



Its really irritating when it happens. I'm getting 3-5 second delays when browsing, and its only on my Mac.

 

Things I have already tried:

Cleared log files, caches, run cron scripts, rebooted router, modem, etc.

 

If the MAC is DIRECTLY connected to your cable/dsl modem what happens?

 

I didn't even try that...duh!

I assumed all was good on the router end if my wife's laptop was fine. I'll have to wait until such time I don't disconnect her from Everquest 2.

I don't want to get my butt kicked

 

You must always narrow down all issues. Networks are always hard to deal with.

Can you PING your router. Do know the IP of your router?

Can you PING www.majorgeeks.com?

Resolve majorgeeks.com's IP.

Ping that address.

If you can't, can you browse, by useing the ip itself?

What about your host table? Etc, etc.

How old/bad is your cable. Wireless (bad bad/shame shame) should be WPA if not WPA2.

I personally hate wireless networks. It is nice, but, in the end, to easy to hack into.

Can you ping your Wife's IP?

 

Yep. Everything works, just with a delay.

Even traceroutes and pings show low latency, yet are slow in displaying in the console and network utility. Router logs don't indicate any trouble, I don't use a static host table. Cable is a 9Mbps/1Mbps connection, which if I do a speedtest from the laptop...well, I'll show you. Wireless network, using WPA-PSK, SSID broadcast disabled, Mac filtering, etc.

Still getting some delays, even between posts.

 

And at this moment, its fine.


Argh!

 

I always find that threating the computer with a hammer, usually cures most problems.


I'd do a ping -t ipaddress, and monitor what is going on.


Not sure if this is the typical continuous ping for Apples. I just did a quick ping /? within xp.

To me, there seems some sort of latency between your MAC and your router.

Is there any firmware updates for your router? What about drivers for you NIC?

Speaking of router, what make/model are you using?

 

Whelp...getting closer.

I'm getting 16% packet loss, sending 100 packets to dslreports.com.

 

The question I have is this. Have we determined this is a router issue, or a MAC (Not Mac Address) issue.

Unfortunately, YOU have a wife who is a major EQ geek (was going to say crackhead, but though better....


A rather simple (maybe) resolution, is to reset the router. No, not by unplugging the power to the router, but by physically, reetting the router. Should be a small pin hole next to the power cable.

Why am I saying this? I ran into a similar situation. I tried everything, that I could think of. At this person's house.

I could describe all the things, but, I'll cut this short. Resetting the router fixed all issues. RESET. Not unplug the power!!!

But, that was my situation, similar to yours, but not identical.

 

I'll give it a shot, if she ever gets out of the game!



To answer your question, no, I havent determined if its router or Mac issue yet. I'm still waiting for her to stop playing.

Evercrackhead, indeed

 

Update:

Wired directly to modem: Same problem.
Cleaned installed OS X: Same problem.
New info: If I enter in an IP, it works great. the hang up is with DNS resolution.
However, it doesn't happen with my other computers.

 

I don't pretend to know how or why, but apparently I am not alone. It must be the OS?

At any rate, I've fixed it be specifying the DNS server, instead of letting DHCP assigning it from the modem, or router.

 

I've been thinking about it. there are two DNS servers listed in my router. If I enter both, I have the same problem.

So...my theory is that there is a slow DNS server on the Cox network. OS X is trying to use it only (its first in the list), and not choosing the fastest path. Windows, OTOH, is. So...to make a long story short, I am wondering if there is some tweak I can make to have OS X "time out" sooner before chooing another DNS server?

I found someone on the Cox forum @dslreports.com with the same exact issue, starting around the same time.

So I think its an ISP DNS server issue, ultimately.

 

Yup, thats exactly the problem. Specified the DNS server in my router, problem solved.