If you have a D-Link DIR-850L router, you should pay attention to this CERT notification. Apparently there’s a flaw in the firmware of this router that allows a remote attacker to run commands on the router. Effectively pwning the device. Now this becomes a really big deal is remote administration is enabled as anyone on the Internet can pwn the router. At present, D-Link has released beta firmware that apparently addresses this issue. However, I would take note of what CERT had to say about that:
The vendor has publicly disclosed the issue along with beta firmware releases (versions 1.14B07 h2ab BETA1 and 2.07B05 h1ke BETA1, depending on the device’s hardware revision), which are available from the product information page, but it is unclear whether the beta releases should be considered a proper solution.
I don’t consider beta anything to be a proper solution. Thus if you have one of these routers, the best that you can do is disable remote administration if you enabled it for whatever reason and wait for D-Link to come out with a proper solution to this.
BREAKING: Rogers Ignite Internet Down Across Southern Ontario
Posted in Commentary with tags Rogers on March 9, 2017 by itnerdRogers appears to have widespread and severe issues across Southern Ontario where Ignite Internet users are intermittently unable to surf the Internet and ping rates that are through the roof. Reports first surfaced on DSLReports of this at 5PM and were later confirmed by Canadian Outages as per this map that I took a screen shot of:
That is not a small piece of real estate. I can confirm that these problems exist and they are serious. As I type this, Rogers appears to not be admitting that they have an issue despite the fact that they clearly do. This will only add to the frustration of Rogers users who have suffered through their rather problematic rollout of DOCSIS 3.1 which I have documented here since late last year. Myself included.
Updates as they come.
UPDATE: A reader pointed me towards this Tweet where Rogers seems to be admitting that there is a problem. But they seem to be minimizing the impact:
UPDATE #2: According to a post on DSLReports, this appears to have started at 1:45PM. I took a screen shot of the post in question where you can see when the trouble began:
UPDATE #3: Rogers has finally publicly admitted on their Twitter feed that there is an issue:
UPDATE #4: At 3:30 AM this morning (Friday March 10th) the issue was apparently resolved. A modem reboot may be required to restore full functionality. But based on the e-mails and the odd Tweet that I have received, this might have been the last straw for Rogers customers who have been frustrated with issues that the provider has had over the last couple of months. Rogers retention department is going to be a very busy place today I suspect.
UPDATE #5: This appears to not be fixed. Please click here for a new story on this issue.
2 Comments »