<p dir="ltr">On Feb 16, 2016 7:07 AM, "Adam Holt" <<a href="mailto:holt@laptop.org">holt@laptop.org</a>> wrote:<br>
><br>
> On Feb 16, 2016 6:09 AM, "T Gillett" <<a href="mailto:tgillett@gmail.com">tgillett@gmail.com</a>> wrote:<br>
> ><br>
> > Understood.<br>
> ><br>
> > In the meantime the remix firmware is available if anyone wants to use an OpenWrt build for the WR841 which has been set up to work out-of-the-box with the XSCE.<br>
> ><br>
> > The advantage of using the OpenWrt build compared to the OEM firmware is primarily that it has been shown to support 30+ concurrent wifi connections.<br>
><br>
> Thank you Terry!<br>
><br>
> I will document this for mass consumption within <a href="http://schoolserver.org/FAQ">http://schoolserver.org/FAQ</a> in coming days: which authoritative documentation/download links do you want included?</p>
<p dir="ltr">Terry,</p>
<p dir="ltr">Feel free also to refine our central FAQ directly:<br>
<a href="http://wiki.laptop.org/go/XS_Community_Edition/FAQ#How_do_I_provide_Wi-Fi_.28wireless.29_to_all_my_kids.3F">http://wiki.laptop.org/go/XS_Community_Edition/FAQ#How_do_I_provide_Wi-Fi_.28wireless.29_to_all_my_kids.3F</a></p>
<p dir="ltr">I will expand this in coming months to cover the most common nanodeployment and microdeployment scenarios -- as you know less-technical staff get stuck, even when trying their best in a foreign language (English!)</p>
<p dir="ltr">> TBD: hopefully soon including Tim Moody's scripting to auto-install this major enhancement, when that becomes more bulletproof for broad consumption.<br>
><br>
> Perhaps also delineating what WR841 firmware/configuration folks most recommend for non-XSCE users??<br>
><br>
> (Am cc'ing more mailing lists as Tony and others get a chance to bang on this, refine it, promote wider usage..whether TP-LINK wants us "doubling" the connection capacity of its low-end Wi-Fi router/AP or not ;)<br>
><br>
> > On Tue, Feb 16, 2016 at 7:02 PM, Tony Anderson <<a href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a>> wrote:<br>
> >><br>
> >> Hi, Terry<br>
> >><br>
> >> I haven't had a chance to work on this - possibly next week. My current focus is on completing the process to install content from BERNIE.<br>
> >> I think the CLI strategy would be the best route to keep the configuration process within reach of a deployer.<br>
> >><br>
> >> Sadly, I have had to move away from usbmount on the CentOS 7 XSCE image from last year. Now, I have a process using CLI primarily to deal <br>
> >> with using root permissions during the install. <br>
> >><br>
> >> Usbmount still has the advantage of executing as root. However, with the install of 600+GB itself taking hours, the advantages of usbmount audio <br>
> >> signals is are lost. Using CLI allows the deployer to monitor progress via SSH.<br>
> >><br>
> >> Thanks,<br>
> >><br>
> >> Tony<br>
> >><br>
> >><br>
> >> On 02/16/2016 02:02 PM, T Gillett wrote:<br>
> >>><br>
> >>> Hi Tony<br>
> >>><br>
> >>> Just wondering how you going with the WR841 configuration?<br>
> >>><br>
> >>> A few things that might be relevant / useful:<br>
> >>><br>
> >>> 1. If you have not already come across this, the OpenWrt firmware supports making changes to the configuration files from the command line using the UCI commands. Basically you can set and get individual parameters in the configuration files. <br>
> >>> This provides an alternative to replacing the files. <br>
> >>> Example below:<br>
> >>><br>
> >>> # uci set network.lan.ipaddr="172.18.126.102" <br>
> >>> # uci commit network <br>
> >>><br>
> >>> These commands set the IP address parameter in the "lan" stanza of the "network" config file, and then saves the change.<br>
> >>><br>
> >>> This might be useful for making the changes from the XSCE server by way of a ssh or telnet session.<br>
> >>><br>
> >>><br>
> >>> 2. The "wireless" config file on these devices in OpenWrt refers to the physical radio by its MAC address in the "device" stanza.<br>
> >>> This effectively prevents you from just replacing the file with a generic file common to all devices.<br>
> >>><br>
> >>> You can also address the radio by means of an alternate "phy0" address construct in the config file, which is what we do in the SECN firmware to avoid the use of the MAC address at all.<br>
> >>><br>
> >>> Alternatively you can use the UCI commands to effectively edit the original file on the device.<br>
> >>> <br>
> >>><br>
> >>> 3. I have updated the remix firmware that I made for Sora to bring it up to date with the latest version of OpenWrt 15.05 so that now it includes hardware versions 8, 9 and 10.<br>
> >>><br>
> >>> The firmware is available here:<br>
> >>> <a href="http://download.villagetelco.org/firmware/secn/unstable/tp-link/SECN-4/XSCE/RC1/">http://download.villagetelco.org/firmware/secn/unstable/tp-link/SECN-4/XSCE/RC1/</a><br>
> >>><br>
> >>> I have tested this firmware on a Ver 10 device.<br>
> >>><br>
> >>> Attached are some screenshots that show the GUI and the default settings for the firmware.<br>
> >>> Also a shot of the Status page which shows a count and list of wifi connected devices.<br>
> >>><br>
> >>> The firmware sets the default IP address of the device to 172.18.126.101, with the wifi SSID set to "Internet_in_a_Box" with no encryption.<br>
> >>><br>
> >>> There are two accounts on the box - root and admin - with the password "g0adm1n". <br>
> >>> The admin account only has access to the web interface while the root account also has access to the CLI.<br>
> >>><br>
> >>> There is also a Fallback IP address (172.31.255.254 Netmask 255.255.255.252) running on the device so that you can always connect to it from a PC configured to IP 172.31.255.253 Netmask 255.255.255.252, regardless of how the main IP has been set up.<br>
> >>><br>
> >>> If you wanted to flash your WR841 devices with the remix firmware, the basic parameters for the XSCE application are set up and it would then be a fairly simple matter to adjust the remaining parameters like IP address using the UCI commands from the XSCE server via ssh.<br>
> >>><br>
> >>> I appreciate that the web GUI is redundant in this scenario, but it does provide an alternate option in case a user has to access the box to make some adjustment or recovery.<br>
> >>><br>
> >>> Regards<br>
> >>> Terry<br>
> >>><br>
> >>><br>
> >>><br>
> >>> n Sun, Feb 7, 2016 at 10:05 AM, Tony Anderson <<a href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a>> wrote:<br>
> >>>><br>
> >>>> Thanks. This looks like exactly what I need to simplify (and complete) the configuration process. It may be a few days before I can <br>
> >>>> test it but I have some routers to test here (and the need to install them).<br>
> >>>><br>
> >>>> Thanks again,<br>
> >>>><br>
> >>>> Tony<br>
</p>