Re: [OpenWrt-Devel] About WDS

2008-08-05 Thread Felix Fietkau
[EMAIL PROTECTED] wrote: Hi, as far as I've understood there have been changes in the wds area. Which is the proper way to setup wds now? For example how should I translate the following config: If you're talking about madwifi, then simply put up an AP on the side that talks to multiple WDS

Re: [OpenWrt-Devel] Etrax support

2008-08-05 Thread Claudio
HI 2008/8/4, Claudio [EMAIL PROTECTED]: 2008/8/4, Hinko Kocevar [EMAIL PROTECTED]: MichelinoK wrote: Hinko Kocevar [EMAIL PROTECTED] ha scritto nel messaggio news:[EMAIL PROTECTED] MichelinoK wrote: Is there a way to have a more verbose boot (to see where it hangs) ? Run sysinit scripts

[OpenWrt-Devel] [Patch] SLUB allocator

2008-08-05 Thread Dirk Nehring
Hi, the SLUB allocator is included in the official kernel since 2.6.22, smaller footprint, better performance and the standard allocator in make defconfig. We should safely switch to this one. Dirk Index: target/linux/generic-2.6/config-2.6.26

Re: [OpenWrt-Devel] About WDS

2008-08-05 Thread Alberto Botti
Il giorno mar, 05/08/2008 alle 09.19 +0200, Felix Fietkau ha scritto: If you're talking about madwifi, then simply put up an AP on the side that talks to multiple WDS peers. On the other side, simply add a regular sta interface. Make sure that you grab the latest trunk (some more fixes just

Re: [OpenWrt-Devel] [PATCH] Allow use of parameters for modules in function autoload

2008-08-05 Thread Frédéric Moulins
It allows to configure kernel modules parameters from uci config files. Interesting. But is it really good to have a separate config file for each module? This can lead to collisions (if a module has the same name as a different config file); also, a set of config files without any

Re: [OpenWrt-Devel] About WDS

2008-08-05 Thread Felix Fietkau
Alberto Botti wrote: Il giorno mar, 05/08/2008 alle 09.19 +0200, Felix Fietkau ha scritto: If you're talking about madwifi, then simply put up an AP on the side that talks to multiple WDS peers. On the other side, simply add a regular sta interface. Make sure that you grab the latest trunk

Re: [OpenWrt-Devel] About WDS

2008-08-05 Thread Alberto Botti
Il giorno mar, 05/08/2008 alle 15.52 +0200, Felix Fietkau ha scritto: It doesn't work between Broadcom and Atheros yet. But if you use only Atheros devices, then WPA-PSK will work. I've tested both WPA and WPA2. Thanks. Is it a specific limitation of the Broadcom hardware (or its crappy binary

[OpenWrt-Devel] [PATCH] Control ssid in madwifi configuration

2008-08-05 Thread Frédéric Moulins
In client mode, this avoid to associate to an AP with different ssid. Signed-off-by: Frédéric Moulins [EMAIL PROTECTED] diff --git a/package/madwifi/files/lib/wifi/madwifi.sh b/package/madwifi/files/lib/wifi/madwifi.sh index 9d08e1f..e996a2c 100755 ---

Re: [OpenWrt-Devel] About WDS

2008-08-05 Thread Felix Fietkau
Alberto Botti wrote: Il giorno mar, 05/08/2008 alle 15.52 +0200, Felix Fietkau ha scritto: It doesn't work between Broadcom and Atheros yet. But if you use only Atheros devices, then WPA-PSK will work. I've tested both WPA and WPA2. Thanks. Is it a specific limitation of the Broadcom

[OpenWrt-Devel] [PATCH] madwifi wpa_supplicant eap calls

2008-08-05 Thread Frédéric Moulins
This patch adds wpa_supplicant calls for EAP TLS, TTLS, PEAP to madwifi configuration script. Defined options correspond to wpa_supplicant options : Common options : * eap * identity * ca_cert * pairwise * group TLS specific options : * client_cert * private_key * private_key_passwd TTLS and

Re: [OpenWrt-Devel] About WDS

2008-08-05 Thread Alberto Botti
Il giorno mar, 05/08/2008 alle 18.47 +0200, Felix Fietkau ha scritto: The WDS thing is fixable in madwifi. I will eventually add compatibility for Broadcom WDS when I find the time. Thanks a lot. Remember me to buy you a beer (or mail you a spare router, the beer might get warm while shipping

[OpenWrt-Devel] Linking problem while building package

2008-08-05 Thread Roberto Riggio
Hi, I'm trying to build mgen (http://cs.itd.nrl.navy.mil/work/mgen/) for kamikaze. Hoever after launching the build I get the following errors: make[5]: Leaving directory `/home/wing/wing-bot-r12098/kamikaze-wrap/build_dir/i386/mgen-4.2b6/protolib/unix' i386-linux-uclibc-gcc -g -g

[OpenWrt-Devel] kernel panic on p54pci insertion on mipsel

2008-08-05 Thread Tomasz Chmielewski
I have a mipsel device (ASUS WL-500gP; it runs a 2.6.25.9 OpenWRT kernel) with a prism54 mini-pci card: 00:02.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01) Subsystem: Intersil Corporation Unknown device

Re: [OpenWrt-Devel] Etrax support

2008-08-05 Thread MichelinoK
I've just downloaded the latest svn trunk...and etrax target cannot be compiled anymore... Can someone test? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] R: Re: Linking problem while building package

2008-08-05 Thread Roberto Riggio
- Karthik Venkateswaran [EMAIL PROTECTED] ha scritto: A simple solution is to use $(CXX) instead of $(CC) in MGEN source Makefile. Sorry for the very simple question, but how do I tell kamikaze to use g++ in the package Makefile. The mgen makefile already spacifies g++ but it is ignored