[Voyage-linux] ath5k
Artie Gold
(spam-protected)
Tue Sep 27 03:15:17 HKT 2011
When you went to restart the network you used the wrong command. You wanted:
/etc/init.d/networking restart
That explains both the errors you saw and the fact that nothing had changed.
Cheers,
--ag
2011/9/26 Laili Aidi <aidi at kth.se>
> Sorry, the essid is as below:
> *root at voyage:~# **vi /etc/network/interfaces*
> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> # /usr/share/doc/ifupdown/examples for more information.
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet dhcp
>
> # mac80211-based drivers
> #auto wlan0
> iface wlan0 inet static
> address 192.168.6.1
> netmask 255.255.255.0
> broadcast 192.168.6.255
> up iwconfig wlan0 essid *Voyage4* mode Master
>
> On 26 sep 2011, at 20.39, Laili Aidi wrote:
>
> Hej,
>
> Not sure if have to start new thread, but I also have trouble set up AP
> with master mode in Voyage 0.7.5. I've configured one in Voyage 0.7.0
> following what's in README file and it's running well, but when I try with
> Voyage 0.7.5 with the same procedure, I can't see my AP running. I still
> can't find any idea what's missing or something wrong. This is the procedure
> and configuration that I've done.
> *root at voyage:~# **vi /etc/network/interfaces*
> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> # /usr/share/doc/ifupdown/examples for more information.
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet dhcp
>
> # mac80211-based drivers
> #auto wlan0
> iface wlan0 inet static
> address 192.168.6.1
> netmask 255.255.255.0
> broadcast 192.168.6.255
> up iwconfig wlan0 essid Bytewalla-Voyage4 mode Master
>
>
> *root at voyage:~#**vi /etc/default/hostapd*
> UN_DAEMON="yes"
>
> *root at voyage:~#**vi /etc/hostapd/hostapd.conf*
> interface=wlan0
> driver=nl80211
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> debug=4
> dump_file=/tmp/hostapd.dump
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> channel=6
> macaddr_acl=0
> auth_algs=3
> eapol_key_index_workaround=0
> eap_server=0
> wpa=3
> ssid=Voyage4
> wpa_passphrase=Voyage4
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP
> eapol_version=1
>
> *root at voyage:~#**vi /etc/dnsmasq.more.conf***
> dhcp-range=wlan0,192.168.6.35,192.168.6.50,24h
> dhcp-leasefile=/var/tmp/dnsmasq.leases
>
> ***root at voyage:~#**/etc/init.d/hostapd restart*
> *root at voyage:~#**/etc/init.d/dnsmasq restart*
> root at voyage:/etc/hostapd# /etc/init.d/dnsmasq restart
> Restarting DNS forwarder and DHCP server: dnsmasq.
> **
> But When I do /etc/network/interfaces restart, it shows this error:
> *root at voyage:~#**/etc/network/interfaces restart*
> root at voyage:/etc/hostapd# /etc/network/interfaces restart
> /etc/network/interfaces: line 3: auto: command not found
> /etc/network/interfaces: line 4: iface: command not found
> /etc/network/interfaces: line 6: auto: command not found
> /etc/network/interfaces: line 7: iface: command not found
> /etc/network/interfaces: line 28: iface: command not found
> /etc/network/interfaces: line 29: address: command not found
> /etc/network/interfaces: line 30: netmask: command not found
> /etc/network/interfaces: line 31: broadcast: command not found
> /etc/network/interfaces: line 32: up: command not found
>
> and in iwconfig, it still say may wlan0 is in "Managed" mode, even I have
> configured it as "Master"
> *root at voyage:~# iwconfig*
> lo no wireless extensions.
> eth0 no wireless extensions.
> eth1 no wireless extensions.
> eth2 no wireless extensions.
> wlan0 IEEE 802.11abg ESSID:"Voyage4"
> *Mode:Managed* Access Point: Not-Associated Tx-Power=20 dBm
>
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
>
> I would helpful for any clue about this.
>
> Aidi
>
> On 26 sep 2011, at 03.27, Kim-man 'Punky' TSE wrote:
>
> Hi ag,
>
> What does it break? I used it everyday and my customer were using it
> without problems.
>
> On 9/26/2011 4:48 AM, Artie Gold wrote:
>
> The ath5k driver works pretty well for an access point on voyage 7.0
> (2.6.32 kernel), with a couple of known bugs that don't seem to cause much
> trouble in terms of functionality. In voyage 7.5 (2.6.38) it appears to be
> significantly broken.
>
>
> Is there a sweet spot somewhere in between? (a better kernel/module
> combination) ...
>
>
> Thanks!
>
> --ag
>
>
> Sent from my iPhone
>
>
> _______________________________________________
>
> Voyage-linux mailing list
>
> Voyage-linux at list.voyage.hk
>
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
>
>
> --
> Regards,
> Kim-man "Punky" Tse
>
> * Open Source Embedded Solutions and Systems
> - Voyage Linux (http://linux.voyage.hk)
> - Voyage ONE (http://linux.voyage.hk/voyage-one)
> - Voyage MPD (http://linux.voyage.hk/voyage-mpd)
> * Voyage Store (http://store.voyage.hk)
>
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
>
--
Artie Gold
Principal Software Engineer
Under Assistant West Coast Promo Man
F4W, Inc.
===================================================
Elegance is not a dispensable luxury but a factor that decides between
success and failure.
--Edsger Dijkstra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20110926/9afb92af/attachment.html>
More information about the Voyage-linux
mailing list