New Build 35927 (BS): 05-13-2018-r35927

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3, 4, 5  Next
Author Message
BrainSlayer
Site Admin


Joined: 06 Jun 2006
Posts: 6814
Location: Dresden, Germany

PostPosted: Wed May 16, 2018 4:28    Post subject: Reply with quote
labo wrote:
Router: Asus RT-AC5300
Firmware: DD-WRT v3.0-r35927 std 05/13/18
Status: boot loop
Errors: 5Ghz radio Repeater Bridge mode is broken again. VHT160 mode is now missing in GUI.


Coredump:

ERROR: Necessary service setting not found: milkfish_username - aborting.
The Milkfish Router Services
Restoring SIP ddsubscriber database from NVRAM…
Empty.
The Milkfish Router Services
Restoring SIP ddaliases database from NVRAM…
Empty.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = 80004000
[00000000] *pgd=00000000
Internal error: Oops - BUG: 80000007 [#1] SMP ARM
Modules linked in: shortcut_fe dhd wl(P) igs(P) emf(P) switch_robo switch_core et(P)
CPU: 1 PID: 207 Comm: kworker/1:1 Tainted: P 4.4.131 #3086
Hardware name: Northstar Prototype
Workqueue: events _254 [dhd]
task: 87bc2800 ti: 87bca000 task.ti: 87bca000
PC is at 0x0
LR is at _939+0x6c/0xa8 [dhd]
pc : [<00000000>] lr : [<7f45fcac>] psr: 80000013
sp : 87bcbe70 ip : 80441f40 fp : 87bcbea4
r10: 00000000 r9 : 00000004 r8 : 00000000
r7 : 00000000 r6 : 87b46dc0 r5 : 00000000 r4 : ffffe000
r3 : 87bcbe70 r2 : 00000004 r1 : 8500a000 r0 : 87b46dc0
Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 070e404a DAC: 00000055
Process kworker/1:1 (pid: 207, stack limit = 0x87bca190)
Stack: (0x87bcbe70 to 0x87bcc000)
be60: 00000000 00000000 857e1900 87b67400
be80: 857e1980 857e8000 a0000013 00000000 00000000 8050ba84 87bcbec4 87bcbea8
bea0: 7f45fd24 7f45fc4c 857e19a0 857e1980 0000000c a0000013 87bcbef4 87bcbec8
bec0: 7f461db8 7f45fcf4 87bcbf0c 87853d08 87b67400 7f45fce8 857e1980 87b92780
bee0: 86be1480 86be6e00 87bcbf24 87bcbef8 8004d42c 7f461d14 00000000 8050ba84
bf00: 87b92780 86be1480 86be1480 87b92798 86be1494 00000000 87bcbf5c 87bcbf28
bf20: 8004e59c 8004d284 804fe100 87bca000 00000000 00000000 87b93780 87b92780
bf40: 8004e39c 00000000 00000000 00000000 87bcbfac 87bcbf60 80052890 8004e3a8
bf60: 40000000 00000000 00000000 87b92780 00000000 00000000 87bcbf78 87bcbf78
bf80: 00000000 00000000 87bcbf88 87bcbf88 87b93780 80052798 00000000 00000000
bfa0: 00000000 87bcbfb0 80009600 800527a4 00000000 00000000 00000000 00000000
bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 87bcbff4 00000000
Backtrace:
[<7f45fc40>] (_939 [dhd]) from [<7f45fd24>] (_336+0x3c/0xfc [dhd])
r10:8050ba84 r9:00000000 r8:00000000 r7:a0000013 r6:857e8000 r5:857e1980
r4:87b67400
[<7f45fce8>] (_336 [dhd]) from [<7f461db8>] (_254+0xb0/0xbc [dhd])
r7:a0000013 r6:0000000c r5:857e1980 r4:857e19a0
[<7f461d08>] (_254 [dhd]) from [<8004d42c>] (process_one_work+0x1b4/0x2d8)
r7:86be6e00 r6:86be1480 r5:87b92780 r4:857e1980
[<8004d278>] (process_one_work) from [<8004e59c>] (worker_thread+0x200/0x3e4)
r9:00000000 r8:86be1494 r7:87b92798 r6:86be1480 r5:86be1480 r4:87b92780
[<8004e39c>] (worker_thread) from [<80052890>] (kthread+0xf8/0x100)
r10:00000000 r9:00000000 r8:00000000 r7:8004e39c r6:87b92780 r5:87b93780
r4:00000000
[<80052798>] (kthread) from [<80009600>] (ret_from_fork+0x14/0x34)
r7:00000000 r6:00000000 r5:80052798 r4:87b93780
Code: bad PC value
—[ end trace 6634b0e0931cb9b6 ]—
Kernel panic - not syncing: Fatal exception
CPU0: stopping
CPU: 0 PID: 0 Comm: swapper/0 Tainted: P D 4.4.131 #3086
Hardware name: Northstar Prototype
Backtrace:
[<8001b950>] (dump_backtrace) from [<8001bbd8>] (show_stack+0x18/0x1c)
r7:804f1f20 r6:60000193 r5:00000000 r4:80510da0
[<8001bbc0>] (show_stack) from [<8016401c>] (dump_stack+0x8c/0xa0)
[<80163f90>] (dump_stack) from [<8001d754>] (handle_IPI+0x110/0x1a8)
r7:804f1f20 r6:00000000 r5:00000000 r4:805231a0
[<8001d644>] (handle_IPI) from [<80009394>] (gic_handle_irq+0x78/0x7c)
r7:b0100100 r6:804f1f20 r5:b010010c r4:804ffb1c
[<8000931c>] (gic_handle_irq) from [<80009ea0>] (__irq_svc+0x40/0x54)
Exception stack(0x804f1f20 to 0x804f1f68)
1f20: 86bd4248 00000000 00040128 8000a9c0 804f0000 804ff8e0 80433a50 804ec224
1f40: 804f1f90 804c38c8 00000000 804f1f7c 804f1f80 804f1f70 80019564 80019568
1f60: 60000013 ffffffff
r9:804c38c8 r8:804f1f90 r7:804f1f54 r6:ffffffff r5:60000013 r4:80019568
[<8001952c>] (arch_cpu_idle) from [<8006c424>] (default_idle_call+0x30/0x34)
[<8006c3f4>] (default_idle_call) from [<8006c530>] (cpu_startup_entry+0x108/0x13c)
[<8006c428>] (cpu_startup_entry) from [<80012aac>] (rest_init+0x80/0x84)
r7:80523020 r4:00000000
[<80012a2c>] (rest_init) from [<8049acc0>] (start_kernel+0x320/0x32c)
[<8049a9a0>] (start_kernel) from [<0000807c>] (0x807c)
Rebooting in 10 seconds..



the crash is related to your repeater bridge tries. the ac5300 has no repeater bridge nor client bridge support. i still left it in the gui for testing. the differences on these devices is that they are all based on a own wifi firmware on the wifi chip itself which will it make impossible to implement fake bridge modes. it may work under some conditions, but officially i cannot support this.

disable it. use client mode or repeater or ap mode, everything else will likelly fail
fo the missing vht160 mode. this is a bug fix. the ac5300 has no vht160 support

thx

_________________
one cigarette costs 2 minutes of your life.
one bottle of beer costs 4 minutes of your life.
one working day costs 8 hours of your life.

Yummee:
Linux DD-WRT 4.14.8 #42 SMP PREEMPT Thu Dec 21 18:11:16 CET 2017 armv7l DD-WRT
root@DD-WRT:/sys# nvram get DD_BOARD
Netgear R7800
Sponsor
Therameatelf
DD-WRT User


Joined: 31 Jan 2016
Posts: 54

PostPosted: Wed May 16, 2018 13:02    Post subject: Reply with quote
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r35927 std (05/13/18)
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Status: VPN AP

CPU Model: Broadcom BCM4708
CPU Cores: 2
CPU Features: EDSP
CPU Clock: 800 MHz
Load Average: 59% 1.00, 1.21, 1.31
Temperature: CPU 64.7 °C / Not available

After some moderate streaming, load averages reported >1. Graph (59%) probably close. Radios are turned off ATM.
parco
DD-WRT Novice


Joined: 10 Sep 2017
Posts: 48

PostPosted: Wed May 16, 2018 15:25    Post subject: Reply with quote
jwh7 wrote:
parco wrote:
But anyway, done a hard reset (30s power on, 30s power off, 30s power on) soon before and now the WebUI become fine again Very Happy And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response!
Weren't you saying before that you had issues in 33555? So it might be that a hard reset in 35927 might work as well?

Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: AP
Issues: All appears ok


No issues in r33555, that's the stablest ever DD-WRT for my EA2700. Only all builds after r33555 until now are buggier and buggier.

What I meant was, when I was flashing the firmware back to r33555 via the Web page of r35927, it bricked the http web interface, can't load http://192.168.1.1 by any browsers, but the router still worked, can still go through to facebook or any other websites else.

The web service bricked until I'd done a hard reset, then I could load into http://192.168.1.1 and saw the page showed me that's r33555. Then I'd just re-flashed to r33555 one more time by the web page of r33555, smoothly successful like a virgin. Now all things just are running very well, no more wifi sessions hangs.

Wireless Mode: AP
Wireless Network Mode: Mixed
Security Mode: WPA2 Personal Mixed
WPA Algorithms: TKIP+AES
Regulatory Domain: Hong Kong
Router Name: "Cisco Linksys EA2700"
Timezone: Asia/Hong_Kong
Time Server Host: stdtime.gov.hk
NAT sessions: 65536
UPnP enabled

All other else stayed in default values.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 881
Location: Texas, USA

PostPosted: Wed May 16, 2018 16:07    Post subject: Reply with quote
parco wrote:
jwh7 wrote:
parco wrote:
But anyway, done a hard reset (30s power on, 30s power off, 30s power on) soon before and now the WebUI become fine again Very Happy And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response!
Weren't you saying before that you had issues in 33555? So it might be that a hard reset in 35927 might work as well?

Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: AP
Issues: All appears ok


No issues in r33555, that's the stablest ever DD-WRT for my EA2700. Only all builds after r33555 until now are buggier and buggier.

What I meant was, when I was flashing the firmware back to r33555 via the Web page of r35927, it bricked the http web interface, can't load http://192.168.1.1 by any browsers, but the router still worked, can still go through to facebook or any other websites else.

The web service bricked until I'd done a hard reset, then I could load into http://192.168.1.1 and saw the page showed me that's r33555. Then I'd just re-flashed to r33555 one more time by the web page of r33555, smoothly successful like a virgin. Now all things just are running very well, no more wifi sessions hangs.

Wireless Mode: AP
Wireless Network Mode: Mixed
Security Mode: WPA2 Personal Mixed
WPA Algorithms: TKIP+AES
Regulatory Domain: Hong Kong
Router Name: "Cisco Linksys EA2700"
Timezone: Asia/Hong_Kong
Time Server Host: stdtime.gov.hk
NAT sessions: 65536
UPnP enabled

All other else stayed in default values.


Try using strictly AES for your algorithms and WPA Personal (not mixed). That and if you're using Windows as your client machine, and the wifi is an Intel adapter, update your drivers directly from Intel. Not having your specific router sitting in front of me to break, er, troubleshoot, I'm taking a shot in the dark here, but.
parco
DD-WRT Novice


Joined: 10 Sep 2017
Posts: 48

PostPosted: Wed May 16, 2018 16:50    Post subject: Reply with quote
kernel-panic69 wrote:
parco wrote:
jwh7 wrote:
parco wrote:
But anyway, done a hard reset (30s power on, 30s power off, 30s power on) soon before and now the WebUI become fine again Very Happy And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response!
Weren't you saying before that you had issues in 33555? So it might be that a hard reset in 35927 might work as well?

Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: AP
Issues: All appears ok


No issues in r33555, that's the stablest ever DD-WRT for my EA2700. Only all builds after r33555 until now are buggier and buggier.

What I meant was, when I was flashing the firmware back to r33555 via the Web page of r35927, it bricked the http web interface, can't load http://192.168.1.1 by any browsers, but the router still worked, can still go through to facebook or any other websites else.

The web service bricked until I'd done a hard reset, then I could load into http://192.168.1.1 and saw the page showed me that's r33555. Then I'd just re-flashed to r33555 one more time by the web page of r33555, smoothly successful like a virgin. Now all things just are running very well, no more wifi sessions hangs.

Wireless Mode: AP
Wireless Network Mode: Mixed
Security Mode: WPA2 Personal Mixed
WPA Algorithms: TKIP+AES
Regulatory Domain: Hong Kong
Router Name: "Cisco Linksys EA2700"
Timezone: Asia/Hong_Kong
Time Server Host: stdtime.gov.hk
NAT sessions: 65536
UPnP enabled

All other else stayed in default values.


Try using strictly AES for your algorithms and WPA Personal (not mixed). That and if you're using Windows as your client machine, and the wifi is an Intel adapter, update your drivers directly from Intel. Not having your specific router sitting in front of me to break, er, troubleshoot, I'm taking a shot in the dark here, but.


But WPA2 Personal Mixed and TKIP+AES are really running very fine in r33555 without any Wifi jams, but only hang wifi from r33607 until r35927 for my EA2700.

All my Wifi clients are android phones, an LG smart TV and a Windows 10 notebook with Broadcom Wireless Adapter. The rest 2 Windows 10 desktop PCs are wired connections. No any connection hangs for ethernet, they're always fine.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 881
Location: Texas, USA

PostPosted: Wed May 16, 2018 17:11    Post subject: Reply with quote
parco wrote:
But WPA2 Personal Mixed and TKIP+AES are really running very fine in r33555 without any Wifi jams, but only hang wifi from r33607 until r35927 for my EA2700.

All my Wifi clients are android phones, an LG smart TV and a Windows 10 notebook with Broadcom Wireless Adapter. The rest 2 Windows 10 desktop PCs are wired connections. No any connection hangs for ethernet, they're always fine.


But you're defeating the purpose of wi-fi security with those settings. All of your client devices should support AES encryption. Running mixed like that is probably half the problem, but that's just my thoughts on the matter.
Brimmy
DD-WRT User


Joined: 29 Mar 2015
Posts: 362

PostPosted: Thu May 17, 2018 11:17    Post subject: Reply with quote
Router/Version: Buffalo WZR-1750DHP/DHPD
Firmware: DD-WRT v3.0-r35927 std (05/13/18
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Previous: BSr34760
Mode/Status: Seems ok
CPU overclocked to 1200mhz from default 800mhz
Reset: yes via webGUI and via telnet erase nvram
Issues/Errors: DNSCrypt kills internet connection only if i use a resolver that is not IPV6, no overclocking support and NTP does not load only if i use a DNSCrypt resolver that is not IPV6 and unit must be power cycled after flash or the Buffalo logo would blink 3 times every ten seconds or so indicating bad/corrupt flash

Not sure if to take out the DNSCrypt as an issues since i saw on another post versin 1 is "dead" and now there is a version 2. WIFI on 2.4&5Ghz works wiht no issues.

The following chains are for iptables -L only.

iptables -L (without a IPV6 DNSCrypt)

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain advgrp_1 (0 references)
target prot opt source destination

Chain advgrp_10 (0 references)
target prot opt source destination

Chain advgrp_2 (0 references)
target prot opt source destination

Chain advgrp_3 (0 references)
target prot opt source destination

Chain advgrp_4 (0 references)
target prot opt source destination

Chain advgrp_5 (0 references)
target prot opt source destination

Chain advgrp_6 (0 references)
target prot opt source destination

Chain advgrp_7 (0 references)
target prot opt source destination

Chain advgrp_8 (0 references)
target prot opt source destination

Chain advgrp_9 (0 references)
target prot opt source destination

Chain grp_1 (0 references)
target prot opt source destination

Chain grp_10 (0 references)
target prot opt source destination

Chain grp_2 (0 references)
target prot opt source destination

Chain grp_3 (0 references)
target prot opt source destination

Chain grp_4 (0 references)
target prot opt source destination

Chain grp_5 (0 references)
target prot opt source destination

Chain grp_6 (0 references)
target prot opt source destination

Chain grp_7 (0 references)
target prot opt source destination

Chain grp_8 (0 references)
target prot opt source destination

Chain grp_9 (0 references)
target prot opt source destination

Chain lan2wan (0 references)
target prot opt source destination

Chain logaccept (0 references)
target prot opt source destination

Chain logdrop (0 references)
target prot opt source destination

Chain logreject (0 references)
target prot opt source destination

Chain trigger_out (0 references)
target prot opt source destination

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

iptables -L (with a IPV6 DNSCrypt)

Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP 0 -- 100.66.0.0/16 100.66.68.216
DROP 0 -f anywhere anywhere
DROP tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE
DROP tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,PSH,ACK,URG
ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT udp -- anywhere anywhere udp spt:bootps dpt:bootpc
DROP udp -- anywhere anywhere udp dpt:route
ACCEPT udp -- anywhere anywhere udp dpt:route
ACCEPT udp -- anywhere anywhere udp dpt:route
ACCEPT 0 -- anywhere anywhere
DROP icmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state NEW
ACCEPT 0 -- anywhere anywhere state NEW
DROP 0 -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere tcp dpt:http limit: avg 25/min burst 100
ACCEPT tcp -- anywhere anywhere tcp flags:RST/RST limit: avg 2/sec burst 2
DROP 0 -- anywhere anywhere recent: CHECK seconds: 8640 name: portscan side: source

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
lan2wan 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere
DROP tcp -- anywhere anywhere tcp dpt:1723
DROP udp -- anywhere anywhere udp dpt:l2f
DROP udp -- anywhere anywhere udp dpt:isakmp
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:27200
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27200
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:27050
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:1500
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3005
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3101
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:4380
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27030
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:28960
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3074
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:3074
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3074
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:27050
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27030
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:1150
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:1150
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:28910
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:5165
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27901
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:27050
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27015
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27030
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:4380
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:27200
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27200
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpts:27014:27050
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:1500
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3005
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3101
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:3478:4380
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:27000:27030
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:28960
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3074
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:3074
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:3074
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpts:27014:27050
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:27000:27030
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpts:1116:1150
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:1116:1150
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:28910
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:5165
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:27900:27901
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpts:27014:27050
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:27000:27015
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpts:27015:27030
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:4380
TRIGGER 0 -- anywhere anywhere TRIGGER type:in match:0 relate:0
trigger_out 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state NEW
DROP 0 -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- anywhere anywhere

Chain advgrp_1 (0 references)
target prot opt source destination

Chain advgrp_10 (0 references)
target prot opt source destination

Chain advgrp_2 (0 references)
target prot opt source destination

Chain advgrp_3 (0 references)
target prot opt source destination

Chain advgrp_4 (0 references)
target prot opt source destination

Chain advgrp_5 (0 references)
target prot opt source destination

Chain advgrp_6 (0 references)
target prot opt source destination

Chain advgrp_7 (0 references)
target prot opt source destination

Chain advgrp_8 (0 references)
target prot opt source destination

Chain advgrp_9 (0 references)
target prot opt source destination

Chain grp_1 (0 references)
target prot opt source destination

Chain grp_10 (0 references)
target prot opt source destination

Chain grp_2 (0 references)
target prot opt source destination

Chain grp_3 (0 references)
target prot opt source destination

Chain grp_4 (0 references)
target prot opt source destination

Chain grp_5 (0 references)
target prot opt source destination

Chain grp_6 (0 references)
target prot opt source destination

Chain grp_7 (0 references)
target prot opt source destination

Chain grp_8 (0 references)
target prot opt source destination

Chain grp_9 (0 references)
target prot opt source destination

Chain lan2wan (1 references)
target prot opt source destination

Chain logaccept (0 references)
target prot opt source destination
LOG 0 -- anywhere anywhere state NEW LOG level warning tcp-sequence tcp-options ip-options prefix `ACCEPT '
ACCEPT 0 -- anywhere anywhere

Chain logdrop (0 references)
target prot opt source destination
LOG 0 -- anywhere anywhere state NEW LOG level warning tcp-sequence tcp-options ip-options prefix `DROP '
LOG 0 -- anywhere anywhere state INVALID LOG level warning tcp-sequence tcp-options ip-options prefix `DROP '
DROP 0 -- anywhere anywhere

Chain logreject (0 references)
target prot opt source destination
LOG 0 -- anywhere anywhere LOG level warning tcp-sequence tcp-options ip-options prefix `WEBDROP '
REJECT tcp -- anywhere anywhere reject-with tcp-reset

Chain trigger_out (1 references)
target prot opt source destination
TRIGGER tcp -- anywhere anywhere tcp dpt:27200 TRIGGER type:out match:27200 relate:27200
TRIGGER udp -- anywhere anywhere udp dpt:27200 TRIGGER type:out match:27200 relate:27200
TRIGGER tcp -- anywhere anywhere tcp dpts:27014:27050 TRIGGER type:out tcp match:27014-27050 relate:27014-27050
TRIGGER udp -- anywhere anywhere udp dpt:1500 TRIGGER type:out udp match:1500 relate:1500
TRIGGER udp -- anywhere anywhere udp dpt:3005 TRIGGER type:out udp match:3005 relate:3005
TRIGGER udp -- anywhere anywhere udp dpt:3101 TRIGGER type:out udp match:3101 relate:3101
TRIGGER udp -- anywhere anywhere udp dpts:3478:4380 TRIGGER type:out udp match:3478-4380 relate:3478-4380
TRIGGER udp -- anywhere anywhere udp dpts:27000:27030 TRIGGER type:out udp match:27000-27030 relate:27000-27030
TRIGGER udp -- anywhere anywhere udp dpt:28960 TRIGGER type:out udp match:28960 relate:28960
TRIGGER udp -- anywhere anywhere udp dpt:3074 TRIGGER type:out udp match:3074 relate:3074
TRIGGER tcp -- anywhere anywhere tcp dpt:3074 TRIGGER type:out match:3074 relate:3074
TRIGGER udp -- anywhere anywhere udp dpt:3074 TRIGGER type:out match:3074 relate:3074
TRIGGER tcp -- anywhere anywhere tcp dpts:27014:27050 TRIGGER type:out tcp match:27014-27050 relate:27014-27050
TRIGGER udp -- anywhere anywhere udp dpts:27000:27030 TRIGGER type:out udp match:27000-27030 relate:27000-27030
TRIGGER tcp -- anywhere anywhere tcp dpts:1116:1150 TRIGGER type:out match:1116-1150 relate:1116-1150
TRIGGER udp -- anywhere anywhere udp dpts:1116:1150 TRIGGER type:out match:1116-1150 relate:1116-1150
TRIGGER tcp -- anywhere anywhere tcp dpt:28910 TRIGGER type:out tcp match:28910 relate:28910
TRIGGER udp -- anywhere anywhere udp dpt:5165 TRIGGER type:out udp match:5165 relate:5165
TRIGGER udp -- anywhere anywhere udp dpts:27900:27901 TRIGGER type:out udp match:27900-27901 relate:27900-27901
TRIGGER tcp -- anywhere anywhere tcp dpts:27014:27050 TRIGGER type:out tcp match:27014-27050 relate:27014-27050
TRIGGER udp -- anywhere anywhere udp dpts:27000:27015 TRIGGER type:out udp match:27000-27015 relate:27000-27015
TRIGGER udp -- anywhere anywhere udp dpts:27015:27030 TRIGGER type:out udp match:27015-27030 relate:27015-27030
TRIGGER udp -- anywhere anywhere udp dpt:4380 TRIGGER type:out udp match:4380 relate:4380
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2155
Location: Indy

PostPosted: Thu May 17, 2018 13:13    Post subject: Reply with quote
Brimmy wrote:
Not sure if to take out the DNSCrypt as an issues since i saw on another post versin 1 is "dead" and now there is a version 2.
Ya, I updated the OP about that a couple days ago actually:
jwh7 wrote:
3. (Brimmy) WZR-1750DHP/DHPD DNSCrypt kills internet connection, no overclocking, NTP does not load
The dnscrypt issue is because mostly only v2 protocols are now used, which requires Golang that DD can't use:
http://svn.dd-wrt.com/ticket/6246

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: Builds, Types, Modes, Changelog, Peacock, Demo #
x64 OPNsense 19.1.6|EA6900v1.1@1GHz FT 2019.2|DD 39572: WNDR4500v2, WNDR4000@533, E1500@353, R6300v1,
2*E2500, WRT54*@250: GLv1.1 nsg, GSv6 µ
|RT-N66U@663 Merlin 380.70|OEM: WGR614v10@400-WNR1000v3 mod
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 881
Location: Texas, USA

PostPosted: Thu May 17, 2018 16:07    Post subject: Reply with quote
myersw wrote:
Submit tickets here.
http://svn.dd-wrt.com/
You will need to create a user id. You can also see what is happening behind the curtain here.


Can't create a user ID, captcha is DOWN. I was going to add to a ticket about Broadcom K3x regarding a nas crash and syslog time errors, because it's not just the webGUI that is spitting out weird offset times now, I get it when I 'tail -f /var/log/messages' and 'cat /var/log/messages' as well as run commands in the webGUI.
Brimmy
DD-WRT User


Joined: 29 Mar 2015
Posts: 362

PostPosted: Thu May 17, 2018 16:07    Post subject: Reply with quote
Nicely done jwh7 and thanks.
parco
DD-WRT Novice


Joined: 10 Sep 2017
Posts: 48

PostPosted: Thu May 17, 2018 16:36    Post subject: Reply with quote
kernel-panic69 wrote:
parco wrote:
But WPA2 Personal Mixed and TKIP+AES are really running very fine in r33555 without any Wifi jams, but only hang wifi from r33607 until r35927 for my EA2700.

All my Wifi clients are android phones, an LG smart TV and a Windows 10 notebook with Broadcom Wireless Adapter. The rest 2 Windows 10 desktop PCs are wired connections. No any connection hangs for ethernet, they're always fine.


But you're defeating the purpose of wi-fi security with those settings. All of your client devices should support AES encryption. Running mixed like that is probably half the problem, but that's just my thoughts on the matter.


OK but anyway WPA2 Personal Mixed and TKIP+AES ain't making my Wifi transportation hang in r33555, so I don't think that matters about the wifi hang problems of the builds after r33555.

There should be some bugs or coding problems for packets scheduling, multi-tasking, multi-threading or something like so in wifi sessions, which make more and more deadlocks for wifi packets TX or RX.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 881
Location: Texas, USA

PostPosted: Thu May 17, 2018 18:55    Post subject: Reply with quote
parco wrote:

OK but anyway WPA2 Personal Mixed and TKIP+AES ain't making my Wifi transportation hang in r33555, so I don't think that matters about the wifi hang problems of the builds after r33555.


The hang problems may not necessarily be related to that, but looking back at a few things, you can run WPA2 Mixed, but you'd want to run AES for encryption for security reasons. There is an open ticket for K3x Broadcom for an NAS crash, which drops the radios:

http://svn.dd-wrt.com/ticket/6310

I have been trying to trap the same crash in my syslogs to post here since svn won't let me create a new account because CAPTCHA is down Rolling Eyes

parco wrote:

There should be some bugs or coding problems for packets scheduling, multi-tasking, multi-threading or something like so in wifi sessions, which make more and more deadlocks for wifi packets TX or RX.


^ So dig through your syslogs and the source code and help find the problem?
mbze430
DD-WRT User


Joined: 14 May 2012
Posts: 196

PostPosted: Thu May 17, 2018 22:59    Post subject: Reply with quote
Router Model: ASUS AC3200
Firmware: DD-WRT v3.0-r35927 std (05/13/1Cool
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Status:


my ASUS AC-3200 completely lost BOTH the 5ghz WIFI. 2.4ghz works fine.

The GUI shows the 5GHZ, BUT doing a Wifi scan on another machine or phone, the 5GHZ WIFI Mac doesnt show up at all.

_________________
ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AC66U - Broken
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 881
Location: Texas, USA

PostPosted: Fri May 18, 2018 2:23    Post subject: Setting time zone to ZULU seems to be a workaround of sorts Reply with quote
Reset the time zone on my E4200 v1 to ZULU (UTC/GMT) in the Setup tab on the webGUI and have not had any wi-fi issues. I am guessing this is possibly related to the NTP / NAS issues. Don't have syslog to prove anything either way and can't register on SVN because of captcha being down, but wanted to share this.

EDIT: And of course, as soon as I post this, wifi goes screwy Rolling Eyes
parco
DD-WRT Novice


Joined: 10 Sep 2017
Posts: 48

PostPosted: Fri May 18, 2018 9:07    Post subject: Reply with quote
kernel-panic69 wrote:
parco wrote:

OK but anyway WPA2 Personal Mixed and TKIP+AES ain't making my Wifi transportation hang in r33555, so I don't think that matters about the wifi hang problems of the builds after r33555.


The hang problems may not necessarily be related to that, but looking back at a few things, you can run WPA2 Mixed, but you'd want to run AES for encryption for security reasons. There is an open ticket for K3x Broadcom for an NAS crash, which drops the radios:

http://svn.dd-wrt.com/ticket/6310

I have been trying to trap the same crash in my syslogs to post here since svn won't let me create a new account because CAPTCHA is down Rolling Eyes

parco wrote:

There should be some bugs or coding problems for packets scheduling, multi-tasking, multi-threading or something like so in wifi sessions, which make more and more deadlocks for wifi packets TX or RX.


^ So dig through your syslogs and the source code and help find the problem?

But..... how...? How to find them out? And I'd fallen back to r33555 now running, so all I can do is for the next build unluckily........
Goto page Previous  1, 2, 3, 4, 5  Next Display posts from previous:    Page 3 of 5
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum