Re: [OpenWrt-Devel] After upgrading to 19.07 WLAN does not work anymore...
On Thu, Apr 30, 2020, 2:36 AM Luca Bertoncello wrote: > > Hi list! > > I upgraded my WLAN Switch to 19.07. > OpenWRT works, but WLAN is off... > > In the "Wireless Overview" page I see: > > radio0 Generic 802.11bg >Device is not active > > and all WLAN i configured are "disabled"... > Could someone help me? I really don't understand why radio0 is not active... What version did you upgrade from? What hardware are you running? Did you do a clean install, or a "upgrade" install keeping your settings? There are issues with upgrading (telling OpenWRT to keep your settings when it upgrades) on platforms that were switched from ar71xx to ath79 with 19.07 and the settings not transferring or causing problems (see: https://openwrt.org/releases/19.07/notes-19.07.0 ),. If you haven't yet done this, I would start with restoring to factory defaults and see if that fixes it. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Is there an Open Issues list for openwrt-18.06.0-rc1
On Mon, Aug 20, 2018 at 6:43 AM Craig Miller wrote: > Sorry if this has been answered else where. Is there a "known issues list" or > tracker for issues for 18.06-rc1? > Thought I'd try openwrt-18.06.0-rc1 on my Netgear R6100 today. > Noted that the 5Ghz wireless radio wasn't even detected (after reseting to > defaults). Nothing in the /etc/config/wireless about it. Under 17.01.4, it > lists the radio as Qualcomm Atheros QCA9880 802.11nac (and the radio works > normally). > thanks, > Craig... The service release 18.06.1 (which supersedes 18.06-rc1 and 18.06) was released on Friday, so I would try that: https://downloads.openwrt.org/releases/18.06.1/targets/ Looking at the changelogs for 18.06(1) and 18.06.01(2), It looks like there were a fair number of changes for the QCA988x related boards, so your issue may be fixed on 18.06.01. (1): https://openwrt.org/releases/18.06/changelog-18.06.0 (2): https://openwrt.org/releases/18.06/changelog-18.06.1 Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] LEDE 17.01.5 release planning -> WNR2000v3 broken
On Sun, May 27, 2018 at 12:19 PM, Hauke Mehrtens wrote: > On 05/25/2018 12:27 PM, Stijn Segers wrote: >> Hi Hauke, >> WNR2000v3 images are still being built but sysupgrading them from old >> versions seems broken, maybe someone could look into this? With 18.06 around >> the corner as well, might be handy to have this fixed. >> https://bugs.openwrt.org/index.php?do=details_id=672=WNR2000 > Thank you for the information. Does someone want to fix this device, > otherwise I would remove it from the lede-17.01 branch in the next days. > I do not have a WNR2000v3. If someone wants to fix it, I have a one that has been sitting my shelf for a while and a serial adapter. Point me to an image and I load it and test it. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.infradead.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Reducing the root file system in openwrt
On Wed, Mar 7, 2018 at 7:14 AM, Felix Fietkau <n...@nbd.name> wrote: > Are you really using a real OpenWrt? > The presence of the "wigig-firmware" package makes me suspect that > you're using the "QSDK" fork instead. In that case, you should probably > ask QCA for support instead. We won't be able to help you properly, > since the system that you're using is very heavily modified in many ways. Good point, looking at https://downloads.openwrt.org/releases/17.01.4/targets/ipq806x/generic/ and https://downloads.openwrt.org/snapshots/targets/ipq806x/generic/, with the exception of the openwrt-ipq806x-vmlinux.elf image, all of the images on there are under 10MB and most are under 6MB. Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be merged into Chaos Calmer
On Wed, Nov 29, 2017 at 10:07 AM, Ronaldo Afonso <rona...@ronaldoafonso.com.br> wrote: > Ok, Aaron, > I'll take a look at the LEDE part of it. > I have a "private OpenWrt feed" where I develop some "private OpenWrt > application"... > If a have to port this feed to the LEDE platform, should I expect a lot of > changes? It should be very similar, it was forked from what was then the trunk and that is where continued development has been going on. Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be merged into Chaos Calmer
On Tue, Nov 28, 2017 at 9:20 AM, Ronaldo Afonso <rona...@ronaldoafonso.com.br> wrote: > Hi all, > What does it take for a commit to be merged into a stable branch? > The thing is ... I really would like to have TL-WR842N Hardware version 3 > running on CC. I noticed that this hardware is already working on trunk > (master) since last year but not merged into CC yet. > How can I help that merge being done? Unless it is a security fix (such as the recent Krack vunerability), updates such as adding a new hardware build are not backported into a stable release. That platform should be there in the next stable release of OpenWrt (presumably the first post-remerge release). It will probbaly not be backported to CC, but it is currently available in LEDE's 17.0.4 stable release (see: https://lede-project.org/toh/hwdata/tp-link/tp-link_tl-wr842n_v3 for links). If you don't know, LEDE is a fork of OpenWrt which is in the process of re-merging with OpenWrt. That is where most of the recent development has happened. Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Support for BTHomeHub5
On Fri, Jan 13, 2017 at 12:30 PM, Mauro M. <open...@ezplanet.net> wrote: > Hello, > > Is OpenWRT going to backport support for BtHomeHub5 from LEDE? > This router is very well supported in LEDE, whilst support is only basic in > OpenWrt, > LEDE implemented some broken changes in the firewall that prevent basic > routing (it defeats the primary purpose of a router!), so I would like to > use OpenWrt where routing works as expected, but I need to run it on BT Home > Hub 5 routers. Might I strongly suggest filing a bug report with LEDE on these broken changes so they can be fixed? IIRC, all changes will eventually end up synced between OpenWRT and LEDE, so if its broken there, it will eventually be broken on OpenWRT as well (unless someone fixes it in the interim). The bug tracker is at: https://bugs.lede-project.org/ Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Tried to update ticket 20982 on dev.openwrt.org
On Wed, Oct 5, 2016 at 4:03 PM, Gareth Parker <garet...@orcon.net.nz> wrote: > The boot loader is different, XM v.5.5.11 was the last version to use the old > bootloader that worked when using tftp to flash openwrt, the new bootloader > starting with XM v5.6.x only accepts official ubnt firmware over tftp. I can > confirm though you can still flash openwrt using the factory image in the web > interface. The other option which I haven’t tested but it may possibly work > is to scp the sysupgrade image to /tmp/ on the ubnt device and then use mtd > to write directly. Ah, I have been downgrading via the web interface to 5.5.10, then upgrading to OpenWrt from the web interface, but I don't have many to deal with. Can you downgrade to XM v.5.5.11 via tftp and then flash OpenWrt from there? Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Tried to update ticket 20982 on dev.openwrt.org
Try downgrading the firmware to XM.v5.5.10 (I use http://www.ubnt.com/downloads/XN-fw-internal/v5.5.10/XM.v5.5.10.24241.141001.1649.bin on my Nanostation LocoM2s at work) It will complain about long passwords not being supported, but it will let you downgrade to it and then you can flash OpenWRT onto it. Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love On Wed, Oct 5, 2016 at 3:56 AM, Russell Senior <russ...@personaltelco.net> wrote: >>>>>> "Bill" == Bill Moffitt <bmoff...@ayrstone.com> writes: > > Bill> I have been busy with other things, but I finally got a shipment > Bill> of brand-new PicoStations (XM, identical to Bullet) here and tried > Bill> to flash both the trunk builds of OpenWRT and LEDE on them. > > Bill> I'm getting the same error I did some months back: > > Bill> sent DATA
Re: [OpenWrt-Devel] Introducing the LEDE project
On Thu, May 5, 2016 at 9:06 AM, Bruno Randolf <b...@einfach.org> wrote: > > But as someone who is following, using, building upon and sometimes > contributing to OpenWRT since ~10 years I can only say that the only > developers who have been visible, reacting and committing stuff have > left. I still wonder why, of course... +1 (although I might change "the only" to "the majority of the"). Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Which image for the Nanostation Loco M2, WAS:Cannot flash UBNT Loco M2
On Fri, Mar 11, 2016 at 11:19 AM, Matthias Schiffer <mschif...@universe-factory.net> wrote: > As I wrote, "bullet" is the correct image for all XM devices with one > ethernet port and no USB. Finally had a chance to play with the Bullet and Nanostation images this week. What I found is that the Nano M image includes the switch driver which lets you use the switch (for example, I am using it to run 3 VLANs and 3 wireless networks from one AP). The Bullet image does not load that driver and as such, does not let you use the switch. Here is my config with working VLANs (LAN is untagged on the switch, network2 is tagged with vlan 1 and network 3 is tagged with vlan 3): ***Begin /etc/config/network on line 8 after the loopback section** config interface 'lan' option type 'bridge' option ifname 'eth0' option proto 'dhcp' config 'switch' 'eth1' option 'reset' '1' option 'enable_vlan' '1' config 'switch_vlan' 'eth0_1' option 'device' 'eth0' option 'vlan' '1' option 'ports' '0t' config interface 'network2' option proto 'dhcp' option type 'bridge' option stp '1' option ifname 'eth0.1' config switch_vlan option device 'switch0' option vlan '3' option vid '3' option ports '0t' config interface 'network3' option proto 'dhcp' option type 'bridge' option stp '1' option ifname 'eth0.3' ***End /etc/config/network** Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Which image for the Nanostation Loco M2, WAS:Cannot flash UBNT Loco M2
)On Fri, Mar 11, 2016 at 9:28 AM, Matthias Schiffer
<mschif...@universe-factory.net> wrote:
> PS. Completely unrelated to this issue: I noticed in your log that you used
> the wrong image ("nanostation" instead of "bullet") for your Loco. This
> isn't really an issue, as the nanostation and bullet images only differ by
> the number of ethernet ports they define, but you'll have a dead "eth1"
> device. The image "nanostation" should used for the NanoStation (as it is
> the only device with two ethernet ports), and "bullet" for everything from
> the AirMax XM series except NanoStation and Rocket (Bullet, Loco,
> PicoStation, ...)
So, which should be used for the Nanostation Loco M2 (
http://www.amazon.com/Ubiquiti-NanoStation-locoM2-2-4GHz-Outdoor/dp/B004EGI3CI/
) which has one Ethernet port?
The one I have is an older (non-XW) device. For CC, I see:
openwrt-15.05-ar71xx-generic-ubnt-bullet-m-squashfs-sysupgrade.bin and
openwrt-15.05-ar71xx-generic-ubnt-nano-m-squashfs-sysupgrade.bin
I had used the nano build, but it has a non-functional eth1 port.
Aaron Z
A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects.
— Robert Heinlein, Time Enough for Love
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Designated Driver
+1 for Designated Driver Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love On Tue, Apr 7, 2015 at 3:47 PM, Hartmut Knaack knaac...@gmx.de wrote: That Doodle poll turned out to be spamed/trolled, and everyone could even change or delete other votes. Since this was just communicated over this mailing list, and subscribers are at least basically verified, why not have a good old fashioned poll? Give your +1 answer on this mail if you prefer Designated Driver. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt release name
On Mon, Apr 6, 2015 at 6:59 AM, Marc Nicholas m...@wimoto.com wrote: +1 on Designated Driver as everyone else is obviously drunk running factory firmware ;) +1 for Designated Driver from me as well ;D Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Wireless Router with openwrt, how to use dual band
This would require that your server has dual NICs and your laptops can connect to both 2.4ghz and 5ghz at the same time. Your device will likely have a configuration for the 2.4 ghz radio and one for the 5ghz radio. Setup 2 networks/firewall zones (LAN and LAN2?), then assign the 2.4ghz radio to LAN and the 5ghz radio to LAN2. Set your server to have an IP on LAN and one LAN2, then set the group messages to be sent from the LAN2 IP and the private messages be sent on the LAN IP. I am curious, are some of these messages large enough to cause issues with the network, or why do you want to use both bands like this? Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love On Thu, Feb 12, 2015 at 12:41 AM, Robert Clove cloverob...@gmail.com wrote: Can u explain in detail.. On Wed, Feb 11, 2015 at 8:01 PM, Aaron Z aczlan+open...@gmail.com wrote: On Wed, Feb 11, 2015 at 9:15 AM, Robert Clove cloverob...@gmail.com wrote: Hi, I have few laptops and two routers with dual band (TP-LINK TL-WDR3600 N600 WIRELESS DUAL BAND GIGABIT ROUTER) . Ported openwrt on the router . What i am trying to achieve is if someone want to send msg to a an individual then one of the band should be used (eg 2.4GHz) and if someone want to send message to the group then it should be send through another band (eg 2.8GHz or 5 GHz). How can i do that.? I have created a mesh network and written a simple client server applications through which all laptops communicate. I would think that you would want to setup different IP ranges for the different bands (ie: 2.4ghz uses 10.0.100.x and 5ghz uses 10.0.101.x) and then set your server to communicate on those IP ranges Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Wireless Router with openwrt, how to use dual band
On Wed, Feb 11, 2015 at 9:15 AM, Robert Clove cloverob...@gmail.com wrote: Hi, I have few laptops and two routers with dual band (TP-LINK TL-WDR3600 N600 WIRELESS DUAL BAND GIGABIT ROUTER) . Ported openwrt on the router . What i am trying to achieve is if someone want to send msg to a an individual then one of the band should be used (eg 2.4GHz) and if someone want to send message to the group then it should be send through another band (eg 2.8GHz or 5 GHz). How can i do that.? I have created a mesh network and written a simple client server applications through which all laptops communicate. I would think that you would want to setup different IP ranges for the different bands (ie: 2.4ghz uses 10.0.100.x and 5ghz uses 10.0.101.x) and then set your server to communicate on those IP ranges Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dual Wifi for OpenWRT
As in to run on 2 different 2.4ghz channels, or to just provide 2 SSIDs? Most platforms can run multiple SSIDs, I personally have several Linksys WRT54GL and TPLink TL-WR1043ND (HW versions 1 and 2) devices that happily run 3 SSIDs (all in AP mode, all on the same channel). Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love On Sat, Jan 10, 2015 at 11:15 AM, Bruno Randolf b...@einfach.org wrote: Hello! Does anyone know a hardware platform with 2 or more wifi interfaces which can both be used in the 2.4 GHz band? I just went thru the table of hardware looking for boards which have more than one wifi. Unfortunately all of the consumer APs tagged with 2WNIC seem to have 1 wifi for 2.4GHz and one for 5GHz. The few other boards which can support more than one wifi (RouterBoard, Complex, Gateworks) are miniPCI or mPCIe based and look like developer boards meaning one has to get the board, cards, casing separately and assemble it manually... Is there really no readily availabe HW with more than one wifi? I'm puzzled... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Configuring ethernet auto-negotiation off, setting speeds explicitly
On Tue, Nov 11, 2014 at 9:09 PM, Shankar Unni shankaru...@netscape.net wrote: Is there any way to disable auto-negotiation on an ethernet interface and manually set the speed and duplex parameters for it via netifd? (some equivalent of option autonegotiate 0, etc.?) I couldn't find anything in netifd that would allow us to specify this directly. Failing this, are there any clever tricks that can allow us to do this? Have you looked into swconfig [1]? that looks like it should let you set link speeds on a per port basis. [1] http://wiki.openwrt.org/doc/techref/swconfig Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Default dhcp (client) hostname is unset - Luci implies $(hostname)
On Tue, Oct 7, 2014 at 7:02 PM, Justin Vallon justinval...@gmail.com wrote: So either: 1) The dhcp hostname option should be blank to indicate no default value (maintain current behavior) 2) When udhcpc is invoked, it should pass -H $(hostname) in case of default (make backend behave as Luci implies) IMO: I find it nice that many hosts pass their hostname automatically, so that the DHCP active lease list is useful, versus a lot of ? entries and ethernet addresses. So, I would vote for 2. Opinions? Where would this bug get posted? (wiki.openwrt.org is down, so I cannot check the wiki) The wiki is working for me now... That info is stored on a per interface basis in /etc/config/network (see Link[1]) and is not set by default, although it may pull from /etc/config/system (see Link[2]) if unset in /etc/config/network. The default value in /etc/config/system is 'OpenWrt' Link[1]: http://wiki.openwrt.org/doc/uci/network#protocol.dhcp Link[2]: http://wiki.openwrt.org/doc/uci/system Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] desperately seeking info on this weird MT7620A/MT7610EN dev board
On Tue, Oct 7, 2014 at 7:06 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: finally, given that this board looks like *someone's* dev board, would anyone know where it might have come from? there's no manufacturer name on it anywhere. in the ramips dts file MT7620a.dts, i can see a reference to a Ralink MT7620a + MT7610e evaluation board. might that be it? i'd post a pic but i signed an NDA, although since no one has any idea where the board came from, i'm not sure what i'd be disclosing by posting a pic. i'm open to any information i can get, particularly support for that MT7610EN radio chip. thanks muchly. Any chance that it has an FCC ID, chip model numbers or other regulatory body unique number on it that you could share? I realize that you are in Canada and its a off brand board but you never know, the OEM might have used the same FCC number when they cloned the board... Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] Fix VLAN on Atheros AR8327N
On Tue, Sep 23, 2014 at 6:22 AM, Felix Fietkau n...@openwrt.org wrote: Hi Valentin, I finally got around to properly reviewing your changes, and they look correct to me. I committed them in r42652, r42653 - let's see if any new issues show up. It works as expected on my TPLink TL-WR1043ND (using the r42653 image). Is there any chance of this making 14.07, or will it need to wait for 14.07.1? Thanks Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] Fix VLAN on Atheros AR8327N
As someone who has spent much of the past week trying to figure out why my TL-WR1043ND V2 wont work with both taggged and untagged packets on the same port, I am all for it being applied. If its not, a note on the 1043 page in the wiki explaining that you cant have tagged and untagged packets on the same port in versions X, Y and Z and linking to the patch would be very useful... Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] TPLink TL-WR1043ND v2.1 WAN bug recurrence in stock firmware wr1043v2_en_3_17_38 (140613)
I have run into what seems to be a re-occurrence of the WAN bug on a TPLink TL-WR1043ND v2.1 with the stock firmware labled wr1043v2_en_3_17_38 (140613). The WAN port works fine with the stock firmware, but is seen as down when I flash over the OpenWRT firmware. I have tried BBrc3, BBrc2 and trunk (r42429 from 7 Sep 2014). My initial flash was from the stock firmware to the Factory BBrc3 image. I then switched to the Sysupgrade rc3 image. I also tried both the Factory and the Sysupgrade images from rc3 and trunk. I have tried flashing with both sysupgrade /tmp/tplink.bin and mtd -r write tplink.bin firmware (after dropping the firmware into the /tmp folder with WinSCP). I also tried flashing back to stock after using dd to remove the boot portion of the image (dd if=orig.bin of=tplink.bin skip=257 bs=512). When I did that, the WAN port started working again. Any suggestions on where to go from here? I can make what I need to do (setting up a trunk with a couple of vlans) work by splitting off a LAN port from the switch but it would be nice to use the WAN port for my Uplink and have 4 LAN ports available to plug in other devices. Any suggestions? Thanks Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Barrier Breaker timeline?
I am curious if there is a timeline for either RC4 or the final release for Barrier Breaker? The RC3 release announcement said ( https://forum.openwrt.org/viewtopic.php?pid=242292 ) on 31 Jul said Depending on how testing goes we will push the final or RC4 within the next 2 weeks. That is obviously past, any idea on a new timeframe? I need to setup a couple of WNR1043ND access points I need to setup and would prefer to go straight to the final if that is coming in the next week or so. Thanks Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Loveove ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker timeline?
On Mon, Sep 8, 2014 at 10:23 AM, John Crispin blo...@openwrt.org wrote: the test build is done and we fixed the 2 problems that came up. SDK now works properly. all the packages from all feeds build (apart from old.packages which has a fallout of ~15 packages) currently we are waiting on a ath9k regression fix that is being tested just now. once that is in the release branch i will restart the builders and generate BB-final. Perfect. Thanks! Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Feeds on Trunk version
On Wed, Sep 3, 2014 at 3:52 PM, William Haynes will...@sabaitechnology.com wrote: It appears to me that feeds.conf.default has been changed to exclude oldpackages, many of which have not been moved yet to the new package location. See: https://forum.openwrt.org/viewtopic.php?id=52219 for the full whys and wherefores of what packages will be available in the next versions. I'm new at this but I had to delete the # in front of oldpackages in the feeds.conf.default to get all the packages needed. I know I saw snort in there... That is intentional. See the forum link above for the whys and the wherefores. Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Lots of missing packages!
On Wed, Aug 13, 2014 at 4:13 AM, Steven Barth cy...@openwrt.org wrote: The current status of oldpackages is this: If you are using trunk and want to use the possibly outdated packages you have to enable the oldpackages feed and build them manually. If you are using barrier breaker in the final version we will still build these outdated packages in binary form but won't enable the package repository in opkg.conf by default, so you have to manually opt-in to use these packages. Some packages there might be broken due to changes in the SDK but this will hopefully get addressed before the final release. The next release after barrier breaker will not include any unmaintained packages at all not even as opt-in. So, are the precompiled packages on openwrt.org [1] indicative of what will be available for the final release of BB? From there on ar71xx, nano was missing from RC1, but is back for RC2 [2] and RC3 [3]. Looking in the same folder [1] for the packages that Valent mentioned in his second ticket, I also see bluez-libs [4], bluez-utils [5], /i2c-tools [6], ntpclient [7], picocom [8] and python [9] as precompiled packages. Will those still be available in the final release? [1] http://downloads.openwrt.org/barrier_breaker/14.07-rc2/ar71xx/generic/packages/ [2] http://downloads.openwrt.org/barrier_breaker/14.07-rc2/ar71xx/generic/packages/nano_2.3.6-1_ar71xx.ipk [3] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/nano_2.3.6-1_ar71xx.ipk [4] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/bluez-libs_3.36-3_ar71xx.ipk [5] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/bluez-utils_3.36-12_ar71xx.ipk [6] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/i2c-tools_2013-12-15-1_ar71xx.ipk [7] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/ntpclient_2007_365-4_ar71xx.ipk [8] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/picocom_1.7-1_ar71xx.ipk [9] http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/python_2.7.3-2_ar71xx.ipk Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1
Will Nano and WiFiDog be in RC2? They are in trunk, but were not included in RC1. Aaron Z - Original Message - From: John Crispin j...@phrozen.org To: openwrt-devel@lists.openwrt.org Sent: Friday, July 25, 2014 9:57:52 AM Subject: Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1 Hi, we did rc1 and rc2 in trunk as we were fixing stuff. rc2 is almost ready, i already have the trunk built, the IB worked for all targets this time after our fixes. i am about to start one of the builder on old.packages and the other builder on all the other feeds. once that is done and rc2 is online we will most likely fork the release branch and only backport fixes from there on. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] IPv6 firewall and Port Control Protocol (Was: Barrier Breaker 14.07-rc1)
- Original Message - On Wednesday, July 16, 2014 2:10:53 PM Gui Iribarren g...@altermundi.net wrote: Benjamin is giving some great examples of real-world scenarios where an default-open firewall simplifies administration, and where a default-closed firewall would be not only unnecessary (provides no benefits), but would indeed complicate setting up things. On the other hand, how many devices realistically need to be accessible from the outside by default in a typical setting (ie: in a home/small office)? On a network you have several classes of devices: 1. Devices that frequently need to run an server or peer to peer connection that requires outside access (ie: servers, some computers, tablets, phones, gaming consoles, VOIP phones, etc) 2. Devices which might need to be accessible from the outside in a few cases, but generally speaking have no need to be accessible from the outside (ie: most computers 3. Devices which generally have no need to be accessible from the outside (ie: NAS, network printer, security camera, security system, phone system, etc) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] IPv6 firewall and Port Control Protocol (Was: Barrier Breaker 14.07-rc1)
Sorry for the earlier email, apparently I accidentally hit send rather than save... - Original Message - On Wednesday, July 16, 2014 2:10:53 PM Gui Iribarren g...@altermundi.net wrote: Benjamin is giving some great examples of real-world scenarios where an default-open firewall simplifies administration, and where a default-closed firewall would be not only unnecessary (provides no benefits), but would indeed complicate setting up things. On the other hand, how many devices realistically need to be accessible from the outside by default in a typical setting (ie: in a home/small office)? On a network you have several classes of devices: 1. Devices that frequently need to run an server or peer to peer connection that requires outside access (ie: servers, some computers VOIP phones, etc) 2. Devices which might need to be accessible from the outside in a few cases, but generally speaking have no need to be accessible from the outside (ie: most computers, media players, phones, tablets, gaming consoles, etc) 3. Devices which have no need to be accessible from the outside except in special circumstances and in fact could be a security risk if exposed to the outside world (ie: NAS, network printer, security camera, security system, phone system, etc) On 16/07/14 12:09, Gert Doering wrote: This actually is a somewhat moot arguments. Devices travel today, and while your home network and office network might be behind a firewall, the hotspot you're using while waiting for your train might not be. That I think is the point. The open everything above port 1024 model is a good idea for some systems (ie: hotspots, hotel networks, etc) but in the typical home or office setting, the great majority of the devices have no need to be accessible from the outside and in fact, making them available from the outside creates a security risk if there is any kind of security flaw on the device. IMO, it comes down to trust: Do you trust that the people who made your NAS, blueray player, etc will release patches when exploits are found 3 years down the road? I don't. Do you trust that the people who made the firmware for your networked camera didn't leave any back doors in it to be found down the road (ie: a hardcoded root password, poor security on the webpage, etc)? I don't. Do you trust that Microsoft didn't miss any bugs in the Windows 7 firewall and that none of the software on the computer is leaving a port open? I certainly don't. I would venture to guess that 95% (or more) of the people who install OpenWRT are quite capable of opening ports in a firewall. == Perhaps a solution would be to do the following: 1. Have a global setting for the firewall that has three options: 1a. Default open from port 0 on up 1b. Default open from port 1024 on up 1c. Default closed 2. Add/change LUCI interface for opening ports. Add a hyperlink or button next to the list of computers on the network that allows setting the following options (for each computer) in the OpenWRT firewall: 2a. Default to open from port 0 on up 2b. Default open from port 1024 on up 2c. Open port X (or service X) for this computer Factory default could be 1c for the time being (to be consistent with the current IPv4 settings) and it could be re-evaluated down the road as things change. == My $0.02. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] IPv6 firewall and Port Control Protocol (Was: Barrier Breaker 14.07-rc1)
- Original Message - On Monday, July 14, 2014 5:36:09 PM Benjamin Cama ben...@dolka.fr wrote: Hi everyone, Le lundi 14 juillet 2014 à 22:17 +0900, Baptiste Jonglez a écrit : On Mon, Jul 14, 2014 at 02:38:16PM +0200, Steven Barth wrote: Hi Baptiste, in general our current firewalling approach is to keep defaults for IPv4 and IPv6 relatively close (not considering NAT here of course). Could you detail the reasoning behind this approach? Don't confuse the user? I'd rather have Don't bother the user: things should generally just work, without having to configure anything (in this case, port forwarding). But there is an obvious tradeoff with security. I agree with Baptiste here. There is no equivalent in IPv4 of “global reachability” by default with the NATs we have today, so we can't have the same defaults. Global reachability is how IP in general was meant to be; please, do not make it broken again. As I understand it, this is NOT adding NAT, but (by default) blocking unsolicited incoming connections from the outside world to devices on the internal network (which dont necessarily need to be accessible from the outside world). That is the whole point in using a firewall is it not? To keep people out of where they shouldn't be. Opening up the IPv6 firewall by default would be unexpected and I don't really like the approach for that matter and honestly I don't trust client devices that much. At least opening UDP ports 1024 seems pretty reasonable, and covers most use-cases regarding VoIP and video. But it does indeed depart from the IPv4 case (not sure if it is such a bad idea though). This looks like a good compromise to me. Knowledgeable users can disable the firewall for needed hosts, while for others this “just work”. PCP may be coming one day, but it's still not there yet, so we need not to break the default configuration while waiting for it. Opening access from the outside to the inside as a default rule goes against the principle of least privilege on which firewall rules are generally predicated. As I understand it, if a device on the inside of the network initiates the connection to a device on the outside (say from a VOIP phone to a VOIP server), return connections from the server are allowed. What gets blocked are unsolicited connections from the outside which are generally unneeded (and can be a security risk) unless one is running a server (in which case, the users should know how to open ports on their firewall). Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?
- Original Message - On Monday, April 7, 2014 at 8:49:25 AM Fernando Frediani fhfredi...@gmail.com wrote: NDA = $$$ = Quiet I just don't understand what is the problem, if it's really true, to tell the most interested people (developers) that you are working on something directly related to the project, even without giving any further details due the NDA. Perhaps the first rule of this particular NDA is that you cant confirm or deny the existence of the project and the associated NDA? That would seem rather shortsighted and counterproductive in this case (given that they claim to want to ensure OpenWRT support, yet none of the core developers is claiming to have even seen one), but it wouldn't be the first case of a contract that was shortsighted and counterproductive. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WNR2000v3 Magic Numbers
On Saturday, February 1, 2014 11:13:25 PM Find Herzfeld f...@seattlemesh.net wrote: Did you flash it with the Web GUI? I've managed it fine with a serial cable booting into tftp mode or whatever it's called, but the default netgear Web interface rejects it. Thinking on how I did it, what version of the stock firmware is on these devices that you are working with? I used the web GUI. As I recall, I tried installing OpenWrt on whatever stock firmware was on there, but none of the files would work, all where rejected. I updated the stock firmware to the latest version (from the Netgear site), then tried openwrt-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img but it was rejected. I then tried openwrt-ar71xx-generic-wnr2000v3-squashfs-factory.img which worked. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WNR2000v3 Magic Numbers
On Saturday, February 1, 2014 3:22:02 AM Finn Herzfeld f...@seattlemesh.net wrote: I've been bumbling around with OpenWRT and someone showed me how tomodify a Makefile to make a build that the default firmware on the Netgear WNR2000v3 will accept as an upgrade, thus making flashing significantly easier. It seems the sort of that you'd want in the main trunk, so here's the patch file. I'm not too good at making patch files, so let me know if I did something wrong, or this is the wrong place to send this or whatever. I am not a developer (more of a power user), but did you try both factory images? I flashed one of these a few weeks back ($5 at the thrift store) and it flashed fine with the then current trunk. IIRC, the openwrt-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img didnt work and I had to use the openwrt-ar71xx-generic-wnr2000v3-squashfs-factory.img but it flashed quite happily and has been acting as a WAP ever since. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Buildbot not working for various snapshots?
Looks like snapshots for the adm5120, ar71xx and adm5120 branches were last built on 19 Jan 2014... Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?
On January 15, 2014 6:06:59 PM Peter Lawler openwrt-de...@bleeter.id.au wrote: Oh, bad me for replying to myself... but from the press release page: http://www.linksys.com/en-us/press/releases/2014-01-06_Linksys_wrt_revolutionizes_wireless_networking Linksys has also been working with the OpenWRT community to make an open source firmware downloadable when product is available. That sentence barely parses. Making a firmware downloadable, but no source huh? Working with the community but this thread suggests otherwise? But hey, marketing. Perhaps marketing is watching this thread? It now reads: Open Source is a vehicle for other communities, such as DD-WRT, Open WRT, and Tomato, to create their own custom versions of open source firmware for the product. OpenWRT developers will be provided hardware and SDKs/APIs to begin creating custom firmware for the WRT1900AC. An OpenWRT custom firmware for WRT1900AC is planned to be available for download online at availability in the spring 2014. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?
On January 15, 2014 7:54:38 PM Fernando Frediani fhfredi...@gmail.com wrote: However if they are only trying to take advantage of the OpenWRT name but not really contributing and engaging with the community they should not get the expected result from anyone here. I suspect there are people from Belkin/Linksys in this mail list and already working on it, but I also believe they should be engaging with us and being more clear with they intentions and plans when they mention OpenWRT in their marketing material. Nobody expects they to show any industrial secrets, but at least to work close to OpenWRT developers and release all the relevant open source material. I agree. Had some spare time tonight, so I sent the contact person in the press release a comment to that effect pointing her to https://lists.openwrt.org/pipermail/openwrt-devel/2014-January/023272.html We shall see what (if anything) comes of it. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] TP-Link TL-WR841ND to replace WRT54GL?
We have about 50 WRT54GL wireless access points in ~40 libraries which act as access points to serve up 2 wireless networks (an encrypted staff one and a unencrypted public one for patron use (using WiFiDog auth/stats)). We have installed all of the 54GLs that we bought a few years back and I am looking at the possibility to starting to send out TP-LINK TL-WR841ND boxes (such as http://www.amazon.com/dp/B0037D51FQ ) for new installs. Anyone have any experience on how stable the UFO models are with OpenWRT? Is there a better option (in the US market) that costs $60 (or less) with a 4+ port switch and at least 802.11G wireless? Thanks Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] TP-Link TL-WR841ND to replace WRT54GL?
Thanks all, we will be going with the TL-WR1043ND to allow for some future-proofing. Its currently the same price as a WRT54GL through Amazon so it will fit well in the budget. Thanks again Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] TP-Link TL-WR841ND to replace WRT54GL?
On 6 Mar 2013 at 2:35:44 PMGert Doering g...@greenie.muc.de wrote: In that case, make this a +5, at least :-) - more RAM, more Flash, GigE switch, faster CPU, ... There's really no reason for a 54GL anymore, unless you specifically need *that* hardware, for example because you have a highly customized image already... No custom images here. We mainly went with the WRT54GL last time because that is what we had used before. We use a stock image, then we install WiFiDog, bandwidth management and tweak the settings in /etc/config (for example, we switch the LAN and WAN ports so that the 4 LAN ports act as a switch on the WAN and the single WAN port is on the LAN). Out of curiosity, what kind of throughput do you see on the wired and N wireless connections? Now that I see these, I may also replace the WRT150N and DIR-601 that I am running (both running OpenWRT) with something that will handle higher throughput. Thanks Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for Openwrt programmers to customize Open-Mesh router code
Paul Fertser fercer...@gmail.com wrote: Brian Epstein br...@deepbluecommunications.com writes: Assuming Gold’s Gym is now the official Gym sponsor for all Wyndham hotels. Now for example when anyone searches for the word “Gym” or “step class” on Google.com at any Super8 from behind our equipment, the search is modified prior to being sent to Google.com such that the search now says “step class golds gym”. Am I reading that right that when somebody wants to send a search query to Google you hijack it and modify however you want? Seriously? That's how I read it. If that happened to me on a free hotel internet connection (which I am paying for with my room charge), I would NOT stay at that hotel again (I would leave after that night if possible) and (at minimum) the following people would be informed why I left: The hotel manager, corporate headquarters (if the hotel was part of a chain), my friends who keep up with me on various social media sites, Google Maps and any other place that I could find online that did reviews on that hotel, anyone who asked me about my trip. If I am on a public network, most anything important is running back home over a OpenVPN or connecting via HTTPS, but messing with guests searches will only lose you goodwill... Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Any status update regarding the Attitude Adjustment release process?
On 29 Sep 2012 at 7:33:11 AM John Crispin j...@phrozen.org wrote: i currently have about 10 more tickets i will process today and tomorrow. the plan is to fork of the beta2 this coming week. we fixed quite a lot of things so we decided to make a beta2. i hope that we can push the final shortly after the beta2 ... it really depends on the testing results Glad to hear that it is progressing. I have 12.09-beta installed on a D-Link DIR-615 and it is much more stable then the stock firmware, currently it has been up for ~20 days (vs 4-5 days before a reboot with the stock firmware). The only (very minor) issue I have run into is that it is listed as a DIR-600 in Luci even though I used the DIR-615 image on DIR-615 hardware. Thanks to all those who have made this possible. Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attitude Adjustment (12.08)
Glad to hear that things are going forward with the Attitude Adjustment release. On Wednesday, August 15, 2012 at 12:09:15 PM John Crispin j...@phrozen.org wrote: The 3 build bots that we are using to generate the binaries have been running none stop for the last 3 weeks. Trunk and the packages feed are now in a state that all packages build for all targets that will be part of the release. Does this mean that there be images built for devices such as the D-Link dir-6xx which have images in 10.03.1[1] but images are not currently being built in trunk[2] as turning on debug symbols in trunk made those packages too big for them[3]? [1]http://downloads.openwrt.org/backfire/10.03.1/ar71xx/ [2]http://downloads.openwrt.org/snapshots/trunk/ar71xx/ [3]https://lists.openwrt.org/pipermail/openwrt-devel/2012-April/014873.html Thanks Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attitude Adjustment (12.08)
- Original Message - From: John Crispin j...@phrozen.org To: openwrt-devel@lists.openwrt.org Sent: Wednesday, August 15, 2012 12:31:41 PM Subject: Re: [OpenWrt-Devel] Attitude Adjustment (12.08) On 15/08/12 18:27, Aaron Z wrote: Glad to hear that things are going forward with the Attitude Adjustment release. On Wednesday, August 15, 2012 at 12:09:15 PM John Crispin j...@phrozen.org wrote: The 3 build bots that we are using to generate the binaries have been running none stop for the last 3 weeks. Trunk and the packages feed are now in a state that all packages build for all targets that will be part of the release. Does this mean that there be images built for devices such as the D-Link dir-6xx which have images in 10.03.1[1] but images are not currently being built in trunk[2] as turning on debug symbols in trunk made those packages too big for them[3]? [1]http://downloads.openwrt.org/backfire/10.03.1/ar71xx/ [2]http://downloads.openwrt.org/snapshots/trunk/ar71xx/ [3]https://lists.openwrt.org/pipermail/openwrt-devel/2012-April/014873.html Thanks Aaron Z yes Glad to hear it. Thanks Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] D-Link DIR-6xx images not listed in snapshots/trunk
Any updates on this? If the debugging symbols are frequently needed with snapshots, would it be possibly perhaps to have /trunk and /trunk_debug directories? Then if someone wanted or needed debugging symbols, they could use the /trunk_debug snapshot for their device? I realize that this would significantly increase the amount of space needed for storing the snapshots and the amount of time needed to compile them, but in my case, I dont currently have the knowledge to compile a build, or the time to learn how (between working full time, going to school, raising a family and my part-time jobs, there isn't much play time in my schedule), but I would like to take advantage of the changes which should make the trunk version of image for the D-Link DIR-601 better than the 10.03.1 image, but without compiling the image myself, I am stuck with the stock firmware. At some point down the road (when I finish with my degree), I hope to setup a build environment so I can create images, but it is not possible now, nor will it be for at least 6 months. Thanks Aaron Z - Original Message - From: Travis Kemen thepeople @ openwrt .org To: OpenWrt Development List openwrt -devel@lists. openwrt .org Sent: Wednesday, April 11, 2012 7:50:52 PM Subject: Re: [ OpenWrt -Devel] D-Link DIR-6xx images not listed in snapshots/trunk Debugging symbols were turned on in the newer builds to help us debug units in the field without having to have people re-flash (this is a change to the snapshots only). It made the kernel image too large for that device, I will look into it. Travis On Wed, Apr 11, 2012 at 4:46 PM, Salander salander @ gmx .us wrote: There were issues around the 14th with the buildbots hanging/crashing and nothing got built for a while under snapshots. Maybe this target got dropped from the scripts accidentally when they were restarted... Sent from my iPhone On 11 Apr 2012, at 18:24, Aaron Z aaronz @pls-net.org wrote: I picked up a D-Link DIR-601 for a couple of bucks today and went to The Google webcache [4] leads me to believe that the 14 Mar snapshot had 14 images for the DIR-6xx platform, but they are no longer found in the 11 Apr snapshot. l ___ openwrt -devel mailing list openwrt -devel@lists. openwrt .org https ://lists. openwrt .org/mailman/ listinfo / openwrt -devel ___ openwrt -devel mailing list openwrt -devel@lists. openwrt .org https ://lists. openwrt .org/mailman/ listinfo / openwrt -devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] D-Link DIR-6xx images not listed in snapshots/trunk
I picked up a D-Link DIR-601 for a couple of bucks today and went to flash it, but I cannot find the correct image listed in the snapshots folder for ar71xx [1] Per the Wiki [2] and and Trac for changeset 30570 [3] there should be an image for the 600 and one for the 601, but neither are listed in the snapshots/trunk folder The Google webcache [4] leads me to believe that the 14 Mar snapshot had 14 images for the DIR-6xx platform, but they are no longer found in the 11 Apr snapshot. [1] http://downloads.openwrt.org/snapshots/trunk/ar71xx/ [2] http://wiki.openwrt.org/toh/d-link/dir-600?s[]=build#installing.of.openwrt.for.first.time [3] https://dev.openwrt.org/changeset/30570/trunk [4] http://webcache.googleusercontent.com/search?q=cache:xknQ5OFNcp8J:downloads.openwrt.org/snapshots/trunk/ar71xx/+cd=2hl=enct=clnkgl=us Am I missing something, or were these snapshots missed in the 11 Apr build? Thanks Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
On 02/02/2012 4:52:09 PM, Hauke Mehrtens wrote: On 01/28/2012 06:55 AM, Aaron Z wrote: When I run killall -9 hostapd then wifi I get told: Configuration file: /var/run/hostapd-phy0.conf and Using interface wlan0 with hwaddr MACADDRESS and ssid 'OpenWrt'wifi is still rejecting connections. When I run killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log it works right away. This behavior is strange it could be that debugging activates some needed code path, hostapd just works after the second start or that there are timing issues. Could you run hostapd just with -d and without -d and report what happens in these cases? Sorry for the delay. Its been busy around here. I ran killall -9 hostapd; /usr/sbin/hostapd -d /var/run/hostapd-phy0.conf /tmp/hostapd.log I was able to connect and go online. The log is attached as hostapd -d.txt (4 KB). I then rebooted the WAP and ran killall -9 hostapd; /usr/sbin/hostapd /var/run/hostapd-phy0.conf /tmp/hostapd.log I was able to connect and go online. The logfile was blank, so I didn't attach it. I tried connecting before running the commands and was rejected both times. Thanks Aaron Zrandom: Trying to read entropy from /dev/random Configuration file: /var/run/hostapd-phy0.conf nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 6 iftype 2 (STATION) nl80211: Failed to set interface 6 to mode 2: -16 (Device or resource busy) nl80211: Interface already in requested mode - ignore error netlink: Operstate: linkmode=1, operstate=5 nl80211: Using driver-based off-channel TX nl80211: Interface wlan0 is in bridge br-lan nl80211: Add own interface ifindex 5 nl80211: Add own interface ifindex 6 nl80211: Set mode ifindex 6 iftype 3 (AP) nl80211: Create interface iftype 6 (MONITOR) Failed to create interface mon.wlan0: -23 (Too many open files in system) Try to remove and re-create mon.wlan0 nl80211: Remove interface ifindex=7 nl80211: Create interface iftype 6 (MONITOR) nl80211: New interface mon.wlan0 created: ifindex=8 nl80211: Add own interface ifindex 8 BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) nl80211: Regulatory information - country=00 nl80211: 2402-2472 @ 40 MHz nl80211: 2457-2482 @ 20 MHz nl80211: 2474-2494 @ 20 MHz nl80211: 5170-5250 @ 40 MHz nl80211: 5735-5835 @ 40 MHz nl80211: Added 802.11b mode based on 802.11g information Completing interface initialization Mode: IEEE 802.11g Channel: 11 Frequency: 2462 MHz nl80211: Set freq 2462 (ht_enabled=0 sec_channel_offset=0) RATE[0] rate=10 flags=0x1 RATE[1] rate=20 flags=0x1 RATE[2] rate=55 flags=0x1 RATE[3] rate=110 flags=0x1 RATE[4] rate=60 flags=0x0 RATE[5] rate=90 flags=0x0 RATE[6] rate=120 flags=0x0 RATE[7] rate=180 flags=0x0 RATE[8] rate=240 flags=0x0 RATE[9] rate=360 flags=0x0 RATE[10] rate=480 flags=0x0 RATE[11] rate=540 flags=0x0 Flushing old station entries Deauthenticate all stations wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0 Using interface wlan0 with hwaddr 00:88:88:88:00:2a and ssid 'OpenWrt' Using existing control interface directory. ctrl_iface bind(PF_UNIX) failed: Address already in use ctrl_iface exists, but does not allow connections - assuming it was leftover from forced program termination Successfully replaced leftover ctrl_iface socket '/var/run/hostapd-phy0/wlan0' nl80211: Set beacon (beacon_set=0) wpa_driver_nl80211_set_operstate: operstate 0-1 (UP) netlink: Operstate: linkmode=-1, operstate=6 wlan0: Setup of interface done. RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP]) netlink: Operstate: linkmode=-1, operstate=6 RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added Unknown event 5 nl80211: Add ifindex 5 for bridge br-lan nl80211: Add own interface ifindex 5 RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP]) netlink: Operstate: linkmode=-1, operstate=6 RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added Unknown event 5 RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up nl80211: Ignore event for foreign ifindex 7 nl80211: Ignore dellink event for foreign ifindex 7 RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface mon.wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) RTM_NEWLINK, IFLA_IFNAME: Interface 'mon.wlan0
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Thanks for looking at my logs. I just installed the trunk that was compiled today (r29915, thanks to whoever ran that build) and SSH seems to be behaving, so my SSH issues may have just been a fluke. Wireless still fails at boot until I run the wifi debugging command as shown below. I tried running just wifi and even though both commands claim to use /var/run/hostapd-phy0.conf for the config, something is different. When I run killall -9 hostapd then wifi I get told: Configuration file: /var/run/hostapd-phy0.conf and Using interface wlan0 with hwaddr MACADDRESS and ssid 'OpenWrt'wifi is still rejecting connections. When I run killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log it works right away. One oddity, I see what may be an extraneous entry in ifconfig called mon.wlan0: Before the debug piece above: mon.wlan0 Link encap:UNSPEC HWaddr 00-88-88-88-00-2A-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:402 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:38292 (37.3 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:18:F8:D7:BB:35 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:1516 (1.4 KiB) After: mon.wlan0 Link encap:UNSPEC HWaddr 00-88-88-88-00-2A-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:136 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:13650 (13.3 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:88:88:88:00:2A UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:119 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:7058 (6.8 KiB) TX bytes:15905 (15.5 KiB) Should mon.wlan0 be there? Why do the errors all go away? Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Monday, January 23, 2012 4:38:16 PM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, thanks for the detailed report. With a quick look I was unable to see anything suspicious in the logs. I will try to reproduce your problems on one of my devices. Hauke On 01/22/2012 07:49 PM, Aaron Z wrote: Got the wireless to work today. I followed the directions at http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH session, then tried to connect. Before I ran it, I would get a connection failed message as soon as I tried to connect. After I ran the above command, it failed once, then connected on the 2nd try. That log is attatched as WiFiLog1.txt. I rebooted by pulling the power cable (I am fairly certain that the reboot command worked in 10.03.1, but cannot say for certain) and I tried connecting to the wifi again. I got a connection failed message as soon as I tried to connect. After I ran the aforementioned command, I was able to connect immediately on the first try. That log is attached as WiFiLog2.txt. Is there a more effective and/or less intrusive way to log this data? I looked in /tmp/log, but the only things I see are lastlog and wtmp both of which are 0 byte files that claim to have been created on 1/1/1970. SSH and SCP both worked fine under 10.03.1. No lockups or reconnects that I remember. Package installation also worked. I was able to install the pciutils package without any drama. Let me know if I can provide any more data to help. Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Sunday, January 22, 2012 8:16:52 AM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, On 01/22/2012 04:54 AM, Aaron Z wrote: Resending as I used the wrong from address last time and it bounced. hmm at least I got your mails. It loaded and booted, but I am seeing some oddities. Not sure if these are related to being bleeding edge or what, but they are noticeable: The patch did what it was supposed to and I will merge it into trunk and Backfire branch. The other problems seam to be related to some other
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Got the wireless to work today. I followed the directions at http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH session, then tried to connect. Before I ran it, I would get a connection failed message as soon as I tried to connect. After I ran the above command, it failed once, then connected on the 2nd try. That log is attatched as WiFiLog1.txt. I rebooted by pulling the power cable (I am fairly certain that the reboot command worked in 10.03.1, but cannot say for certain) and I tried connecting to the wifi again. I got a connection failed message as soon as I tried to connect. After I ran the aforementioned command, I was able to connect immediately on the first try. That log is attached as WiFiLog2.txt. Is there a more effective and/or less intrusive way to log this data? I looked in /tmp/log, but the only things I see are lastlog and wtmp both of which are 0 byte files that claim to have been created on 1/1/1970. SSH and SCP both worked fine under 10.03.1. No lockups or reconnects that I remember. Package installation also worked. I was able to install the pciutils package without any drama. Let me know if I can provide any more data to help. Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Sunday, January 22, 2012 8:16:52 AM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, On 01/22/2012 04:54 AM, Aaron Z wrote: Resending as I used the wrong from address last time and it bounced. hmm at least I got your mails. It loaded and booted, but I am seeing some oddities. Not sure if these are related to being bleeding edge or what, but they are noticeable: The patch did what it was supposed to and I will merge it into trunk and Backfire branch. The other problems seam to be related to some other problems with trunk or with the wifi never used before. 1. luci (the web interface) times out and never loads The image I gave you did not contain luci so it will not load. 2. Installing packages does not seem to be working. When I run opkg update it gets to Inflating http://downloads.openwrt.org/snapshots/trunk/brcm47xx/packages/Packages.gz; then locks up my SSH session and I have to reconnect The image is a self build from trunk so with installing packages you could run into problems. But this problem is strange. 3. The reboot command does not seem to do anything (as determined by watching the LEDs and the response to ping). Did this work with 10.03.1? 4. It seems that ssh and scp lock up and force me to re-login frequently. No idea what it is related to, but it seems to do it every few minutes. Did this work with 10.03.1? 5. I see the OpenWrt wireless network after enabling the wireless, but I cannot connect to it (fails right away). When I run connection diagnostics, Windows 7 tells me Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint Do you see anything interesting in the log regarding wifi while trying to connect? 6. The Wireless LED on the WAP does not turn on Probably something is wrong in the wireless driver. There is a know issue with the wireless chip used in your device, but I do not know, if you are seeing this issue or if it is already fixed: BCM4321: some cards do not work in DMA mode (PIO is needed). Attached are: 1. dmesg2.txt (15.5 KB, the output of dmesg) The log looks good to me at least OpenWrt finds your wifi and does not panic. ;-) 2. nvram2.txt (11.8 KB, the output of nvram show) 3. wireless2.txt (330 B, the contents of /var/config/wireless) Aaron Z I asked for the serial in the case the changes in the patch are causing a kernel panic and the device does not boot any more, so that you were able to recover or debug the issue, but it looks like it is not needed. But be aware that the normal serial port of a PC uses 12V and the serial TTL port of most embedded devices are using 3.3V Hauke root@OpenWrt:~# killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log #/tmp/hostapd.log random: Trying to read entropy from /dev/random Configuration file: /var/run/hostapd-phy0.conf nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 6 iftype 2 (STATION) nl80211: Failed to set interface 6 to mode 2: -16 (Device or resource busy) nl80211: Interface already in requested mode - ignore error netlink: Operstate: linkmode=1, operstate=5 nl80211: Using driver-based off-channel TX nl80211: Interface wlan0 is in bridge br-lan nl80211: Add own interface ifindex 5 nl80211: Add own interface ifindex 6 nl80211: Set mode ifindex 6 iftype 3 (AP) nl80211: Create interface iftype 6 (MONITOR) Failed to create interface
Re: [OpenWrt-Devel] [INFO] Failsafe provider restore and why care?
- Daniel Dickinson crazycsh...@gmail.com wrote: Basically if this is in the firmware you can update all your routers by pressing the reset button, or for certain types of bricking, recover via reset button. It is also possible to do upgrades of many units in the field, and with future work we'll be doing, to schedule updates for routers that stay in contact with us via a reverse connect tunnel. Sounds like a we might be interested in doing something similar down the road for maintenance/recovery of our WAPs, we just deployed 44 WRT54GL routers. They are in our member libraries and provide: 1. Patron wireless network: Unencrypted, on the lan of the 54GL lets patrons login with their library card number and get online. This network will only let them go online (not to the intranet or library computers) and is throttled to 2.5M/250k 2. Staff wireless network: Encrypted with WPA2, bridged to the WAN of the 54GL lets library owned computers be connected to the library network as is they were hooked to the wired network. No throttling or login (beyond the passkey for the WPA2 anyways). All these have a cron job that runs at 3am. It uses wget to download a update script from our webserver and run it. After that finishes, it reboots (to keep WiFiDog from locking up). The plan is to use the update script for when we need to change the settings for WiFiDog (or for the WAP itslelf). Updates for an individual WAP can be done with an IF statement in the script to check the WAP name Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
