Gustin Johnson <gus...@...> writes:
> Has the ath0 device been created?
>
> run iwconfig with no arguments. If you do not see ath0 then the device
> is not being created properly.
>
> I also have my athX device as part of a bridge, which I needed to
> specify in the hostapd.conf.
>
> > wpa_pairwise=TKIP CCMP
>
> Unless you are absolutely sure you need it, there is no reason to use
> TKIP. This has nothing to do with your problem, just a security tip.
>
I already tried to reply twice but my replies are gone. Something wrong with
this forum. So I try to reply to myself
here is my iwconfig
--------------------------------------
voyage:~# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
eth2 no wireless extensions.
wifi0 no wireless extensions.
br0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"Voyage" Nickname:""
Mode:Master Frequency:2.417 GHz Access Point: 06:09:5B:D1:35:5C
Bit Rate:0 kb/s Tx-Power:20 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70 Signal level=-96 dBm Noise level=-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
----------------------------------------
and here is a part of my ifconfig
---------------------------------------
voyage:~# ifconfig
ath0 Link encap:Ethernet HWaddr 06:09:5b:d1:35:5c
inet addr:192.18.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
inet6 addr: fe80::409:5bff:fed1:355c/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
br0 Link encap:Ethernet HWaddr 00:0d:b9:16:65:a8
inet addr:192.168.5.200 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::20d:b9ff:fe16:65a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:484 errors:0 dropped:0 overruns:0 frame:0
TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39404 (38.4 KiB) TX bytes:53787 (52.5 KiB)
wifi0 Link encap:UNSPEC HWaddr
00-09-99-99-99-99-99-99-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:3
TX packets:10 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:280
RX bytes:184 (184.0 B) TX bytes:1320 (1.2 KiB)
Interrupt:9
-----------------------------------------
I removed TKIP as was suggested but still cannot start hostapd. Neither can I
connect to the AP wrom a Windows host. Windows shows my AP and it says it is
WPA2 but it cannot connect.
Strange but if I start a kismet on a linux host it shows my AP as non secure.
ps using wext as driver in hostapd.conf doesn't help (it says no such driver)
psps bridging lan and wlan interfaces doesn't help either
_______________________________________________
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux
