I am trying to connect my TP-Link AC600 wireless adapter through the USB port to connect to Kali linux Rolling but I am having issues getting it to show up with ifconfig
root@kali:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.139 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 0000::000:0000:0000:0000 prefixlen 64 scopeid 0x20<link>
ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 125 bytes 20180 (19.7 KiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 72 bytes 14284 (13.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 20 bytes 1116 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 1116 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@kali:~#
Note: I intentionally set the MAC address and inet6 to all 0’s for posting this.
I know it exists because i ran iwconfig:
root@kali:~# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
ra0 Ralink STA
root@kali:~#
I tried to bring it up but I got an error:
root@kali:~# ifconfig ra0 up
SIOCSIFFLAGS: Operation not permitted
root@kali:~#
I have confirmed that kali knows my adapter is plugged in:
root@kali:~# lsusb
Bus 001 Device 002: ID 148f:761a Ralink Technology, Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@kali:~#
I never used to have this problem with my old wifi adapter Edimax N150.
Any help will be greatly appreciated!!
Edit:
This is the output of my linux version:
root@kali:~# cat /proc/version
Linux version 4.9.0-kali3-amd64 (devel@kali.org) (gcc version 6.3.0
20170321 (Debian 6.3.0-11) ) #1 SMP Debian 4.9.18-1kali1 (2017-04-04)
Output of ip link (again, I censored my MAC Address)
root@kali:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
link/ether 01:01:01:01:01:01 brd ff:ff:ff:ff:ff:ff
3: ra0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
No output of iw ra0 scan dump:
root@kali:~# iw ra0 scan dump
root@kali:~#
It may help to know that I’m running a virtual machine with VirtualBox Version 5.1.20 r114628 (Qt5.6.2) with Guest Additions installed.
Edit 2:
I installed the driver from this github repository using the directions in its README file.
When I run lsmod the following entry appears in the list:
mt7650u_sta 913408 0
This is what I get when I run airmon-ng:
root@kali:~# airmon-ng
PHY Interface Driver Chipset
Warn ON: USB
null ra0 ?????? Ralink Technology, Corp.
Here is what appears after I run dmesg --follow and then plug in the adapter:
[ 96.244532] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 96.626526] usb 1-1: New USB device found, idVendor=148f, idProduct=761a
[ 96.626528] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 96.626529] usb 1-1: Product: WiFi
[ 96.626530] usb 1-1: Manufacturer: MediaTek
[ 96.626531] usb 1-1: SerialNumber: 1.0
[ 97.370532] rtusb init rt2870 --->
[ 97.370717]
=== pAd = ffffac2782215000, size = 884464 ===
[ 97.370755] <-- RTMPAllocTxRxRingMemory, Status=0
[ 97.370843] <-- RTMPAllocAdapterBlock, Status=0
[ 97.374196] ==>RT65xx_WLAN_ChipOnOff(): OnOff:1, Reset= 0, pAd- >WlanFunCtrl:0x0, Reg-WlanFunCtrl=0xff000002
[ 97.407040] MCUType = 2
[ 97.413761] NVM is EFUSE
[ 97.413763] Endpoint(8) is for In-band Command
[ 97.413764] Endpoint(4) is for WMM0 AC0
[ 97.413764] Endpoint(5) is for WMM0 AC1
[ 97.413765] Endpoint(6) is for WMM0 AC2
[ 97.413765] Endpoint(7) is for WMM0 AC3
[ 97.413766] Endpoint(9) is for WMM1 AC0
[ 97.413766] Endpoint(84) is for Data-In
[ 97.413767] Endpoint(85) is for Command Rsp
[ 97.413962] usbcore: registered new interface driver rt2870
Here is what appears in dmesg --follow after I attempt ifconfig ra0 up.
It seems that at the end an error occurs due to a firmware problem:
[ 452.409459] -->RTUSBVenderReset
[ 452.412895] <--RTUSBVenderReset
[ 452.417861] fw version:0.1.00
[ 452.417862] build:7640
[ 452.417862] build time:
[ 452.417862] 2
[ 452.417863] 0
[ 452.417863] 1
[ 452.417863] 3
[ 452.417864] 0
[ 452.417864] 8
[ 452.417864] 2
[ 452.417865] 2
[ 452.417865] 1
[ 452.417865] 6
[ 452.417866] 5
[ 452.417866] 5
[ 452.417866] _
[ 452.417866] _
[ 452.417867] _
[ 452.417867] _
[ 452.417868] ilm length = 68780(bytes)
[ 452.417868] dlm length = 11476(bytes)
[ 452.499268] #
[ 452.584208] #
[ 452.669704] #
[ 452.751712] #
[ 452.835845] #
[ 452.921746] #
[ 453.002859] #
[ 453.086978] #
[ 453.171254] #
[ 453.254671] #
[ 453.259703] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x800,pAd->Flags=0x0
[ 453.259703] VendrCmdMultiWrite_nBytes failed!
[ 453.339791] #
[ 453.425475] #
[ 453.511495] #
[ 453.595779] #
[ 453.678897] #
[ 453.762715] #
[ 453.846344] #
[ 453.930761] #
[ 454.015048] #
[ 454.101210] #
[ 454.106299] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x9a0,pAd->Flags=0x0
[ 454.106299] VendrCmdMultiWrite_nBytes failed!
[ 454.187120] #
[ 454.271227] #
[ 454.356669] #
[ 454.438907] #
[ 454.522086] #
[ 454.606318] #
[ 454.691650] #
[ 454.774580] #
[ 454.861492] #
[ 454.946881] #
[ 454.951937] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x9a4,pAd->Flags=0x0
[ 454.951937] VendrCmdMultiWrite_nBytes failed!
[ 455.030339] #
[ 455.113684] #
[ 455.198504] #
[ 455.281715] #
[ 455.366429] #
[ 455.457864] #
[ 455.541956] #
[ 455.627037] #
[ 455.712217] #
[ 455.793512] #
[ 455.798542] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x9c4,pAd->Flags=0x0
[ 455.798542] VendrCmdMultiWrite_nBytes failed!
[ 455.877982] #
[ 455.961774] #
[ 456.045695] #
[ 456.131480] #
[ 456.215752] #
[ 456.297832] #
[ 456.382229] #
[ 456.465221] #
[ 456.549737] #
[ 456.635715] #
[ 456.640787] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0xa6c,pAd->Flags=0x0
[ 456.640787] VendrCmdMultiWrite_nBytes failed!
[ 456.719216] #
[ 456.801377] #
[ 456.889631] #
[ 456.976462] #
[ 457.061738] #
[ 457.144773] #
[ 457.228654] #
[ 457.313486] #
[ 457.397397] #
[ 457.481365] #
[ 457.486455] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=IN, Req=0x7, Idx=0x238,pAd->Flags=0x0
[ 457.564521] #
[ 457.648699] #
[ 457.732465] #
[ 457.817127] #
[ 457.900727] #
[ 457.984601] #
[ 458.068554] #
[ 458.152929] #
[ 458.236699] #
[ 458.321164] #
[ 458.326274] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x238,pAd->Flags=0x0
[ 458.326275] VendrCmdMultiWrite_nBytes failed!
[ 458.405021] #
[ 458.489897] #
[ 458.575184] #
[ 458.660094] #
[ 458.747811] #
[ 458.832438] #
[ 458.915785] #
[ 458.999740] #
[ 459.084463] #
[ 459.168569] #
[ 459.173586] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x238,pAd->Flags=0x0
[ 459.173586] VendrCmdMultiWrite_nBytes failed!
[ 459.173590] loading fw
[ 459.255437] #
[ 459.341691] #
[ 459.426935] #
[ 459.512550] #
[ 459.595554] #
[ 459.682797] #
[ 459.769404] #
[ 459.851295] #
[ 459.939827] #
[ 460.023352] #
[ 460.028362] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x42, Idx=0x230,pAd->Flags=0x0
[ 460.028363] set fce dma descriptor fail
[ 460.108241] #
[ 460.195122] #
[ 460.280030] #
[ 460.367394] #
[ 460.455716] #
[ 460.538948] #
[ 460.623427] #
[ 460.711544] #
[ 460.795256] #
[ 460.878787] #
[ 460.883846] RTUSB_VendorRequest failed(-110),TxFlags=0x0, ReqType=OUT, Req=0x6, Idx=0x800,pAd->Flags=0x0
[ 460.883847] VendrCmdMultiWrite_nBytes failed!
[ 460.883848] ERROR!!!
[ 460.883848] NICLoadFirmware failed, Status[=0x00000001]
[ 460.883849] !!! rt28xx init fail !!!
I recently rebuilt my laptop and reloaded the applications I use for pentesting including Virtualbox and Kali Linux. If you need help setting up Kali Linux in Virtualbox here is a great link that walks through the setup process.
Once I had Kali up and running in my virtual environment I plugged in my ALFA wireless adapter and made sure the USB device was running in the virtual environment.
I ran iwconfig to verify the wireless interface.
So far so good and I ran ifconfig to verify the interface was up, but the only interface returned was the loopback.
After discovering the wireless interface was not up and I ran ifconfig wlan0 up to bring it up and got the SIOCSIFFLAGS error.
I wrote about this error a while back when I was running Backtrack 5 and I first started using the Fern WiFi Cracker. I decided to expand on that post plus I was asked about creating a script to run all the commands at one time instead of typing them individually. The script should be run every time Kali is booted, but after your adapter is plugged in and recognized.
First open a text editor and type in the script shown in the screen shot below. I prefer the gedit text editor and since that is not loaded in Kali I used Leafpad and coming from the Windows world it reminds me of Notepad.
Name the file and save it to the Root directory.
Open the Terminal window and do a quick ls command to verify the file is present.
To run the script type ./<file name>
You’ll probably get an error message about permissions denied and running the chmod 755 <file name> command will adjust the permissions on the file as needed.
Rerun the script ./<file name>
If there are no errors you are good to go and can run ifconfig to verify the wireless interface is up.
I will run the script every time I boot Kali whether or not the interface shows as being up in the ifconfig results.
Trouble shooting wireless issues in Kali Linux can be a frustrating process, but use your Google Fu skills and you’ll find a lot of good links and people offering up advice. Good Luck!
- ALFA
- backtrack 5
- Fern Wifi Cracker
- kali linux
- network interface card
- pentesting
- script
- siocsifflags
- virtualbox
- wireless adapter
- wireless network
- Печать
Страницы: 1 [2] Все Вниз
Тема: Как дать права ? (Прочитано 10573 раз)
0 Пользователей и 1 Гость просматривают эту тему.
alf138
Добавил модуль
lsmod | grep iwl3945
но при попытки
sudo iwconfig wlan0 channel 1 Bit 54Mb/s essid ‘alf_linux’ && ifconfig wlan0 192.168.0.1 netmask 255.255.255.0 up
выдает
Aspire 5920G C2D T7300, 2Gb DDR2, GF 8600M GT.
Windows 7.
Ubuntu 9.10.
aliftin
Странно, а когда раздельно вводим, то не ругается. Тогда пробуйте так:
sudo iwconfig wlan0 channel 1 Bit 54Mb/s essid 'alf_linux'
sudo ifconfig wlan0 192.168.0.1 netmask 255.255.255.0 up
Если мы не можем до чего то дотянуться, мы виним в этом не свой рост, не отсутствие табуретки, а свою цель.
Mam(O)n
Странно, а когда раздельно вводим, то не ругается. Тогда пробуйте так:
Ничего странного. После && исполняется уже другая команда и ей тоже нужен sudo.
aliftin
Ух, я и не знал что «sudo» в таких конструкциях писать каждый раз нужно. Спасибо, Mam(O)n, буду знать. Тогда скрипт будет выгляить так:
#!/bin/bash
iwconfig wlan0 channel 1 Bit 54Mb/s essid 'alf_linux'
ifconfig wlan0 192.168.0.1 netmask 255.255.255.0 up
Если мы не можем до чего то дотянуться, мы виним в этом не свой рост, не отсутствие табуретки, а свою цель.
Frank
Вигня получается записал в rc.local запустится он конечно запустился, но мне нужно что бы при ВХОДЕ в систму он пускался а не призапуске ее, так wifi поднялось «вижу по лампочке» но соединение нет ….
Соединения с кем? Вы хотите настроить клиента или точку доступа?
alf138
точку доступа?
точку доступа
Aspire 5920G C2D T7300, 2Gb DDR2, GF 8600M GT.
Windows 7.
Ubuntu 9.10.
Frank
Ну, сетевую карту wlan0 для этого вы уже настроили. Теперь настраивайте NAT, форвардинг, и клиентский комп.
alf138
мне нужно чтобы запускалось автоматически без тыканья на кнопочки… 
Скрипт запускается, как его запустить в без sudo …
« Последнее редактирование: 27 Марта 2010, 15:10:22 от alf138 »
Aspire 5920G C2D T7300, 2Gb DDR2, GF 8600M GT.
Windows 7.
Ubuntu 9.10.
Frank
Поместить в /etc/rc.local вестимо. Уже сказано же было.
- Печать
Страницы: 1 [2] Все Вверх
I would like to know if I have in my folder /lib/firmware/ the firmware to use correctly a wifi driver.
The general problem is:
root@bananapim2plus:/home/guillaume# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted
I suspect the firmware is not correctly loaded.
So, I don’t know if it’s possible to know what is the firmware needs the driver bcmdhd.
Some informations with this driver loaded:
# iwconfig
lo no wireless extensions.
tunl0 no wireless extensions.
wlan0 IEEE 802.11 Access Point: Not-Associated
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid crypt:0 invalid misc:0
eth0 no wireless extensions.
p2p0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
# modinfo bcmdhd
filename: /lib/modules/3.4.112-sun8i/kernel/drivers/net/wireless/bcmdhd/bcmdhd.ko
license: GPL v2
alias: sdio:c00v*d*
alias: sdio:c*v02D0dA8E7*
alias: sdio:c*v02D0d4324*
alias: sdio:c*v02D0d4334*
alias: sdio:c*v02D0d4330*
alias: sdio:c*v02D0d4319*
alias: sdio:c*v02D0d4329*
alias: sdio:c*v02D0d0493*
alias: sdio:c*v02D0d0492*
alias: sdio:c*v02D0d0000*
depends:
intree: Y
vermagic: 3.4.112-sun8i SMP preempt mod_unload modversions ARMv7 p2v8
parm: dhd_doflow:uint
parm: dhd_dpcpoll:uint
parm: clockoverride:SDIO card clock override (int)
parm: sd_msglevel:uint
parm: sd_power:uint
parm: sd_clock:uint
parm: sd_divisor:uint
parm: sd_sdmode:uint
parm: sd_hiok:uint
parm: sd_f2_blocksize:int
parm: g_assert_type:int
parm: dhd_oob_gpio_num:DHD oob gpio number (int)
parm: info_string:string
parm: op_mode:int
parm: dhd_msg_level:int
parm: iw_msg_level:int
parm: wl_dbg_level:int
parm: android_msg_level:int
parm: config_msg_level:int
parm: dhd_arp_enable:uint
parm: dhd_arp_mode:uint
parm: disable_proptx:int
parm: firmware_path:string
parm: nvram_path:string
parm: config_path:string
parm: dhd_watchdog_ms:uint
parm: dhd_console_ms:uint
parm: dhd_slpauto:uint
parm: dhd_pkt_filter_enable:uint
parm: dhd_pkt_filter_init:uint
parm: dhd_master_mode:uint
parm: dhd_watchdog_prio:int
parm: dhd_dpc_prio:int
parm: dhd_rxf_prio:int
parm: dhd_dongle_ramsize:int
parm: instance_base:int
parm: iface_name:string
parm: dhd_idletime:int
parm: dhd_poll:uint
parm: dhd_intr:uint
parm: dhd_sdiod_drive_strength:uint
parm: dhd_txbound:uint
parm: dhd_rxbound:uint
parm: dhd_deferred_tx:uint
parm: dhd_pktgen:uint
parm: dhd_pktgen_len:uint
# iwlist wlan0 scan
wlan0 Interface doesn't support scanning.
The chip is AP6212, with inside wifi&BT.
The wifi chip is a Broadcom BCM43438
Edit:
Here is the dmesg after loading the driver:
[ 3554.318513] dhd_module_init: in
[ 3554.318606] ======== bcm_wlan_set_plat_data ========
[ 3554.318628] bcm_wlan_get_oob_irq enter.
[ 3554.318726] gpio [202] map to virq [10] ok
[ 3554.318737] host_oob_irq: 10
[ 3554.318747] host_oob_irq_flags=4
[ 3554.318761] dhd_wifi_platform_load: Enter
[ 3554.318798] Power-up adapter 'DHD generic adapter'
[ 3554.318881] wifi_platform_set_power = 1
[ 3554.318891] ======== PULL WL_REG_ON HIGH! ========
[ 3554.318905] [wifi_pm]: set wl_reg_on 1 !
[ 3554.620077] wifi_platform_bus_enumerate device present 1
[ 3554.620094] ======== Card detection to detect SDIO card! ========
[ 3554.620170] [mmc]: sdc1 set ios: clk 0Hz bm PP pm UP vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[ 3554.621769] [mmc]: sdc1 power_supply is null
[ 3554.640176] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[ 3554.663569] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[ 3554.666448] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[ 3554.669198] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[ 3554.681097] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 3554.683035] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3554.684883] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3554.688154] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 3554.794874] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing SD-HS(SDR25) dt B
[ 3554.795309] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing SD-HS(SDR25) dt B
[ 3554.795918] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[ 3554.801215] mmc1: new high speed SDIO card at address 0001
[ 3554.803707] *******************sdio init ok*******************
[ 3554.820313] bcmsdh_register: register client driver
[ 3554.820838] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[ 3554.821258] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[ 3554.821307] bus num (host idx)=1, slot num (rca)=1
[ 3554.821349] found adapter info 'DHD generic adapter'
[ 3554.824019] F1 signature read @0x18000000=0x1540a9a6
[ 3554.835758] F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x4
[ 3554.838490] DHD: dongle ram size is set to 524288(orig 524288) at 0x0
[ 3554.838903] wifi_platform_get_mac_addr
[ 3554.838947] dhd_custom_get_mac_address Enter
[ 3554.838996] dhd_custom_get_mac_address wifi_mac=
[ 3554.842332] wl_create_event_handler(): thread:wl_event_handler:48f6 started
[ 3554.842386] tsk Enter, tsk = 0xca361430
[ 3554.846837] p2p0: P2P Interface Registered
[ 3554.847434] dhd_attach(): thread:dhd_watchdog_thread:48f7 started
[ 3554.847818] dhd_attach(): thread:dhd_dpc:48f8 started
[ 3554.848101] dhd_attach(): thread:dhd_rxf:48f9 started
[ 3554.848170] dhd_deferred_work_init: work queue initialized
[ 3554.849269] dhd_custom_get_mac_address Enter
[ 3554.849327] dhd_custom_get_mac_address wifi_mac=
[ 3554.849376] Dongle Host Driver, version 1.201.34.2 (r491657)
[ 3554.849401] Compiled in drivers/net/wireless/bcmdhd on May 31 2016 at 18:59:58
[ 3554.857790] Register interface [wlan0] MAC: 00:90:4c:11:22:33
[ 3554.857945] dhd_prot_ioctl : bus is down. we have nothing to do
[ 3554.858147] bcmsdh_oob_intr_unregister: Enter
[ 3554.858190] bcmsdh_oob_intr_unregister: irq is not registered
[ 3554.858249] dhd_txglom_enable: enable 0
[ 3554.858284] dhd_bus_devreset: WLAN OFF DONE
[ 3554.858433] wifi_platform_set_power = 0
[ 3554.858470] ======== PULL WL_REG_ON LOW! ========
[ 3554.858508] [wifi_pm]: set wl_reg_on 0 !
[ 3554.858843] dhd_module_init: Exit err=0
Then, later:
3582.385697] dhd_open: Enter eeb0f000
[ 3582.385725] Dongle Host Driver, version 1.201.34.2 (r491657)
[ 3582.385732] Compiled in drivers/net/wireless/bcmdhd on May 31 2016 at 18:59:58
[ 3582.385746] wl_android_wifi_on in 1
[ 3582.385757] wl_android_wifi_on in 2: g_wifi_on=0
[ 3582.385768] wifi_platform_set_power = 1
[ 3582.385777] ======== PULL WL_REG_ON HIGH! ========
[ 3582.385788] [wifi_pm]: set wl_reg_on 1 !
[ 3582.690095] sdio_reset_comm():
[ 3582.690121] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[ 3582.692314] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[ 3582.693424] [mmc]: sdc1 set ios: clk 150000Hz bm PP pm ON vdd 3.3V width 4 timing LEGACY(SDR12) dt B
[ 3582.694492] [mmc]: sdc1 set ios: clk 150000Hz bm PP pm ON vdd 3.3V width 4 timing LEGACY(SDR12) dt B
[ 3582.719356] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 3582.723753] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3582.728098] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3582.736031] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 3582.993042] [mmc]: sdc1 set ios: clk 150000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[ 3582.993574] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[ 3582.994313] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[ 3582.995842] dhd_bus_devreset: == WLAN ON ==
[ 3582.996150] F1 signature read @0x18000000=0x1540a9a6
[ 3583.003433] F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x4
[ 3583.005948] DHD: dongle ram size is set to 524288(orig 524288) at 0x0
[ 3583.006979] dhd_conf_read_config: Ignore config file /lib/firmware/ap6212/config.txt
[ 3583.007056] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/ap6212/fw_bcm43438a0.bin
[ 3583.007111] Final fw_path=/lib/firmware/ap6212/fw_bcm43438a0.bin
[ 3583.007153] Final nv_path=/lib/firmware/ap6212/nvram.txt
[ 3583.007191] Final conf_path=/lib/firmware/ap6212/config.txt
[ 3583.009955] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/ap6212/fw_bcm43438a0.bin
[ 3583.010180] _dhdsdio_download_firmware: dongle image file download failed
[ 3583.010332] dhd_net_bus_devreset: dhd_bus_devreset: -35
[ 3583.010386] dhd_prot_ioctl : bus is down. we have nothing to do
[ 3583.010436] dhd_net_bus_devreset: dhd_bus_devreset: -35
[ 3583.010591] wifi_platform_set_power = 0
[ 3583.010630] ======== PULL WL_REG_ON LOW! ========
[ 3583.010671] [wifi_pm]: set wl_reg_on 0 !
[ 3583.010715] wl_android_wifi_on: Failed
[ 3583.010756] dhd_open : wl_android_wifi_on failed (-35)
[ 3583.010803] dhd_stop: Enter eeb0f000
[ 3583.010839] wl_android_wifi_off in 1
[ 3583.010876] wl_android_wifi_off in 2: g_wifi_on=0
[ 3583.010913] wl_android_wifi_off out
[ 3583.010946] dhd_stop: Exit
[ 3583.010992] dhd_open: Exit ret=-1
[ 3583.080833] dhd_ioctl_entry: Interface is down
[ 3583.177057] dhd_ioctl_entry: Interface is down
[ 3583.177092] dhd_ioctl_entry: Interface is down
[ 3583.177108] dhd_ioctl_entry: Interface is down
[ 3583.177127] dhd_ioctl_entry: Interface is down
[ 3583.177145] dhd_ioctl_entry: Interface is down
SIOCSIFFLAGS: operation not permitted (Lucid)
Hi! I am trying to establish my wireless connection! I have installed successfully ndiswrapper driver, but wireless (ralink 3090) wouldn’t connect. Every time (as a root)
I get this error. I am not the only one with this problem, and the solutions about iwconfig wlan0 txpower auto, adding .dat file to /etc/wireless/RT*, renaming said directory also did not help, especially when the latter did not exist… I did not have this issue with previous releases, and I don’t have access to wired network; ndiswrapper driver works flawlessly.
The funny thing is that I can put the network down, but the error occurs when I try to «up» it. Please help.By the way, with previous builds I was able to install the driver from launchpad, since it required only dkms package. In this release, dkms requires gcc dependency. I can’t download the whole bunch of dependencies, so thank God that ndiswrapper supports my card.
Please help! I would like to know if there is anyone else experiencing the same problem with this release.
Re: SIOCSIFFLAGS: operation not permitted (Lucid)
What happens if you try:
Code:
sudo service networking restart
Re: SIOCSIFFLAGS: operation not permitted (Lucid)
Thank you! Everything is settled now! I saw via lsmod that there was pre-installed driver — rt3090sta, so I removed it from the kernel; then ndiswrapper module was functioning, and I am now writing through this connection
Re: SIOCSIFFLAGS: operation not permitted (Lucid)
What happens if you try:
Code:
sudo service networking restartI tried entering the above code and received the following response:
restart: Unknown instance:
Originally Posted by cariboo907
Re: SIOCSIFFLAGS: operation not permitted (Lucid)
I tried entering the above code and received the following response:
restart: Unknown instance:
What is your actual problem? What type of connection do you have?
Re: SIOCSIFFLAGS: operation not permitted (Lucid) + unknown code
Hmm, this is going to be my first public post on Ubuntu forums…
After battling with the «wireless disabled» problem on my box HP Compaq CQ60, I eventually solved it -and thanks to many forums threads.
Actually, the problem occurred when I hibernated my system and trying to resume, my network appeared grayed and disabled on my gnome network manger.
Various forums had different solutions deleting NetworkManager.state file in /var/lib/NetworkManager, installing wicd….blah, blah. But none never worked for me.
Infact, running lshw -C network shows *network disabled. Of course, If you try enabling the network interface,
$sudo ifconfig wlan0 upyou get the error message SIOCSIFFLAGS: operation not permitted unknown code 132…
well, I eventually got the wireless working when I read a post on a forum and I’m going to post it here as the authoritative solution to the problem. (Sorry, I can’t figure the original URL, but you can always paste it here for due credit!).
$sudo rmmod ath5k (you may have to replace with your driver module e.g ath9k)
$ sudo rfkill unblock all
$sudo modprobe ath5k (you may have to replace with your driver module e.g ath9k)I found out that the rfkill program is not installed on my ubuntu 9.04 so I had to download the package and installed it manually.
Now, everything works fine!!!
Re: SIOCSIFFLAGS: operation not permitted (Lucid) + unknown code
Thank you for pointing this out! In fact, it seems to be the problem of pre-installed modules. The «original» ones wouldn’t load because of some incompatibility issues with the hardware. Sometimes differs depending on the module that is currently loaded. Thank God who brought us Linux!
Offtopic: I installed XP on my friend’s Compaq notebook, newest model. The sound card wouldn’t be recognized, of course (no drivers for XP). So, first thing to check: ran Xubuntu 10.04 live CD, everything works out of the box. Not hardware issue. I had to install 2 drivers before I found the one for Vista that worked! I mean, I spend about an hour or so, instead, I would prefer to install Ubuntu
But, of course, I am the only one around who uses all kinds of Linux distros… The situation in the nearest future wouldn’t change, sadly! Thanks to the community, however, we become more and more ingenious! YES!
Re: SIOCSIFFLAGS: operation not permitted (Lucid) + unknown code
$sudo rmmod ath5k (you may have to replace with your driver module e.g ath9k)
$ sudo rfkill unblock all
$sudo modprobe ath5k (you may have to replace with your driver module e.g ath9k)I found out that the rfkill program is not installed on my ubuntu 9.04 so I had to download the package and installed it manually.
Now, everything works fine!!!
Mine is DWA-125. By installing driver for rt3070sta from ralink, no problem exists and no need for above commands.
Hope it helps someone.
Last edited by ario; October 17th, 2010 at 07:07 PM.
Presumably you were getting a backtrace like this:
msf6 auxiliary(scanner/portscan/syn) > run
SIOCSIFFLAGS: Operation not permitted
[-] Auxiliary failed: RuntimeError eth0: You don't have permission to capture on that device (socket: Operation not permitted)
[-] Call stack:
[-] /root/Desktop/metasploit-framework/lib/msf/core/exploit/capture.rb:124:in `open_live'
[-] /root/Desktop/metasploit-framework/lib/msf/core/exploit/capture.rb:124:in `open_pcap'
[-] /root/Desktop/metasploit-framework/modules/auxiliary/scanner/portscan/syn.rb:58:in `run_batch'
[-] /root/Desktop/metasploit-framework/lib/msf/core/auxiliary/scanner.rb:205:in `block in run'
[-] /root/Desktop/metasploit-framework/lib/msf/core/thread_manager.rb:105:in `block in spawn'
[*] Auxiliary module execution completed
As you can see I have set the
cap_net_admincapability which is required,
Presumably, after adding capabilities, you receive only the following output:
msf6 auxiliary(scanner/portscan/syn) > run
SIOCSIFFLAGS: Operation not permitted
but I can’t figure out what are those other executables that may require additional capabilities. Could anybody please suggest any info on how I can find this out? Thank you.
The only executable which should require capabilities is the Ruby interpreter (and it should only need cap_net_raw).
setcap cap_net_raw=eip /usr/bin/ruby2.7
Allowing any user to gain cap_net_admin privileges via the Ruby interpreter is probably not a good idea. I suggest removing whichever capabilities you’ve applied.
The interpreter does not drop capabilities.
# pidof ruby2.7
66718
# getpcaps 66718
66718: cap_net_raw=ep
Regardless of the SIOCSIFFLAGS: Operation not permitted output, the cap_net_raw capability is sufficient to craft the raw SYN packets required to use this module.
msf6 > use auxiliary/scanner/portscan/syn
msf6 auxiliary(scanner/portscan/syn) > set rhosts 10.1.1.1
rhosts => 10.1.1.1
msf6 auxiliary(scanner/portscan/syn) > pidof ruby2.7
[*] exec: pidof ruby2.7
67359
msf6 auxiliary(scanner/portscan/syn) > getpcaps 67359
[*] exec: getpcaps 67359
67359: cap_net_raw=ep
msf6 auxiliary(scanner/portscan/syn) > set ports 80-90
ports => 80-90
msf6 auxiliary(scanner/portscan/syn) > run
SIOCSIFFLAGS: Operation not permitted
[+] TCP OPEN 10.1.1.1:80
[*] Scanned 1 of 1 hosts (100% complete)
[*] Auxiliary module execution completed
msf6 auxiliary(scanner/portscan/syn) >
Note that this module is excruciatingly slow.