Resolved: OBI110 GV says "Resolving DNS" in dashboard
RonR:
Quote from: QBZappy on April 06, 2011, 02:37:46 pm
I am using a different build version of Tomato on my router.
You're two builds out of date. Time for an update. :)
QBZappy:
RonR,
When I find some time, I'll do it. I hope I don't suffer "Pandora's fate" re the OBi. This will become known as the official name for this issue. :D
Pandora:
Got it up and working this morning. I have several layers of protection on my router / network. One is opendns which should have been overridden by manually entering my Comcast HSI DNS servers to the OBi110 network configuraiton. Today I put talk.google.com on my white list in Opendns.
The following were blocked on the router:
TCP/UDP, all ports, L7: directconnect
TCP/UDP, all ports, L7: netbios
TCP/UDP, all ports, L7: msn-filetransfer
TCP/UDP, all ports, L7: pcanywhere
TCP/UDP, all ports, L7: radmin
also blocked were the following patterns:
analytics
hitbox
edge.quantserve.com
iv_drawAd
adserver
srv2.wa.marketingsolutions.yahoo.com$
wpad
***
I'm undertain which of the above were the source of my connection issue, but will begin to try and better resolve the problem by identifying the specific cause. I'll report back once I have more information so this thread can be available to future users with similar connectivity issues.
Pandora:
Resolved:
Opendns repoted over 500 attempts to access talk.google.com yesterday. My router uses opendns, but I had configured my OBI110 to use Comcast's DNS servers and not my router to resolve URL's.
After testing disabling and re-enabling filters, it turns out my OBI110 was trying to access talk.google.com via opendns (through my router) despite having configured different DNS servers on my OBI network configuraiton page.
The problem seems to be the OBI firmware at least in part using the DHCP DNS server even if another DNS server is specified.
Thanks to all who helped. With any luck a future firmware fix will fully resolve this issue.
freetalk:
Hi Pandora,
OBi will always contact the statically configured DNS first. For this issue, I suspected that:
1. opendns probably blocked all DNS requests other than to the router OR
2. opendns intercepted all outgoing DNS requests and replied itself.
Navigation
[0] Message Index
[#] Next page
[*] Previous page