odd... when I first tried pinging it, we had a customer on the phone
with the issue (as well as a few after that). I wonder if the routers
needed to be rebooted after it came back up before they work.
As long as the customers don't know you fixed it, there shouldn't
really be much of a worry that customers will make it your problem in
the future.
--------------------------------------------------------------------------------
From: Af [af-boun...@afmug.com] on behalf of Tushar Patel via Af
[af@afmug.com]
Sent: Tuesday, October 07, 2014 11:38 AM
To:af@afmug.com
Subject: Re: [AFMUG] Belkin routers going nuts
We did “torch” (one of the Mikrotik tools), that allows me to see the
destination address of 67.20.176.130, with protocol and the number of
source address accessing that. The number of source address trying to
access that was very high. Since morning we must have taken over 20 to
25 calls on the subject. So from the resource stand point it was more
efficient for us to implement loopback response then to keep taking
the call. We did not tell any customers what we did to fix it.
How it works: it appears that those Belkin routers were just trying to
ping the that ip address, so by putting loop back on our network, we
are essentially responding to that ip address and that make the Belkin
router happy.
As you mentioned below that you were able to ping it, earlier we were
not able to ping that ip address, may be they have already fix the
problem.
Thanks,
Tushar Patel
512-257-1077
www.westernbroadband.com
From: Af [mailto:af-boun...@afmug.com] On Behalf Of Mathew Howard via
Af
Sent: Tuesday, October 07, 2014 11:18 AM
To:af@afmug.com
Subject: Re: [AFMUG] Belkin routers going nuts
Yeah... if I were to do something like that, I wouldn't let any
customers know I did it... but I don't like messing with the network
to fix things that aren't really my problem anyway, it would be nice
to make those calls stop, but it doesn't seem worth it.
I'm still a bit confused how that is making it work anyway though,
since I can ping that IP... how does putting it on an internal router
make it work? for those who have done it, is your router giving any
HTTP response on that IP?
--------------------------------------------------------------------------------
From: Af [af-boun...@afmug.com] on behalf of That One Guy via Af
[af@afmug.com]
Sent: Tuesday, October 07, 2014 11:06 AM
To:af@afmug.com
Subject: Re: [AFMUG] Belkin routers going nuts
that sounds alot like doing Belkins job for them, and guarantees from
that point forward everytime a customer has any issue. "just do that
brokeback loop thing you did, this is your problem, fix it now, i pay
good money for this service, i run a business, and my kids go to
school and my pacemaker will stop"
On Tue, Oct 7, 2014 at 10:53 AM, Tushar Patel via Af <af@afmug.com>
wrote:
As somebody suggested earlier to put loopback with the 67.20.176.130,
on one
of the internal router appears to fix the problem.
Thanks,
Tushar Patel
512-257-1077
www.westernbroadband.com
-----Original Message-----
From: Af [mailto:af-boun...@afmug.com] On Behalf Of David via Af
Sent: Tuesday, October 07, 2014 10:42 AM
To: af@afmug.com
Subject: Re: [AFMUG] Belkin routers going nuts
We are seeing this also..
Belkin domain is down
Also be aware that the belkins use heartbeat.belkin.com to check to
see
if there is internet access and if the answer
comes back negative then it will not connect any lan clients to
internet.
Also there are a few exploits that have been exposed on 1.00 firmware
which do bad things to the wan side of things.
I am currently trying to spoof heartbeat.belkin.com to our internal
dns
to fool the router into thinking everything is ok.
On 10/07/2014 09:11 AM, Mark Radabaugh via Af wrote:
> 13 customers so far today - all Belkin.
>
> Powned?
>
> Mark
>
> On 10/7/14, 10:04 AM, Darren Shea via Af wrote:
>> Is anyone else getting inundated with a flood of customers who
can't
>> connect to the internet through their Belkin routers this
>> morning?
>> What's the deal with that?,
>> Darren
>>
>>
>>
>
>
--
All parts should go together without forcing. You must remember that
the parts you are reassembling were disassembled by you. Therefore, if
you can't get them together again, there must be a reason. By all
means, do not use a hammer. -- IBM maintenance manual, 1925
