From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>, Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] security guidelines for home routers
Date: Mon, 26 Nov 2018 22:05:05 +0100 [thread overview]
Message-ID: <87mupvwnwe.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4La1v=tQOFPZGr6QZ04yfcu2Z+pVQegyLpQwSaFevyEw@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> writes:
> Sigh... I have zip, zero problem, if cable folk *leased* you a modem,
> managed it, and then provided a new one when their support costs got
> too great. It would do wonders for the entire industry if they simply
> gave away new docsis 3 or 3.1 modems to every one still running an
> earlier one....
FWIW, this model is roughly what is usually happening in Denmark for DSL
(dunno about cable, but may be similar). I've had multiple occasions
where I've been talking to support about an unrelated issue, and they
noticed I had an ancient router and went "wait, let me send you a new
one". Free of charge, and you just return the old one.
(In all cases the router has just been an expensive DSL model in bridge
mode to my OpenWrt router, but still, nice practice...)
-Toke
next prev parent reply other threads:[~2018-11-26 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 18:05 Dave Taht
2018-11-26 18:24 ` Sebastian Moeller
2018-11-26 18:35 ` Mikael Abrahamsson
2018-11-26 22:13 ` Sebastian Moeller
2018-11-27 11:03 ` Mikael Abrahamsson
2018-11-27 11:52 ` Sebastian Moeller
2018-11-27 13:34 ` Mikael Abrahamsson
2018-11-28 13:49 ` Sebastian Moeller
2018-11-27 18:23 ` valdis.kletnieks
2018-11-26 18:40 ` Dave Taht
2018-11-26 21:05 ` Toke Høiland-Jørgensen [this message]
2018-11-26 22:28 ` Sebastian Moeller
2018-11-27 0:29 ` David P. Reed
2018-11-27 11:07 ` Mikael Abrahamsson
2018-11-27 11:17 ` Jonathan Morton
2018-11-28 9:17 ` Michael Richardson
2018-11-28 9:14 ` Michael Richardson
2018-11-28 19:10 ` David P. Reed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mupvwnwe.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox