Cannot connect ESP8266 MQTT devices

[hagensieker]

I have a Linksys WRT1900ACS with DD-WRT dated 3/30 which works perfectly and controls many IoT devices in my home.

I have a WRT3200ACM that I intended to deploy as my main router in the home. Using the latest Brain Slayer DD-WRT versions 31 May and 1 June. With this router, using the mwlwifi driver, and configuring the wifi identical to the previous router 10 of my devices, all of which use ESP8266 chips will not connect to the same network. I have tried turning off the SPI firewall, port forwarding to the MQTT server, changing the wifi name entirely and reconfiguring a device to that new name...........nothing allows these devices to connect.

Out of curiosity I took an Archer C7v2 and put latest DD-WRT on it and it will connect all my ESP8266 devices with no problem.

I posted about this issue on the DD-WRT forums and there is another person with similar problems on the forum using WRT3200ACM and Home Automation devices.

I suspect this is an issue with the mwlwifi driver possibly.

Thanks............John, New Bern, NC.

[yuhhaurlin]

The client can't connect to AP? What is the client chip?

[hagensieker]

ESP8266. I have 11 of them in my home that will not connect to my wifi with the DD-WRT with latest driver. I have confirmed now that an Archer C7v2 with latest DD-WRT will connect them and a DIR-860L router with LEDE installed will connect them. It is only the DD-WRT with that latest mwlwifi driver installed that cannot connect the IoT devices .

[yuhhaurlin]

Can you give me more information about your problem?

[yuhhaurlin]

Please let me know version of your mwlwifi and firmware. Setting of your AP. If possible, please use "logread | grep hostapd" and "dmesg" to get more information for me.

[hagensieker]

dmesg

