From: Maxim Kharlamov <mcs@podsolnuh.biz>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] First-time install on brand new WNDR3700v2 not working
Date: Thu, 3 Nov 2011 11:32:47 +1300 [thread overview]
Message-ID: <CADq85jb=YXXC6BDTJEHFuyV88bra80UqFWChn+7fgffH+M39aQ@mail.gmail.com> (raw)
In-Reply-To: <CAK-n8j52RHxTJ0zTz2r-ZFQ7QtYUqg1vqyTJn375kd0uCresAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
I tried tftp-ing many times and also tried renaming the firmware to o.img -
it didn't help at all.
It's worth noticing though that I tried jffs2 firmware initially (as per
the original instructions).
When it didn't work, I downloaded OpenWRT beta for WND3800, which happen to
be a squashfs image, so decided to stick to squashfs, uploaded squashfs
CeroWRT image and it worked.
I've never tried tftp-ing squashfs image, maybe it will work straight away?
It requires more experimenting to figure out what was the problem.
Max
On 3 November 2011 11:14, Jim Reisert AD1C <jjreisert@alum.mit.edu> wrote:
> On Wed, Nov 2, 2011 at 3:39 PM, Maxim Kharlamov wrote:
>
> > 2. flashed OpenWRT using netgear web gui (it shows a warning but allows
> to continue)
>
> This is interesting:
>
> http://wiki.openwrt.org/toh/netgear/wndr3700
>
> "OEM installation using the TFTP method
>
> "However, note that the router will not accept the firmware when the
> filename is too long! Using firmware.img as filename should work."
>
> I wonder if this is the problem. I'll try this first, then try the
> OpenWRT-as-intermediate-step method if this doesn't work.
>
> - Jim
>
> --
> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
>
--
Thanks,
Max
[-- Attachment #2: Type: text/html, Size: 1952 bytes --]
next prev parent reply other threads:[~2011-11-02 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 21:20 Jim Reisert AD1C
2011-11-02 21:39 ` Maxim Kharlamov
2011-11-02 22:14 ` Jim Reisert AD1C
2011-11-02 22:32 ` Maxim Kharlamov [this message]
2011-11-03 3:30 ` Jim Reisert AD1C
2011-11-03 11:54 ` Shane Turner
2011-11-03 14:22 ` Dave Taht
2011-11-04 6:53 ` Maxim Kharlamov
2011-11-04 8:37 ` Petri Rosenström
2011-11-04 9:11 ` Maxim Kharlamov
2011-11-04 10:45 ` Petri Rosenström
2011-11-05 19:42 ` Maxim Kharlamov
2011-11-04 16:32 ` Dave Taht
2011-11-05 19:55 ` Maxim Kharlamov
2011-11-05 20:33 ` Dave Taht
2011-11-06 0:44 ` Maxim Kharlamov
2011-11-05 4:23 ` Shane Turner
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADq85jb=YXXC6BDTJEHFuyV88bra80UqFWChn+7fgffH+M39aQ@mail.gmail.com' \
--to=mcs@podsolnuh.biz \
--cc=bloat@lists.bufferbloat.net \
--cc=jjreisert@alum.mit.edu \
/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