[Voyage-linux] Re: Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3
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 lono 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
Re: [Voyage-linux] Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3
You need to define the bridge as part of the hostapd.conf ie: interface=ath0 bridge=br0 otherwise driver will not pass traffic through the bridge and initialization will fail. On Apr 11, 2009, at 8:04 PM, Punky Tse wrote: Hi Alex, Try change driver=wext. Regards, Punky Alex wrote: Hi, I'm having problem trying to start hostapt on an Alix.2d3 board with an Atheros wifi card (AR5213 chipset) I'm able to turn the wifi interface into managed mode and I can see the unsecure Access Point (canno't connect to it though). But when I try to start the hostapd I always get the following message: voyage:~# hostapd -dd -K -t /etc/hostapd/hostapd.conf Configuration file: /etc/hostapd/hostapd.conf ioctl(SIOCGIFINDEX): No such device madwifi driver initialization failed. 946687574.419793: ath0 : Unable to setup interface. 946687574.419854: Flushing old station entries 946687574.419875: Deauthenticate all stations my hostapd.conf is here -- interface=ath0 driver=madwifi ssid=Voyage hw_mode=g channel=1 logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=1 # Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps, 4 = excessive debug=4 # Dump file for state information (on SIGUSR1) dump_file=/tmp/hostapd.dump #macaddr_acl=0 #auth_algs=1 #ignore_broadcast_ssid=0 wpa=2 wpa_psk =57602025b05e9c5765f3d68c8949598473143f3ece66dd0f96ae4b4869b99bd4 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP CCMP --- my interfaces are here --- # 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 #auto eth0 #iface eth0 inet static # address 192.168.5.200 # netmask 255.255.255.0 # broadcast 192.168.5.255 # gateway 192.168.5.1 auto br0 iface br0 inet static address 192.168.5.200 netmask 255.255.255.0 broadcast 192.168.5.255 gateway 192.168.5.1 bridge_ports eth0 eth1 eth2 eth3 auto ath0 iface ath0 inet static pre-up wlanconfig ath0 destroy || true pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap post-down wlanconfig ath0 destroy address 192.18.4.1 netmask 255.255.255.0 broadcast 192.168.4.255 #network 192.168.4.0madwifi-base wifi0 madwifi-mode Master wireless-channel 2 wireless-essid Voyage wireless-txpower 18dBm #wireless-rate 54M up iwpriv ath0 mode 3 #up iwconfig ath0 channel 2 #up iwconfig ath0 essid Voyage #up iwconfig ath0 txpower 18 #up iwconfig ath0 rate auto -- I tried to compile the newest version of the hostapd (0.6.8) but it didn't help either. Some help would be appreciated ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] kernel 2.6.29
Hello, my name is Nacho, from Spain. I'm trying to get a voyage linux OS working on a ALIX routerboard with 802.11n WiFi radio cards installed. To reach it with ath9k madwifi driver, I've read that it is necessary having a 2.6.29 kernel running on the routerboard, and I wanted to ask you if anyone has already done it, and if somebody knows if it's intended to be reachable this kernel in repositories (the higher version I've found is 2.6.26). Thank's for all. I'm waiting for your answers. Best regards. -- Ignacio Foche Pérez Fundación Enlace Hispano Americano de Salud (EHAS) Responsable de Administración y Sistemas Tlfno: 914888422 Ext.96 Clave pública PGP: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x8185416E signature.asc Description: Digital signature ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kelly Hogan wrote: You need to define the bridge as part of the hostapd.conf ie: interface=ath0 bridge=br0 otherwise driver will not pass traffic through the bridge and initialization will fail. This should only matter if the wireless device is part of a bridge. - From the configs that he posted, it does not look like ath0 is part of a bridge (it has a different IP from the bridged interface). For this setting to work, you also need to add ath0 to your bridge br0. Ath0 at that point will not need it's own IP. Also, kismet is showing your AP as unsecured because hostap is not running. If hostap is not running, then kismet is not detecting encrypted frames. Here are my configs: ** note, I have two physical devices in my ALix, which is why the bridged device is ath1 ## /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 ath1 iface ath1 inet manual pre-up wlanconfig ath1 destroy || true # set up the ath1 device in AP mode before bringing up the interface (unless you're using AutoCreate) pre-up wlanconfig ath1 create wlandev wifi1 wlanmode ap # remove the ath1 device when bringing the interface down post-down wlanconfig ath1 destroy up iwconfig ath1 essid whytebread5 rate 54M channel 11 up ip link set ath1 up auto br0 iface br0 inet static # Assign your IP address, subnet and mask, broadcast address, and default gateway address 192.168.1.4 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.2 # Bridge eth0 and ath1 with br0. bridge_ports eth0 ath1 ##EOF## ## /etc/hostapd/hostapd.conf ## # based on howto at http://www.linux.com/articles/55617 interface=ath1 bridge=br0 driver=madwifi logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=2 debug=2 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=0 ssid=mySSID #macaddr_acl=1 #accept_mac_file=/etc/hostapd/accept auth_algs=3 eapol_key_index_workaround=0 eap_server=0 wpa=1 wpa_psk_file=/etc/hostapd/hostapd.wpa_psk wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP wpa_group_rekey=600 wpa_gmk_rekey=86400 ##EOF## The file /etc/hostapd/hostapd.wpa_psk just contains MAC addresses and keys (the PSK I get from running wpa_passphrase). A simpler option might be to use wpa_passphrase=someasciipassphrase in your hostapd.conf Also, when making changes to hostapd.conf, don't forget to restart it with /etc/init.d/hostapd restart Hth, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkniN6wACgkQwRXgH3rKGfNUPgCdGvViHbRsaWITxF/A9LFzDrE1 ztgAn0rw9rJCR36mFHXWTgtaMmSdpm6o =nZ11 -END PGP SIGNATURE- ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] HOWTO: How do I make an image that I can write to a CF card?
On Sun, 08 Mar 2009 16:54:10 -0700, Sean kn...@toaster.net said: Hello Voyagers, Lots of people on this list have asked how they can make an image of their CF card. I have been trying to figure out how to do this, and I finally made a breakthrough. Here are some easy instructions on how to make an image of your CF card. This is handy for your field techs that only have Windows. :D http://wiki.voyage.hk/dokuwiki/doku.php?id=how_do_i_make_an_image_that_i_can_write_to_a_cf_card This post is over a month old, but responding anyway. The following blog post describes a different way to do this. This guy has figured out how to install Grub to a disk image file so this method doesn't require a physical device at all. http://www.wand.net.nz/~smr26/wordpress/2008/08/28/kvm-the-hard-way/ --- Andrew Malcolmson ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
