10 ms·
D-Link says it won't patch 60k older modems
- smitelli 2y agoBackground on the underlying context of the bug: https://www.youtube.com/watch?v=-vpGswuYVg8 https://www.youtube.com/watch?v=-vpGswuYVg8 -- It's objectively unforgivable.
- amiga386 2y agoTL;DW: Call GET /cgi-bin/account_mgr.cgi?cmd=cgi_user_add&name=%27;<INJECTED_SHELL_COMMAND>;%27 account_mgr.cgi is safe, it takes web parameters "name", "pw" and calls the equivalent of execlp(..., "account", "-u", name, "-p", pw); "account" was written by the intern and runs sprintf(buf, "adduser \"%s\" -p \"%s\" >/dev/null", opt_u, opt_p); system(buf);
- jasonladuke0311 2y agoThat’s insane.
- rstuart4133 2y agoIt's also wrong. If the C code presented is accurate the URL would have to contain &name=%22;shell-command-to-run;%22, or perhaps &name=$(shell-command-to-run). name=%27;shell-command-to-run%27 is mostly harmless. That's nit-picky I know, but when some dude on the internet is trying to get clicks via manufactured rage at incompetent programmers, it's kinda ironic his code is buggy too.
- amiga386 2y agoDon't shoot the messenger. This is from the people who discovered it: https://netsecfish.notion.site/Command-Injection-Vulnerability-in-name-parameter-for-D-Link-NAS-12d6b683e67c80c49ffcc9214c239a07 https://netsecfish.notion.site/Command-Injection-Vulnerabili... > The vulnerability is localized to the account_mgr.cgi script, particularly in the handling of the cgi_user_add command. The name parameter in this script does not adequately sanitize input, allowing for command execution. > /cgi-bin/account_mgr.cgi?cmd=cgi_user_add&name=%27;<INJECTED_SHELL_COMMAND>;%27 I know, I know, that would mean the exact command run, based on the reversed code shown on screen at https://youtu.be/-vpGswuYVg8?t=656 https://youtu.be/-vpGswuYVg8?t=656 would be adduser -u "';<INJECTED_SHELL_COMMAND>;'" -p "" >/dev/null which would be harmless, so clearly if the PoC says %27 then the real format string must be more like "adduser -u '%s' ...". Maybe the Youtuber reversed the wrong firmware. But nonetheless, the point is gotten across.
- zahlman 2y agoNever mind the actual mistake "the intern" made. Not only was "the intern" tapped to write code that accepts user input from HTTP and also use system administration shell commands - and use C to do raw string handling, for that matter; who knows if `buf` is properly allocated? - but there was either no review/oversight or nobody saw the problem. Plus there are two layers of invoking a new program where surely one would suffice; and it's obviously done in a different way each time. Even programmers who have never used Linux and know nothing about its shells or core utilities, should be raising an eyebrow at that. Meanwhile, people want to use AI to generate boilerplate so that their own company's "the intern" can feel like a "10x developer" (or managers can delude themselves that they found one).
- o11c 2y agoDiscussion around this seems very confused; there are quite a few severe vulnerabilities this year in various products (routers and NASes). https://nvd.nist.gov/vuln/detail/CVE-2024-3273 https://nvd.nist.gov/vuln/detail/CVE-2024-3273 https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10383 https://supportannouncement.us.dlink.com/security/publicatio... (April 4) affects NASes (DNS-* products, same as one of the November vulnerabilities), no fix, official recommendation "buy a new one". https://nvd.nist.gov/vuln/detail/CVE-2024-45694 https://nvd.nist.gov/vuln/detail/CVE-2024-45694 https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10412 https://supportannouncement.us.dlink.com/security/publicatio... (September 16) affects routers (DIR-* products), fix by upgrading frimware https://nvd.nist.gov/vuln/detail/CVE-2024-10914 https://nvd.nist.gov/vuln/detail/CVE-2024-10914 https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10413 https://supportannouncement.us.dlink.com/security/publicatio... (November 6) affects NASes (DNS-* products), no fix, official recommendation "buy a new one" (despite not selling NASes anymore?). CVE-2024-10915 looks to be identical to CVE-2024-10914 at a glance https://nvd.nist.gov/vuln/detail/CVE-2024-11066 https://nvd.nist.gov/vuln/detail/CVE-2024-11066 https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10414 https://supportannouncement.us.dlink.com/security/publicatio... (November 11) affects routers (DSL* products), no fix, official recommendation "buy a new one". Note that you need to look at multiple CVEs to get the full picture here. (no CVE?) https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10415 https://supportannouncement.us.dlink.com/security/publicatio... (November 18) affects routers (DSR-* products), no fix, official recommendation "buy a new one". (several other RCEs require login first, and I could not find an associated login vulnerability. Additionally there are several buffer overflows that theoretically could become an RCE)
- slimebot80 2y agoMost "Critical" thing is: you buy a new router that is not from Duh-Link.
- zahlman 2y agoTo be fair, CVE scores generally don't seem very useful in assessing the real impact of a security vulnerability. The CUPS thing was a 9.9 and that was completely irrelevant for a large swath of people.
- ronsor 2y agoI'm pretty sure a 9.8 CVE for something connected directly to WAN is a very bad thing.
- zahlman 2y agoThe point is that the title puts the number up there to sensationalize. It doesn't concretely explain the scope or magnitude of the vulnerability.
- likeabatterycar 2y agoThe 9.8 CVE was for their NAS. Exposing any NAS directly to the open Internet is a Bad Idea. For that matter, nearly every shit-tier NAS vendor (WD, QNAP) has had some critical remote vulnerability in recent years. Some were notable for mass data loss incidents. That aside, these companies are all very good at making very, very nice hardware at a price point consumers can afford. Some corners have to be cut and it's often software. The dirty secret is many Internet of Shit device vendors outsource the software development, often to the lowest bidder in some offshore sweatshop. In some cases it's just a repackage of an ODM design from some no-name company in Shenzhen. None of which are known for secure coding or good software practices. Criticize all you want but this is a textbook example of getting what you paid for. It's unreasonable to pay $100 for a D-Link box and expect it's Cisco ASA quality with free indefinite support. Cisco, Juniper, and Palo Alto would all tell you to pound sand if you expect support after EOL or if you let your maintenance contract (aka protection racket) lapse.
- BeefWellington 2y agoThe problem is the way those specifics are handled. The Complexity metric is intended to handle the "specific configuration required" scenario but nobody is really incentivized to properly score their stuff.
- autoexec 2y agoHere's an article for those who'd rather read than watch someone's youtube video: https://www.techradar.com/pro/security/d-link-says-it-wont-patch-60-000-older-modems-as-theyre-not-worth-saving https://www.techradar.com/pro/security/d-link-says-it-wont-p... Dlink has a long history of putting out insecure and even backdoored devices and so anyone with a dlink device is probably better off buying something different
- xyst 2y agoAnother 60,000 devices ripe for malicious entities to use in their botnet.
- chipdart 2y ago> Another 60,000 devices ripe for malicious entities to use in their botnet. Right, my immediate reaction after reading the title was that D-Link might not patch their hardware, but others certainly will.
- daghamm 2y agoSpeaking of things others could do: Dlink competitors should use this in their marketing.
- bell-cot 2y agoHow much of Dlink's target market would both understand and care?
- sbarre 2y agoI think, thankfully, that the average user is increasingly aware of these kinds of problems, and hopefully the era of companies being this irresponsible is starting to come to an end. Anecdotally, my elderly parents have asked me questions about ransomware and "our house getting hacked" because of segments they've seen on the mainstream nightly news. So the awareness is out there..
- dmix 2y agoNot downplaying the risks, but could a vulnerability on a d-link router really let you monitor traffic on the device in a practical sense (as mentioned in the video)? Assuming it is non-SSL is there enough computing power to even do any meaningful monitoring and subsequent exfiltration? Or are the SOCs used on them powerful enough these days.
- op00to 2y agoIt’s powerful enough to mitm traffic if you get someone to install a certificate, and it can easily pass packets where ever the attacker wants.
- likeabatterycar 2y agoThis is also true of every intermediate router between you and the destination. TLS would not need to exist otherwise.
- stephen_g 2y agoMost intermediate routers don't have easily exploitable holes allowing attackers to take them over to MITM traffic though...
- op00to 2y agoI thought most internet routers in the US at least were pwned by the NSA. :D
- dmix 2y agoReminds me of a Dan Greer talk he gave at NSA from 2014 http://geer.tinho.net/geer.nsa.26iii14.txt http://geer.tinho.net/geer.nsa.26iii14.txt the basic gist is in the event of a cyberwar you could brick millions of peoples routers and their only natural solution would be to go to BestBuy to get a new one... which almost certainly is running a 4-5yr old linux/firmware version that is equally vulnerable. Of course this requires some remote access or lateral entry from other systems on the network, but it's an interesting thought experiment regardless.
- likeabatterycar 2y agoI cannot identify who the aggrieved parties are, aside from bandwagoning D-Link haters. These devices are end of life. Anyone running an EOL device doesn't care about security and probably wouldn't update the firmware if it was available. For comparison, Apple does not update EOL devices outside exceptional circumstances. I never received a 20% discount to upgrade.
- slimebot80 2y agoWait, has Apple ever exposed an end-point like this? Do we know how they'd react if they ever did?
- EasyMark 2y agoYour Mac is a network endpoint. It can easily be hacked after apple stops putting out security patches of your EOL’d air on your EOL’d d-link router
- luizfelberti 2y agoSure, but is EOL really a defense given the absolutely pathetic security posture that created this exploit in the first place? Is there a statute of limitations on mind boggling levels of incompetence? I'd usually give the EOL argument some credit, but this exploit is not an accident, someone deliberately wrote an unauthenticated remote command execution as a feature, and it made it to production, and no one in this long chain of failures thought to themselves "gee, maybe we shouldn't do this"
- wmf 2y agoWe could have passed a law requiring minimum security standards but we didn't. The result was predictable and here it is.
- philipwhiuk 2y agoHow long should a consumer expect their modem to last? How long ago were they last being sold at retailers?
- clwg 2y agoJust opensource the firmware and redirect the update url.
- wmf 2y agoThat doesn't set a good precedent though. The community shouldn't be expected to carry every IoT device.
- doubled112 2y agoMaybe not, but it'd be nice to have the option. Wouldn't it?
- wmf 2y agoIf you as a user want third-party firmware usually you can jailbreak and install it yourself (especially if the original firmware has zero security). If we allow a vendor to choose to make "the community" responsible for their firmware, almost every vendor will choose that as quickly as possible (e.g. one year).
- OtomotO 2y agoThat's why in sane countries there is jurisdiction to deal with that. If you leave capitalism unchecked it will fuck you as hard as any other system.
- rbetts 2y agoThis assumes that vendors have IP rights to open source the firmware, which seems unlikely. Presumably there are third party commercial components they don't have rights to publish. A rule like this essentially forbids closed source software. (Which, hey, might be a good thing... but then just mandate that directly and outlaw closed source software licensing.)
- 486sx33 2y agoOr well… if you have one of these models, this is the way. https://openwrt.org/toh/d-link/start https://openwrt.org/toh/d-link/start
- anonymfus 2y agoI didn't find most of the affected models there, and for these which I did, pages are full of warnings like that OpenWrt support is obsolete since 2022 and/or that 4 MB of flash and 32 MB of RAM is not enough to do anything useful
- znkynz 2y agoD-Link says buy a new router after vulnerability emerges after the signposted end of support date.
- mr_toad 2y agoHaving experienced D-link products first hand I’d say that anyone with a D-link product should buy something else anyway.
- aforty 2y agoSomething that supports OpenWRT.
- jasonladuke0311 2y agoI don’t think there’s much overlap between “people who run OpenWRT” and “people who use EOL D-Link routers”
- cesarb 2y agoWouldn't the overlap between “people who run OpenWRT” and “people who use EOL D-Link routers” be "people who run OpenWRT on EOL D-Link routers"? The table of supported hardware at the OpenWRT site lists several D-Link models which can run the latest OpenWRT release, and several of them are marked as "discontinued" (that is, no longer sold), a few of them even being in that status for more than five years.
- remuskaos 2y agoI don't know, I've installed openwrt on each device I've owned especially because their original firmware wasn't supported anymore (or crap to begin with). Often because the cheap devices were either all I could afford or because I've even gotten them for free or basically free, like on flea markets.
- TheRealPomax 2y agoI mean... yes? "we no longer support these" devices were hit with critical vulnerabilities, and that'll never get patched, just like any other device that hit EOL. You knew your device was no longer supported and would no longer receive security updates, "someone found an exploit" is kind of a given, and "d-link won't patch it" equally so?
- yjftsjthsd-h 2y ago> You knew your device was no longer supported and would no longer receive security updates I'm less confident that this is true. I think I know what the EOL is for all my networking equipment[0], you probably know the EOLs on your networking equipment, but I would wager that a majority of the population very understandably regards these things as appliances that you buy, plug in, and then it works indefinitely, and they do not in fact have any clue when the vendor will decide to stop providing security patches for it. [0] Actually, now that I think about it no I don't; I was thinking of the core bits that I control, but the edge of my network is an ISP-provided box that I know essentially nothing about. Given that I don't manage it, I hope my ISP will send me a new one when it hits EOL but I don't know that.
- TheRealPomax 2y agoAs an adult paying for your ISP service: you have some responsibility here. Whether you want that responsibility or not.
- bdangubic 2y agoyou are on HN so this makes sense to you. imagine your car was hacked while driving your family in the middle of the desert and bricked. as an adult that bought the car is this your responsibility that you endangered your family’s well-being?
- TheRealPomax 2y agoA legally binding as well as moral yes. If you drive a 2000 pound death machine, know how it can kill you. The idea that you are somehow not culpable in the situation you've given is baffling. Of course you are.
- tptacek 2y agoLook I am just being grumpy about this and I know it has nothing really substantive to do with the underlying story, which is D-Link EOL'ing products, but: there is really no such thing as a "9.8" or "9.2" vulnerability; there is more actual science in Pitchfork's 0.0-10.0 scale than there is in CVSS.
- 616c 2y agoWhat is this Pitchfork scale? Is it an actual one, searching didn't return any useful results.
- hiddencost 2y agoIt's a music review site.
- juliusdavies 2y agohttps://pitchfork.com/features/lists-and-guides/pitchfork-reviews-rescored/ https://pitchfork.com/features/lists-and-guides/pitchfork-re...
- fresh_broccoli 2y agoIt's a shame that MikroTik routers' UI is completely unsuitable for non-powerusers. Otherwise they would be perfect. Cheap and supported practically forever. Their trick seems to be that they use a single firmware image for all routers with the same CPU architecture.
- Maxious 2y agoThey've been trying lately though, you can supposedly set one up for a basic pppoe and dhcp scenario using the Mikrotik phone app and they have a Back To Home wireguard VPN setup app
- protocolture 2y agoI dunno its pretty basic. It has lots of options but users only need to be guided to quick setup or a few other places.
- TiredOfLife 2y agoThere is https://play.google.com/store/apps/details?id=com.mikrotik.android.mikrotikhome https://play.google.com/store/apps/details?id=com.mikrotik.a... official Home user app And the default page on routers ip is https://help.mikrotik.com/docs/spaces/ROS/pages/328060/Quick+Set https://help.mikrotik.com/docs/spaces/ROS/pages/328060/Quick...
- wuming2 2y agoWasteful choice enabled by not being entirely responsible for pollution, energy consumption and trash. If they had to pay for environmental full restoration, energy at full cost and careful disposal of unsuitable hardware decision would have been different.
- CTDOCodebases 2y agoIMHO once devices are EOL'd the company should be legally required to release the source code for them.
- gtsop 2y agoI like this. But i also assume parts of the stack are going to be reused in newer models as well, so this is probably going to be a blocker for them accepting it.
- precommunicator 2y agoIf it's reused without much changes, why not make it available for older hardware? If it changed enough it won't matter.
- zer8k 2y agoI'd settle for not getting sued when I try to jailbreak it.
- ChrisArchitect 2y agoRelated: D-Link tells users to trash old VPN routers over bug too dangerous to identify https://news.ycombinator.com/item?id=42201639 https://news.ycombinator.com/item?id=42201639
- markhahn 2y agohow about this: you can only abandon hardware if you enable open firmware on it.
- guidedlight 2y agoI remember this happened before, and someone smarter than me exploited the vulnerability to access every router and patch it remotely.
- DocTomoe 2y ago„Just buy a new modem“ they say … sure won’t be a D-Link ever again.
- ak217 2y agoIf anyone is looking for alternatives as far as long term supported products go... I've had nothing but good experiences with Ubiquiti (Unifi) and OpenWRT. At the lower end of the price spectrum, OpenWRT supported devices can be an incredible value, and most will probably remain supported for decades to come. More broadly, it's not just about the support commitment but also about the company's reputation for shipping solid software. i.e. what is the prior on a scenario like this after the product goes EOL.
- hedora 2y agoOpenBSD also works great for such things.
- xanth 2y agoAnyone have any OPNSense budget hardware recommendations?
- senectus1 2y agoN100 is an excellent chip to go for. I'm currently using a aliexpress special with a celeron n5105 chipset in it.. it works fine as well, but I'd opt for the N100 next time if I had to replace it. Celeron N5105 CPU: Intel Jasper Lake Celeron Processor N5105, 4 core 4 threads,64 bit, 10nm, 2.0GHz up to 2.9GHz, 4M cache GPU: Intel UHD Graphics GPU, 24EU, 450MHz up to 800MHz vs Alder Lake N100 CPU: Intel Alder Lake Processor N100, 4 core 4 threads,64 bit, 10nm, Up to 3.4GHz, 6M cache GPU: Intel UHD Graphics GPU, 24EU, Up to 750MHz I bought a N100 model to run as my backup server (PBS etc) and its a cracker. Debian is so snappy on it.
- BLKNSLVR 2y agoAlso running OPNSense (in a VM) on an N5105 from an AliExpress mini box, with four Ethernet ports. Thing gets hot though, passively cooled, but I put a fan on top of it. Also runs another VM with some lightweight docker containers. Reliable little thing. Would also go N100 if needed replacement.
- Uptrenda 2y agoYeah, this doesn't surprise me one bit. The number of vulns that get patched in home routers is staggering (D-Link is particularly shit-tier and known for this.) If there's that many vulns being fixed then imagine the backlog of unfixed vulns... Then imagine how many legitimate issues have to be hand-waved away because engineers know there's no way in hell they'll ever get the time to fix them. And have to prioritize the worst problems. It kind of surprises me that you can just release a commercial product that is dangerous, make tons of money from it, then totally refuse to fix any problems with it. These devices are going to sit on innocent peoples networks who deserve to have privacy and security like anyone else. It's not outside the realm of possibly that an owned device leads to crypto extortion which leads to a business going under. Or maybe someone's intimate pics get stolen and that person then... yeah. Security has a human cost when its done badly.
- seam_carver 2y agoHuh I recently retired all my Dlink routers as soon as they stopped getting security updates, lucky me.
- EasyMark 2y agoJust curious how old they were. Nothing in the article mentions of these were 2 year old routers or 10 years old
- seam_carver 2y agoLike 2010-2012
- isodev 2y agoCan't there be a law that says something like "you can't release new hardware while you have unpatched older hardware still in use"? Recall or update your stuff first, release new things second.
- malux85 2y agoHow would that be defined? What about low CVEs? Does that mean a company cant release a keyboard while theres unpatched network switches? What about devices that are hybrid like no releasing DSL modems but what if it has an integrated switch? Does that mean no switches too? Whos going to enforce this? I cant see a way this would't be turned into a "game the system" and wouldn't solve the unpatched product problem at all.
- thesnide 2y agosimpler. Just open up the firmware when EOL. So a 3rd party can patch it. Stop e-waste and planned obsolcence. If you fear loosing sales on new HW, make it significantly better.
- isodev 2y agoYes, that would be better. I have a drawer full of old iPhone and Mac devices that are practically blobs of ewaste because their OS doesn't update.
- phire 2y agoIt would be nice. Though, as a life-long Android user, I've been jealously looking at how long apple have actually been supporting their iPhones (at least since the iPhone 6) and I'm seriously considering switching. The 6S, 7, 8 all got feature updates for 7 years, and are still getting security updates after 9 years. The iPhone XS is still getting feature updates after 6 years. On Android, you are lucky to get 3 years of feature updates and 5 years of security updates.
- yrro 2y ago
- sitkack 2y agoI could see them facing criminal liability here. Someone is having hard conversations with their insurance company.
- pt_PT_guy 2y agoOne of the reasons why there are major security f-ups: no accountability and no consequences
- alias_neo 2y agoI've had a box of old wifi-routers for years that I'd been meaning to reverse engineer and write up blog posts on the vulnerabilities to educate people on just how poor quality the software is written for the things you buy in your local electronics store. Every 3-4 years I'd have to buy another because the manufacturer stopped providing updates, even when I was buying their higher-end stuff. I myself moved on to an Ubiquiti Edge Router almost 10 years ago, but Ubiquiti didn't do a great job of that in the long term and they ditched the EdgeRouter/EdgeMAX line so I ended up (and I wasn't interested in Unifi line for my router/firewall) buying a Protectli box, flashed coreboot and used pfSense for a while before eventually moving to OPNSense. I came to the conclusion over this time that any consumer network equipment is basically junk and if you care at all about security you shouldn't use it; sadly that's easier said than done for non-techy folks. Many pieces of older/cheaper hardware can be flashed with OpenWRT and I'd recommend that as the cheapest option for anyone who cares just a little, and doesn't want to buy new hardware, and for everyone who really wants to make an effort should buy some hardware that can run a properly maintained router OS like pfSense or OPNSense, even an all-in-one wifi-router-switch if you don't want to build out an entire SMB network.
- jart 2y agoYeah Ubiquiti used to be great before they went the other way. Now Mikrotik is the new hotness.
- alias_neo 2y agoI've been looking at some of the Mikrotik releases; I'll almost certainly be going Mikrotik when I get around to upgrading my home network to 10Gb, I'm just looking out for new APs and will probably replace them all at once. Current using Unifi AP-AC Pros and Unifi 6 Pro around the house, but I keep having to move them around because the (newer) U6 Pro has atrocious range on both 2.4GHz and 5GHz compared to the AP-AC-Pro and my wife is getting annoyed at the poor WiFi signal on the living room TV (constant buffering), so I put the AP-AC-Pro back and it's better for the TV but slower for everything else. Not sure if there's a better Unifi AP I can get for this part of the house or if I need to switch everything out as don't want to mix AP manufacturers/management tools.
- pcl 2y agoI see a lot of comments here recommending OpenWRT. I’ve been happy with it in some deployments, but also don’t overlook the alternatives! I just had a wonderful experience with Fresh Tomato repurposing an integrated router / AP / 4-port switch as a multi-WAN router. It would have been doable with OpenWRT’s robust scripting support, but was just a few clicks in the UI with Fresh Tomato. https://freshtomato.org/ https://freshtomato.org/ https://en.m.wikipedia.org/wiki/Tomato_(firmware) https://en.m.wikipedia.org/wiki/Tomato_(firmware)
- mitjam 2y agoThis is something the EU Product Liability Directive potentially addresses. It demands that vendors (or importers) of products need to update their product if that's required to keep them secure. Otherwise they are liable for damages, even psychological damages. There is no specific duration mentioned in the directive, so it's probably best from a vendor point of view to add product lifetime info to the product description or the contract, up front. In Germany there is something similar in place, already and the expectation is that products (and necessary apps to run the products) need to be updated for 5 years on average.
- mnau 2y agoThat D-Link DSL6740C device was released in 2014. It's well past lifetime. I am not sure about PLD, but CRA is only for lifetime or ~5 year. > When placing a product with digital elements on the market, and for the expected product lifetime or for a period of five years from the placing of the product on the market, whichever is shorter, manufacturers shall ensure that vulnerabilities of that product are handled effectively and in accordance with the essential requirements set out in Section 2 of Annex I.
- xmodem 2y agoThe 5 year clock should start from the last time a consumer purchased the product new, though. I can't find anything concrete but some poking around on wayback machine indicates it was likely discontinued late 2018. Which probably still means they are in the clear in this instance even if you assume it takes a year for the inventory in the channel to sell through.
- bell-cot 2y ago> The 5 year clock should start from the last time a consumer purchased the product new... Obvious problem - how could the manufacturer determine (let alone control) when, literally, that happened? They might tell when their major distributors and online retailers ran out of stock...but small distributors and bottom-feeding resellers and mom-and-pop retail? Impossible. On-package labeling ("Software security updates for this thingie will be available until at least Dec. 31, 2029; also check our web site at https://support https://support...") would be the only fool-proofish method.
- a1o 2y agoAny good router access point that has nice gigabit Ethernet and really good WiFi, for a second access point in the house?
- chipweinberger 2y agoThe D-Link DSR-150 was released in 2012 It was the first information I wanted to know, but it wasn't in the article.