Hi!<br><br>thanks for your response! :)<br><br><b>follow the lspci -v</b>:<br>00:0c.0 Network controller: Atheros Communications Inc. Device 0029 (rev 01)<br> Subsystem: Atheros Communications Inc. Device 2091<br> Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 9<br>
Memory at e00c0000 (32-bit, non-prefetchable) [size=64K]<br> Capabilities: [44] Power Management version 2<br> Kernel driver in use: ath9k<br> Kernel modules: ath9k<br><br>I'm using the daily build of Voyage. With new kernel which supports ath9k.<br>
<br><br><b>in /etc/network/interfaces I have:</b><br>auto wlan0<br>iface wlan0 inet static<br> address 10.1.10.1<br> netmask 255.255.255.0<br> broadcast 10.1.10.255<br> up iwconfig wlan0 essid "voyage"<br>
up nat.sh wlan0 eth0 "<a href="http://10.1.10.0/24">10.1.10.0/24</a>"<br><br><br><b>and if I write "ifup wlan0" returns:</b><br>voyage:~# ifup wlan0<br>if-up.d/mountnfs[wlan0]: waiting for interface ath0 before doing NFS mounts (warning)<br>
<br>I need start ath0 too?<br><br><b>because if I try to up ath0, returns:</b><br>voyage:~# ifup ath0<br>SIOCSIFADDR: No such device<br>ath0: ERROR while getting interface flags: No such device<br>SIOCSIFNETMASK: No such device<br>
SIOCSIFBRDADDR: No such device<br>ath0: ERROR while getting interface flags: No such device<br>ath0: ERROR while getting interface flags: No such device<br>Failed to bring up ath0.<br><br><br>wlan0 interface seams to up.. has IP address.. but not appears in list of wireless networks in other devices... <br>
<br><b>follow the ifconfig:</b><br>wlan0 Link encap:Ethernet HWaddr 00:0c:42:51:b1:b4 <br> inet addr:10.1.10.1 Bcast:10.1.10.255 Mask:255.255.255.0<br> UP BROADCAST MULTICAST MTU:1500 Metric:1<br>
RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000 <br> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)<br>
<br>wmaster0 Link encap:UNSPEC HWaddr 00-0C-42-51-B1-B4-65-74-00-00-00-00-00-00-00-00 <br> UP RUNNING MTU:0 Metric:1<br> RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:1000 <br> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)<br><br><br><br>Thanks!<br><br><br><br><div class="gmail_quote">On Sun, Oct 18, 2009 at 11:24 PM, Kim-man 'Punky' TSE <span dir="ltr"><<a href="mailto:punkytse@punknix.com">punkytse@punknix.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Daniel,<br>
<br>
Perhap I read too fast. You should be using ath9k instead of ath5k. Show us the lspci -v output to confirm.<br>
<br>
you should use:<br>
"iwconfig wlan0 mode master" instead of "ap"<br>
<br>
Regards,<br>
Punky<div class="im"><br>
<br>
Punky wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Daniel,<br>
<br>
If you are using ath5k, then I would say ath5k driver does not support<br>
AP mode.<br>
<br>
See <a href="http://www.punknix.com/building-compat-wireless-drivers-for-2.6.30" target="_blank">http://www.punknix.com/building-compat-wireless-drivers-for-2.6.30</a><br>
<br>
Regards,<br>
Punky<br>
<br>
<br>
</blockquote>
<br>
<br></div>
-- <br>
Regards,<br><font color="#888888">
Punky</font><div><div></div><div class="h5"><br>
<br>
Voyage Solutions (<a href="http://solution.voyage.hk" target="_blank">http://solution.voyage.hk</a>)<br>
* Embedded Solutions and Systems<br>
- Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX<br>
- Network Engineering, Development Platform and Consultation<br>
<br>
<br>
</div></div></blockquote></div><br>