Re: [OpenWrt-Devel] Designated Driver
On Thu, Apr 9, 2015 at 12:37 PM, Eric Schultz wrote: > +1 > > I agree with Imre that Dirty Diamond should be avoided due to its unpleasant > connotations with blood diamonds. > > Eric > > -- > Eric Schultz, Community Manager, prpl Foundation > http://www.prplfoundation.org > eschu...@prplfoundation.org > cell: 920-539-0404 > skype: ericschultzwi > @EricPrpl > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > +1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attitude Adjustment (12.08)
On Wed, Aug 15, 2012 at 2:43 PM, Hannu Nyman wrote: > On Wednesday, August 15, 2012 at 12:09:15 PM "John Crispin" > wrote: >> As you may have noticed we are getting prepared for the Attitude >> Adjustment release. > > Does that also mean that Backfire is going to be retired? With no formal > 10.03.2 forthcoming? > > Is the plan that AA will be the new "stable branch" and the trunk gets a new > name after the release? > > Have you thought about the future release strategy? Continuing the current > practice of "a major release every two years with some interim releases"? Or > Firefox/Chrome type of new releases more rapidly, e.g. every 6 months? > Personally I prefer the 2 year major release cycle. That is what people like RedHat and commercial unices like to do. And maybe support the old stables for another year or two. > Based on Backfire's recent history, I believe that trying to maintain a > stable branch for too long periods (like over 2 years for Backfire) is going > to succeed, as the trunk will get too much ahead of the stable branch and as > the developers' attention tends to be on the bleeding-edge trunk, the stable > branch is almost dead in practice. I suggest Openwrt to rethink the release > strategy towards a bit more rapid "stable" releases. > Can't stuff done in the bleeding-edge be backported to the stable? > > ___ > 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] NAND Flash questions and Dockstar
I think I am experiencing the issues mentioned in http://www.dslreports.com/forum/r24833189-Other-Seagate-DockStar-U-Boot-NAND-flash-considerations. Namely, I installed the os in the flash memory; after a while it will degrade enough (probably due to writing/reading to it) that the dockstar will stop working and cannot successfully boot. Writing the root partition back to the nand solves the problem for a few more weeks. Could it be files are not being read/written in a way to keep the the flash storage happy (with all its block management and so on)? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Stuck beacon in Atheros on ASUS WL500-W
I have a ASUS WL500-W router running stock Backfire 10.03 whose (broadcom) wireless card was replaced with a Atheros 5416 card (kmod-madwifi installed) because I thought it was better supported. My /etc/config/wireless file look like this: config 'wifi-device' 'wifi0' option 'type' 'atheros' option 'channel' '7' option 'diversity' '0' config 'wifi-iface' option 'device' 'wifi0' option 'mode' 'ap' option 'network' 'wifi' option 'ssid' 'Moonbase' # option 'encryption' 'psk2' option 'encryption' 'psk2-aes' option 'key' 'lame passphrase here' option 'eap_type' 'TLS' Here are some things I have noticed: 1) I am seeing a lot of "stuck beacon" messages in dmesg: wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11) wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11) wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11) wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11) wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11) [...] At the same time, the wireless connection seems to fluctuate between nice and responsive to quite sluggish. By that I mean it feels like it is timing out a lot or it has no connection but the connection itself never drops. For instance ping times between my laptop and router or a machine in the wired side will increase hundredfold (2ms to 200ms). If I manage to go to the router and issue a 'wifi up' command, the wireless will become fast once again. Googling around I found pages such as http://spod.cx/blog/debian_lenny_madwifi_hostapd_stability_issues.shtml and http://madwifi-project.org/wiki/StuckBeacon stating it might be a problem with madwifi itself. Can anybody confirm or deny that? If the latter, what else can be causing these issues? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Dockstar + Attitude Adjustment = no kmod-usb-core?
So I am trying to install kmod-usb-uhci (or kmod-usb-ohci; I forgot which one is the right one for this device) in my dockstar. Since it never made to the stable release, I have to use the trunk, which is attitude adjustment. root@kong:~# opkg update Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/Packages.gz. Inflating http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/Packages.gz. Updated list of available packages in /var/opkg-lists/snapshots. root@kong:~# opkg install kmod-usb-ohci Installing kmod-usb-ohci (2.6.35.11-1) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/kmod-usb-ohci_2.6.35.11-1_kirkwood.ipk. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-ohci: * kmod-usb-core * * opkg_install_cmd: Cannot install package kmod-usb-ohci. root@kong:~# opkg install kmod-usb-uhci Installing kmod-usb-uhci (2.6.35.11-1) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/kmod-usb-uhci_2.6.35.11-1_kirkwood.ipk. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-uhci: * kmod-usb-core * * opkg_install_cmd: Cannot install package kmod-usb-uhci. root@kong:~# Ok, so we instal kmod-usb-core: root@kong:~# opkg install kmod-usb-core Unknown package 'kmod-usb-core'. Collected errors: * opkg_install_cmd: Cannot install package kmod-usb-core. root@kong:~# opkg list also tells me it knows nothing about kmod-usb-core. Am I missing something here? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] netatalk: Can only connect using guest/nobody account
I do not know if this question should be directed at the maintainer of the netatalk package, but since I do not know how to contact him I am posting it here. I am running Attitude Adjustment r26175 in my Seagate Dockstar, kong, and netatalk 2.1.3. So, my afpd.conf looks like this: - -noddp -uampath /usr/lib/uams \ -uamlist uams_guest.so,uams_randum.so \ -passwdfile /etc/netatalk/afppasswd \ -defaultvol /etc/netatalk/AppleVolumes.default \ -systemvol /etc/netatalk/AppleVolumes.system -guestname "nobody" \ -unsetuplog "default level file" -setuplog "default log_maxdebug" \ -sleep 1 -icon and my AppleVolumes.default is - /export/backup/system/time_machine "Time Machine Dump" allow:timelord,nobody \ options:tm volsizelimit:7 allowed_hosts:10.0.0.0/24 cnidscheme:dbd I have an password for local user timelord defined in afppassword. Now, let's say I am trying to connect from a Mac to kong's afp share. In this case I am using the GUI/Finder way since I do not know how to do it through command line yet. When I connect as guest user, which is translated to local user nobody as defined above in afpd.conf, I am successful. But, when I try to login as timelord, I am told told the username/pw does not work. I was capturing log in kong (using "logread -f") and this is how the log for the transaction looks like: May 18 18:07:06 kong daemon.info afpd[14690]: server_child[1] 14704 exited 1 May 18 18:07:06 kong daemon.info afpd[14705]: AFP/TCP session from 10.0.0.198:55655 May 18 18:07:06 kong daemon.info afpd[14690]: server_child[1] 14705 done May 18 18:07:18 kong daemon.info afpd[14706]: AFP/TCP session from 10.0.0.198:55656 May 18 18:07:18 kong daemon.info afpd[14706]: login noauth May 18 18:07:18 kong daemon.info afpd[14706]: login nobody (uid 65534, gid 65534) AFP3.2 May 18 18:07:18 kong daemon.warn afpd[14706]: volume "Time Machine Dump" does not support Extended Attributes, using ea:ad instead May 18 18:07:18 kong daemon.info afpd[14706]: logout nobody May 18 18:07:18 kong daemon.info afpd[14706]: 0.12KB read, 0.12KB written May 18 18:07:18 kong daemon.info afpd[14690]: server_child[1] 14706 done May 18 18:07:22 kong daemon.info afpd[14690]: server_child[1] 14707 exited 1 May 18 18:07:22 kong daemon.info afpd[14708]: AFP/TCP session from 10.0.0.198:55658 May 18 18:07:22 kong daemon.info afpd[14690]: server_child[1] 14708 done Why did it login and then logout as nobody when I specifically logged in as timelord at that exact time? And why it did not record any errors whatsoever? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] avahi-daemon, kirkwood snapshot, and D-Bus
Quick question: I just installed avahi-daemon on my dockstar running Attitude Adjustment r26175 (since dockstar is only available in a kirkwood snapshot): root@kong:~# opkg install avahi-daemon Installing avahi-daemon (0.6.30-1) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/avahi-daemon_0.6.30-1_kirkwood.ipk. Multiple packages (libpthread and libpthread) providing same name marked HOLD or PREFER. Using latest. Installing libavahi (0.6.30-1) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/libavahi_0.6.30-1_kirkwood.ipk. Installing libdaemon (0.14-2) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/libdaemon_0.14-2_kirkwood.ipk. Installing libgdbm (1.8.3-1) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/libgdbm_1.8.3-1_kirkwood.ipk. Installing libexpat (2.0.1-1) to root... Downloading http://downloads.openwrt.org/snapshots/trunk/kirkwood/packages/libexpat_2.0.1-1_kirkwood.ipk. Configuring libdaemon. Configuring libgdbm. Configuring libavahi. Configuring libexpat. Configuring avahi-daemon. root@kong:~# When I tried to run, root@kong:~# /etc/init.d/avahi-daemon start avahi-daemon: can't load library 'libdbus-1.so.3' root@kong:~# I am told I need the D-bus library. Reading the comments in https://dev.openwrt.org/browser/packages/libs/avahi/files/avahi-daemon.init, I would have guessed I did not need d-bus support since I did not get libavahi-client (and I thought that was the difference between libavahi and libavahi-dbus-support). Am I missing anything obvious here? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
