[tatsuya46]

whats wrong with r7800 exactly? many problems are ddwrt sided instead of the router or radio fw etc, such as qos as example..

and broadcom section has or had many trigger happy mods that silently delete posts, threads, have their precious peacock thread they think is the god of the universe.. its been inaccurate & plain wrong about many things for years, wonder if its cleaned up yet

[roadrun777]

Your reports for Atheros units are greatly appreciated !
Router: 7500v2
Firmware: v3.0-r33010M kongat (08/09/17)
Kernel: Linux 3.18.63 #145 SMP PREEMPT armv7l DD-WRT
Status: Running with minor errors
Reset: ? If you mean nvram clear and redo then yes
Errors:

--From dmesg--
[ 0.200624] pcie_init: pcie_init: unable to create IPC log context for pcie0-short
[ 0.200639] pcie_init: pcie_init: unable to create IPC log context for pcie0-long
[ 0.200648] pcie_init: pcie_init: unable to create IPC log context for pcie1-short
[ 0.200658] pcie_init: pcie_init: unable to create IPC log context for pcie1-long
[ 2.981080] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

[ 2.988885] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
[ 5.252258] UBIFS error (pid 450): ubifs_mount: cannot open "ubi0:rootfs_data", error -19
[ 7.133404] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[ 8.933141] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:01:00.0.bin failed with error -2

[ 11.047134] qcom-dwc3-ssphy 100f8830.phy: cannot get HSIO settings from device node, using default values
[ 11.047285] qcom-dwc3-ssphy 110f8830.phy: cannot get HSIO settings from device node, using default values

[ 11.090787] qcom-dwc3-hsphy 110f8800.phy: cannot set voltage for vddcx
[ 11.099992] qcom-dwc3-hsphy 110f8800.phy: cannot set voltage for v3p3
[ 11.106385] qcom-dwc3-hsphy 110f8800.phy: cannot set voltage for v1p8
[ 11.115442] qcom-dwc3-ssphy 110f8830.phy: cannot set voltage for vddcx
[ 11.409556] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for vddcx
[ 11.411288] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for v3p3
[ 11.417958] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for v1p8
[ 11.426659] qcom-dwc3-ssphy 100f8830.phy: cannot set voltage for vddcx
--end--
--from logging environment--
user.info : igmprt : multicast daemon successfully stopped
user.warn igmpproxy[2284]: select() failure; Errno(4): Interrupted system call
user.warn igmpproxy[2284]: MRT_DROP_MEMBERSHIP failed; Errno(99): Address not available

Something strange, I have read that igmprt is not necessary for IPv6, but IPv6 ceases to work if I have 'filter multicast' selected. So I am forced to uncheck it to get IPv6 working. I've toggled it back and forth and IPv6 always fails when 'filter multicast' is enabled. I'm not sure why, my br0 interface is assigned an ipv6 address from DHCPv6 w/PD, but I get "network unavilable" if I filter multicast.

Wifi on this build seems to be half power on 5ghz, only one room away it is giving me half the reception from previous builds. All the exact same settings as the previous builds. I always reset nvram and retype everything in manually to be certain.

--- Here is suspicious log entries--
--- You will note that it always thinks it is christmas even though the time shows correctly--
--- I assume it is from the klogd and syslod not being able to retrieve the time correctly ---
Dec 31 19:00:14 kern.info kernel: [ 6.820853] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
Dec 31 19:00:14 kern.info kernel: [ 6.821475] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Dec 31 19:00:14 kern.warn kernel: [ 6.953647] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
Dec 31 19:00:14 kern.warn kernel: [ 6.953696] ath10k_pci 0000:01:00.0: Falling back to user helper
Dec 31 19:00:14 kern.info kernel: [ 7.351005] ath10k_pci 0000:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
Dec 31 19:00:14 kern.info kernel: [ 7.351053] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
Dec 31 19:00:14 kern.info kernel: [ 7.362058] ath10k_pci 0000:01:00.0: firmware ver 10.4.3.00063 api 5 features no-p2p,peer-flow-ctrl crc32 a0d385ce
Dec 31 19:00:14 kern.err kernel: [ 7.371155] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
Dec 31 19:00:14 kern.info kernel: [ 7.377894] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 cab818b2
Dec 31 19:00:14 kern.info kernel: [ 8.566829] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1
Dec 31 19:00:14 kern.info kernel: [ 8.643888] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
Dec 31 19:00:14 kern.info kernel: [ 8.644452] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Dec 31 19:00:14 kern.warn kernel: [ 8.783531] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:01:00.0.bin failed with error -2
Dec 31 19:00:14 kern.warn kernel: [ 8.783562] ath10k_pci 0001:01:00.0: Falling back to user helper
Dec 31 19:00:14 kern.info kernel: [ 8.796289] ath10k_pci 0001:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
Dec 31 19:00:14 kern.info kernel: [ 8.799301] ath10k_pci 0001:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
Dec 31 19:00:14 kern.info kernel: [ 8.813935] ath10k_pci 0001:01:00.0: firmware ver 10.4.3.00063 api 5 features no-p2p,peer-flow-ctrl crc32 a0d385ce
Dec 31 19:00:14 kern.err kernel: [ 8.817122] ath10k_pci 0001:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
Dec 31 19:00:14 kern.info kernel: [ 8.827412] ath10k_pci 0001:01:00.0: board_file api 1 bmi_id N/A crc32 8b97f911
Dec 31 19:00:14 kern.info kernel: [ 10.019185] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1

----------
Looking in the source code I am assuming all the boardID rewrites are someone covering their tracks for selling rebranded hardware from other markets.
Searching chinanet I found that this board is actually 6500 over there so I am assuming it was pruchased rebranded and sold here as 7500v2.
I would be nice to know the truth but I live under information black out, they will censor everything and sell you anything but real information.
Love my country (waves cheap plastic flag)

[mscottdemarco]

I am having a problem with the PPTP server and both site surveys on this build. Anyone else getting them to work? Think the PPTP may be iptables related

[s_shitalkumar]

I upgraded from 30590M Kong to 33010M Kong (08/09/17).

I have OpenVPN setup, 5 GHz radio is configured in AC+N mode and 2.4 radio is configured in N+G mode. The later has two vlans (One of them being used as guest and the other one for home automation sensors and cameras). Each vlan has different set of packet filtering/IP Forwarding rules.

Positives:
1. This upgrade was triggered by network speed upgrade by my ISP (50 MbPS to 200 MbPS). I am able to get up-to 240 MbPS from 8 feet on 5GHZ radio. This is substantial improvement over earlier 114 MbPS. (Disclaimer: I hadn't tried tuning RTS Threashold, pre-amble, beam forming etc)
2. My 4/5 years old Epson printer was not able to connect to the WIFI earlier, now after the upgrade it can.
3. I noticed the CPU and memory utilization stays low. I am tempted to run additional services on the router.

Issues:
--- This is resolved - it was caused by finicky cameras --- 1. My one year old IP Cameras (TENVIS TH 661) are no longer able to connect to the WiFi. This issue started happening only after the upgrade.
2. My LG OLED TV (OLED65B6P) cannot connect if I configured the radio in AC only mode. I never tried this a/c only mode on the old build. Per TV documentation AC WiFi is supported.

I will probably create a separate thread seeking help on the issue with IP Cameras.