On 10/7/14 10:14 PM, Christopher Morrow morrowc.li...@gmail.com wrote:
On Tue, Oct 7, 2014 at 8:56 PM, Larry Sheldon larryshel...@cox.net
wrote:
I am having trouble understanding why a router would need a heartbeat
from
some foreign location. Or even what it would do with one.
One, not
On Wed, Oct 8, 2014 at 10:18 AM, Lee Howard l...@asgard.org wrote:
On 10/7/14 10:14 PM, Christopher Morrow morrowc.li...@gmail.com wrote:
On Tue, Oct 7, 2014 at 8:56 PM, Larry Sheldon larryshel...@cox.net
wrote:
I am having trouble understanding why a router would need a heartbeat
from
some
Seeing reports bounce around on the WISPA lists. Looks to be widespread.
Reports on their twitter as well.
I've had one customer with an issue related thus far.
Nick Olsen
Network Operations (855) FLSPEED x106
From: Parrish, Luke
, as reported by several random
people on the Internet.
From: Nick Olsen [n...@flhsi.com]
Sent: Tuesday, October 07, 2014 8:56 AM
To: Parrish, Luke; nanog@nanog.org
Subject: re: Belkin Router issues this morning?
Seeing reports bounce around on the WISPA lists
On Oct 7, 2014, at 8:34 AM, Justin Krejci jkre...@usinternet.com wrote:
https://twitter.com/search?q=%23belkin
Sounds like a bad firmware update most likely.
Presumably the Belkin routers perform caching DNS for the LAN clients for if
the LAN clients use alternate DNS servers (OpenDNS,
Geesh. It was a tough day - lots of our customers with Belkin devices. Agree it
has been fixable with customer changes but would have been better not to have
to respond to this today (obviously).
Regards,
Jason
Jason Livingood
Comcast - Internet Services
On Oct 7, 2014, at 12:08, Steve
Sounds like it might have been a DNS issue of some sort. The end result was
that the customer routers couldn't reach their heartbeat server, which made
them think they weren't on the net. The routers would then be helpful and
redirect all customer port 80 traffic to the router's configuration page
And this, my friends, is why friends don't let friends buy Belkin...
Apparently, you still can't fix stupid, no matter how hard you try.
-Mike
On Tuesday, October 7, 2014, John Neiberger jneiber...@gmail.com wrote:
Sounds like it might have been a DNS issue of some sort. The end result was
While we weren't really impacted by this issue, my understanding is that
the Belkin devices ping 'heartbeat.belkin.com' periodically. If their
pings fail, they do DNS redirection to the device's configuration
interface and alert the user of the error.
It appears that this server went down or had
Looks like belkin¹s fix was to add different records.
DNS response this morning.
heartbeat.belkin.com. 4h14m31s IN A 67.20.176.130
DNS response this evening.
dig heartbeat.belkin.com +short
54.163.115.57
23.20.47.97
54.227.172.225
54.161.217.33
54.163.87.225
54.87.220.73
54.163.74.132
On Tue, 07 Oct 2014 16:27:16 -0600, John Neiberger said:
Sounds like it might have been a DNS issue of some sort. The end result was
that the customer routers couldn't reach their heartbeat server, which made
them think they weren't on the net.
Seems like a dubious idea to equate can't reach
On 10/7/2014 17:32, Mike Lyon wrote:
And this, my friends, is why friends don't let friends buy Belkin...
Amen.
Side question? What happens is somebody is unwise to use Belkin routers
on an internal, not-connected-to-the-Interatubes network (Like, for
example, the network I tried to get
On Tue, Oct 7, 2014 at 8:56 PM, Larry Sheldon larryshel...@cox.net wrote:
I am having trouble understanding why a router would need a heartbeat from
some foreign location. Or even what it would do with one.
One, not crazy, line of thinking is that: Instead of being cryptic
and difficult to
13 matches
Mail list logo
