From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] fixing reboots behind comcast modems
Date: Wed, 8 Feb 2017 09:47:31 -0800 [thread overview]
Message-ID: <CALQXh-OgcUtCkByrxZ1Ju1JxjVYWbxjPxcNmyDsL3ZaEQf2ePg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7XG+nnZpPQW25M95bgfHuaeaL+VUFjTcx3xZTyMj=LYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
I've not had to reboot my modem (SB6141) when rebooting my WRT1900AC
(running stock fw, OpenWRT, or LEDE). I always have to reboot the SB if I
change the router out (different MAC).
I've had the same experiences with all the Surfboard-line modems I've had
in the past (going back to 2004).
-Aaron
On Wed, Feb 8, 2017 at 7:46 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I finally found what seems to be a fix for rebooting a
> cerowrt/openwrt/lede box behind a comcast cablemodem
>
> I'd put "broadcast" in the uci config file, that didn't help.
>
> After googling a bit, someone suggested adding
>
> --retries=2 --timeout=5 --tryagain=310 to the
>
> /lib/netifd/proto/dhcp.sh invocation...
>
> And that worked, after a few minutes. I'm irked enough to poke at it
> harder, but I'm curious if anyone here had come up with a solution?
> (I'd actually always assumed it was a quirk in my particular brand of
> cablemodem, but I got a new one, and it did the same thing)
>
> https://plus.google.com/u/0/107942175615993706558/posts/Z5CD63e5kmt
>
> That said, I'm irked enough at it, and at how long it takes, to poke
> into it harder (lots of reboots here of late), the best idea I can
> think of is to have udhcpc have an option to save the last xid and ip
> info to flash and always start in a renew state, using that. The
> modems tend to offer a 192.x for about a minute when they boot, tho,
> so I guess we'd defer writing that until it had been stable for an
> hour.
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2694 bytes --]
prev parent reply other threads:[~2017-02-08 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 15:46 Dave Taht
2017-02-08 17:47 ` Aaron Wood [this message]
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=CALQXh-OgcUtCkByrxZ1Ju1JxjVYWbxjPxcNmyDsL3ZaEQf2ePg@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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