`[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.30 (root@seg-desktop) (gcc version 7.1.0 (LEDE GCC 7.1.0 r4105-9448e16959) ) #14 SMP Sat May 27 01:12:16 CEST 2017 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt:Machine model: Linksys WRT3200ACM [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 131072 [ 0.000000] free_area_init_node: node 0, pgdat c082b380, node_mem_map dfbf9000 [ 0.000000] Normal zone: 1024 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 131072 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 13 pages/cpu @dfbce000 s22860 r8192 d22196 u53248 [ 0.000000] pcpu-alloc: s22860 r8192 d22196 u53248 alloc=13*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock8 ro rootdelay=1 rootfstype=jffs2 earlyprintk mtdparts=armada-nand:2048K(uboot)ro,128K(u_env),256K(s_env),256K@8064K(devinfo),1920K@8320K(sysdiag),80m@10m(kernel),74m@16m(rootfs ,80m@90m(alt_kernel),74m@96m(alt_rootfs),160m@10m(ubifs),-@170m(syscfg) [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 511848K/524288K available (4096K kernel code, 176K rwdata, 912K rodata, 1024K init, 350K bss, 12440K reserved, 0K cma-reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff800000 ( 496 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc0500000 (5088 kB) [ 0.000000] .init : 0xc0700000 - 0xc0800000 (1024 kB) [ 0.000000] .data : 0xc0800000 - 0xc082c0b0 ( 177 kB) [ 0.000000] .bss : 0xc082e000 - 0xc0885b3c ( 351 kB) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, suspend/resume will not work [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 D prefetch enabled, offset 1 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB [ 0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001 [ 0.000000] Switching to timer-based delay loop, resolution 40ns [ 0.000003] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns [ 0.000008] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns [ 0.000147] Calibrating local timer... 933.15MHz. [ 0.060028] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000) [ 0.060033] pid_max: default: 32768 minimum: 301 [ 0.060078] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.060082] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.060258] CPU: Testing write buffer coherency: ok [ 0.060343] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.060354] Setting up static identity map for 0x100000 - 0x100058 [ 0.060409] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4 [ 0.060463] mvebu-pmsu: Initializing Power Management Service Unit [ 0.060865] Booting CPU 1 [ 0.061000] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.061030] Brought up 2 CPUs [ 0.061035] SMP: Total of 2 processors activated (100.00 BogoMIPS). [ 0.062666] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.062718] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.062725] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.062757] pinctrl core: initialized pinctrl subsystem [ 0.063011] NET: Registered protocol family 16 [ 0.063449] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.090040] cpuidle: using governor ladder [ 0.090161] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling [ 0.090167] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling [ 0.120551] reg-fixed-voltage xhci0-vbus: could not find pctldev for node /soc/internal-regs/pinctrl@18000/xhci0-vbus-pins, deferring probe [ 0.120686] SCSI subsystem initialized [ 0.120759] libata version 3.00 loaded. [ 0.121355] clocksource: Switched to clocksource armada_370_xp_clocksource [ 0.121667] NET: Registered protocol family 2 [ 0.121882] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 0.121902] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 0.121929] TCP: Hash tables configured (established 4096 bind 4096) [ 0.121951] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.121963] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.122021] NET: Registered protocol family 1 [ 0.122032] PCI: CLS 0 bytes, default 64 [ 0.122949] workingset: timestamp_bits=30 max_order=17 bucket_order=0 [ 0.123013] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.124163] io scheduler noop registered [ 0.124168] io scheduler deadline registered (default) [ 0.124495] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver [ 0.125049] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00 [ 0.125057] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 0.125061] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff] [ 0.125065] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.125078] pci 0000:00:01.0: [11ab:6820] type 01 class 0x060400 [ 0.125155] pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400 [ 0.125221] PCI: bus0: Fast back to back transfers disabled [ 0.125227] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.125232] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.125281] pci 0000:01:00.0: [11ab:2b40] type 00 class 0x020000 [ 0.125296] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x401fffff 64bit pref] [ 0.125305] pci 0000:01:00.0: reg 0x18: [mem 0x40200000-0x402fffff 64bit pref] [ 0.125363] pci 0000:01:00.0: supports D1 D2 [ 0.125365] pci 0000:01:00.0: PME# supported from D0 D1 D3hot D3cold [ 0.125425] PCI: bus1: Fast back to back transfers disabled [ 0.125431] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.125479] pci 0000:02:00.0: [11ab:2b40] type 00 class 0x020000 [ 0.125497] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x421fffff 64bit pref] [ 0.125508] pci 0000:02:00.0: reg 0x18: [mem 0x42200000-0x422fffff 64bit pref] [ 0.125588] pci 0000:02:00.0: supports D1 D2 [ 0.125591] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold [ 0.125656] PCI: bus2: Fast back to back transfers disabled [ 0.125661] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 [ 0.125729] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff] [ 0.125734] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0400000-0xe06fffff] [ 0.125740] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit pref] [ 0.125750] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0200000-0xe02fffff 64bit pref] [ 0.125758] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.125762] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe02fffff] [ 0.125768] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0400000-0xe05fffff 64bit pref] [ 0.125778] pci 0000:02:00.0: BAR 2: assigned [mem 0xe0600000-0xe06fffff 64bit pref] [ 0.125786] pci 0000:00:02.0: PCI bridge to [bus 02] [ 0.125790] pci 0000:00:02.0: bridge window [mem 0xe0400000-0xe06fffff] [ 0.125971] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.181593] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 0.181670] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.241572] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 0.241697] serial8250_init [ 0.241702] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 0.241933] console [ttyS0] disabled [ 0.261993] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 21, base_baud = 12500000) is a 16550A [ 0.939810] console [ttyS0] enabled [ 0.943597] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device [ 0.951421] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xda [ 0.957800] nand: AMD/Spansion S34ML02G2 [ 0.961743] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128 [ 0.969432] pxa3xx-nand f10d0000.flash: ECC strength 16, ECC step size 2048 [ 0.976616] Bad block table found at page 131008, version 0x01 [ 0.982812] Bad block table found at page 130944, version 0x01 [ 0.988897] found commandline [ 0.991880] rename part 8 to ubi [ 0.994963] 11 ofpart partitions found on MTD device pxa3xx_nand-0 [ 1.001168] Creating 11 MTD partitions on MTD depxa3xx_nand-0and-0 [ 1.006681] 0x000000000000-0x000000200000 : D depxu-bootand-0a [ 1.011950] 0x000000200000-0x000000220000 : D depxu_env;and-0 [ 1.017080] 0x000000220000-0x000000240000 : D depxs_env;and-0 [ 1.022227] 0x0000007e0000-0x000000820000 : D depxdevinfond-0 [ 1.027537] 0x000000820000-0x000000a00000 : D depxsysdiagnd-0 [ 1.032858] 0x000000a00000-0x000005a00000 : D depxlinux;gnd-0 [ 1.038107] 0x000001000000-0x000005a00000 : D depxrootfsgnd-0 [ 1.043443] mtd: partition 0x0000rootfs00 : D set to be root filesystem [ 1.049383] magic E0011985 vs 73717368 [ 1.053241] split_squashfs: no squashfs found in to bepxa3xxnand-0tem [ 1.059271] 0x000005a00000-0x00000aa00000 : d in linux2xa3xx [ 1.064627] 0x000006000000-0x00000a900000 : d in ubiot;xa3 [ 1.069702] 0x00000a900000-0x00000a940000 : d in nvram;xa3 [ 1.074839] 0x00000aa00000-0x00000ff00000 : d in ddwrt;xa3 [ 1.080345] libphy: Fixed MDIO Bus: probed [ 1.084618] tun: Universal TUN/TAP device driver, 1.6 [ 1.089689] tun: (C) 1999-2004 Max Krasnyansky [ 1.096004] libphy: orion_mdio_bus: probed [ 1.100232] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled [ 1.108896] mvneta f1034000.ethernet eth0: Using random mac address 02:c3:64:dd:ae:95 [ 1.117719] mvneta f1070000.ethernet eth1: Using hardware mac address 60:38:e0:b6:ee:28 [ 1.125812] PPP generic driver version 2.4.2 [ 1.130139] PPP BSD Compression module registered [ 1.134866] PPP Deflate Compression module registered [ 1.139946] PPP MPPE Compression module registered [ 1.144759] NET: Registered protocol family 24 [ 1.149225] i2c /dev entries driver [ 1.163920] marvell-cesa f1090000.crypto: CESA device successfully registered [ 1.171192] GACT probability NOT on [ 1.174710] Mirror/redirect action on [ 1.178391] Simple TC action Loaded [ 1.182103] netem: version 1.3 [ 1.185171] u32 classifier [ 1.187886] Performance counters on [ 1.191741] input device check on [ 1.195415] Actions configured [ 1.198829] Netfilter messages via NETLINK v0.30. [ 1.203600] nf_conntrack version 0.5.0 (8192 buckets, 32768 max) [ 1.209745] nf_conntrack_rtsp v0.7 loading [ 1.213937] xt_time: kernel timezone is -0000 [ 1.218313] ip_set: protocol 6 [ 1.221487] gre: GRE over IPv4 demultiplexor driver [ 1.226492] nf_nat_rtsp v0.7 loading [ 1.230089] ip_tables: (C) 2000-2006 Netfilter Core Team [ 1.235488] NET: Registered protocol family 17 [ 1.239967] Bridge firewalling registered [ 1.243998] 8021q: 802.1Q VLAN Support v1.8 [ 1.248245] Registering SWP/SWPB emulation handler [ 1.253796] searching for nvram [ 1.256955] nvram size = 262144 [ 1.266162] auto-attach mtd8 [ 1.268882] ubi0: attaching mtd8 [ 1.275662] random: fast init done [ 1.469843] ubi0: scanning is finished [ 1.477906] ubi0: attached mtd8 (name [ 1.483336] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 1.490238] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 1.497056] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 1.504048] ubi0: good PEBs: 584, bad PEBs: 0, corrupted PEBs: 0 [ 1.510078] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128 [ 1.517330] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 500531166 [ 1.526415] ubi0: available PEBs: 0, total reserved PEBs: 584, PEBs reserved for bad PEB handling: 40 [ 1.535687] ubi0: background thread totalubi_bgt0d PEBs: started, PID 506 [ 1.542055] block ubiblock0_0: created from ubi0:0(rootfs) [ 1.547739] mvsw61xx 10.mvsw61xx: Found MV88E6352 at f1072004.mdio-mi:10 [ 1.554476] mvsw61xx 10.mvsw61xx: Using direct addressing [ 1.567547] xhci0-vbus: disabling [ 1.570949] Waiting 1 sec before mounting root device... [ 2.642458] VFS: Mounted root (squashfs filesystem) readonly on device 254:0. [ 2.650098] Freeing unused kernel memory: 1024K (c0700000 - c0800000) [ 3.803905] orion_wdt: Initial timeout 171 sec, nowayout [ 3.926309] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f [ 3.934366] Backport generated by backports.git backports-20160324-13-g24da7d3c [ 4.040398] <> [ 4.048467] pci 0000:00:01.0: enabling device (0140 -> 0142) [ 4.054249] ieee80211 phy0: priv->pcmd_buf = de5e0000 priv->pphys_cmd_buf = 1e5e0000 [ 4.108793] ieee80211 phy0: fw download start [ 4.108797] ieee80211 phy0: ddr init: download start [ 4.109175] ieee80211 phy0: ddr init: download complete [ 4.245928] ieee80211 phy0: FwSize = 447620 downloaded Size = 447620 curr_iteration 65522 [ 7.117345] ieee80211 phy0: fw download complete [ 7.130210] ieee80211 phy0: pcmd = de5e0000 [ 7.147379] ieee80211 phy0: firmware version: 0x9030007 [ 7.508345] ieee80211 phy0: firmware region code: 10 [ 7.536992] ieee80211 phy0: 2G enabled, 5G enabled [ 7.541829] ieee80211 phy0: 4 TX antennas, 4 RX antennas [ 7.547223] pci 0000:00:02.0: enabling device (0140 -> 0142) [ 7.553013] ieee80211 phy1: priv->pcmd_buf = de5f8000 priv->pphys_cmd_buf = 1e5f8000 [ 7.559639] ieee80211 phy1: fw download start [ 7.559644] ieee80211 phy1: ddr init: download start [ 7.560025] ieee80211 phy1: ddr init: download complete [ 7.699874] ieee80211 phy1: FwSize = 447620 downloaded Size = 447620 curr_iteration 65527 [ 8.897348] ieee80211 phy1: fw download complete [ 8.910137] ieee80211 phy1: pcmd = de5f8000 [ 8.927386] ieee80211 phy1: firmware version: 0x9030007 [ 9.288346] ieee80211 phy1: firmware region code: 10 [ 9.310979] ieee80211 phy1: 2G enabled, 5G disabled [ 9.315916] ieee80211 phy1: 4 TX antennas, 4 RX antennas [ 9.388537] sdhci: Secure Digital Host Controller Interface driver [ 9.394776] sdhci: Copyright(c) Pierre Ossman [ 9.411464] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.481345] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA [ 9.539025] mmc0: new high speed SDIO card at address 0001 [ 9.546864] Bluetooth: Core ver 2.22 [ 9.550477] NET: Registered protocol family 31 [ 9.554957] Bluetooth: HCI device and connection manager initialized [ 9.561346] Bluetooth: HCI socket layer initialized [ 9.566243] Bluetooth: L2CAP socket layer initialized [ 9.571635] mwifiex: rx work enabled, cpus 2 [ 9.604562] Bluetooth: vendor=0x2df, device=0x9136, class=255, fn=2 [ 9.891017] random: crng init done [ 10.396776] mwifiex_sdio mmc0:0001:1: info: FW download over, size 695532 bytes [ 10.911360] mwifiex_sdio mmc0:0001:1: WLAN FW is active [ 10.911404] sdio platform data not available [ 10.931083] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2 [ 10.938089] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during initialization [ 10.959396] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p71) [ 10.967448] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (15.68.7.p71) [ 11.035381] usbcore: registered new interface driver usbfs [ 11.040935] usbcore: registered new interface driver hub [ 11.046315] usbcore: registered new device driver usb [ 11.065166] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 11.074740] ehci-platform: EHCI generic platform driver [ 11.087936] ehci-pci: EHCI PCI platform driver [ 14.136231] xhci-hcd f10f8000.usb3: xHCI Host Controller [ 14.141606] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 1 [ 14.149176] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010 [ 14.157763] xhci-hcd f10f8000.usb3: irq 44, io mem 0xf10f8000 [ 14.163815] hub 1-0:1.0: USB hub found [ 14.167616] hub 1-0:1.0: 1 port detected [ 14.171723] xhci-hcd f10f8000.usb3: xHCI Host Controller [ 14.177071] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2 [ 14.184644] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 14.192983] hub 2-0:1.0: USB hub found [ 14.196773] hub 2-0:1.0: 1 port detected [ 14.288809] usbcore: registered new interface driver usb-storage [ 14.314914] ehci-orion: EHCI orion driver [ 14.319034] orion-ehci f1058000.usb: EHCI Host Controller [ 14.324487] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 3 [ 14.332127] orion-ehci f1058000.usb: irq 37, io mem 0xf1058000 [ 14.361347] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00 [ 14.367818] hub 3-0:1.0: USB hub found [ 14.371934] hub 3-0:1.0: 1 port detected [ 14.417908] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode [ 14.427010] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 14.436339] scsi host0: ahci-mvebu [ 14.440006] scsi host1: ahci-mvebu [ 14.443617] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 41 [ 14.451574] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 41 [ 14.782508] ata2: SATA link down (SStatus 0 SControl 300) [ 14.792993] ata1: SATA link down (SStatus 0 SControl 300) [ 16.419138] device br0 entered promiscuous mode [ 16.431185] mvneta f1034000.ethernet eth0: configuring for fixed link mode [ 16.439204] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 16.457589] mvneta f1034000.ethernet eth0: configuring for fixed link mode [ 16.464582] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 16.482178] mvneta f1034000.ethernet eth0: configuring for fixed link mode [ 16.489155] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 16.498237] br0: port 1(eth0) entered blocking state [ 16.503253] br0: port 1(eth0) entered disabled state [ 16.508327] device eth0 entered promiscuous mode [ 16.513786] mvneta f1070000.ethernet eth1: configuring for fixed link mode [ 16.521070] mvneta f1070000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 16.538323] mvneta f1070000.ethernet eth1: configuring for fixed link mode [ 16.545329] mvneta f1070000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 16.562889] mvneta f1070000.ethernet eth1: configuring for fixed link mode [ 16.569869] mvneta f1070000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 16.578974] br0: port 2(eth1) entered blocking state [ 16.583990] br0: port 2(eth1) entered disabled state [ 16.589066] device eth1 entered promiscuous mode [ 16.595119] br0: port 2(eth1) entered blocking state [ 16.600260] br0: port 2(eth1) entered forwarding state [ 16.606827] br0: port 1(eth0) entered blocking state [ 16.611814] br0: port 1(eth0) entered forwarding state [ 16.617009] device br0 left promiscuous mode [ 16.622483] device br0 entered promiscuous mode [ 16.630892] device br0 left promiscuous mode [ 21.047229] br0: port 3(ath0) entered blocking state [ 21.052241] br0: port 3(ath0) entered disabled state [ 21.057319] device ath0 entered promiscuous mode [ 26.788373] br0: port 3(ath0) entered blocking state [ 26.793367] br0: port 3(ath0) entered forwarding state [ 27.157210] br0: port 4(ath1) entered blocking state [ 27.162210] br0: port 4(ath1) entered disabled state [ 27.167335] device ath1 entered promiscuous mode [ 27.172012] br0: port 4(ath1) entered blocking state [ 27.176999] br0: port 4(ath1) entered forwarding state [ 27.841367] br0: port 4(ath1) entered disabled state [ 34.564386] br0: port 4(ath1) entered blocking state [ 34.569376] br0: port 4(ath1) entered forwarding state [ 37.394728] ieee80211 phy1: staid 7 deleted [ 40.176608] ieee80211 phy1: staid 14 deleted [ 47.659318] br0: port 5(ath2) entered blocking state [ 47.664342] br0: port 5(ath2) entered disabled state [ 47.669472] device ath2 entered promiscuous mode [ 47.674152] br0: port 5(ath2) entered blocking state [ 47.679140] br0: port 5(ath2) entered forwarding state [ 52.319701] ieee80211 phy1: staid 11 deleted [ 52.331375] ieee80211 phy1: staid 10 deleted [ 52.341612] ieee80211 phy1: staid 9 deleted [ 52.351625] ieee80211 phy1: staid 8 deleted [ 52.361638] ieee80211 phy1: staid 6 deleted [ 52.371603] ieee80211 phy1: staid 5 deleted [ 52.381662] ieee80211 phy1: staid 4 deleted [ 52.391630] ieee80211 phy1: staid 3 deleted [ 52.401619] ieee80211 phy1: staid 2 deleted [ 52.707058] ieee80211 phy1: staid 1 deleted [ 99.820631] ieee80211 phy1: staid 20 deleted [ 173.599900] ieee80211 phy1: staid 22 deleted [ 173.934066] ieee80211 phy1: staid 22 deleted [ 177.953683] ieee80211 phy1: staid 22 deleted [ 178.821681] ieee80211 phy1: staid 22 deleted [ 188.606635] ieee80211 phy1: staid 18 deleted [ 193.456382] ieee80211 phy1: staid 18 deleted

`

