Printable View
I have searched the internet thick and thin and I dont know how to fix the rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping issue, the dmesg kernel log shows loads of tx errors. There must be a fix for this as it started in 2011. If someone has advice or can help it would be great. I am using Kali and Parrot OS, ive tested from kerel 3.12 to 3.14.8
Thanks
DG
AFAIK the problem it's not solved and it's affecting only rt2800usb. Not the rt2800pci driver.
Sometime it help when you set:
But in general you will get something like:Code:iwconfig wlan0 retry 30
iwconfig wlan0 rts 2347
iwconfig wlan0 frag 2346
......this is from my card.Code:[90150.448926] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90150.448941] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90150.448945] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90159.652305] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 2
[90159.652320] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 2
[90159.652325] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 2
[90159.814307] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90160.080927] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90160.080940] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90160.080944] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90160.808430] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 4 in queue 2
[90160.808442] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 4 in queue 2
[90160.808449] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 4 in queue 2
[90160.904052] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 0
[90160.904063] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 0
[90160.904067] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 0
[90161.304432] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 0, dropping
[90161.304680] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90161.304805] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90161.589053] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
[90161.589067] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
[90161.589071] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
[90162.818184] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90162.981053] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2
[90162.981063] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2
[90162.981070] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2
[90163.814685] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90164.840930] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 10 in queue 2
[90164.840943] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 10 in queue 2
[90164.840948] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 10 in queue 2
[90164.916304] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 3 in queue 0
[90164.916316] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 3 in queue 0
[90164.916320] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 3 in queue 0
[90165.869683] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 0, dropping
[90166.034683] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90166.296180] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 15 in queue 2
[90166.296193] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 15 in queue 2
[90166.296197] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 15 in queue 2
[90166.481934] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90166.580431] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 3
[90166.580444] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 3
[90166.580448] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 3
[90166.737054] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 2
[90166.737066] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 2
[90166.737070] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 0 in queue 2
[90166.818184] ieee80211 phy1: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[90167.228056] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90167.228070] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[90167.228074] ieee80211 phy1: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
Thanks so much for the reply I will try the suggestions, yes thats what my dmesg output looks like, I saw patches from 2012 but it looks like they are outdated and have been applied, did the commands you showed me make a difference for you? I can assume its something you do at every boot. Thanks again
You're welcome dataghost.Quote:
Originally Posted by dataghost
No, it doesn't make any noticeable differences for me. dmesg output it's flooded with the above messages. If I got some time in the weekend I will try to dig it a little more, but to be honest I don't expect to find any workaround. Most of the people revert back to very old kernels to solve this.
As for me I use that NIC only for creating a rogue AP with hostap and I can assure you it works quite well.
Sorry for my English. I hope you understand what I'm talking about. :o
Well I just tried the following:
Ralink_5370sta-2.5.0.3_dkms is a new (?) revised version.
with no sucess....:mad:Code:apt-get install --reinstall linux-headers-$(uname -r) build-essential dkms
wget media.cdn.ubuntu-de.org/forum/attachments/13/16/4365112-Ralink_5370sta-2.5.0.3_dkms.tar.gz
tar xvf 4365112-Ralink_5370sta-2.5.0.3_dkms.tar.gz -C /usr/src
dkms add -m Ralink_5370sta -v 2.5.0.3
dkms build -m Ralink_5370sta -v 2.5.0.3
dkms install -m Ralink_5370sta -v 2.5.0.3
mkdir -p /etc/Wireless/RT2870STA
cp /usr/src/Ralink_5370sta-2.5.0.3/src/RT2870STA.dat /etc/Wireless/RT2870STA
echo "blacklist rt2800usb" | sudo tee -a /etc/modprobe.d/blacklist.conf
apt-get install tofrodos
dos2unix /etc/Wireless/RT2870STA/RT2870STA.dat
chmod +x /etc/Wireless/RT2870STA/RT2870STA.dat
cp common/rt2870.bin /lib/firmware/
A new interface came up (ra0) but I got too many errors and two kernel panic and freezes. Beautiful!!
After that I un-blacklist rt2800usb from /etc/modprobe.d/blacklist.conf file and blacklist the rt5370sta that I just have created. I run depmod -a and I plug the usb dongle again.
Then the good old rt2800usb driver loaded but I could connect at 60 Mb/s and dmesg's errors are gone.
Maybe its the firmware that I have copied ? Don't know. Can remember which version I have had before the :Quote:
root@kali:~# iwconfig wlan1
wlan1 IEEE 802.11bgn ESSID:"xxxxxx257xxxx"
Mode:Managed Frequency:2.447 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate=60 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=57/70 Signal level=-53 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:5 Invalid misc:9 Missed beacon:0
and I didn't kept any backup of the old one.Code:cp common/rt2870.bin /lib/firmware/
So if you have rt2870.bin version lower than 0.32 download the 4365112-Ralink_5370sta-2.5.0.3_dkms.tar.gz file from above and copy the rt2870.bin to /lib/firmware/.
Until know no errors are coming. Only few:
"Tx excessive retries:6 Invalid misc:9"
Here is a dmesg output:
Code:[ 975.716019] usb 5-7: new high-speed USB device number 3 using ehci-pci
[ 975.865545] usb 5-7: New USB device found, idVendor=148f, idProduct=5370
[ 975.865549] usb 5-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 975.865552] usb 5-7: Product: 802.11 n WLAN
[ 975.865554] usb 5-7: Manufacturer: Ralink
[ 975.865557] usb 5-7: SerialNumber: 1.0
[ 976.008020] usb 5-7: reset high-speed USB device number 3 using ehci-pci
[ 976.150670] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[ 976.178795] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 5370 detected
[ 976.179127] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 976.179354] usbcore: registered new interface driver rt2800usb
[ 976.209717] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 976.229604] rt2800usb 5-7:1.0: firmware: direct-loading firmware rt2870.bin
[ 976.229611] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.32
[ 976.457825] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 978.276061] wlan1: authenticate with xx:xx:xx:xx:xx
[ 978.306800] wlan1: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[ 978.307931] wlan1: authenticated
[ 978.312009] wlan1: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[ 978.317179] wlan1: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=1)
[ 978.323673] wlan1: associated
[ 978.323700] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 1006.748634] wlan1: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
[ 1050.409964] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
[ 1050.410769] cfg80211: Calling CRDA to update world regulatory domain
[ 1050.429432] cfg80211: World regulatory domain updated:
[ 1050.429435] cfg80211: DFS Master region: unset
[ 1050.429436] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1050.429438] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1050.429439] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1050.429440] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[ 1050.429442] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[ 1050.429443] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[ 1050.429444] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[ 1054.388067] wlan1: authenticate with xx:xx:xx:xx:xx:xx
[ 1054.416703] wlan1: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[ 1054.422331] wlan1: authenticated
[ 1054.424010] wlan1: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[ 1054.426082] wlan1: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=1)
[ 1054.432576] wlan1: associated
Thank you so much for doing everything you have done, I am going to try this in the evening, I use the NIC for rogue ap host then i was using the 2800usb as the wireless ap, the tx power issue and warning is what was causing disconnects etc. I appreciate all the help and effort you have done here. From the looks of it, it seems much better
:)
Yes I can confirm now. Kali offers firmware rt2870.bin version 0.29.
So, in summary:Code:[84009.184277] usb 1-2: new high-speed USB device number 7 using ehci-pci
[84009.334080] usb 1-2: New USB device found, idVendor=148f, idProduct=5370
[84009.334101] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[84009.334115] usb 1-2: Product: 802.11 n WLAN
[84009.334126] usb 1-2: Manufacturer: Ralink
[84009.334137] usb 1-2: SerialNumber: 1.0
[84009.644219] usb 1-2: reset high-speed USB device number 7 using ehci-pci
[84009.787320] ieee80211 phy13: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[84009.816076] ieee80211 phy13: rt2x00_set_rf: Info - RF chipset 5370 detected
[84009.817350] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
[84009.820749] usbcore: registered new interface driver rt2800usb
[84010.033360] ieee80211 phy13: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[84010.058414] rt2800usb 1-2:1.0: firmware: direct-loading firmware rt2870.bin
[84010.058440] ieee80211 phy13: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
[84010.314586] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Code:#Download:
wget media.cdn.ubuntu-de.org/forum/attachments/13/16/4365112-Ralink_5370sta-2.5.0.3_dkms.tar.gz
# Extract:
tar zxf 4365112-Ralink_5370sta-2.5.0.3_dkms.tar.gz
# Backup the old one
mv /lib/firmware/rt2870.bin /lib/firmware/rt2870.bin.bak
# And copy the new one:
cd Ralink_5370sta-2.5.0.3/src/common
cp rt2870.bin /lib/firmware/rt2870.bin
You're done!Code:[85228.662551] usb 1-2: USB disconnect, device number 7
[85240.388270] usb 1-2: new high-speed USB device number 8 using ehci-pci
[85240.538228] usb 1-2: New USB device found, idVendor=148f, idProduct=5370
[85240.538251] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[85240.538265] usb 1-2: Product: 802.11 n WLAN
[85240.538277] usb 1-2: Manufacturer: Ralink
[85240.538288] usb 1-2: SerialNumber: 1.0
[85240.656277] usb 1-2: reset high-speed USB device number 8 using ehci-pci
[85240.799184] ieee80211 phy14: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[85240.828187] ieee80211 phy14: rt2x00_set_rf: Info - RF chipset 5370 detected
[85240.829248] ieee80211 phy14: Selected rate control algorithm 'minstrel_ht'
[85241.009113] ieee80211 phy14: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[85241.009272] rt2800usb 1-2:1.0: firmware: direct-loading firmware rt2870.bin
[85241.009289] ieee80211 phy14: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.32
and no errors in dmesg.Code:wlan3 IEEE 802.11bgn ESSID:"xxxxxxxxxx"
Mode:Managed Frequency:2.447 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate=120 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:8 Missed beacon:0
If you don't mind, since I'm using the same NIC for a rogue AP, can you please try my script Aerial:Quote:
Originally Posted by dataghost
Aerial - How to E-Z Setup a Multi-mode wireless LAN Based on a Software Access point
create a hostapd based 80.211 g/n rogueAP width 40MHz channel width and tell me how it performs? It's a menu driven script and very easy to use.
I'm not in a rush. When you got time...
Ill try the script today Nick, **** man you're a rockstar, this issue has been occuring for years and you figured it out in a night. Thanks for all the hard work, amazing dude.
I just installed the the rt2870.bin as you said to do and I will now give it a shot. I will post my results.
Hello Nick, when running the script i get a lot of jumbled writing see below
033[1;34mI n t e r n e t a n d W i r e l e s s i n t e r f a c e s :033[1;37m
033[1;34mInternet Interface033[1;37m
Please have in mind that if you DON'T want to be prompted every time for your Internet
and wireless interfaces you can set \033[1;31mINET_WIRELESS_PROMPT yes\033[1;37m to \033[1;32mINET_WIRELESS_PROMPT no\033[1;37m
in \033[1;32m/root/Aerial/aerial.conf\033[1;37m file
You're currently using:
Internet through : \033[1;32mwlan0 - pci:ath9k\033[1;37m
Enter the name of the interface that you are
connected to the Internet, [e.g.\033[1;31mppp0\033[1;37m,\033[1;31meth0\033[1;37m,\033[1;31mwlan0\033[1;37m ]
Press ENTER for current (\033[1;32mwlan0\033[1;37m):
There is a lot of settings, what would you like me to try for an attack in the menu 1-14 i believe, I tried sslsplit and no internet was provided.
I will try some others. I still get the txpower issue when I ran the kali version of 911_ap, fake ap. I didnt seem to lose internet access though, I will test further.
Also is there a clean way to shut the script down to clean up
Hi Nick
Update - I have tried MITMproxy, sslsplit, and sslstrip, I have tried both softap airbase and hostap, I have never heard of hostap so I am not sure exactly how it works, No matter what I am getting the channel -1 error, when i make a fake ap using kali normally i dont get that, at worst i run ifconfig wlanX down and its fine. Any ideas why this is happening and why I can not connect to the fake ap i am creating, it tries to connect but it cant. I am not using a 64 bit system its 32. Ill check back today, I hope I hear back, Thanks again Nick!!
Hi dataghost and thank you for your time :)
If you don't mind let's continue the discussion about Aerial here:
https://forums.kali.org/showthread.p...e-Access-point
since Aerial has nothing to do with your topic.
As for the current topic (yours) I don't thing the new(?) firmware is solving everything. The problems doesn't disappear completely:
but they are very limited, I will test more to see how it behaves.Quote:
[ 2205.623855] wlan1: associated
[ 2205.623882] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 2226.257487] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2226.257731] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2226.257984] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2407.412019] ath5k: ath5k_hw_get_isr: ISR: 0x00040001 IMR: 0x00000000
[ 2506.220589] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2506.220835] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2506.221084] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2626.234139] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2626.234385] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2626.234505] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2866.261848] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2866.262093] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 2866.262343] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 3567.380057] usb 4-2: USB disconnect, device number 2
rt2800usb is the culprit, maybe a driver issue, a few others worked ok, any ideas on the rt2800usb?
Hi my friend dataghost.Quote:
Originally Posted by dataghost
If I'm not mistaken I've read somewhere (can't remember) that in recent kernels 3.15 3.16 the problems that occur the rt2800usb are very limited. If you want you can try installing recent kernel by following this:
https://forums.kali.org/showthread.p...ll=1#post37163
Please have I mind that I don't recommend installing a kernel from another distro because trying to fix something you might broke something else. I haven't try it though.
Have a good day!
Thanks Nick, Before i reinstalled Kali last time i compiled and installed 3.17 rc3 i believe it was and it ran great but the issue was headers etc for virtualbox and a few other things. Thanks for all the help
No problem dataghost.Quote:
Originally Posted by dataghost
I'm glad to help people and specially those ones who willing to learn.
Hey Nick sorry they closed your Aerial thread, I thought it was great, and clearly so did others, I guess someone got their pannies in a knot. Thanks for all the help you give to the community, I along with others appreciate all your efforts
We moved the Aerial thread to a more appropriate sub-forum. Seeing how we received hate mail from dataghost, we've banned his account from our forums. We have zero tolerance for tards.
Quote:
Originally Posted by dataghost
UH OH! What did I miss? Aerial thread isn't moved either is closed.Quote:
Originally Posted by muts
@muts I know that you don't have to get permission to close it, but if you think that you have to close Aerial thread please feel free to do it so. I moved Aerial to github since I've read more carefully g0tmi1k's signature:
and I realize that maybe kali forums maybe isn't the right place to distribute my script or any other script even if is made to run in Kali.Quote:
This is a Kali Linux support forum - not general IT/infosec help.
(Please correct me if I'm wrong)
Anyway, I'm a Linux hobbyist not a pro pentester and I loved to share my limited knowledge with you guys.
Have a nice day to both of you guys!
Not to go to off-topic, the thread can be found here: https://forums.kali.org/showthread.p...e-Access-pointQuote:
Originally Posted by Nick_the_Greek
Selective posting here in this forum i see... I posted something about Dataghost and it was never allowed by the admin's I guess. Too bad