Jump to content

digitaladdictions

Members
  • Posts

    4
  • Joined

  • Last visited

  • Days Won

    1

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

digitaladdictions's Achievements

Newbie

Newbie (1/14)

  1. Im not 100% sure power draw is the only problem. I took it out in the field today and no mater what power settings I had it at it would disassociate after 10-15min. It seemed like when I started up something that would be a bit more CPU intensive like part of the dsniff suite it would happen quicker. Although the CPU load itself was still only 0.40 to 0.50. Sometimes it even kicked me of the karma side when it happened and required a reboot. If it is purely power related I think the device itself is close to the max power the USB can provide before you even take into consideration transmit power. I do not have a powered hub available at the moment but that will be the next thing I try. Yesterday was the first day I ever looked at OpenWRT so what I posted may not be optimal. I already tweaked that config in that I removed option network wan and I added option bssid 00:01:02:03:04:05 There where two identical SSID's for two different networks and despite the desired one being 10dBm stronger 9 times out of 10 it would connect to the wrong one without that or worse change to the wrong on its own after being all setup properly. I then added this to the startup script udhcpc -i wlan1 -b iptables -A FORWARD -i wlan0 -o wlan1 -s 172.16.42.0/24 -m state --state NEW -j ACCEPT iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A POSTROUTING -t nat -j MASQUERADE Again yesterday was the first time I ever looked at OpenWRT so take my configs with a grain of salt.
  2. It looks like you where right. I did not think you where to be honest since I was plugged into the wall and the adapter in question is designed to be powered from USB but you where. I also upgraded to the latest firmware and added the country code to the configuration which seemed to help a bit by itself but it still would disconnect in 1-2min on its own and immediately when I tried to get a DHCP lease. After dropping the power down to 5 dBm (just went real low to test) it has stayed up for about 10min so far and I was able to request a DHCP lease and do several pings. I still need to slowly bring that value up and see where it starts to have problems. The driver default was 20 dBm. The pineapples built in adapter is running at 18 dBm. Thanks === UPDATE === 18 dBm seems to be reliable so far. It just was having trouble with the default 20 dBm. === UPDATE === I spoke to soon at 18 dBm it disassociated after about 30min. I tried 16 and it immediately disconnected with the DHCP request. I am now at 14 dBm. I will see how this goes.
  3. Just received my Pineapple Mk4 yesterday. My first experiment was the "typical" setup where I had it hardwired to my laptop (well actually a VM) that was acting as a router. Other than having some problems with Ubuntu's network-manager insisting overwriting my default gateway with the ip of the pineapple every few minutes (I eventually removed network manager and set the networking up manually) everything worked well. Still this all seems rather pointless if your using a laptop since you can almost just as easily do all this without any additional hardware that needs to be powered. I really want to make this stand alone with a spare ALFA USB WiFi AWUS036NHA I bought at the same time but am having problems. I am a Linux admin and Linux is not a problem for me but I am completely new to OpenWRT and busybox. I can get the Alfa to connect briefly but it immediately disconnects. I believe the problem is with the network interface I am using. I think I need to define a new physical interface in /etc/config/network but I am not sure what that would be. config wifi-device radio0 option type mac80211 option channel 11 option macaddr 00:c0:ca:60:ef:62 option hwmode 11ng option htmode HT20 list ht_capab SHORT-GI-20 list ht_capab SHORT-GI-40 list ht_capab RX-STBC1 list ht_capab DSSS_CCK-40 # REMOVE THIS LINE TO ENABLE WIFI: # option disabled 1 config wifi-iface option device radio0 option network lan option mode ap option ssid "pineapple" option encryption none config wifi-device radio1 option type mac80211 option channel 1 option macaddr 00:c0:ca:57:24:b5 option hwmode 11ng option htmode HT20 list ht_capab SHORT-GI-20 list ht_capab SHORT-GI-40 list ht_capab RX-STBC1 list ht_capab DSSS_CCK-40 # REMOVE THIS LINE TO ENABLE WIFI: # option disabled 1 config wifi-iface option device radio1 option network wan option mode sta option ssid MyNetwork option encryption psk2+tkip+aes option key *********** Followed by: wifi ifup wan At this point it will connect and associate with my wireless network but within a few seconds disconnect. Here are the last several lines of my system log. 00:01:08 Pineapple kern.debug kernel: [ 68.940000] wlan1: deauthenticating from 00:1d:7e:38:ca:2b by local choice (reason=3) 00:01:08 Pineapple kern.debug kernel: [ 68.730000] wlan1: associated 00:01:08 Pineapple kern.debug kernel: [ 68.730000] wlan1: associate with 00:1d:7e:38:ca:2b (try 1/3) 00:01:08 Pineapple kern.debug kernel: [ 68.730000] wlan1: RX AssocResp from 00:1d:7e:38:ca:2b (capab=0x431 status=0 aid=6) 00:01:08 Pineapple kern.debug kernel: [ 68.670000] wlan1: send auth to 00:1d:7e:38:ca:2b (try 1/3) 00:01:08 Pineapple kern.debug kernel: [ 68.670000] wlan1: authenticated 00:01:08 Pineapple kern.debug kernel: [ 68.580000] wlan1: authenticate with 00:1d:7e:38:ca:2b 00:01:06 Pineapple kern.info kernel: [ 66.230000] ieee80211 phy3: Atheros AR9271 Rev:1 00:01:06 Pineapple kern.info kernel: [ 66.230000] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3 00:01:06 Pineapple kern.info kernel: [ 66.040000] br-lan: port 2(eth0) entering forwarding state 00:01:06 Pineapple kern.info kernel: [ 66.030000] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits 00:01:06 Pineapple kern.debug kernel: [ 66.240000] Registered led device: ath9k_htc-phy3 00:01:06 Pineapple kern.debug kernel: [ 66.230000] ath: doing EEPROM country->regdmn map search 00:01:06 Pineapple kern.debug kernel: [ 66.230000] ath: country maps to regdmn code: 0x37 00:01:06 Pineapple kern.debug kernel: [ 66.230000] ath: Regpair used: 0x37 00:01:06 Pineapple kern.debug kernel: [ 66.230000] ath: EEPROM regdomain: 0x833a 00:01:06 Pineapple kern.debug kernel: [ 66.230000] ath: EEPROM indicates we should expect a country code 00:01:06 Pineapple kern.debug kernel: [ 66.230000] ath: Country alpha2 being used: GB 00:01:05 Pineapple user.notice usb-modeswitch: 1-1:1.0: Manufacturer=ATHEROS Product=UB91C Serial=12345 00:01:05 Pineapple kern.info kernel: [ 65.790000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272 00:01:05 Pineapple kern.info kernel: [ 65.400000] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested 00:01:00 Pineapple kern.info kernel: [ 60.220000] usb 1-1: new high-speed USB device number 4 using ath79-ehci 00:00:59 Pineapple user.info sysinit: sh: write error: Invalid argument 00:00:59 Pineapple user.info sysinit: sh: write error: Invalid argument 00:00:59 Pineapple user.info sysinit: setting up led WLAN 00:00:59 Pineapple user.info sysinit: setting up led WAN 00:00:59 Pineapple user.info sysinit: setting up led USB 00:00:59 Pineapple user.info sysinit: setting up led LAN 00:00:59 Pineapple user.info sysinit: OK 00:00:59 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:wan/mode: nonexistent directory 00:00:59 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:wan/device_name: nonexistent directory 00:00:59 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:lan/mode: nonexistent directory 00:00:59 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:lan/device_name: nonexistent directory 00:00:59 Pineapple kern.info kernel: [ 59.940000] usb 1-1: ath9k_htc: USB layer deinitialized 00:00:59 Pineapple kern.info kernel: [ 59.870000] usb 1-1: USB disconnect, device number 3 00:00:59 Pineapple kern.err kernel: [ 59.910000] ath: Failed to wakeup in 500us 00:00:59 Pineapple kern.err kernel: [ 59.900000] ath: Failed to wakeup in 500us 00:00:59 Pineapple kern.err kernel: [ 59.890000] ath: Failed to wakeup in 500us Any suggestions? I did not see any guide guide on doing this so I have just been piecing stuff together.
×
×
  • Create New...