logread

logread: can't find syslogd buffer: No such file or directory

mwlwifi

driver name: mwlwifi chip type: 88W8964 hw version: 7 driver version: 10.3.4.0-20170512 firmware version: 0x09030007 power table loaded from dts: no firmware region code: 0x10 mac address: 60:38:e0:b6:ee:29 2g: enable 5g: disable antenna: 4 4 irq number: 46 ap macid support: 0000ffff sta macid support: 00010000 macid used: 00000001 radio: enable iobase0: e0f80000 iobase1: e1200000 tx limit: 1024 rx limit: 16384

[hagensieker]

[yuhhaurlin]

Please help to check if this problem will happen if only one client is used to connect to AP. Thanks.

[hagensieker]

The AP's both 2.4 and 5Ghz will connect to clients, just not the ESP8266's. I changed the wifi name and reprogrammed one ESP8266 and it still wouldn't connect. Subsequently then changed the wifi connection for a raspberry pi and it connected fine.

[yuhhaurlin]

What is ESP8266? Subsequently then changed the wifi connection for a raspberry pi and it connected fine. => So the problem is gone?

[hagensieker]

ESP8266 is an Internet of Things chip found in a lot of Home Automation stuff. I have 6 wifi outlets, a motion sensor, 2 relays and an LED strip all controlled by ESP8266 chips. What they do is broadcast a hotspot which you connect to and then configure them to run on your local network. These devices all work brilliantly on any SSID named "dd-wrt" with the appropriate password.

