Search the Community
Showing results for tags 'timeout'.
I'm still running in the payload timeout after 1 Minute. So I did some investigation about it. I made the attached payload.txt for testing. I put the command logger "#### Start Test payload #### at the beginning of the payload and logger "#### End Test payload ####" at the end. So I can examine the syslog what happens during ten payload run. After approx. 1:30 min bunny.service is running into a timeout ......... Apr 6 09:56:52 bunny logger: #### Loop Test payload #### Apr 6 09:56:54 bunny logger: #### Loop Test payload #### Apr 6 09:56:56 bunny logger: #### Loop Test payload #### Apr 6 09:56:58 bunny systemd: bunny.service start operation timed out. Terminating. Apr 6 09:56:58 bunny systemd: Failed to start bunny.service. Apr 6 09:56:58 bunny systemd: Unit bunny.service entered failed state. Apr 6 09:56:58 bunny systemd: Starting Multi-User System. Apr 6 09:56:58 bunny systemd: Reached target Multi-User System. Apr 6 09:56:59 bunny systemd: Startup finished in 2.366s (kernel) + 1min 34.343s (userspace) = 1min 36.710s. The result of the command systemctl show bunny.service |grep Timeout is TimeoutStartUSec=1min 30s TimeoutStopUSec=1min 30s JobTimeoutUSec=0 Guess this is the reason for the payload timeout. Can anybody confirm this? I willl do more investigations syslog payload.txt ______________________________________________________________________________________________________________________ OK got it..... I insert the value TimeoutSec=5min under the [Service] section of file /lib/systemd/system/bunny.service Now it works with a timeout of 5 min. (see attached syslog.solved_5min_Timeout) Be carefully, I'm not responsible for any damage of the bunny :-) @Darren Kitchen @Sebkinne If you agree (because its part of Firmware) I can make a payload who will patch this. syslog.solved_5min_Timeout
Well i just recently got back into using tor and it had been working fairly well for me (with the usual bothersome slowness). Now whenever i try to connect to a specific website (apparently not down) and login it tells me that it timed out, howevver this seems to be the only webiste that it does it for. Any suggestions or ideas would be muchly appreciated! Or if anyone has had a similar experience! (yes I've done all the usual crud to try and fix it including reinstalling, restarting my computer, restarting the router, using a different wifi etc.)
Hello - first post, and my first bite of the pineapple. I requested and received one for the holidays, and have spent the last few days playing with it. I'm attempting to perform a simple deauth/hijack of a client on my local network, and my use of the Alfa adapter isn't working out the way I had hoped. Some details: - Connecting the USB adapter does not show an interface available - lsusb reflects that a device was connected - iwconfig or ifconfig can be used to bring the device up, light the LED, and perform further commands after which the device is 'usable' - Once the device is available, the channel is modified to match that of the ap being spoofed - The actual aireplay-ng command results in the following: root@Pineapple:/tmp# aireplay-ng -0 5 -e MYESSID -c xx:xx:xx:a8:b8:2c wlan1 22:05:21 Waiting for beacon frame (ESSID: MYESSID) on channel 11 Found BSSID "xx:xx:xx:64:80:66" to given ESSID "MYESSID". write failed: Network is down wi_write(): Network is down directed DeAuth. STMAC: [XX:XX:XX:A8:B8:2C] [ 0| 0 ACKs] - Once this occurs, the device appears to have been removed completely. - An lsusb shows only the hub, not the adapter - The following is displayed in the system log: 22:06:44 Pineapple kern.err kernel: [ 2468.490000] usb 1-1: device not accepting address 28, error -145 22:06:44 Pineapple kern.err kernel: [ 2468.490000] hub 1-0:1.0: unable to enumerate USB device on port 1 ERRNO ~145 is a connection timeout. I expect that I'm doing something wrong, as these devices are used together quite often, but I'm unable to figure out exactly what that is. If someone could point me in the right direction, I'd very much appreciate it. Thanks!