[OpenWrt-Devel] [PATCH] strongswan4 update to 4.5.1

2011-04-13 Thread Lars Hjersted
This patch updates the strongswan4 package from 4.3.7 to 4.5.1. I have added the following plugins which get built as strongswan4-mod- packages: constraints - X.509 constraint checking dhcp - DHCP-based IP and DNS farp - Fake arp responses led - LED blink on IKE activity revocation - X.509 revoc

[OpenWrt-Devel] Bob Green(e?): We Ain't Metric And They Ain't Either

2011-04-13 Thread Larry Vaden
In the 60s IIRC, Chicago newspaper columnist Bob Green(e?) visited Europe for the first time and wrote a column entitled "We Ain't Metric and They AIn't Either" based on his reputed findings that European tires were measured in inches, just like American tires. So, I'd like to ask "Why are the ETS

[OpenWrt-Devel] [PATCH] x86: missing kernel symbols

2011-04-13 Thread Philip Prindeville
Please include these two missing kernel CONFIG_ symbols. Index: target/linux/x86/config-default === --- target/linux/x86/config-default (revision 26655) +++ target/linux/x86/config-default (working copy) @@ -382,6 +382,7 @@ C

Re: [OpenWrt-Devel] signal: -109 dBm signal avg: -107 dBm, latencies circa 400 msec

2011-04-13 Thread Larry Vaden
Please excuse a pig; a hog knows better :) The report of 400 msec latency was due to another problem. It is noted that the latency is typically under 2 msec for most of the houses in this neighborhood. Thus the report of unusual signal strengths stands, just the subject line was (WRONG|TOO LONG

[OpenWrt-Devel] signal: -109 dBm signal avg: -107 dBm, latencies circa 400 msec

2011-04-13 Thread Larry Vaden
Is the Bullet M2 HP data sheet this wrong? It seems one interpretation is that the Bullet M2 HP has far greater sensitivity than the published data sheets, which is somewhat hard to believe. For a moment, I thought I had incorrectly logged into our troublesome M900 :) r26651 on a Bullet M2 HP wi

[OpenWrt-Devel] Requirement from 2 miles E of middle of nowhere: DMADBG_7=0x000084c0 should not live, it raises my blood pressure

2011-04-13 Thread Larry Vaden
On Wed, Apr 13, 2011 at 5:34 PM, Philip Prindeville wrote: > > There's such an etiquette?  If there is, it would seem to be misguided. > > There are always going to be more users than developers (if it was easy, > everyone would be doing it, right?). > > Users are well placed to say what they nee

Re: [OpenWrt-Devel] [OpenWrt-Commits] r26654 - packages/utils/hdparm

2011-04-13 Thread Philip Prindeville
I actually think the older description was a lot more informative. The -f, -t, -T, and -z flags don't get or set parameters, for example... and these are amongst the handiest arguments to the command. On 4/13/11 4:20 PM, openwrt-comm...@openwrt.org wrote: > Author: luka > Date: 2011-04-14 00:20

Re: [OpenWrt-Devel] [PATCH] /etc/config/wireless - 'powersave' setting optional

2011-04-13 Thread Philip Prindeville
On 4/13/11 3:10 PM, Larry Vaden wrote: > On Wed, Apr 13, 2011 at 2:59 PM, Felix Fietkau wrote: >> On 2011-04-12 2:18 PM, Jan Čapek wrote: >>> >>> - this configuration option seems to be undocumented. Unfortunately, >>> it tries to disable powersaving by default for all mac80211 based >>> wifi

Re: [OpenWrt-Devel] [PATCH] /etc/config/wireless - 'powersave' setting optional

2011-04-13 Thread Larry Vaden
On Wed, Apr 13, 2011 at 2:59 PM, Felix Fietkau wrote: > On 2011-04-12 2:18 PM, Jan Čapek wrote: >> >> - this configuration option seems to be undocumented. Unfortunately, >>   it tries to disable powersaving by default for all mac80211 based >>   wifi interfaces that use 'sta' mode. Some drivers (

Re: [OpenWrt-Devel] [PATCH] /etc/config/wireless - 'powersave' setting optional

2011-04-13 Thread Felix Fietkau
On 2011-04-12 2:18 PM, Jan Čapek wrote: - this configuration option seems to be undocumented. Unfortunately, it tries to disable powersaving by default for all mac80211 based wifi interfaces that use 'sta' mode. Some drivers (e.g. ath5k) don't support setting/enabling powersaving mode. T

Re: [OpenWrt-Devel] Retaining WAN IP addresses across reboots

2011-04-13 Thread Philip Prindeville
I was thinking about this some more... if we simply took the leased IP address and stuffed it up into: config 'wan' option ipaddr x.x.x.x in network, the /lib/network/config.sh script would then try to request that address the next time the box rebooted. If the address was in use, the

Re: [OpenWrt-Devel] Retaining WAN IP addresses across reboots

2011-04-13 Thread Philip Prindeville
On 4/13/11 1:16 PM, edgar.sol...@web.de wrote: > On 13.04.2011 19:18, Philip Prindeville wrote: >> All of the platforms I have use a CMOS NVRAM with RTC built-in. >> >> > > do they have names? ;) > > ..ede Alix, net5501, Geos... and a couple of others that haven't yet been publicly announced.

Re: [OpenWrt-Devel] Retaining WAN IP addresses across reboots

2011-04-13 Thread edgar . soldin
On 13.04.2011 19:18, Philip Prindeville wrote: > All of the platforms I have use a CMOS NVRAM with RTC built-in. > > do they have names? ;) ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo

Re: [OpenWrt-Devel] Retaining WAN IP addresses across reboots

2011-04-13 Thread Philip Prindeville
All of the platforms I have use a CMOS NVRAM with RTC built-in. On 4/12/11 5:02 PM, Nuno Gonçalves wrote: > Please also note that the real time clock is important for knowing if > the DHCP lease is still valid. > Since most routers don't have a hardware RTC, there is no way to know > it the DHCP

[OpenWrt-Devel] Not able to see all the symbols in the output of "nm" command

2011-04-13 Thread Madhavi Manchala
Dear All, I build the OpenWRT image for my target device. I am able to see the "vmlinux" image in trunk/build_dir/linux-s3c2510/linux-2.6.36 directory where linux-s3c2510 indicates my target device. I am NOT able to see some of the function names (symbols), which I developed, in the output of the

Re: [OpenWrt-Devel] Retaining WAN IP addresses across reboots

2011-04-13 Thread Bastian Bittorf
> Please also note that the real time clock is important for knowing > if > the DHCP lease is still valid. > Since most routers don't have a hardware RTC, there is no way to > know > it the DHCP lease is still valid before you get WAN connectivity to > update the time with NTP. in our special open

Re: [OpenWrt-Devel] [PATCH] base-files: Make bridge MAC address sticky

2011-04-13 Thread Helmut Schaa
Am Dienstag, 12. April 2011 schrieb Jo-Philipp Wich: > is this patch still applicable after > https://dev.openwrt.org/changeset/26426 ? Haven't tested but I think it's still needed. Setting a fixed MAC address for a bridge interface will force the kernel to make it sticky. Even with changeset 2