Works with my WRT1900ACS, Archer C7v2, DIR-860L, and R7800 routers. Those ESP8266 devices will not connect using the last two (and possibly previous) BrainSlayer DD-WRT versions using the mwlwifi version I posted above.

Regular computers work just fine. I can connect my laptop, my raspberry pi's, anything but the ESP8266 devices.

[hagensieker]

This will give you a rough idea of the device

http://www.hagensieker.com/blog/page/?post_id=44&title=esp8266-hack-of-inexpensive-wifi-outlet

[yuhhaurlin]

The latest driver can work for WRT1900ACS and WRT3200ACM, you only encounter this problem with WRT3200ACM, right?

[yuhhaurlin]

BTW, do you have the same problem with stock firmware of WRT3200ACM?

[hagensieker]

That is correct. Only on the 3200ACM The version of DD-WRT I'm running on the WRT1900ACS is dated 3/30 and I haven't run latest firmware yet.

Have not tried stock yet but every other dd-wrt on every other device works fine.

[yuhhaurlin]

1. Please use the same driver on WRT1900ACS to see if it is working.
2. Please check if you have the same problem with stock firmware.
3. BTW, no matter open or security has the same problem, right?

[hagensieker]

I'm booting to stock now will know in a few minutes. I haven't tried to test on open network as I'd have to reprogram the devices. I can later but not a ton of time before work this morning. Will test stock now.

