From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-f48.google.com (mail-qa0-f48.google.com [209.85.216.48]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 1DA3721F15E for ; Mon, 14 Apr 2014 04:49:02 -0700 (PDT) Received: by mail-qa0-f48.google.com with SMTP id s7so7284201qap.7 for ; Mon, 14 Apr 2014 04:49:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :thread-index:content-language; bh=vjc8RKx1s1OnAAkN8F7wI+8p0ENQVXmcaxRFhfuCgiI=; b=WDuZnj8p2lik9goenyyKVpavq88KLkqgI8SOKfpHulanZHvcjWJTk9U77JE/4leu62 C+MHkKzeG9Ynxc6LF/hHaDX25Bj/VbGsQgkFuTrZLOBeg6IA5pceplYHL60xC5PFvzWn EXeF3WnYkdngOTrrffiULhUlvX85s7RwgXCaCrGGjtd08gI91DSzmpuXTz7Rr2odGZgq osHbWLPZUAyIf1Y/bhItEz5ADB+AbeVAiZFOnR6bSq2AT4DivX0DoEi0Oqw1HALFim0G mt9N2oGkrgMacLGTSPRDRY5GDHY3maAV1xX7gqoFgClPQWIfn1dTncaosddul5BVfO4o ba1g== X-Gm-Message-State: ALoCoQlq1Eeq2k2EObIA38mqnKQacElclh961G8UqsbWvMUktEXeiIaUa5HJ9mF4VfujiUbW6kV4 X-Received: by 10.224.161.10 with SMTP id p10mr36165777qax.12.1397476141778; Mon, 14 Apr 2014 04:49:01 -0700 (PDT) Received: from RiepD630 (pool-108-49-217-37.bstnma.fios.verizon.net. [108.49.217.37]) by mx.google.com with ESMTPSA id 11sm17215594qgv.20.2014.04.14.04.49.00 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 14 Apr 2014 04:49:01 -0700 (PDT) From: "Frits Riep" To: "'Joel Stanley'" , "'Sebastian Moeller'" References: <000001cf567f$80b2f1c0$8218d540$@riepnet.com> In-Reply-To: Date: Mon, 14 Apr 2014 07:48:42 -0400 Message-ID: <000001cf57d7$7c8b68d0$75a23a70$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac9XIGFMxmk+hBiOQSqi2xUeuEETIQAs2VIA Content-Language: en-us Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] Having issue upgrading to latest image 3.10.36-4 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 11:49:03 -0000 Thanks, Joel, Sebastian, and Valdis for your information and assistance. I didn't know how to do the manual routes described, so I used a TFTP tool to update the firmware to the latest by using the information on the OpenWRT website on TFTP updating of the Netgear WNDR-3800. Of course, I could not use the sysupdate version of the firmware, and in the TFTP update to the bootloader the IP address for the target is 192.168.1.1 which is the default for the bootloader. The description on how to do this is actually in the WNDR3700 router: http://wiki.openwrt.org/toh/netgear/wndr3700#upgrading.openwrt "OEM installation using the TFTP method (recommended) "Hold the 'System Restore' button on the underside of the router while powering it on, and hold the button until the power led blinks green. Then, upload the .img firmware as described in Installing OpenWrt via TFTP (see the section titled Bootloader contains TFTP server). However, note that the router will not accept the firmware when the filename is too long! Using firmware.img as filename should work. After upload, the power led is turned off and flashing starts, after that is finished the router will restart and the power led will eventually become stable green (it will be stable orange for quite some time first)." Naturally, at this point I was at the factory defaults and needed to restore my settings. Once I did that everything seems to be working well so far. The wireless is working fine on both 2.4 and 5 Ghz. I also set up the sqm to "fq-codel" and the latencies are rock stable on pings while running a Speedtest (both up and down). Thanks to all for the good work on this release. So the only issue I had was that I could not get to this release using a firmware upgrade via the web interface. Frits -----Original Message----- From: joel.stan@gmail.com [mailto:joel.stan@gmail.com] On Behalf Of Joel Stanley Sent: Sunday, April 13, 2014 9:58 AM To: Sebastian Moeller Cc: Frits Riep; Valdis.Kletnieks@vt.edu; cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] Having issue upgrading to latest image 3.10.36-4 On Sun, Apr 13, 2014 at 5:58 AM, Sebastian Moeller wrote: > I think Valdis Kletnieks reported the same for a 3800. Please try the "manual" route described below and report back your results to the list: I attempted an upgrade using the web interface from -3 to -4 and it also failed. I tried from the shell: root@cerowrt:/tmp# sysupgrade -c -v openwrt-ar71xx-generic-wndr3800-squashfs-sysupgrade_new.bin Saving config files... etc/lighttpd/lighttpd.pem etc/passwd- etc/fw_env.config etc/shadow etc/passwd etc/group- etc/ethers etc/config/wireless etc/config/system etc/config/polipo etc/config/ucitrack etc/config/network etc/config/ubootenv etc/config/dropbear etc/config/firewall etc/config/upnpd etc/config/fstab etc/config/luci etc/config/dhcp etc/config/sqm etc/dropbear/dropbear_rsa_host_key etc/dropbear/authorized_keys etc/dropbear/dropbear_dss_host_key etc/sudoers etc/shadow- etc/samba/secrets.tdb etc/samba/smbpasswd etc/group etc/firewall.user killall: watchdog: no process killed Sending TERM to remaining processes ... logd netifd odhcpd lighttpd crond lighttpd snmpd pimd xinetd dbus-daemon smbd nmbd avahi-daemon miniupnpd polipo babeld natpmp ahcpd rngd ntpd dnsmasq ubusd askfirst Sending KILL to remaining processes ... askfirst Switching to ramdisk... Performing system upgrade... Unlocking firmware ... Writing from to firmware ... Appending jffs2 data from /tmp/sysupgrade.tgz to firmware...TRX header not found Error fixing up TRX header Upgrade completed Rebooting system... After reboot: root@cerowrt:~# cat /etc/openwrt_release DISTRIB_ID="CeroWrt" DISTRIB_RELEASE="3.10.36-4" DISTRIB_REVISION="r40438" The system appears to be working okay, except my 2.4GHz interface is missing - I haven't spent any real time looking into that. Regards, Joel