Well friend
i can't put my eth1 at mode monitor...
Interface Chipset Driver
eth1 Unknown wl - [phy0]mon0: ERROR mientras se obtenían las banderas de interfaz: No existe el dispositivo
(monitor mode enabled on mon0)
and when run the monitor appear:
sudo airodump-ng mon0Interface mon0:
ioctl(SIOCGIFINDEX) failed: No such device
Anyone can helpme?
Few things I can think of, 1st is unsupported chipset! which if you provide info for would be helpful. 2nd is missing libraries or unpatched driver!
Tested and working cards
AWUS036H (rtl8187, r8187) - both mac80211 and IEEE drivers - passed
AWUS036NH (Ralink RT2870/3070) - using the mac80211 rt2x00usb drivers - passed
BCM4312 802.11b/g LP-PHY (rev 01) - using the mac80211 b43, works well - passed
Rockland N3 - (Ralink RT2870/3070) - using the mac80211 rt2x00usb drivers -passed
Edimax EW-7318USG USB - (Ralink RT2501/RT2573) - using the mac80211 rt2500usb/rt73usb drivers -passed
ASUSTek Computer, Inc. RT2573 - using the mac80211 rt2500usb/rt73usb drivers -passed
Linksys WUSB54GC ver 3 - using the mac80211 rt2800usb drivers -passed
Ubiquiti SRC - using the mac80211 ath9k drivers-passed
Internal Intel Corporation PRO/Wireless 3945ABG - using the mac80211 iwl3945 drivers-passed
Dlink WNA-2330 PCMCIA - using the mac80211 ath5k drivers-passed
Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) - using the mac80211 ath9k drivers-passed
Netgear wg111v2 - using the mac80211 rtl8187 drivers-passed
ZyXEL AG-225H v2 - using the mac80211 zd1211 drivers - passed
Intel 4956/5xxx - using the iwlagn drivers - passed
Working, without injection
Broadcom Corporation BCM4321 802.11a/b/g/n (rev 03)
Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
NON working cards
D-Link DWL-122 - using the mac80211 prism2_usb drivers - fail
Linksys WUSB600N v2 - using the mac80211 rt2800usb drivers - fail
AWUS051NH - fail
Your chipset does not support the injection.
try with kali linux http://www.kali.org
Related
Trying to debug ESP32-S3 with PlatformIO on VSCode with macOS on M1.
Installed ftdi drivers from their website. (installed the VCP drivers, not the D3XX ones as I couldn't find a way to compile and install them).
As ESP32-S3 has an internal debugger, I just created a USB that connects D-/D+ pins to the board gpio 19 and 20 (and grd). BTW, when I connect it to the macbook, I dont see any additional port under /dev/*
Getting the following error, regardless of my platform.ini configuration.
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz
adapter speed: 5000 kHz
Info : tcl server disabled
Info : telnet server disabled
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6014, description '*', serial '*' at bus location '*'
.pioinit:11: Error in sourced command file:
Remote connection closed
My platformio.ini:
[env:esp32-s3-devkitc-1]
platform = espressif32
board = esp32-s3-devkitc-1
framework = arduino
upload_port = /dev/cu.wchusbserial553C0085431
monitor_speed=115200
build_type = debug
debug_init_break = tbreak setup
;debug_tool = esp-builtin
debug_tool = esp-prog
Removed and installed the ftdi drivers.
Got a similar error when trying with ESP-IDF.
Any thoughts?
If you are connecting the USB conector directly on esp32s3 module, you should try to change the board parameter from esp32-s3-devkitc-1 to esp32s3-builtin. This way you specify that you are using the built-in debugger.
I'm setting up Linux device to act as BLE host, and ESP32 to work as a BLE controller over UART.
I'm using BlueZ v5.55, with btattach and bluetoothctl utilities, and bluetoothd running in the background. However, after finishing the setup bluetoothctl still says No default controller available.
# /usr/bin/btattach -B /dev/ttymxc1 -S 921600 --protocol h4 &
# Attaching Primary controller to /dev/ttymxc1
Switched line discipline from 0 to 15
Device index 0 attached
# /usr/libexec/bluetooth/bluetoothd
# bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
Output of btmon:
# btmon
Bluetooth monitor ver 5.55
= Note: Linux version 5.4.8 (armv7l) 0.258161
= Note: Bluetooth subsystem version 2.22 0.258269
= New Index: 00:00:00:00:00:00 (Primary,UART,hci0) [hci0] 0.258314
# MGMT Open: bluetoothd (privileged) version 1.14 {0x0001} 0.258357
Output of dmesg during kernel start:
# dmesg | grep Blu
[ 0.643821] Bluetooth: Core ver 2.22
[ 0.644222] Bluetooth: HCI device and connection manager initialized
[ 0.644528] Bluetooth: HCI socket layer initialized
[ 0.644622] Bluetooth: L2CAP socket layer initialized
[ 0.645069] Bluetooth: SCO socket layer initialized
[ 4.678559] Bluetooth: HCI UART driver ver 2.3
[ 4.683346] Bluetooth: HCI UART protocol H4 registered
[ 4.688821] Bluetooth: HCI UART protocol LL registered
The ESP32 is running UART HCI controller firmware: https://github.com/espressif/esp-idf/tree/master/examples/bluetooth/hci/controller_hci_uart
The host is running a Buildroot-created Linux with BR2_PACKAGE_BLUEZ_TOOLS=y and a kernel with CONFIG_BT=y, CONFIG_BT_LE=y, CONFIG_BT_HCIUART=y, CONFIG_BT_HCIUART_H4=y.
I have 4 UART lines connected TX->RX, RX->TX, RTS->CTS and CTS->RTS.
I have checked the UART communication with the same HW setup - I can exchange data over UART with the ESP32 (in both directions).
The commands are run as root.
What am I missing here?
If you have any decent documentation on BlueZ HCI setup, I'll be happy to see it.
EDIT: I also installed hcidump and hciconfig (normally deprecated in BLueZ v5.55). Here is a log from hcidump:
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 5.55
device: hci0 snap_len: 1500 filter: 0xffffffff
< HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
< HCI Command: Read BD ADDR (0x04|0x0009) plen 0
(in 2nd terminal)
# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
After a few days, I have found a solution of this problem.
I have also used nRF52 DK as an alternative to better understand if the problem lies on the side of ESP32 controller, or on the side of Linux host. Because the nRF HCI UART worked on Ubuntu 20.04, but didn't work on my embedded Linux, I looked deeper on the Linux host side.
After starting BlueZ daemon with
bluetoothd -n
it showed more details:
bluetoothd[593]: src/adapter.c:get_static_addr() Failed to open crypto
bluetoothd[593]: No Bluetooth address for index 0
Which led me to this topic: https://github.com/raspberrypi/linux/issues/3628
It turns out, when attaching the UART HCI controller with btattach, BlueZ was not able to create a static address, because of missing Linux kernel crypto interface in user-space.
I compiled the kernel with additional configs:
CONFIG_CRYPTO_USER
CONFIG_CRYPTO_USER_API
CONFIG_CRYPTO_USER_API_AEAD
CONFIG_CRYPTO_USER_API_HASH
CONFIG_CRYPTO_AES
CONFIG_CRYPTO_CCM
CONFIG_CRYPTO_AEAD
CONFIG_CRYPTO_CMAC
After that change, I was able to attach the Bluetooth controller to my Embedded Linux host.
OS: Ubuntu 16.04
Ethernet chip: Intel I210
Ethernet driver: igb
I've looked into my etherent device attribute.
By typing the command
udevadm info -p -a /sys/class/net/eth0
I got the following information:
looking at device '/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/eth0':
KERNEL=="eth0"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="1000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{gro_flush_timeout}=="0"
ATTR{iflink}=="2"
ATTR{addr_len}=="6"
ATTR{address}=="0c:c4:7a:12:b4:e4"
ATTR{operstate}=="up"
ATTR{carrier_changes}=="2"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{dev_port}=="0"
ATTR{ifalias}==""
ATTR{ifindex}=="2"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1c.2/0000:02:00.0':
KERNELS=="0000:02:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="18"
ATTRS{subsystem_vendor}=="0x15d9"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{index}=="1"
ATTRS{label}==" Intel Ethernet controller#1 i210"
ATTRS{driver_override}=="(null)"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f"
ATTRS{device}=="0x1533"
ATTRS{enable}=="1"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-3"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x1533"
ATTRS{numa_node}=="-1"
ATTRS{d3cold_allowed}=="1"
Some questions below:
what is the relationship between "device" and "parent device"
Are these attributes retrieved from firmware ( on device ) or BIOS or driver ?
Is it possible to modify the attribute value ?
I ask this is because as you may know, Ubuntu 15.10 and newer version has taken the rule of predictable network interface names. For the onboard device, it will be recognized as "enox" and x means its index.
Unfortunately, on my host, my two ethernets have the same index and this causes the race condition. If I did not revert back to the original network interface naming rule, the boot is gonna take about 4 mins.
I suspect it's the firmware issue.
I have made a signed USB Serial inf file for a custom device and created an installer that successfully installs the driver to Windows 7 (32/64), Windows 8.1 (64) but not Windows 10. This applies to the default installation (right-click, install) directly on the file, using Device Manager and using PNPUTIL. The device driver successfully installs but the OEM usbser driver is used instead. After clicking "Update Driver" and selecting my driver in Device Manager, Windows prompts me with "The best driver software is already installed for your device". If I use Device Manager and choose "Have Disk" I can successfully get around the issue with Windows 10 enforcing their own driver. This doesn't get me any closer to having a successful inf file and installer though.
My process for default installation:
Unplug the device from the USB port
Load a snap shot of freshly-installed Windows 10 Professional
Right click, install on the .inf file
Plug in the device
Look at Device Manager and see that the standard USB Serial Device driver made by Microsoft is used instead of my driver
If I then uninstall it and repeat steps 3-5 it sometimes allows my custom driver to stick.
I've been told that my driver installs on Windows 10 Enterprise, which confuses matters further.
Question: What am I doing wrong?
My inf file:
;************************************************************
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation
; Version v1.1, updated 17 April 2013
[Strings]
DriverPackageDisplayName="Rinstrum USB Serial Drivers"
ManufacturerName="Rinstrum"
ServiceName="USB RS-232 Emulation Driver"
linux.gserial="Rinstrum USB Gadget Serial"
MFGNAME="Rinstrum"
[DefaultInstall]
CopyINF=c500.inf
[Version]
DriverVer=03/02/2017,1.0.0.0
Signature=$Windows NT$
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
CatalogFile=c500.cat
DriverPackageDisplayName=%DriverPackageDisplayName%
PnpLockdown=1
[Manufacturer]
%MFGNAME%=Models,NTx86,NTamd64,NTarm
[DestinationDirs]
DefaultDestDir=12
FakeModemCopyFileSection=12
[Models.NTx86]
%linux.gserial%=DriverInstall, USB\VID_1FC9&PID_816A, USB\VID_1FC9&PID_816A&MI_00
[Models.NTamd64]
%linux.gserial%=DriverInstall, USB\VID_1FC9&PID_816A, USB\VID_1FC9&PID_816A&MI_00
[Models.NTarm]
%linux.gserial%=DriverInstall, USB\VID_1FC9&PID_816A, USB\VID_1FC9&PID_816A&MI_00
[DriverInstall]
Include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=DriverAddReg
[DriverAddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
[DriverInstall.Services]
Include=mdmcpq.inf
AddService=usbser,0x2,DriverService
[DriverService]
DisplayName=%ServiceName%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\usbser.sys
LoadOrderGroup=Base
Update: additional info from setupapi.dev.log
>>> [Device Install (DiInstallDriver) - C:\Users\R&D\Desktop\c500.inf]
>>> Section start 2017/02/03 17:17:58.321
cmd: "C:\Windows\System32\InfDefaultInstall.exe" "C:\Users\R&D\Desktop\c500.inf"
ndv: Flags: 0x00000000
ndv: INF path: C:\Users\R&D\Desktop\c500.inf
inf: {SetupCopyOEMInf: C:\Users\R&D\Desktop\c500.inf} 17:17:58.337
inf: Copy style: 0x00000000 !
inf: Driver package is already in driver store
inf: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\c500.inf_amd64_4fee793fb11027ac\c500.inf inf: Published Inf Path: C:\Windows\INF\oem4.inf
inf: {SetupCopyOEMInf exit (0x00000000)} 17:17:58.368
<<< Section end 2017/02/03 17:17:58.399
<<< [Exit status: SUCCESS]
Update:
setupapi.dev.log gives the following error when trying to install the device
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
Update:
The VBox guest additions installer manages to install my inf file in WIN10. Here is the source:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/WINNT/Installer/VBoxDrvInst.cpp#L433
Windows needs to be activated before the user is granted the permission to override the OEM drivers in Windows 10. Activating windows on my test machine solved this issue.
Try setting your DriverVer directive correctly, with today's date and 1.0.0.0. The date is one thing that Windows looks at when deciding what driver to use.
I saw there are several discussions on the subject but none of them managed to help me solve mine.
I am trying to compile my Matlab proj. without much success.
I saw this video and pretty much followed it guidances: -> I used 'deploytool'.
When I tried to build the project, I got the below plot. The line has been showed a lot:
2013-03-10 14:29:21.014 mcc[39814:4303] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
Some discussions stated I need to do write "sudu matlab" somewhere but I do not know where...
Compilation plot:
ant:
mcc -o Untitled1 -W main:Untitled1 -T link:exe -d /Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src -w enable:specified_file_mismatch -w enable:repeated_file -w enable:switch_ignored -w enable:missing_lib_sentinel -w enable:demo_license -v /Users/Nimrod/Documents/MATLAB/Temp/temp.m
2013-03-10 14:29:17.073 mcc[39814:4303] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
2013-03-10 14:29:17.075 mcc[39814:4303] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
2013-03-10 14:29:41.167 mcc[39814:4303] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
Compiler version: 4.18 (R2012b)
Processing /Applications/MATLAB_R2012b.app/toolbox/matlab/mcc.enc
Processing /Applications/MATLAB_R2012b.app/toolbox/shared/spcuilib/mcc.enc
Processing include files...
2 item(s) added.
Processing directories installed with MCR...
The file /Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src/mccExcludedFiles.log contains a list of functions excluded from the CTF archive.
0 item(s) added.
Generating MATLAB path for the compil ed application...
Created 39 path items.
Begin validation of MEX files: Sun Mar 10 14:30:16 2013
End validation of MEX files: Sun Mar 10 14:30:16 2013
2013-03-10 14:30:16.783 mcc[39814:4303] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
2013-03-10 14:30:39.015 mcc[39814:4303] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
Warning: Adding path "/Users/Nimrod/Documents/MATLAB/Temp" to Compiler path
instance.
Parsing file "/Users/Nimrod/Documents/MATLAB/Temp/temp.m"
(Referenced from: "Compiler Command Line").
Parsing file "/Applications/MATLAB_R2012b.app/toolbox/compiler/deploy/deployprint.m"
(Referenced from: "Compiler Command Line").
Parsing file "/Applications/MATLAB_R2012b.app/toolbox/compiler/deploy/printdlg.m"
(Referenced from: "Compiler Command Line").
Deleting 0 temporary MEX authorization files.
Generating file "/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src/readme.txt".
Generating file "/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src/run_Untitled1.sh".
copy '/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src/Untitled1.app' '/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/distrib/Untitled1.app'
copy '/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src/run_Untitled1.sh' '/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/distrib/run_Untitled1.sh'
copy '/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/src/readme.txt' '/Users/Nimrod/Documents/MATLAB/Temp/Untitled1/distrib/readme.txt'
When trying to run the app file I get the following crash:
Process: prelaunch [39864]
Path: /Users/USER/Documents/*/Untitled1.app/Contents/MacOS/prelaunch
Identifier: Untitled1
Version: 1
Code Type: X86-64 (Native)
Parent Process: launchd [134]
User ID: 501
Date/Time: 2013-03-10 14:37:28.848 +0200
OS Version: Mac OS X 10.8.2 (12C2034)
Report Version: 10
Interval Since Last Report: 9226 sec
Crashes Since Last Report: 5
Per-App Crashes Since Last Report: 5
Anonymous UUID: 6DB02735-2968-B918-129B-82542E2D0F24
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: #rpath/libmwcpp11compat.dylib
Referenced from: /Users/USER/Documents/*/Untitled1.app/Contents/MacOS/prelaunch
Reason: image not found
Binary Images:
0x100000000 - 0x100000ff7 +Untitled1 (1) /Users/USER/Documents/*/Untitled1.app/Contents/MacOS/prelaunch
0x7fff6205c000 - 0x7fff6209093f dyld (210.2.3) <36CAA36E-72BC-3E48-96D9-B96A2DF77730> /usr/lib/dyld
Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.1f173
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.14)
Bluetooth: Version 4.1.2f9 11046, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci11c1,5901, sppci_ieee1394openhci, Thunderbolt#62,0,0
PCI Card: Apple 57761-B0, sppci_ethernet, Thunderbolt#61,0,0
PCI Card: pci12d8,400e, sppci_usbopenhost, Thunderbolt#60,0,0
PCI Card: pci12d8,400e, sppci_usbopenhost, Thunderbolt#60,0,1
PCI Card: pci12d8,400f, USB Enhanced Host Controller, Thunderbolt#60,0,2
Serial ATA Device: APPLE HDD HTS547575A9E384, 750.16 GB
Serial ATA Device: HL-DT-ST DVDRW GS31N
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0x1d180000 / 3
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 6
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0253, 0x1d183000 / 5
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 4
USB Device: hub_device, apple_vendor_id, 0x9127, 0x40100000 / 2
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0x40130000 / 6
USB Device: Apple Keyboard, apple_vendor_id, 0x0250, 0x40132000 / 7
USB Device: Display Audio, apple_vendor_id, 0x1107, 0x40140000 / 5
USB Device: FaceTime HD Camera (Display), apple_vendor_id, 0x1112, 0x40150000 / 4
USB Device: Apple Thunderbolt Display, apple_vendor_id, 0x9227, 0x40170000 / 3