[yuhhaurlin]

Thank you. These tests can help me to check this problem. If you can capture traffic between AP and ESP8266, it would be even better.

[hagensieker]

Stock works.

[yuhhaurlin]

Can you help just connect one ESP8266 to AP to see if it works. Thanks.

[hagensieker]

I'll try to wireshark but won't be able to get to it for a couple days. Quick work trip.

[yuhhaurlin]

1. Can you help to test for one ESP8266 to see if this problem happen?
2. If you have Macbook Pro, you can install Wireshark to capture packets, you need to connect to AP first before packet capture.
3. If needed, I can build LEDE for you to get more debug information later.

[hagensieker]

One ESP8266 does not connect. I have wireshark but will have to capture later.

Consequently yesterday I installed 17.01.1 LEDE and then updated the kmod-mwlwifi driver and it also did not work

[hagensieker]

This driver

https://github.com/eduperez/mwlwifi_LEDE/releases

[yuhhaurlin]

If you use LEDE, you can use "logread | grep hostapd" to get more debug information.

[hagensieker]

Will give that a shot later. Out the door for work and probably won't be able to provide more info until Wed. Many thanks for your help here this morning.

[davidelang]

I think I've seen a post reporting problems with recent drivers that only happened with an encrypted connection, an open connection worked (using the esp8266)

[yuhhaurlin]

Please use https://drive.google.com/open?id=0B3qLWtcWB9EdcHJvd2tIbHl3dnM to do test and use "logread | grep hostapd" to get more information. I will check the log and update needed debug package to check this problem. Thanks.

[hagensieker]

Will do tomorrow when I get back off my trip. Thanks.

[hagensieker]

Installed your LEDE and here is the logread:

