Hello Jeremy, >> I will send you a complete set of modules, madwifi.lrp and wireless.lrp >> with the latest HAL update from yesterday. > > > Yahoo!!!!! it works! (sort of). > THANK YOU, THANK YOU, THANK YOU!
:-) > Eric, after you sent me the newest packages and modules I loaded them on > my backup router. When I loaded the modules manually I no longer received > an error message when passing the autocreate option to the module so I > knew we were on the right track. The AP still didn't seem to work > correctly though. The mode was not being setup properly. Then I decided > to try this on my production router using all the same options. This one > works perfectly (so, there must be something odd about the old machine > hardware I have). I can scan, find and connect to my AP from my laptop. > Now the last hurdle I have > is to be able to get on the internet with it. For starters, I can't even > ping my AP. Here are the paticulars- > > Laptop- > > > IP 172.16.1.11 > Mask 255.255.0.0 > Gateway 172.16.1.10 > DNS 172.16.1.10 > > > -set to ESSID "test" with no WEP > -it finds AP in infrastructure mode (just as it should) > > ath0 IEEE 802.11g ESSID:"test" Mode:Master Frequency:2.412 GHz > Access Point: 00:13:46:6E:E5:DF > Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > The Signal level is low, but because you can just connect to the AP it's probably just the NIC not advertising the right value. About your real problem: You have defined 1 network 172.16.1.0/16 (172.16.1.0 (eth1 and ath0), 172.16.2.0 (eth2)) and are trying to route and create zones within the same subnet. This won't work and you are creating some sort of bridge setup like this. You have to define three seperate networks to make routing possible, so for example: eth1: 172.16.1.0/24 (255.255.255.0) eth2: 172.16.2.0/24 (255.255.255.0) ath0: 172.16.3.0/24 (255.255.255.0) Your setup would be something like this for example: auto eth1 iface ath1 inet static address 172.16.1.1 netmask 255.255.255.0 broadcast 172.16.1.255 auto eth2 iface ath2 inet static address 172.16.2.1 netmask 255.255.255.0 broadcast 172.16.2.255 auto ath0 iface ath0 inet static address 172.16.3.10 netmask 255.255.255.0 broadcast 172.16.3.255 madwifi-base wifi0 wireless-channel 1 wireless-essid test wireless-mode master And your laptop setup: IP 172.16.3.11 Mask 255.255.255.0 Gateway 172.16.3.10 DNS 172.16.3.10 > BTW, I notice wlan_scan_ap is unused. I guess this module is for running > wireless as a client not the AP, correct? > No, it's used for scanning and will be "used" in some cases. Eric ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
