All devices backing off
SteveInWA:
Obihai is investigating this now.
sorin:
Same here on both my devices, 100 and 200. I restarted my modem, router, obi gizmo, same results. I noticed similar messages on other forums (dslreports) as well so it appears to be an outage. OBI support, any help? Thanks
GPz1100:
@Webslinger,
I think you changed one of your comments after posting, but this gave me an idea.
Quote
Occasionally the obi box will create a successful connection too.
There's no issue when the router is booted, followed by the ATA.
When the ATA reboots on its own, then this issue can occur.
This suggests that whatever the obi box is trying to access is probably down, but is still part of a dns hunt group.
I think you or someone else posted this earlier.
Code:
name 74.125.130.125 GTalk01 description Google talk server
name 74.125.134.125 GTalk02 description Google talk server
name 74.125.139.125 GTalk03 description Google Talk server
*name 74.125.142.125 GTalk04 description Google Talk server
name 74.125.192.125 GTalk05 description Google Talk server
name 74.125.140.125 GTalk06 description Google Talk server
*name 74.125.137.125 GTalk07
name 74.125.138.125 GTalk08
name 74.125.141.125 GTalk09
name 74.125.136.125 GTalk10
name 74.125.135.125 Gtalk11
The two addresses with * next to them don't respond to ping. I wonder if what happens is when rebooting the obi, it tries to connect to one of those two. Since the router has cached the ip's, it keeps trying until the router is rebooted (or cache cleared). Randomly, another ip is chosen. It may be the same one, may be different.
I think that explains why sometimes a connection happens, other times not.
sorin:
Working now - thanks, OBI!
Webslinger:
Quote from: GPz1100 on October 31, 2017, 05:45:10 pm
@Webslinger,
I think you changed one of your comments after posting
Yeah, I deleted that because I wasn't entirely sure how random the issue was, but when
I was testing for a friend, the issue was occurring only when the ATA was being rebooted without
the router also being rebooted.
When the router rebooted as well, before the ATA rebooted, then the issue didn't occur.
But it wasn't as though I was testing that over and over again for hours.
Quote
I think you or someone else posted this earlier.
Yes, that's a very old search result though. I was just randomly looking for Google Talk IPs and stumbled across that link.
Quote
Since the router has cached the ip's, it keeps trying until the router is rebooted (or cache cleared). Randomly, another ip is chosen.
Sure, but I'm more interested in where these backward server IPs are getting pulled from. I'd have to, remotely, check someone's logs, telnet into her router, etc.
Navigation
[0] Message Index
[#] Next page
[*] Previous page