root@LEDE:~# logread | grep hostapd Wed Jun 7 12:40:08 2017 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf Wed Jun 7 12:40:09 2017 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE Wed Jun 7 12:40:09 2017 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->HT_SCAN Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:09 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: handle_probe_req: send failed Wed Jun 7 12:40:11 2017 daemon.notice hostapd: 20/40 MHz operation not permitted on channel pri=2 sec=6 based on overlapping BSSes Wed Jun 7 12:40:11 2017 daemon.err hostapd: Using interface wlan1 with hwaddr 60:38:e0:b6:ee:29 and ssid "dd-wrt" Wed Jun 7 12:40:11 2017 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED Wed Jun 7 12:40:11 2017 daemon.notice hostapd: wlan1: AP-ENABLED Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 80:1f:02:94:58:b1 IEEE 802.11: associated (aid 1) Wed Jun 7 12:46:20 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 80:1f:02:94:58:b1 Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 80:1f:02:94:58:b1 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 IEEE 802.11: associated (aid 2) Wed Jun 7 12:46:20 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 94:10:3e:4d:10:d1 Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f IEEE 802.11: associated (aid 3) Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA a0:20:a6:12:54:81 IEEE 802.11: associated (aid 4) Wed Jun 7 12:46:20 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type Wed Jun 7 12:46:20 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:14:3f Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 80:1f:02:94:58:b1 IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA a0:20:a6:12:54:81 IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:15:f8 IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:49:c1 IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:55:71 IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:02:f0:3a IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:15:f8 IEEE 802.11: associated (aid 5) Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:55:71 IEEE 802.11: associated (aid 6) Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:49:c1 IEEE 802.11: associated (aid 7) Wed Jun 7 12:46:20 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:02:f0:3a IEEE 802.11: associated (aid 8) Wed Jun 7 12:46:20 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:15:f8 Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:15:f8 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:02:f0:3a Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 38:2b:78:02:f0:3a WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED a0:20:a6:12:54:81 Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA a0:20:a6:12:54:81 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:49:c1 Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:49:c1 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:55:71 Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:55:71 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA d0:73:d5:21:7b:1f IEEE 802.11: associated (aid 9) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED d0:73:d5:21:7b:1f Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA d0:73:d5:21:7b:1f WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA d0:73:d5:21:a2:56 IEEE 802.11: associated (aid 10) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED d0:73:d5:21:a2:56 Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA d0:73:d5:21:a2:56 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 74:da:38:0a:0f:85 IEEE 802.11: associated (aid 11) Wed Jun 7 12:46:21 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 74:da:38:0a:0f:85 Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 74:da:38:0a:0f:85 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA d0:73:d5:21:7b:1f IEEE 802.11: authenticated Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA d0:73:d5:21:a2:56 IEEE 802.11: authenticated Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 74:da:38:0a:0f:85 IEEE 802.11: authenticated Wed Jun 7 12:46:21 2017 daemon.info hostapd: wlan1: STA 18:b4:30:14:14:e5 IEEE 802.11: associated (aid 12) Wed Jun 7 12:46:22 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 18:b4:30:14:14:e5 Wed Jun 7 12:46:22 2017 daemon.info hostapd: wlan1: STA 18:b4:30:14:14:e5 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 5c:cf:7f:30:11:e1 IEEE 802.11: associated (aid 13) Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA a0:20:a6:02:6d:c6 IEEE 802.11: associated (aid 14) Wed Jun 7 12:46:23 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 5c:cf:7f:8f:6e:48 IEEE 802.11: associated (aid 15) Wed Jun 7 12:46:23 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED a0:20:a6:02:6d:c6 Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA a0:20:a6:02:6d:c6 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:23 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 5c:cf:7f:30:11:e1 Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 5c:cf:7f:30:11:e1 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 18:b4:30:14:14:e5 IEEE 802.11: authenticated Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 5c:cf:7f:30:11:e1 IEEE 802.11: authenticated Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA a0:20:a6:02:6d:c6 IEEE 802.11: authenticated Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 5c:cf:7f:8f:6e:48 IEEE 802.11: authenticated Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:42:c4 IEEE 802.11: associated (aid 16) Wed Jun 7 12:46:23 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:42:c4 Wed Jun 7 12:46:23 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:42:c4 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:24 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 5c:cf:7f:8f:6e:48 Wed Jun 7 12:46:24 2017 daemon.info hostapd: wlan1: STA 5c:cf:7f:8f:6e:48 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:24 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 94:10:3e:4d:10:d1 Wed Jun 7 12:46:25 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:42:c4 IEEE 802.11: authenticated Wed Jun 7 12:46:26 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 IEEE 802.11: associated (aid 2) Wed Jun 7 12:46:26 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 94:10:3e:4d:10:d1 Wed Jun 7 12:46:26 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:26 2017 daemon.info hostapd: wlan1: STA a4:8d:3b:f2:36:86 IEEE 802.11: associated (aid 17) Wed Jun 7 12:46:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 94:10:3e:4d:10:d1 Wed Jun 7 12:46:26 2017 daemon.info hostapd: wlan1: STA 74:da:38:41:f8:8f IEEE 802.11: associated (aid 2) Wed Jun 7 12:46:27 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 74:da:38:41:f8:8f Wed Jun 7 12:46:27 2017 daemon.info hostapd: wlan1: STA 74:da:38:41:f8:8f WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:27 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED a4:8d:3b:f2:36:86 Wed Jun 7 12:46:27 2017 daemon.info hostapd: wlan1: STA a4:8d:3b:f2:36:86 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:28 2017 daemon.notice hostapd: handle_auth_cb: STA 94:10:3e:4d:10:d1 not found Wed Jun 7 12:46:28 2017 daemon.info hostapd: wlan1: STA a4:8d:3b:f2:36:86 IEEE 802.11: authenticated Wed Jun 7 12:46:28 2017 daemon.info hostapd: wlan1: STA 74:da:38:41:f8:8f IEEE 802.11: authenticated Wed Jun 7 12:46:28 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 IEEE 802.11: associated (aid 18) Wed Jun 7 12:46:28 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 94:10:3e:4d:10:d1 Wed Jun 7 12:46:28 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 IEEE 802.11: associated (aid 19) Wed Jun 7 12:46:29 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED e0:4f:43:0f:7d:16 Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA 98:01:a7:bc:bc:71 IEEE 802.11: associated (aid 20) Wed Jun 7 12:46:29 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 98:01:a7:bc:bc:71 Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA 98:01:a7:bc:bc:71 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA 94:10:3e:4d:10:d1 IEEE 802.11: authenticated Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 IEEE 802.11: authenticated Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA 98:01:a7:bc:bc:71 IEEE 802.11: authenticated Wed Jun 7 12:46:39 2017 daemon.info hostapd: wlan1: STA 00:24:2c:a1:49:dd IEEE 802.11: associated (aid 21) Wed Jun 7 12:46:39 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 00:24:2c:a1:49:dd Wed Jun 7 12:46:39 2017 daemon.info hostapd: wlan1: STA 00:24:2c:a1:49:dd WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:46:39 2017 daemon.info hostapd: wlan1: STA 00:24:2c:a1:49:dd IEEE 802.11: authenticated Wed Jun 7 12:47:12 2017 daemon.info hostapd: wlan1: STA 70:f0:87:4f:3f:f2 IEEE 802.11: associated (aid 22) Wed Jun 7 12:47:12 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 70:f0:87:4f:3f:f2 Wed Jun 7 12:47:12 2017 daemon.info hostapd: wlan1: STA 70:f0:87:4f:3f:f2 WPA: pairwise key handshake completed (RSN) Wed Jun 7 12:47:13 2017 daemon.info hostapd: wlan1: STA 70:f0:87:4f:3f:f2 IEEE 802.11: authenticated

