Philip A. Prindeville wrote: > Actually, wpa_supplicant is half-baked. I never got it running > completely, and since most people use it as an AP and not a client, it > got neglected. If you can debug the config, I'll update the scripts. >
Well, as wpa_supplicant is used for wpa/wpa2 authentification it runs on every linux box that uses wpa/wpa2 (as far as I know). All my Debian systems run wpa_supplicant per default. So, I guess, there are much much more wpa_supplicant clients than AP hosts running in the world. So far, wpa_supplicant is working fine here, except in this special case where the interface is a bridge. The problem has been described on the internet, but nobody seems to care, as I guess this is a very rare scenario, that someone wants to bridge WLAN and not use it as an AP. Here is a description of the problem: http://fixunix.com/networking/528617-bridge-wlan0-interface-using-wpa.html I get the same error messages. Of course, it would be nice to get that fixed. But that won't be easy, I am afraid. And I am missing the necessary Know-How to dig deeper into the error messages. :-( Btw. wpa_supplicant it not a shell script but a binary program. Debugging and fixing won't be easy, thus. > Also, don't use "route add"... that might be going away. > > Use "ip route add" instead. > O.K. thanks, I'll do that. :-) Cheers, Michael > > On 07/14/2010 02:30 AM, Michael wrote: >> Hello >> >> Just a short question: Where would I add static routes into astlinux? >> >> In my LAN I have another (small) router with a subnet. Actually, it is a >> linux box that simply connects another room via WLAN with the astlinux >> main router. >> >> I would liked to have used bridging instead of nat for the small router >> but there seems to be a bug in wpa_supplicant that does not allow it to >> work properly on a bridge. >> >> So I need to define a static route into the astlinux router, something >> like: >> >> So, if my main LAN is 192.168.0.0/25 and the subnet is 192.168.0.128/29 >> then I would need to add a route like this >> >> route add -net 192.168.0.128 netmask 255.255.255.248 gw 192.168.0.129 dev >> br1 >> >> Hmm, I guess I also need to adapt the firewall as it will only forward >> data from EXTIF to INTIF for the main net... (?!) >> >> Or is there a simple way to do it which also adapts the firewall >> accordingly? >> >> Thanks >> >> Michael >> ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
