Any reason why you wouldn't want to be notified if I ditch the r7500v2? Lol
No, I love netgear and they are generally easier to bring back to life when you kill one
but I've got this fixation with the ea8500 ... and probably when done playing around I'll use it
for openVPN server but I want it behind main router.
root@---:~# dmesg | tail -15
[ 35.288212] device vlan2 left promiscuous mode
[ 35.861455] br0: port 3(ath1) entered forwarding state
[ 37.531484] old slottime_reg 9 and timeout_reg 100A1616
[ 37.531508] set coverageclass 1 with slot 9
[ 37.535520] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
[ 37.669732] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[235367.413566] old slottime_reg 9 and timeout_reg 100A1616
[235367.413615] set coverageclass 1 with slot 9
[235367.417962] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
[235917.803548] old slottime_reg 9 and timeout_reg 100A1616
[235917.803616] set coverageclass 1 with slot 9
[235917.807971] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
[235921.014662] old slottime_reg 9 and timeout_reg 100A1616
[235921.014696] set coverageclass 1 with slot 9
[235921.019059] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
root@---:~# uptime
07:32:06 up 3 days, 8:50, load average: 0.00, 0.02, 0.00
----
@tatsuya46, I seen your ticket for r7800 >>> 'svn.dd-wrt.com/ticket/5486' I've never seen it w/ Kong.
Below is a consecutive string from syslog -
The xx:xx:xx:xx:54:83 is a Atheros AR5005G in an ACER WIN-XP laptop was just connected last night.
No problems with it and no missing ACKs with it.
Don't know that it actually has anything to do with the 'slottime_reg' --
it's just that old has-been derelict computers have always followed me home for some reason
Oct 10 20:59:16 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc RADIUS: starting accounting session D62B414AC1816899
Oct 10 20:59:16 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc WPA: pairwise key handshake completed (RSN)
Oct 10 21:04:07 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 IEEE 802.11: authenticated
Oct 10 21:04:07 --- kern.info kernel: [235367.413566] old slottime_reg 9 and timeout_reg 100A1616
Oct 10 21:04:07 --- kern.info kernel: [235367.413615] set coverageclass 1 with slot 9
Oct 10 21:04:07 --- kern.info kernel: [235367.417962] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
Oct 10 21:04:07 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 IEEE 802.11: associated (aid 1)
Oct 10 21:04:07 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 RADIUS: starting accounting session 8C730C559E96E287
Oct 10 21:04:07 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 WPA: pairwise key handshake completed (RSN)
Oct 10 21:13:17 --- kern.info kernel: [235917.803548] old slottime_reg 9 and timeout_reg 100A1616
Oct 10 21:13:17 --- kern.info kernel: [235917.803616] set coverageclass 1 with slot 9
Oct 10 21:13:17 --- kern.info kernel: [235917.807971] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
Oct 10 21:13:20 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 IEEE 802.11: authenticated
Oct 10 21:13:20 --- kern.info kernel: [235921.014662] old slottime_reg 9 and timeout_reg 100A1616
Oct 10 21:13:20 --- kern.info kernel: [235921.014696] set coverageclass 1 with slot 9
Oct 10 21:13:20 --- kern.info kernel: [235921.019059] new slottime_reg C and timeout_reg 100A1616 sifs A sifs_pipeline 5A0
Oct 10 21:13:20 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 IEEE 802.11: associated (aid 1)
Oct 10 21:13:20 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 RADIUS: starting accounting session 55D2B66193E5D8D8
Oct 10 21:13:20 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 WPA: pairwise key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath0: STA 1c:3e:84:8d:15:99 WPA: group key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 WPA: group key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:61:0b WPA: group key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:9f:e6 WPA: group key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:8c:96 WPA: group key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc WPA: group key handshake completed (RSN)
Oct 10 21:41:52 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:07:3e WPA: group key handshake completed (RSN)
Oct 10 22:14:24 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:9f:12 IEEE 802.11: authenticated
Oct 10 22:14:24 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:9f:12 IEEE 802.11: associated (aid 5)
Oct 10 22:14:24 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:9f:12 RADIUS: starting accounting session 24F269CD81A448D7
Oct 10 22:14:24 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:9f:12 WPA: pairwise key handshake completed (RSN)
----------
This is not a consecutive string but just all missing ACKs in syslog -
Oct 10 18:56:53 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:8c:96 IEEE 802.11: disconnected due to excessive missing ACKs
Oct 11 01:27:57 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc IEEE 802.11: disconnected due to excessive missing ACKs
Oct 11 01:28:26 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:9f:e6 IEEE 802.11: disconnected due to excessive missing ACKs
Oct 11 01:29:32 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc IEEE 802.11: disconnected due to excessive missing ACKs
Oct 11 01:33:42 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc IEEE 802.11: disconnected due to excessive missing ACKs
Oct 11 01:36:02 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc IEEE 802.11: disconnected due to excessive missing ACKs
Oct 11 01:44:04 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:53:bc IEEE 802.11: disconnected due to excessive missing ACKs
xx:xx:xx:xx:8c:96 droid turbo probably same reason as mentioned next.
xx:xx:xx:xx:53:bc is galaxy note 8 -- and I know when it drops is due to close proximity to the ea8500.
Closer than 4 feet will cause this. Seen same thing with the 'Verizon Ellipsis 10' on ath0 .. even with Kong build.
BS r30731M seems even more sensitive.
xx:xx:xx:xx:9f:e6 is E2500 (tomato) client bridge next room, been there forever - streams netflix, hulu, youtube for a BRDP.
It's never been a problem also have a 2nd E2500 connecetd same that's much further away -- but not much traffic on it.
I set key renewal to '0' on all wireless and set ACK timing to '0' both radios.
Just did a reboot -- now we see ----
well everything connected back -- that's a good sign
'bout all I know
root@----:~# dmesg | tail
[ 33.118785] device ath1 entered promiscuous mode
[ 33.511460] br0: port 2(ath0) entered forwarding state
[ 33.882212] br0: port 3(ath1) entered forwarding state
[ 33.882267] br0: port 3(ath1) entered forwarding state
[ 34.401932] device vlan2 entered promiscuous mode
[ 35.286162] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle
[ 35.297075] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle
[ 35.380628] device vlan2 left promiscuous mode
[ 35.882698] br0: port 3(ath1) entered forwarding state
[ 2521.239776] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jan 1 00:00:21 ---- kern.err kernel: [ 35.286162] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle
Jan 1 00:00:21 ---- kern.err kernel: [ 35.297075] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle
only valid in nat table, not mangle
The only other change I made was put IP in DMZ. It is to a router w/static WAN running openVPN server which is working fine.
If decide to leave as is I'll just do a port forward and take out of DMZ ... but never seen that error before????
root@----:~# uptime
07:53:31 up 23:08, load average: 0.04, 0.02, 0.00
--
DD-WRT v3.0-r30731M std (10/06/16)
Linux 3.18.42 #107 SMP PREEMPT Thu Oct 6 01:39:39 CEST 2016 armv7l
This is good build!!!
DD-WRT v3.0-r30731M std (10/06/16)
Key Renewal back to normal setting
Leave Sensitivity Range (ACK Timing) on '0' both radios
Disable DMZ
Add new in Static Leases
Add set in Port Range Forwarding
Reboot
Not up 'bout 45 min but there is NO funny stuff in dmesg or syslogd.
The Note-8 is streaming news 2' from the ea8500 - no problem now.
All looks veddy berry good -
DD-WRT v3.0-r30731M std (10/06/16)
Key Renewal back to normal setting
Leave Sensitivity Range (ACK Timing) on '0' both radios
Disable DMZ
Add new in Static Leases
Add set in Port Range Forwarding
Reboot
Not up 'bout 45 min but there is NO funny stuff in dmesg or syslogd.
The Note-8 is streaming news 2' from the ea8500 - no problem now.
All looks veddy berry good -
This is a darn good router and BS-30731M is good build .. think I'm gonna keep both
root@--:~# dmesg | tail
[ 30.353376] br0: port 2(ath0) entered forwarding state
[ 30.353411] br0: port 2(ath0) entered forwarding state
[ 31.913732] device ath1 entered promiscuous mode
[ 32.351702] br0: port 2(ath0) entered forwarding state
[ 32.620903] br0: port 3(ath1) entered forwarding state
[ 32.620952] br0: port 3(ath1) entered forwarding state
[ 33.082896] device vlan2 entered promiscuous mode
[ 33.938564] device vlan2 left promiscuous mode
[ 34.611449] br0: port 3(ath1) entered forwarding state
[ 633.515635] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
root@--:~# uptime
09:02:41 up 16:38, load average: 1.88, 1.21, 0.49
high load -- doing file transfer thru SAMBA
and I can live with this
alrighthen I'll go away & quit talking to myself unless something breaks
--
EDIT:
only spikes I see in bufferbloat is in upload
r30731M std (10/06/16)
htb blip couple days ago .... hummm
root@--:~# dmesg | tail
[ 30.353411] br0: port 2(ath0) entered forwarding state
[ 31.913732] device ath1 entered promiscuous mode
[ 32.351702] br0: port 2(ath0) entered forwarding state
[ 32.620903] br0: port 3(ath1) entered forwarding state
[ 32.620952] br0: port 3(ath1) entered forwarding state
[ 33.082896] device vlan2 entered promiscuous mode
[ 33.938564] device vlan2 left promiscuous mode
[ 34.611449] br0: port 3(ath1) entered forwarding state
[ 633.515635] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[263097.611965] htb: too many events!
root@--:~# uptime
07:30:38 up 5 days, 15:05, load average: 0.00, 0.02, 0.00
What is the default dBm setting for both radios? What is the max and what is a safe setting? _________________ I am far from a guru, I'm barely a novice.
DD-WRT v3.0-r30800M kongat (10/27/16)
Linux 3.18.42 #231 SMP PREEMPT Thu Oct 27 22:57:22 CEST 2016 armv7l
NO RESET
Not good.
Looked real clean & pretty with new fixes.
Even copied several GBs to/from SAMBA share without problem.
Nothing noteworthy in logs.
1st crash/reboot approx 18 min at normal use.
In GUI disabled SAMBA, unmount and disable core USB --- that caused crash.
Top light out, all port lights flashing. Power button off for 10 sec.
Booted back into 30800M fine all good for approx 12 min then it crashed & rebooted.
Run well for 23 minutes this time till crashed again.
Reenabled USB & SAMBA without problem ... No time to fool with it any
longer so booted part2 back into BS_30771 -- all good there....
Would like to know if anyone has better luck with 30800M
I started having problems after 30690M
Since I'm not having any issues with this build, it looks like this is where I get off. Don't fix what isn't broken, as they say
I started having problems after 30690M
Since I'm not having any issues with this build, it looks like this is where I get off. Don't fix what isn't broken, as they say
kong 30700M is a very good build + it has Recursive DNS Resolving.
I had to set ack timing to '0' both radios for all devices to work well..... Had no problems then.
BS 30731 also very good .... just showing wrong tx rates in GUI
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Oct 28, 2016 3:14 Post subject:
if anyone would like r30805 bs build for testing i can provide it (assuming u know how to restore this router in the event its a broken build, i take no responsibility etc bla bla). im running it on the somewhat similar r7800 its fine, runs no brick, also running it on dir-862L, runs no brick. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
if anyone would like r30805 bs build for testing i can provide it (assuming u know how to restore this router in the event its a broken build, i take no responsibility etc bla bla). im running it on the somewhat similar r7800 its fine, runs no brick, also running it on dir-862L, runs no brick.
Did you run 30800M on the r7800?
Give me a second and I'll PM you an UL directory to send bs 30805
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Oct 28, 2016 3:46 Post subject:
mrjcd wrote:
tatsuya46 wrote:
if anyone would like r30805 bs build for testing i can provide it (assuming u know how to restore this router in the event its a broken build, i take no responsibility etc bla bla). im running it on the somewhat similar r7800 its fine, runs no brick, also running it on dir-862L, runs no brick.
Did you run 30800M on the r7800?
Give me a second and I'll PM you an UL directory to send bs 30805
yes, it seemed identical as r30805, but thats on a r7800. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