[yuhhaurlin]

1. Can you just use one client?
2. It looks like client is connected to AP and completes 4 ways handshake. When the client is connected, can you use "iw wlan1 station dump" to dump station information for me.

[hagensieker]

Not following here as the clients in question won't connect I have a bunch of computers, devices, etc. They all connect fine, just the ESP8266 devices won't connect. Not sure how I can give a dump that reveals that issue without one of those clients getting rejected or something.

[yuhhaurlin]

You can just use one ESP8266 to connect to AP. BTW, althoughh you set 40 MHz on 2.4g, but hostapd resets to 20 MHz due to overlapping BSS.

[hagensieker]

That's just it. The ESP8266 won't connect.

[yuhhaurlin]

If you have problem to do that, please let me know MAC address of ESP8266.

[hagensieker]

One of them is 38:2B:78:07:14:3F

On Jun 7, 2017, at 9:50 AM, yuhhaurlin notifications@github.com wrote:

If you have problem to do that, please let me know MAC address of ESP8266.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kaloz/mwlwifi/issues/170#issuecomment-306800911, or mute the thread https://github.com/notifications/unsubscribe-auth/AGdig0CST4NkFaMRd4qOKjTmTH8xZd2Kks5sBqq5gaJpZM4NvVJe.

[yuhhaurlin]

Thanks. I will check it.

[yuhhaurlin]

From the log, 38:2b:78:07:14:3f is connected and completes 4 ways handshake, I can't find AP disconnects it. The only one be disconnected is 94:10:3e:4d:10:d1. You can help to check your log again to see if I am right. Can you help to use "iw wlan1 station dump to check if 38:2b:78:07:14:3f is connected?

<<38:2b:78:07:14:3f>> Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f IEEE 802.11: associated (aid 3) Wed Jun 7 12:46:20 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:14:3f Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f WPA: pairwise key handshake completed (RSN)

<> Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 IEEE 802.11: authenticated Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 IEEE 802.11: associated (aid 19) Wed Jun 7 12:46:29 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED e0:4f:43:0f:7d:16 Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 WPA: pairwise key handshake completed (RSN)

<<94:10:3e:4d:10:d1>> Wed Jun 7 12:46:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 94:10:3e:4d:10:d1

[hagensieker]

That’s interesting. My specific issue is that the ESP8266 devices do not respond to commands when (now I know) connected to the WRT3200ACM. If connected to Stock, or any other router in the home these devices can be controlled from a program called Home Assistant. One thing most of the devices have in common is they all (a couple exceptions) are also connected to my MQTT server, an Ubuntu Linux machine.

Looks like I need to look towards the Home Assistant Raspberry Pi or the MQTT server now.

Something is still not playing correctly though with this router config. Perhaps it is not mwlwifi but some other issue. Again though, literally every other router in my home connects and controls all these devices. Let me dig a little deeper and I’ll get back to this here.

Thanks.

On Jun 7, 2017, at 11:17 PM, yuhhaurlin notifications@github.com wrote:

From the log, 38:2b:78:07:14:3f is connected and completes 4 ways handshake, I can't find AP disconnects it. The only one be disconnected is 94:10:3e:4d:10:d1. You can help to check your log again to see if I am right. Can you help to use "iw wlan1 station dump to check if 38:2b:78:07:14:3f is connected?

<<38:2b:78:07:14:3f>> Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f IEEE 802.11: authenticated Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f IEEE 802.11: associated (aid 3) Wed Jun 7 12:46:20 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 38:2b:78:07:14:3f Wed Jun 7 12:46:20 2017 daemon.info hostapd: wlan1: STA 38:2b:78:07:14:3f WPA: pairwise key handshake completed (RSN)

Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 IEEE 802.11: authenticated Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 IEEE 802.11: associated (aid 19) Wed Jun 7 12:46:29 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED e0:4f:43:0f:7d:16 Wed Jun 7 12:46:29 2017 daemon.info hostapd: wlan1: STA e0:4f:43:0f:7d:16 WPA: pairwise key handshake completed (RSN) <<94:10:3e:4d:10:d1>> Wed Jun 7 12:46:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 94:10:3e:4d:10:d1 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

[yuhhaurlin]

