upgrading to LEDE 17.01.1 - but without 5Ghz

Event though 15.05 has been running stable upgrading to 17.01 seems like a good idea.
Going the lazy route and simply using luci to do the upgrade.
(note: it's a good idea to keep a list of all the packages you installed, you'll have to add them all again)

Since this is an upgrade from wrt we grab this file:
https://downloads.lede-project.org/releases/17.01.0/targets/ar71xx/nand/lede-17.01.0-r3205-59508e3-ar71xx-nand-nbg6716-squashfs-sysupgrade.tar
(yes it is a tar) under System->Flash/Back (make sure keep settings is checked)
and.... somewhat success: system reboots, is accessible over ssh but luci isn't (but uhttpd is running).
/etc/init.d/uhttpd restart seems to bring it back online. (with an enable).

onward with restoring the missing packages: opkg update
for ddns (settings were nicely maintained as expected)
opkg install ddns-scripts luci-app-ddns
for wake on LAN (i did have to recreate my wakenas script manually, and luci-app-wol doesn't show in luci)
 opkg install etherwake luci-app-wol
then let's get our DLNA server back, first get USB sticks supported:
opkg install kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-usb-storageopkg install block-mountopkg install install kmod-fs-vfat kmod-fs-ext4 kmod-nls-cp437 kmod-nls-iso8859-1
(i had to do a reboot here to get the drives recognized.. don't forget to do an opkg update when you continue)
configure the mount points via luci and onwards with minidlna/samba
opkg install minidlna luci-app-minidlna
opkg install samba36-server luci-app-samba
and we are back to where we were... minus the 5Ghz radio...again.
should've stuck with 15.05 it seems. :(

 






Comments

Post a Comment

Popular posts from this blog

wpad - caching proxy part 2

proxy autoconfig is a combination of DHCP optons, and a bit of JS in a wpad.dat file. under  network>hostnames  add an entry ' wpad ' pointing to your router's lan-ip then create a /www/wpad.dat file (got mine from here ). and changed the default rule to point to polipo - 10.0.0.1:8123 also changed .local into .lan for lan hosts , and commented some stuff out that didn't seem relevant. function FindProxyForURL(url, host) { // If the hostname matches, send direct. //   if (dnsDomainIs(host, "intranet.domain.com") || //        shExpMatch(host, "(*.abcdomain.com|abcdomain.com)")) //        return "DIRECT"; // If the protocol or URL matches, send direct.     if (url.substring(0, 4)=="ftp:" ||         shExpMatch(url, "http://abcdomain.com/folder/*"))         return "DIRECT"; // If the requested website is hosted within the internal network, send direct. ...
Read more

Traffic accounting

Got this from here: http://www.catonmat.net/blog/traffic-accounting-with-iptables/ All i'm interested in is my monthly bandwidth consumption, not the individual devices, there are plenty of forum threads/tools to do that. But why bring in additional tools when iptables has it all? iptables -N TRAFFIC_ACCT iptables -I FORWARD -j TRAFFIC_ACCT iptables -A TRAFFIC_ACCT and to just get the number: iptables -L TRAFFIC_ACCT -v | sed -n 3p | cut -d' ' -f2 to reset the counters /usr/sbin/iptables -L TRAFFIC_ACCT -Z the cron job to reset at the begining of the month, and a daily telegram msg 1 0 1 * * /usr/sbin/iptables -L TRAFFIC_ACCT -Z  0 8 * * * /usr/bin/curl -s -X POST https://api.telegram.org/<BOTID>/sendMessage -d chat_id=<CHATID> -d text="$(/usr/sbin/iptables -L TRAFFIC_ACCT -v | /bin/sed -n 3p | /usr/bin/cut -d' ' -f3)" >/dev/null 2>&1 (you'll need to opkg install ca-bundle for the https to work)
Read more

QoS with SQM (and something about bufferbloat)

another feature that came with stock zyxel fw is their 'optimized' (the one with the 400mbps nag) QoS packages. As far as i can tell the standard SQM package should come pretty close. install uci-app-sqm a Network>SQM QoS menu item will appear check enable, double check your interface name is really your wan port(eth1), and set your down/up speeds to what you measured with e.g. dslreports . under linklayer adaptation set to Ethernet (for VDSL) with 8 bytes overhead. i reran the test, and it seems my up/down throughput dropped about 10%,  but my bufferbloat report went from D to B.... whatever that means in reality I'll have to find out :)
Read more