Modify ↓
#13033 closed defect (fixed)
Reaver problem with monitor mode
| Reported by: | d.buffa@… | Owned by: | developers |
|---|---|---|---|
| Priority: | response-needed | Milestone: | Chaos Calmer 15.05 |
| Component: | base system | Version: | Trunk |
| Keywords: | Cc: |
Description
Hi,
I would report an issue using Reaver (but also wifite.py, and I think other similar scripts) with the "native" monitor mode of ath5k (at least I found the issue on this hardware).
Using reaver, in particular the wash command, ath5k goes in error and I didn't found a way to restore it if not rebooting the whole router. I have also the issue with reaver command, in this case after few minutes. When the issue occurred this is what I have on dmesg
[ 308.750000] net_ratelimit: 8 callbacks suppressed [ 308.750000] ath5k: phy0: invalid tx power: 70 [ 308.760000] ath5k: phy0: failed to initialize PHY (-22) ! [ 308.760000] ath5k: phy0: can't reset hardware (-22) [ 309.750000] ath5k: phy0: invalid tx power: 70 [ 309.750000] ath5k: phy0: failed to initialize PHY (-22) ! [ 309.760000] ath5k: phy0: can't reset hardware (-22) [ 310.750000] ath5k: phy0: invalid tx power: 70 [ 310.750000] ath5k: phy0: failed to initialize PHY (-22) ! [ 310.760000] ath5k: phy0: can't reset hardware (-22) [ 311.750000] ath5k: phy0: invalid tx power: 70 [ 314.750000] net_ratelimit: 8 callbacks suppressed [ 314.750000] ath5k: phy0: invalid tx power: 70 [ 314.760000] ath5k: phy0: failed to initialize PHY (-22) ! [ 314.760000] ath5k: phy0: can't reset hardware (-22) [ 315.750000] ath5k: phy0: invalid tx power: 70 [ 315.750000] ath5k: phy0: failed to initialize PHY (-22) ! [ 315.760000] ath5k: phy0: can't reset hardware (-22) [ 316.750000] ath5k: phy0: invalid tx power: 70 [ 316.750000] ath5k: phy0: failed to initialize PHY (-22) ! [ 316.760000] ath5k: phy0: can't reset hardware (-22) [ 317.750000] ath5k: phy0: invalid tx power: 70 [ 320.750000] net_ratelimit: 8 callbacks suppressed [ 320.750000] ath5k: phy0: invalid tx power: 70 [ 320.760000] ath5k: phy0: failed to initialize PHY (-22) ! [ 320.760000] ath5k: phy0: can't reset hardware (-22) [ 321.780000] ath5k: phy0: invalid tx power: 70 [ 321.780000] ath5k: phy0: failed to initialize PHY (-22) ! [ 321.790000] ath5k: phy0: can't reset hardware (-22) [ 322.390000] device wlan0 left promiscuous mode [ 323.680000] ath5k: phy0: invalid tx power: 70 [ 323.680000] ath5k: phy0: failed to initialize PHY (-22) ! [ 323.690000] ath5k: phy0: can't reset hardware (-22) [ 323.690000] ath5k: phy0: invalid tx power: 70
because I know that someone could suggest it, Regdomain was not hacked
[ 30.720000] ath5k 0000:00:11.0: registered as 'phy0' [ 31.350000] ath: EEPROM regdomain: 0x0 [ 31.350000] ath: EEPROM indicates default country code should be used [ 31.350000] ath: doing EEPROM country->regdmn map search [ 31.350000] ath: country maps to regdmn code: 0x3a [ 31.350000] ath: Country alpha2 being used: US [ 31.350000] ath: Regpair used: 0x3a [ 31.350000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 31.350000] ath5k: phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61) [ 31.360000] cfg80211: Calling CRDA for country: US [ 31.360000] cfg80211: Regulatory domain changed to country: US [ 31.370000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 31.370000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 31.380000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 31.390000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.400000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.410000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.410000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
The issue was found on RouterStationPro hardware with Ubiquiti XR2 card and revision r35593 and I think was recently introduced, because this is the first time I see it.
I conclude by saying the monitor mode enabled with airmon-ng is useless for reaver (wash doesn't show any results!)
I remain at your disposal for questions
Daniele Buffa.
Attachments (0)
Change History (20)
comment:1 Changed 5 years ago by anonymous
comment:2 Changed 5 years ago by nbd
- Priority changed from highest to response-needed
please try latest trunk
comment:3 Changed 5 years ago by anonymous
I'm trying to build latest trunk but I have an error due to unavailability of a git repository
make[3]: Entering directory `/home/daniele/dev/openwrt/trunk/package/network/config/netifd' mkdir -p /home/daniele/dev/openwrt/trunk/dl echo "Checking out files from the git repository..."; mkdir -p /home/daniele/dev/openwrt/trunk/tmp/dl && cd /home/daniele/dev/openwrt/trunk/tmp/dl && rm -rf netifd-2013-02-19 && [ \! -d netifd-2013-02-19 ] && git clone git://nbd.name/luci2/netifd.git netifd-2013-02-19 --recursive && (cd netifd-2013-02-19 && git checkout 486aa750a164d41905beb61afec89268e3eb7f48) && echo "Packing checkout..." && rm -rf netifd-2013-02-19/.git && /bin/gtar czf /home/daniele/dev/openwrt/trunk/tmp/dl/netifd-2013-02-19-486aa750a164d41905beb61afec89268e3eb7f48.tar.gz netifd-2013-02-19 && mv /home/daniele/dev/openwrt/trunk/tmp/dl/netifd-2013-02-19-486aa750a164d41905beb61afec89268e3eb7f48.tar.gz /home/daniele/dev/openwrt/trunk/dl/ && rm -rf netifd-2013-02-19; Checking out files from the git repository... Cloning into 'netifd-2013-02-19'... fatal: unable to connect to nbd.name: nbd.name[0: 46.4.11.11]: errno=Connection timed out make[3]: *** [/home/daniele/dev/openwrt/trunk/dl/netifd-2013-02-19-486aa750a164d41905beb61afec89268e3eb7f48.tar.gz] Error 128 make[3]: Leaving directory `/home/daniele/dev/openwrt/trunk/package/network/config/netifd' make[2]: *** [package/network/config/netifd/compile] Error 2 make[2]: Leaving directory `/home/daniele/dev/openwrt/trunk' make[1]: *** [/home/daniele/dev/openwrt/trunk/staging_dir/target-mips_r2_uClibc-0.9.33.2/stamp/.package_compile] Error 2 make[1]: Leaving directory `/home/daniele/dev/openwrt/trunk' make: *** [world] Errore 2
I'll try later
comment:4 Changed 5 years ago by nbd
nbd.name is up again
comment:5 Changed 5 years ago by nbd
- Resolution set to fixed
- Status changed from new to closed
monitor mode injection is confirmed to be fixed in recent versions
comment:6 Changed 5 years ago by d.buffa@…
- Resolution fixed deleted
- Status changed from closed to reopened
Sorry for the delay, I tried now with r35820, and I have the same identical behaviour
[ 402.060000] device wlan0 entered promiscuous mode [ 414.080000] ath5k: phy0: invalid tx power: 70 [ 415.080000] ath5k: phy0: invalid tx power: 70 [ 415.080000] ath5k: phy0: failed to initialize PHY (-22) ! [ 415.090000] ath5k: phy0: can't reset hardware (-22) [ 416.080000] ath5k: phy0: invalid tx power: 70 [ 416.080000] ath5k: phy0: failed to initialize PHY (-22) ! [ 416.090000] ath5k: phy0: can't reset hardware (-22) [ 417.080000] ath5k: phy0: invalid tx power: 70 [ 417.080000] ath5k: phy0: failed to initialize PHY (-22) ! [ 417.090000] ath5k: phy0: can't reset hardware (-22) [ 420.080000] net_ratelimit: 6 callbacks suppressed [ 420.080000] ath5k: phy0: invalid tx power: 70 [ 420.090000] ath5k: phy0: failed to initialize PHY (-22) ! [ 420.090000] ath5k: phy0: can't reset hardware (-22) [ 421.080000] ath5k: phy0: invalid tx power: 70 [ 421.080000] ath5k: phy0: failed to initialize PHY (-22) ! [ 421.090000] ath5k: phy0: can't reset hardware (-22) [ 422.080000] ath5k: phy0: invalid tx power: 70 [ 422.080000] ath5k: phy0: failed to initialize PHY (-22) ! [ 422.090000] ath5k: phy0: can't reset hardware (-22) [ 423.080000] ath5k: phy0: invalid tx power: 70 [ 426.080000] net_ratelimit: 8 callbacks suppressed [ 426.080000] ath5k: phy0: invalid tx power: 70 [ 426.090000] ath5k: phy0: failed to initialize PHY (-22) ! [ 426.090000] ath5k: phy0: can't reset hardware (-22) [ 427.000000] device wlan0 left promiscuous mode
Tell me if you need more information.
Thanks
Daniele Buffa.
comment:7 Changed 5 years ago by nbd
do you have any regulatory database hacks on your system?
comment:8 Changed 5 years ago by d.buffa@…
No,
I tried with and without regulatory database hack, same issue. Now, after flashing r35820, I have no hack at all.
Unfortunately the only ath5k hardware I have is Ubiquiti XR2...
comment:9 Changed 5 years ago by anonymous
Later I'll try another hardware, always XR2...
comment:10 Changed 5 years ago by nbd
it does not make any sense to me that it's trying to set a txpower of 35 dBm. are you sure it's not a local build issue? did you try flashing a snapshot build?
comment:11 Changed 5 years ago by anonymous
I build my own images, anyway I can test a snapshot build. I'll try it. I don't know where it take 35 dBm value, with the regulaory database hack I use 30 dBm and when I tried the r35820 15...
I must tell you something.
comment:12 Changed 5 years ago by d.buffa@…
Tried also on another hardware (Ubiquiti RouterStationPro) with another Ubiquiti XR2 card.
This is the full boot log
[ 0.000000] Linux version 3.7.9 (daniele@danfedvm.localdomain) (gcc version 4.6.4 20121210 (prerelease) (Linaro GCC 4.6-2012.12) ) #1 Wed Feb 27 21:26:41 CET 2013 [ 0.000000] MyLoader: sysp=00000000, boardp=00000000, parts=ace50014 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU revision is: 00019374 (MIPS 24Kc) [ 0.000000] SoC: Atheros AR7161 rev 2 [ 0.000000] Clocks: CPU:720.000MHz, DDR:360.000MHz, AHB:180.000MHz, Ref:40.000MHz [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 08000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x00000000-0x07ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x07ffffff] [ 0.000000] On node 0 totalpages: 32768 [ 0.000000] free_area_init_node: node 0, pgdat 802efc90, node_mem_map 81000000 [ 0.000000] Normal zone: 256 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32512 pages, LIFO batch:7 [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: board=UBNT-RSPRO console=ttyS0,115200 ethaddr=00.15.6d.c1.c7.69 rootfstype=squashfs,jffs2 noinitrd [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] __ex_table already sorted, skipping sort [ 0.000000] Writing ErrCtl register=00002002 [ 0.000000] Readback ErrCtl register=00002002 [ 0.000000] Memory: 126384k/131072k available (2135k kernel code, 4688k reserved, 577k data, 228k init, 0k highmem) [ 0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:51 [ 0.050000] Calibrating delay loop... 479.23 BogoMIPS (lpj=2396160) [ 0.060000] pid_max: default: 32768 minimum: 301 [ 0.060000] Mount-cache hash table entries: 512 [ 0.070000] NET: Registered protocol family 16 [ 0.070000] MIPS: machine is Ubiquiti RouterStation Pro [ 0.380000] registering PCI controller with io_map_base unset [ 2.680000] bio: create slab <bio-0> at 0 [ 2.690000] PCI host bridge to bus 0000:00 [ 2.690000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x16ffffff] [ 2.700000] pci_bus 0000:00: root bus resource [io 0x0000] [ 2.700000] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff] [ 2.710000] pci 0000:00:11.0: [168c:001b] type 00 class 0x020000 [ 2.710000] pci 0000:00:11.0: reg 10: [mem 0x00000000-0x0000ffff] [ 2.710000] pci 0000:00:12.0: [168c:001b] type 00 class 0x020000 [ 2.710000] pci 0000:00:12.0: reg 10: [mem 0x00000000-0x0000ffff] [ 2.710000] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00 [ 2.710000] pci 0000:00:11.0: BAR 0: assigned [mem 0x10000000-0x1000ffff] [ 2.710000] pci 0000:00:12.0: BAR 0: assigned [mem 0x10010000-0x1001ffff] [ 2.720000] pci 0000:00:11.0: using irq 40 for pin 1 [ 2.720000] pci 0000:00:12.0: using irq 41 for pin 1 [ 2.730000] Switching to clocksource MIPS [ 2.730000] NET: Registered protocol family 2 [ 2.740000] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 2.740000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [ 2.750000] TCP: Hash tables configured (established 4096 bind 4096) [ 2.750000] TCP: reno registered [ 2.750000] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 2.760000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 2.770000] NET: Registered protocol family 1 [ 2.770000] PCI: CLS 0 bytes, default 32 [ 2.780000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 2.790000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 2.800000] msgmni has been set to 246 [ 2.800000] io scheduler noop registered [ 2.810000] io scheduler deadline registered (default) [ 2.810000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled [ 2.840000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A [ 2.840000] console [ttyS0] enabled, bootconsole disabled [ 2.860000] ath79-spi ath79-spi: master is unqueued, this is deprecated [ 2.860000] m25p80 spi0.0: found mx25l12805d, expected m25p80 [ 2.870000] m25p80 spi0.0: mx25l12805d (16384 Kbytes) [ 2.880000] Searching for RedBoot partition table in spi0.0 at offset 0xfe0000 [ 2.900000] Searching for RedBoot partition table in spi0.0 at offset 0xff0000 [ 2.930000] 5 RedBoot partitions found on MTD device spi0.0 [ 2.940000] Creating 5 MTD partitions on "spi0.0": [ 2.940000] 0x000000000000-0x000000030000 : "RedBoot" [ 2.950000] 0x000000030000-0x000000130000 : "kernel" [ 2.960000] 0x000000130000-0x000000ff0000 : "rootfs" [ 2.960000] mtd: partition "rootfs" set to be root filesystem [ 2.970000] mtd: partition "rootfs_data" created automatically, ofs=490000, len=B60000 [ 2.980000] 0x000000490000-0x000000ff0000 : "rootfs_data" [ 2.980000] 0x000000ff0000-0x000000fff000 : "FIS directory" [ 2.990000] 0x000000fff000-0x000001000000 : "RedBoot config" [ 3.020000] switch0: Atheros AR8316 switch registered on ag71xx-mdio.0 [ 3.030000] libphy: ag71xx_mdio: probed [ 3.040000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII [ 3.350000] ar8316: Using port 4 as PHY [ 3.350000] ag71xx ag71xx.0 eth0: connected to PHY at ag71xx-mdio.0:04 [uid=004dd041, driver=Atheros AR8216/AR8236/AR8316] [ 3.360000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RGMII [ 3.670000] ar8316: Using port 4 as PHY [ 3.760000] ag71xx ag71xx.1 eth1: connected to PHY at ag71xx-mdio.0:00 [uid=004dd041, driver=Atheros AR8216/AR8236/AR8316] [ 3.770000] TCP: cubic registered [ 3.770000] NET: Registered protocol family 17 [ 3.780000] 8021q: 802.1Q VLAN Support v1.8 [ 3.790000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. [ 3.800000] Freeing unused kernel memory: 228k freed [ 5.170000] Registered led device: ubnt:green:rf [ 8.390000] jffs2: notice: (422) jffs2_build_xattr_subsystem: complete building xattr subsystem, 24 of xdatum (0 unchecked, 23 orphan) and 36 of xref (0 dead, 23 orphan) found. [ 8.740000] SCSI subsystem initialized [ 8.880000] usbcore: registered new interface driver usbfs [ 8.890000] usbcore: registered new interface driver hub [ 8.890000] usbcore: registered new device driver usb [ 9.200000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 9.200000] ehci-platform ehci-platform: Generic Platform EHCI Controller [ 9.210000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 [ 9.250000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 [ 9.270000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 [ 9.270000] hub 1-0:1.0: USB hub found [ 9.280000] hub 1-0:1.0: 2 ports detected [ 9.340000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 9.340000] ohci-platform ohci-platform: Generic Platform OHCI Controller [ 9.350000] ohci-platform ohci-platform: new USB bus registered, assigned bus number 2 [ 9.360000] ohci-platform ohci-platform: irq 14, io mem 0x1c000000 [ 9.430000] hub 2-0:1.0: USB hub found [ 9.430000] hub 2-0:1.0: 2 ports detected [ 9.470000] Initializing USB Mass Storage driver... [ 9.480000] usbcore: registered new interface driver usb-storage [ 9.490000] USB Mass Storage support registered. [ 9.620000] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 9.770000] scsi0 : usb-storage 1-1:1.0 [ 9.890000] usb 1-2: new high-speed USB device number 3 using ehci-platform [ 10.040000] usb-storage 1-2:1.0: Quirks match for vid 05e3 pid 0723: 8000 [ 10.050000] scsi1 : usb-storage 1-2:1.0 [ 10.770000] scsi 0:0:0:0: Direct-Access TOSHIBA External USB 3.0 0201 PQ: 0 ANSI: 6 [ 10.780000] sd 0:0:0:0: [sda] 976773164 512-byte logical blocks: (500 GB/465 GiB) [ 10.780000] sd 0:0:0:0: [sda] Write Protect is off [ 10.790000] sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00 [ 10.790000] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 10.870000] sda: sda1 sda2 sda3 [ 10.880000] sd 0:0:0:0: [sda] Attached SCSI disk [ 11.050000] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 9451 PQ: 0 ANSI: 0 [ 11.060000] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 30.800000] Compat-drivers backport release: compat-drivers-2013-01-21-1 [ 30.810000] Backport based on wireless-testing.git master-2013-02-22 [ 30.820000] compat.git: wireless-testing.git [ 30.930000] cfg80211: Calling CRDA to update world regulatory domain [ 30.980000] cfg80211: World regulatory domain updated: [ 30.980000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 30.990000] cfg80211: (2402000 KHz - 2494000 KHz @ 40000 KHz), (500 mBi, 3500 mBm) [ 31.000000] cfg80211: (4910000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3500 mBm) [ 31.420000] PCI: Enabling device 0000:00:11.0 (0000 -> 0002) [ 31.430000] ath5k 0000:00:11.0: registered as 'phy0' [ 32.070000] ath: EEPROM regdomain: 0x0 [ 32.070000] ath: EEPROM indicates default country code should be used [ 32.070000] ath: doing EEPROM country->regdmn map search [ 32.070000] ath: country maps to regdmn code: 0x3a [ 32.070000] ath: Country alpha2 being used: US [ 32.070000] ath: Regpair used: 0x3a [ 32.070000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 32.070000] ath5k: phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61) [ 32.080000] PCI: Enabling device 0000:00:12.0 (0000 -> 0002) [ 32.080000] ath5k 0000:00:12.0: registered as 'phy1' [ 32.090000] cfg80211: Calling CRDA for country: US [ 32.090000] cfg80211: Regulatory domain changed to country: US [ 32.100000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 32.110000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 32.110000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 32.120000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 32.130000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 32.140000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 32.150000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 32.800000] ath: EEPROM regdomain: 0x0 [ 32.800000] ath: EEPROM indicates default country code should be used [ 32.800000] ath: doing EEPROM country->regdmn map search [ 32.800000] ath: country maps to regdmn code: 0x3a [ 32.800000] ath: Country alpha2 being used: US [ 32.800000] ath: Regpair used: 0x3a [ 32.800000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 32.800000] ath5k: phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61) [ 33.180000] PPP generic driver version 2.4.2 [ 33.200000] tun: Universal TUN/TAP device driver, 1.6 [ 33.200000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 33.400000] ip_tables: (C) 2000-2006 Netfilter Core Team [ 33.540000] NET: Registered protocol family 24 [ 33.630000] nf_conntrack version 0.5.0 (1978 buckets, 7912 max) [ 34.200000] xt_time: kernel timezone is -0000 [ 34.520000] usbcore: registered new interface driver cdc_acm [ 34.530000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 34.610000] usbcore: registered new interface driver usbserial [ 34.610000] usbcore: registered new interface driver usbserial_generic [ 34.620000] usbserial: USB Serial support registered for generic [ 34.700000] usbcore: registered new interface driver ums-alauda [ 34.720000] usbcore: registered new interface driver ums-cypress [ 34.760000] usbcore: registered new interface driver ums-datafab [ 34.780000] usbcore: registered new interface driver ums-freecom [ 34.790000] usbcore: registered new interface driver ums-isd200 [ 34.810000] usbcore: registered new interface driver ums-jumpshot [ 34.820000] usbcore: registered new interface driver ums-karma [ 34.840000] usbcore: registered new interface driver ums-sddr09 [ 34.850000] usbcore: registered new interface driver ums-sddr55 [ 34.870000] usbcore: registered new interface driver ums-usbat [ 34.950000] usbcore: registered new interface driver option [ 34.950000] usbserial: USB Serial support registered for GSM modem (1-port) [ 35.090000] u32 classifier [ 35.100000] Performance counters on [ 35.100000] input device check on [ 35.100000] Actions configured [ 35.210000] Mirror/redirect action on [ 37.360000] EXT4-fs (sda3): warning: maximal mount count reached, running e2fsck is recommended [ 37.650000] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 39.160000] device eth1 entered promiscuous mode [ 40.370000] ar71xx: pll_reg 0xb8050014: 0x110000 [ 40.370000] eth1: link up (1000Mbps/Full duplex) [ 40.380000] br-lan: port 1(eth1) entered forwarding state [ 40.390000] br-lan: port 1(eth1) entered forwarding state [ 42.080000] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities [ 42.090000] EXT4-fs (sda2): couldn't mount as ext2 due to feature incompatibilities [ 42.120000] EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended [ 42.130000] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 42.390000] br-lan: port 1(eth1) entered forwarding state [ 45.340000] device wlan0 entered promiscuous mode [ 45.520000] br-lan: port 2(wlan0) entered forwarding state [ 45.530000] br-lan: port 2(wlan0) entered forwarding state [ 47.530000] br-lan: port 2(wlan0) entered forwarding state [ 48.450000] device wlan1 entered promiscuous mode [ 48.640000] br-lan: port 3(wlan1) entered forwarding state [ 48.640000] br-lan: port 3(wlan1) entered forwarding state [ 50.640000] br-lan: port 3(wlan1) entered forwarding state [ 90.820000] device wlan1.sta1 entered promiscuous mode [ 90.820000] br-lan: port 4(wlan1.sta1) entered forwarding state [ 90.830000] br-lan: port 4(wlan1.sta1) entered forwarding state [ 92.830000] br-lan: port 4(wlan1.sta1) entered forwarding state
This is wifi hardware capabilities
root@ApCasa:/store# iw list
Wiphy phy1
Band 1:
Frequencies:
* 5040 MHz [8] (disabled)
* 5060 MHz [12] (disabled)
* 5080 MHz [16] (disabled)
* 5180 MHz [36] (17.0 dBm)
* 5200 MHz [40] (17.0 dBm)
* 5220 MHz [44] (17.0 dBm)
* 5240 MHz [48] (17.0 dBm)
* 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
* 5745 MHz [149] (30.0 dBm)
* 5765 MHz [153] (30.0 dBm)
* 5785 MHz [157] (30.0 dBm)
* 5805 MHz [161] (30.0 dBm)
* 5825 MHz [165] (30.0 dBm)
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
max scan IEs length: 2289 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 2048, #{ AP, mesh point } <= 4, #{ IBSS } <= 1,
total <= 2048, #channels <= 1
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* Unknown command (89)
* Unknown command (92)
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* (null): 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* (null): 0x40 0xd0
Device supports RSN-IBSS.
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Wiphy phy0
Band 1:
Frequencies:
* 2412 MHz [1] (27.0 dBm)
* 2417 MHz [2] (27.0 dBm)
* 2422 MHz [3] (27.0 dBm)
* 2427 MHz [4] (27.0 dBm)
* 2432 MHz [5] (27.0 dBm)
* 2437 MHz [6] (27.0 dBm)
* 2442 MHz [7] (27.0 dBm)
* 2447 MHz [8] (27.0 dBm)
* 2452 MHz [9] (27.0 dBm)
* 2457 MHz [10] (27.0 dBm)
* 2462 MHz [11] (27.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 2048, #{ AP, mesh point } <= 4, #{ IBSS } <= 1,
total <= 2048, #channels <= 1
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* Unknown command (89)
* Unknown command (92)
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* (null): 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* (null): 0x40 0xd0
Device supports RSN-IBSS.
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Txpower is setted to 20 dBm, so I switched in monitor mode, started wash -i wan0 and after approximately ten seconds and a couple of access point discovered, ath5k crashed
[ 293.800000] br-lan: port 4(wlan1.sta1) entered disabled state [ 293.850000] device wlan1 left promiscuous mode [ 293.850000] br-lan: port 3(wlan1) entered disabled state [ 295.950000] device wlan1 entered promiscuous mode [ 296.140000] br-lan: port 2(wlan1) entered forwarding state [ 296.150000] br-lan: port 2(wlan1) entered forwarding state [ 298.150000] br-lan: port 2(wlan1) entered forwarding state [ 300.280000] device wlan1.sta1 entered promiscuous mode [ 300.280000] br-lan: port 3(wlan1.sta1) entered forwarding state [ 300.290000] br-lan: port 3(wlan1.sta1) entered forwarding state [ 302.290000] br-lan: port 3(wlan1.sta1) entered forwarding state [ 325.090000] device wlan0 entered promiscuous mode [ 337.110000] ath5k: phy0: invalid tx power: 70 [ 338.110000] ath5k: phy0: invalid tx power: 70 [ 338.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 338.120000] ath5k: phy0: can't reset hardware (-22) [ 339.110000] ath5k: phy0: invalid tx power: 70 [ 339.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 339.120000] ath5k: phy0: can't reset hardware (-22) [ 340.110000] ath5k: phy0: invalid tx power: 70 [ 340.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 340.120000] ath5k: phy0: can't reset hardware (-22) [ 343.110000] net_ratelimit: 6 callbacks suppressed [ 343.110000] ath5k: phy0: invalid tx power: 70 [ 343.120000] ath5k: phy0: failed to initialize PHY (-22) ! [ 343.120000] ath5k: phy0: can't reset hardware (-22) [ 344.110000] ath5k: phy0: invalid tx power: 70 [ 344.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 344.120000] ath5k: phy0: can't reset hardware (-22) [ 345.110000] ath5k: phy0: invalid tx power: 70 [ 345.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 345.120000] ath5k: phy0: can't reset hardware (-22) [ 346.110000] ath5k: phy0: invalid tx power: 70 [ 349.110000] net_ratelimit: 8 callbacks suppressed [ 349.110000] ath5k: phy0: invalid tx power: 70 [ 349.120000] ath5k: phy0: failed to initialize PHY (-22) ! [ 349.120000] ath5k: phy0: can't reset hardware (-22) [ 350.110000] ath5k: phy0: invalid tx power: 70 [ 350.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 350.120000] ath5k: phy0: can't reset hardware (-22) [ 351.110000] ath5k: phy0: invalid tx power: 70 [ 351.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 351.120000] ath5k: phy0: can't reset hardware (-22) [ 352.110000] ath5k: phy0: invalid tx power: 70 [ 355.110000] net_ratelimit: 8 callbacks suppressed [ 355.110000] ath5k: phy0: invalid tx power: 70 [ 355.120000] ath5k: phy0: failed to initialize PHY (-22) ! [ 355.120000] ath5k: phy0: can't reset hardware (-22) [ 356.110000] ath5k: phy0: invalid tx power: 70 [ 356.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 356.120000] ath5k: phy0: can't reset hardware (-22) [ 357.110000] ath5k: phy0: invalid tx power: 70 [ 357.110000] ath5k: phy0: failed to initialize PHY (-22) ! [ 357.120000] ath5k: phy0: can't reset hardware (-22) [ 358.110000] ath5k: phy0: invalid tx power: 70 [ 358.730000] device wlan0 left promiscuous mode
And I have to reboot the router!
I tried also snapshot, but unfortunately there is no ath5k driver build in it.
Daniele.
comment:13 Changed 5 years ago by nbd
you can install the ath5k driver with opkg
comment:14 Changed 5 years ago by d.buffa@…
you're right, I did not think... I'll try later.
D,
comment:15 Changed 5 years ago by anonymous
The snaphot seems to be working like a charme, I tried my own build also doing a factory reset and I have the issue. Does not make sense for me, I didn't changed anything regardless wireless
I'll try with a clean compile... have you any advice for me, something that i can check to solve this issue?
comment:16 Changed 5 years ago by d.buffa@…
ok,
tried with a clean build, it's fixed, you can close.
Thanks
D.
comment:17 Changed 5 years ago by nbd
- Resolution set to fixed
- Status changed from reopened to closed
comment:18 Changed 3 years ago by valery
Hi,
This problem with nbd.name is visible again:
Checking out files from the git repository...
Cloning into 'ubus-2015-01-22'...
fatal: unable to connect to nbd.name:
nbd.name[0: 46.4.11.11]: errno=Connection refused
comment:19 Changed 3 years ago by thomas.ganahl@…
- Resolution fixed deleted
- Status changed from closed to reopened
Hi,
i have the same problem again:
Cloning into 'ubus'... fatal: unable to connect to nbd.name: nbd.name[0: 46.4.11.11]: errno=Connection refused
Can anybody help me or is there a mirror where i can get this repository?
Best Regards
Thomas
comment:20 Changed 3 years ago by nbd
- Resolution set to fixed
- Status changed from reopened to closed
looks like you reopened the wrong ticket.
Note: See
TracTickets for help on using
tickets.
Because the subject could lead to misunderstandings, the error does not depend on reaver but the monitor mode used with reaver