segarrra

July 24, 2013

I'm running the 2.8.1 firmware and had the same problem. I've read here (http://forums.kali.org/archive/index.php/t-89.html) that, in order to run wash, you need this package "libsqlite3-dev", at least in regular GNU/Linux distros.

Besides that, it seems that you also need to create the directory "/etc/reaver/" (http://em3rgency.com/a-great-kali-update-script/):

...

#FIX wash
apt-get -y install libsqlite3-dev &>/dev/null
mkdir -p /etc/reaver &>/dev/null

...

So, in my case, after finding out that the package "libsqlite3" was already installed, I created the "/etc/reaver" directory and now wash is showing results!

Edit: http://code.google.com/p/reaver-wps/issues/detail?id=46#c37

July 15, 2013

First of all, congratulations for the great work Moriarty and Whistle Master!

And now the doubt: I've found that when trying to launch any of the "Airodump" commands from a monitor interface it just doesn't work.

I can see the pop-up with the command (for example: airodump-ng --output-format csv -w ../data/captura mon0 >/dev/null 2>/dev/null), but no file is created in "data".

The thing is that if I launch that command from a SSH terminal, then I can see how the file is created and it appears in the GUI. Does it happens to anyone else? Maybe it's corrected in UWUI version 0.52? (The infusion is using 0.51).

Thanks!

EDIT:

I found the problem: in the file "uwui_actions_exec.php", when executing commands in the background (as with the airodump options), it is using "nohup":

...

if ( isset($_GET["cmd_bg"]) ) {
                echo "$_GET[cmd_bg]\n";
                shell_exec("${sudo}nohup $_GET[cmd_bg] &");
        }
...

Which is not present in the pinneaple. I changed it to a "doble fork" (got the idea from here: http://stackoverflow.com/a/9646251):

...

if ( isset($_GET["cmd_bg"]) ) {
                echo "$_GET[cmd_bg]\n";
                shell_exec("((${sudo}$_GET[cmd_bg])&)");
        }
...

And now is working!

I guess Moriarty could change it in the original code, as I think it doesn't harm the functionality...

July 8, 2013

Ok, finally found the configuration that works!

First, I had to use the ttyUSB4 interface:

...
uci set network.wan2.device=/dev/ttyUSB4
...

And also had to change the number of the ATD command in /etc/chatscripts/3g.chat (I think that this is related to the 3g operator):

...
OK "ATD*99#"
...

July 8, 2013

Hi,

We just bought a WiFi Pineapple Mark IV and we are not able to configure a ZTE MF110 with Movistar (Spain). We are using version 2.8.1 and this is our information:

lsusb output

Bus 001 Device 005: ID 19d2:0124 ZTE WCDMA Technologies MSM

Switch case

*19d2:0124*)
        echo "ZTE MF110 (Movistar) detected. Attempting mode switch"
        uci delete network.wan2                                                             
        uci set network.wan2=interface
        uci set network.wan2.ifname=ppp0
        uci set network.wan2.proto=3g
        uci set network.wan2.service=umts
        uci set network.wan2.device=/dev/ttyUSB1
        uci set network.wan2.apn=movistar.es
        uci set network.wan2.username=MOVISTAR
        uci set network.wan2.password=MOVISTAR
        uci set network.wan2.defaultroute=1
        uci commit network
        # There is no need to use the usb_modeswitch command because the kernel does the switching alone for ZTE USB sticks
        #usb_modeswitch -v 19d2 -p 0124 -V 19d2 -P 0124 -M 5553424312345678000000000000061b000000020000000000000000000000 -n 1 -s 20
        #usb_modeswitch -v 19d2 -p 0124
        sleep 10; rmmod usbserial
        sleep 3; insmod usbserial vendor=0x19d2 product=0x0124
        # Firewall is not needed anymore
        #sleep 5; /etc/init.d/firewall disable; /etc/init.d/firewall stop
        #logger "3G: firewall stopped"
        iptables -t nat -A POSTROUTING -s 172.16.42.0/24 -o 3g-wan2 -j MASQUERADE
        iptables -A FORWARD -s 172.16.42.0/24 -o 3g-wan2 -j ACCEPT                                                                 
        iptables -A FORWARD -d 172.16.42.0/24 -m state --state ESTABLISHED,RELATED -i 3g-wan2 -j ACCEPT

We think that the mode switch is done correctly, because we can see the usb-serial interfaces:

root@Pineapple:~# ls /dev/ttyUSB*
/dev/ttyUSB0  /dev/ttyUSB1  /dev/ttyUSB2  /dev/ttyUSB3  /dev/ttyUSB4  /dev/ttyUSB5

And when executing the comgt it looks like we are registered in the net:

root@Pineapple:~# comgt
Trying list of devices
SIM ready
Waiting for Registration..(120 sec max)
Registered on Home network: "movistar",2
Signal Quality: 23,99

But when booting the pineapple with the "3G bootup" activated, we can see this messages in the logs:

00:02:14 Pineapple daemon.info pppd[2305]: Exit.
00:02:13 Pineapple local2.info chat[2309]: alarm
00:02:13 Pineapple local2.info chat[2309]: Failed
00:02:13 Pineapple daemon.err pppd[2305]: Connect script failed
00:02:03 Pineapple local2.info chat[2309]: timeout set to 10 seconds
00:02:03 Pineapple local2.info chat[2309]: send (AT&F^M)
00:02:03 Pineapple local2.info chat[2309]: report (CONNECT)
00:02:03 Pineapple local2.info chat[2309]: expect (OK)
00:02:03 Pineapple local2.info chat[2309]: abort on (NO CARRIER)
00:02:03 Pineapple local2.info chat[2309]: abort on (ERROR)
00:02:03 Pineapple local2.info chat[2309]: abort on (BUSY)
00:02:02 Pineapple daemon.notice pppd[2305]: pppd 2.4.5 started by root, uid 0
00:02:02 Pineapple daemon.info dnsmasq[1808]: using nameserver 8.8.8.8#53
00:02:02 Pineapple daemon.info dnsmasq[1808]: using local addresses only for domain lan
00:02:02 Pineapple daemon.info dnsmasq[1808]: reading /tmp/resolv.conf.auto
00:02:00 Pineapple daemon.notice pppd[2237]: Modem hangup
00:02:00 Pineapple daemon.notice netifd: Interface 'wan2' is now down
00:02:00 Pineapple daemon.info pppd[2237]: Exit.
00:01:59 Pineapple daemon.warn pppd[2237]: LCP: timeout sending Config-Requests
00:01:59 Pineapple daemon.notice pppd[2237]: Connection terminated.
00:01:28 Pineapple local2.info chat[2253]: timeout set to 30 seconds
00:01:28 Pineapple local2.info chat[2253]: timeout set to 10 seconds
00:01:28 Pineapple local2.info chat[2253]: send (ATE1^M)
00:01:28 Pineapple local2.info chat[2253]: send (ATD*99***1#^M)
00:01:28 Pineapple local2.info chat[2253]: send (AT+CGDCONT=1,"IP","movistar.es"^M)
00:01:28 Pineapple local2.info chat[2253]: send (AT&F^M)
00:01:28 Pineapple local2.info chat[2253]: send ( ^M)
00:01:28 Pineapple local2.info chat[2253]: report (CONNECT)
00:01:28 Pineapple local2.info chat[2253]: expect (OK)
00:01:28 Pineapple local2.info chat[2253]: expect (OK)
00:01:28 Pineapple local2.info chat[2253]: expect (OK)
00:01:28 Pineapple local2.info chat[2253]: expect (CONNECT)
00:01:28 Pineapple local2.info chat[2253]: abort on (NO CARRIER)
00:01:28 Pineapple local2.info chat[2253]: abort on (ERROR)
00:01:28 Pineapple local2.info chat[2253]: abort on (BUSY)
00:01:28 Pineapple local2.info chat[2253]: ^M
00:01:28 Pineapple local2.info chat[2253]: ^M
00:01:28 Pineapple local2.info chat[2253]: ^M
00:01:28 Pineapple local2.info chat[2253]: OK
00:01:28 Pineapple local2.info chat[2253]: OK
00:01:28 Pineapple local2.info chat[2253]: OK
00:01:28 Pineapple local2.info chat[2253]: CONNECT
00:01:28 Pineapple local2.info chat[2253]: ATE1^M^M
00:01:28 Pineapple local2.info chat[2253]: ATD*99***1#^M^M
00:01:28 Pineapple local2.info chat[2253]: AT+CGDCONT=1,"IP","movistar.es"^M^M
00:01:28 Pineapple local2.info chat[2253]: AT&F^M^M
00:01:28 Pineapple local2.info chat[2253]: -- got it
00:01:28 Pineapple local2.info chat[2253]: -- got it
00:01:28 Pineapple local2.info chat[2253]: -- got it
00:01:28 Pineapple local2.info chat[2253]: -- got it
00:01:28 Pineapple daemon.notice pppd[2237]: Connect: 3g-wan2 <--> /dev/ttyUSB1
00:01:28 Pineapple daemon.info pppd[2237]: Using interface 3g-wan2
00:01:28 Pineapple daemon.info pppd[2237]: Serial connection established.
00:01:27 Pineapple daemon.notice pppd[2237]: pppd 2.4.5 started by root, uid 0
00:01:25 Pineapple kern.info kernel: [ 85.410000] device wlan0 left promiscuous mode
00:01:25 Pineapple kern.info kernel: [ 85.410000] br-lan: port 2(wlan0) entered disabled state
00:01:25 Pineapple kern.info kernel: [ 85.300000] br-lan: port 2(wlan0) entered disabled state
00:01:24 Pineapple user.info sysinit: setting up led WLAN
00:01:24 Pineapple user.info sysinit: setting up led WAN
00:01:24 Pineapple user.info sysinit: setting up led USB
00:01:24 Pineapple user.info sysinit: setting up led LAN
00:01:23 Pineapple kern.info kernel: [ 83.720000] usbserial_generic 1-1.4.4:1.4: generic converter detected
00:01:23 Pineapple kern.info kernel: [ 83.720000] usb 1-1.4.4: generic converter now attached to ttyUSB3
00:01:23 Pineapple kern.info kernel: [ 83.710000] usbserial_generic 1-1.4.4:1.3: generic converter detected
00:01:23 Pineapple kern.info kernel: [ 83.700000] usbserial_generic 1-1.4.4:1.2: generic converter detected
00:01:23 Pineapple kern.info kernel: [ 83.700000] usb 1-1.4.4: generic converter now attached to ttyUSB2
00:01:23 Pineapple kern.info kernel: [ 83.690000] usb 1-1.4.4: generic converter now attached to ttyUSB1
00:01:23 Pineapple kern.info kernel: [ 83.680000] usbserial_generic 1-1.4.4:1.1: generic converter detected
00:01:23 Pineapple kern.info kernel: [ 83.680000] usb 1-1.4.4: generic converter now attached to ttyUSB0
00:01:23 Pineapple kern.info kernel: [ 83.670000] usbserial_generic 1-1.4.4:1.0: generic converter detected
00:01:23 Pineapple kern.info kernel: [ 83.670000] USB Serial support registered for generic
00:01:23 Pineapple kern.info kernel: [ 83.660000] usbcore: registered new interface driver usbserial
00:01:20 Pineapple kern.info kernel: [ 80.600000] usbcore: deregistering interface driver usbserial
00:01:20 Pineapple kern.info kernel: [ 80.590000] usbcore: deregistering interface driver usbserial_generic
00:01:20 Pineapple kern.info kernel: [ 80.590000] USB Serial deregistering driver generic
00:01:10 Pineapple user.info sysinit: ZTE MF110 (Movistar) detected. Attempting mode switch
00:01:10 Pineapple user.info sysinit: 1d6b:0002 2109:0810 0781:5571 1a40:0101 19d2:0124
00:01:08 Pineapple user.notice root: 3G: Connection Script here, searching for modems

Ant the connection does not work.

We think that the problem is in the pppd daemon and the "LCP: timeout sending Config-Requests" but we're not sure if we're doing everything OK.

We also tried to modify the switch case and change the

uci set network.wan2.device=/dev/ttyUSB1

To

uci set network.wan2.device=/dev/ttyUSB2

But with no success. Any ideas?

Thank you very much!

Sign In

segarrra

Posts

Joined

Last visited

Content Type

Profiles

Forums

Posts posted by segarrra

wash/reaver (glitch/error) pineapple IV

New Web Interface for Hacking Funcionalities

Mark IV problem with 3G modem ZTE MF110 & Movistar (Spain)

Mark IV problem with 3G modem ZTE MF110 & Movistar (Spain)

Browse

Activity