1. Use "iw wlan1 station dump | grep 38:2b:78:07:14:3f" to check if station is connected. It will tell if the client is authenticated, associated and authorized.
2. If the station is connected, the next step should be check if data traffic is all right via ping.

root@LEDE:/# iw wlan0 station dump Station b8:e8:56:3b:b5:34 (on wlan0) inactive time: 0 ms rx bytes: 5373259941 rx packets: 62478303 tx bytes: 139214342797 tx packets: 91310113 tx retries: 0 tx failed: 0 rx drop misc: 2 signal: 0 dBm signal avg: 0 dBm tx bitrate: 6.0 MBit/s rx bitrate: 6.0 MBit/s authorized: yes authenticated: yes associated: yes preamble: long WMM/WME: yes MFP: no TDLS peer: no DTIM period: 2 beacon interval:100 short slot time:yes connected time: 3092 seconds

[yuhhaurlin]

You mentioned that WRT1900ACS is all right. The same driver can work for WRT1900ACS, you can get LEDE image here: https://drive.google.com/open?id=0B3qLWtcWB9EdeEZOT2ZTUWJkZW8.

[hagensieker]

Station 38:2b:78:07:14:3f (on wlan1) inactive time: 52410 ms rx bytes: 4623 rx packets: 4 tx bytes: 487 tx packets: 4 tx retries: 0 tx failed: 0 rx drop misc: 11 signal: 0 dBm signal avg: 0 dBm tx bitrate: 1.0 MBit/s rx bitrate: 1.0 MBit/s authorized: yes authenticated: yes associated: yes preamble: short WMM/WME: yes MFP: no TDLS peer: no DTIM period: 2 beacon interval:100 short preamble: yes connected time: 415 seconds

[hagensieker]

so looks like the device is connected. May be another issue with Home Assistant or MQTT. I'll dig deeper

[yuhhaurlin]

Yes, the client is connected and it is authenticated, associated and authorized. It shows the same result as what we saw in the log. I wonder if the data traffic is all right? You can try to ping to AP first.

[hagensieker]

I’m trying to Wireshark it but the odd thing is that it doesn’t show up on my network list when using an app like Fing to find all connected network devices.

On Jun 8, 2017, at 5:25 AM, yuhhaurlin notifications@github.com wrote:

Yes, the client is connected and it is authenticated, associated and authorized. It shows the same result as what we saw in the log. I wonder if the data traffic is all right? You can try to ping to AP first.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kaloz/mwlwifi/issues/170#issuecomment-307049493, or mute the thread https://github.com/notifications/unsubscribe-auth/AGdigzoaIXUm-ZRBstM9dU7cNaGpn9Vxks5sB74WgaJpZM4NvVJe.

[davidelang]

did you try connecting with encryption disabled?

[hagensieker]

Not yet because i have to reprogram the ESP8266 chip(s) which isn’t impossible to do but I haven’t gotten that far yet.

Although my devices seem connected (under LEDE) they don’t show up on the DHCP list or on a network scan like with an app like Fing, and I can’t control the devices from Home Assistant (home automation software).

On Jun 8, 2017, at 2:58 PM, David Lang notifications@github.com wrote:

did you try connecting with encryption disabled? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kaloz/mwlwifi/issues/170#issuecomment-307196003, or mute the thread https://github.com/notifications/unsubscribe-auth/AGdig5RIY5UZMQ1UcH0r_ShIWyJlNGRcks5sCERPgaJpZM4NvVJe.

[yuhhaurlin]

Yes, you can use open mode to see if problem is there. BTW, can you make sure data traffic is all right between your device and AP?

[yuhhaurlin]

Please confirm data path is all right. If there is no more information from you, I will close this one. BTW, if anyone encounters the same problem, please let me know. Connection and key is established, what we need to check is if data is all right.

[hagensieker]

I’m working on this this morning. Will have some info for you in a bit. Had to take it to work as every time I take the old router out, experiment with this one it gives me new DHCP addresses on everything and it fouls up some of my media servers and Home Automation.

On Jun 12, 2017, at 12:14 AM, yuhhaurlin notifications@github.com wrote:

Please confirm data path is all right. If there is no more information from you, I will close this one. BTW, if anyone encounters the same problem, please let me know. Connection and key is established, what we need to check is if data is all right.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kaloz/mwlwifi/issues/170#issuecomment-307686304, or mute the thread https://github.com/notifications/unsubscribe-auth/AGdig8RrZUqBAGrgsuUWYV39h6pEDimrks5sDLsWgaJpZM4NvVJe.

[hagensieker]

Ok I set up LEDE with latest driver and hooked ESP8266 device on an open network and it works. I just flashed a device that hooks to WeatherUnderground and I have no real idea or not if it is working as I don't have it hooked to an LCD however it is most definitely connected and I can ping it.

Then I made the network SSID the same as at home with the same password and re-flashed the ESP8266. Same thing. It shows up as connected in the DHCP list and I can ping it.

I have NO idea at this point why my devices don't connect at home.

I can say that MOST of my ESP8266 devices also connect to an MQTT server on another computer. I've turned off the firewall and even done a port forward just to be sure.

I'm stumped.

I know this as well. I can take any other router in my home and give it the same SSID and password and it will immediately connect the device. I just recently got a Synology RT2600AC this weekend. Plug it in.........it immediately sees the devices and controls them.

It is only with the WRT3200ACM that it isn't working and this is with both LEDE or latest BrainSlayer DD-WRT. Maybe it is something goofy with my network but it's odd that it will connect with seemingly any other router in the world.