Update: lsmod on my box shows the following:
[snip] wlan_xauth 2160 (unused) wlan_tkip 83680 (unused) wlan_ccmp 45640 (unused) wlan_acl 15280 (unused) ath_pci 61504 1 ath_rate_sample 7540 1 wlan_scan_sta 7408 1 wlan_scan_ap 19640 (unused) wlan 1355561 [wlan_xauth wlan_tkip wlan_ccmp wlan_acl ath_pci ath_rate_sample wlan_scan_sta wlan_scan_ap] ath_hal 1744801 [ath_pci ath_rate_sample] [snip] I notice that there are several unused modules in the list. These were included in the documentation for creating an AP, so probably they are not needed in a wireless client setup. I am surprised to see that wlan_scan_ap.ko is unused. No doubt, the iwlist utility included in the wireless.lrp package does not need this module... Also, a correction to my configuration instructions in point 7 where I mention that you may require dsnmasq.lrp if you want to get an IP address via DHCP. This is incorrect. dnsmasq is a DNS caching and DHCP server daemon. You don't need this for a DHCP client. You probably want dhcpcd.lrp (client daemon). regards, Werner On Sat, 2011-07-09 at 15:00 +0200, Erich Titl wrote: > Werner, > > on 09.07.2011 10:10, Werner van Staden wrote: > > Erich, > > > > Not sure this is the scenario you are talking about: > > > > I set up my LEAF firewall as a client in a wireless network which > > extends across my neighbourhood. Installed wireless.lrp and loaded the > > following modules for the Atheros radio & client state: > > Sounds like the thing I have in mind > > > > > ath_hal > > wlan > > wlan_scan_ap > > wlan_scan_sta > > ath_rate_sample > > ath_pci > > wlan_acl > > wlan_ccmp > > wlan_tkip > > wlan_xauth > > What packages did you install? > > > > > The LEAF box is therefore both a wifi client and a firewall to my > > private LAN. However, because the community wireless network has a Class > > C address space (192.168.2.0/24) there are issues when my private > > network hosts (192.168.0.0/24) try to make encrypted connections to > > remote hosts. This is no-doubt a private address routing issue... > > If you are talking IPSEC it is a nat traversal issue > > > > > Overall, internet browsing, mail and day-to-day connectivity is stable > > and perfectly usable. > > Fine, would you mind to share your settings? How about usability? I am > looking to use this as a gateway which changes uplink WLAN providers > often (on my boat :-) > > I have been able to look at the Buffalo product, it has quite a nice > user interface with a few things lacking. As it is built on top of > DD-WRT we should be able to provide something similar but more flexible. > > Thanks > > Erich > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > ------------------------------------------------------------------------ > leaf-user mailing list: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- > http://leaf-project.org/ ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
