New Build 35898 (BS): 05-07-2018-r35898 [k3x/2x wifi broken]

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Mon May 07, 2018 17:01    Post subject: New Build 35898 (BS): 05-07-2018-r35898 [k3x/2x wifi broken] Reply with quote
Downloads at:
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/05-07-2018-r35898/
ftp://ftp.dd-wrt.com/betas/2018/05-07-2018-r35898/
Also: alternate DD-WRT website link.

Changelogs:
SVN Changelog: Since last build: 35874
Summary: (deprecated after 29739)

Notes:
1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer
2. krack fixes for Broadcom were completed in 33678, including k26 (33655) & k24 (33656).

Tickets closed as 'fixed' (Broadcom-related and general):

Issues, observations, and/or workarounds reported:
1. (egc) Policy-Based Routing broken if SFE enabled: http://svn.dd-wrt.com/ticket/5900
quarkysg's PBR+SFE fix: http://svn.dd-wrt.com/ticket/5986
2. Many router builds too big to flash: http://svn.dd-wrt.com/ticket/6144
3. (Brimmy) WZR-1750DHP/DHPD DNSCrypt kills internet connection, no overclocking, NTP does not load
4. ntp doesn't get time at boot in CB mode: fixed in r35920
Startup command: sleep 10;startservice process_monitor (alternative: ntpclient {ntp server})
5. Wireless is broken for all modes on all k3.x and k2.x builds after 35531.
Fixed in r35905 thru r35907, and validated with test build 35910; try 35912 Tickets: 6258, 6259, 6260

Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put in SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).

Template to copy (after "Code:") for posting a reply, be sure to include the mode in use:
Code:
[b]Router/Version: [/b]
[b]Firmware: [/b]
[b]Kernel: [/b]
[b]Mode: [/b]
[b]Issues: [/b]

WARNING: This build thread is for reporting success and/or problems with loading this experimental test build.
This is important info for developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Create a new thread to discuss specific problems or questions, and refrain to respond as this thread is for reporting, not support. Posts not meeting this criteria may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4


Last edited by jwh7 on Sat May 12, 2018 14:22; edited 8 times in total
Sponsor
myersw
DD-WRT Guru


Joined: 13 Jun 2006
Posts: 1608
Location: SE Michigan USA

PostPosted: Mon May 07, 2018 18:27    Post subject: Reply with quote
Router/Version: Netgear R8000
Firmware: DD-WRT v3.0-r35898 std (05/07/1Cool
Kernel: Linux 4.4.131 #3071 SMP Mon May 7 08:35:11 CEST 2018 armv7l
Mode: Gateway
Issues: None, but up less then 30 minutes

First again. Had already installed as I monitor the Marvell site and they had already announced the new build.

No issues so far, but I do not do anything like VPN, NAS or port forwarding, just good old routing and network wired and wireless support.

_________________
Unifi Security Gateway: Unifi Firmware
Netgear r7800: Voxel Firmware
Modem:Netgear CM500V voice and Data.
ISP:Comcast
tutorial for flashing "WRT" series:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813
DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117
Kong DD-WRT Config Tutorial:
http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/
I tried to be normal once. Worst 2 minutes ever.
flyzipper
DD-WRT Guru


Joined: 21 Feb 2016
Posts: 504

PostPosted: Mon May 07, 2018 18:41    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r35898 std ( 05/07/18 )
Kernel: Linux 4.4.131 #3066 SMP Mon May 7 08:04:54 CEST 2018 armv7l
Previous: r35874
Mode/Status: Gateway / working
Reset: no
Issues/Errors: None so far, but the paint's still wet.

Uptime: 1h 31m
Temperatures: CPU 64.1 °C / WL0 45.7 °C / WL1 49.5 °C

Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6868
Location: Romerike, Norway

PostPosted: Mon May 07, 2018 20:43    Post subject: Reply with quote
Router/Version: Asus RT-AC66U

Issues: Wifi still in Ad-hoc mode. Last working build is 35531. The Channel width setting (20/40/80) is back in the GUI.
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 1857
Location: Hung Hom, Hong Kong

PostPosted: Mon May 07, 2018 20:43    Post subject: Blank Source Net in Port Forwarding no longer affect WAN Reply with quote
A blank Source Net in Port Forwarding no longer crippled the WAN connection. Will post a full test report later.


_________________
Router: Asus RT-N18U (rev. A1)

Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
GitHub: https://github.com/changmw/changmw
jrscs
DD-WRT User


Joined: 09 Aug 2010
Posts: 425

PostPosted: Mon May 07, 2018 21:49    Post subject: Reply with quote
Router/Version: RT-AC87U A1
Firmware: DD-WRT v3.0-r35898 std (05/07/18 )
Kernel: Linux 4.4.131 #3073 SMP Mon May 7 08:49:26 CEST 2018 armv7l
Previous: DD-WRT v3.0-r35531
Mode/Status: Gateway/Ok
Reset: No
Issues/Errors: OK

Router/Version: RT-AC68R A1
Firmware: DD-WRT v3.0-r35898 std (05/07/18 )
Kernel: Linux 4.4.131 #3066 SMP Mon May 7 08:04:54 CEST 2018 armv7l
Previous: DD-WRT v3.0-r33986 std (12/04/17)
Mode/Status: Gateway/OK
Reset: No
Issues/Errors: OK

Tried to upgrade through the webgui but the router(s) became nonresponsive so telnet into the router to reboot. Tried it again with the same result. Tried a third time, but first rebooted the router using the webgui and then uploaded the update successfully through the webgui.

_________________
Netgear XR500, R7800
Asus AC87Ua1
Repeater Bridge
Netgear R6400v2otp


Last edited by jrscs on Wed May 09, 2018 15:51; edited 2 times in total
diyegr
DD-WRT Novice


Joined: 20 Dec 2014
Posts: 11

PostPosted: Tue May 08, 2018 2:32    Post subject: "Hairpin Mode" broken Reply with quote
Router/Version: RT-AC68U
Firmware: v3.0-r35898 std
Kernel: 4.4.131
Mode: Gateway
Issues: "Hairpin Mode" broken

I have my wireless network (eth1) on its own bridge (br1) to keep it isolated from my LAN on br0. When enabling "Hairpin Mode" on br1, WiFi breaks and computer can no longer connect.



cannot_connect_wifi.jpg
 Description:
 Filesize:  8.79 KB
 Viewed:  6075 Time(s)

cannot_connect_wifi.jpg



br1_hairpin_setting.jpg
 Description:
 Filesize:  39.57 KB
 Viewed:  6075 Time(s)

br1_hairpin_setting.jpg



syslog.txt
 Description:

Download
 Filename:  syslog.txt
 Filesize:  72.13 KB
 Downloaded:  404 Time(s)


_________________
Hardware: RT-AC68U - Firmware: DD-WRT v3.0-r35898 std - Kernel: 4.4.131
Brimmy
DD-WRT User


Joined: 29 Mar 2015
Posts: 398

PostPosted: Tue May 08, 2018 11:52    Post subject: Reply with quote
Router/Version: Buffalo WZR-1750DHP/DHPD
Firmware: DD-WRT v3.0-r35898 std (05/07/18
Kernel: Linux 4.4.131 #3066 SMP Mon May 7 08:04:54 CEST 2018 armv7l
Previous: BSr34760
Mode/Status: Wonky?/Different/not sure how to express it
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, unit must be power cycled after flash or the Buffalo logo would blink 3 times every ten seconds or so indicating bad/corrupt flash

IP addresses were changed for obvious reasons but matched in the initial read out. 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.

iptables -L

Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP 0 -- 22.40.0.1/16 22.44.0.212
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 udp -- anywhere PortaL.flowtrinidad.com udp dpt:53558
ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT gre -- 22.40.0.1/16 anywhere
ACCEPT tcp -- 22.40.0.1/16 anywhere tcp dpt:1723
lan2wan 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere
ACCEPT tcp -- anywhere PortaL.flowtrinidad.com tcp dpt:27391
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27391
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:27391
ACCEPT udp -- anywhere PortaL.flowtrinidad.com udp dpt:27391
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:27391 TRIGGER type:out match:27391 relate:27391
TRIGGER udp -- anywhere anywhere udp dpt:27391 TRIGGER type:out match:27391 relate:27391
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

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

iptables -t nat -L

Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT icmp -- anywhere 22.44.0.212 to:22.44.0.2
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:27391 to:22.44.0.133:27391
DNAT udp -- anywhere 22.44.0.212 udp dpt:27391 to:22.44.0.133:27391
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:27014 to:22.44.0.133:27050
DNAT udp -- anywhere 22.44.0.212 udp dpt:1500 to:22.44.0.133:1500
DNAT udp -- anywhere 22.44.0.212 udp dpt:3005 to:22.44.0.133:3005
DNAT udp -- anywhere 22.44.0.212 udp dpt:3101 to:22.44.0.133:3101
DNAT udp -- anywhere 22.44.0.212 udp dpt:3478 to:22.44.0.133:4380
DNAT udp -- anywhere 22.44.0.212 udp dpt:27000 to:22.44.0.133:27030
DNAT udp -- anywhere 22.44.0.212 udp dpt:28960 to:22.44.0.133:28960
DNAT udp -- anywhere 22.44.0.212 udp dpt:3074 to:22.44.0.133:3074
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:3074 to:22.44.0.133:3074
DNAT udp -- anywhere 22.44.0.212 udp dpt:3074 to:22.44.0.133:3074
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:27014 to:22.44.0.133:27050
DNAT udp -- anywhere 22.44.0.212 udp dpt:27000 to:122.44.0.133:27030
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:1116 to:22.44.0.133:1150
DNAT udp -- anywhere 22.44.0.212 udp dpt:1116 to:22.44.0.133:1150
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:28910 to:22.44.0.133:28910
DNAT udp -- anywhere 22.44.0.212 udp dpt:5165 to:22.44.0.133:5165
DNAT udp -- anywhere 22.44.0.212 udp dpt:27900 to:22.44.0.133:27901
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:27014 to:22.44.0.133:27050
DNAT udp -- anywhere 22.44.0.212 udp dpt:27000 to:22.44.0.133:27015
DNAT udp -- anywhere 22.44.0.212 udp dpt:27015 to:22.44.0.133:27030
DNAT udp -- anywhere 22.44.0.212 udp dpt:4380 to:22.44.0.133:4380
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:27391 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:27391 to:122.44.0.133
DNAT tcp -- anywhere 22.44.0.212 tcp dpts:27014:27050 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:1500 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:3005 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:3101 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:3478:4380 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:27000:27030 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:28960 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:3074 to:22.44.0.133
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:3074 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:3074 to:22.44.0.133
DNAT tcp -- anywhere 22.44.0.212 tcp dpts:27014:27050 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:27000:27030 to:22.44.0.133
DNAT tcp -- anywhere 22.44.0.212 tcp dpts:1116:1150 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:1116:1150 to:22.44.0.133
DNAT tcp -- anywhere 22.44.0.212 tcp dpt:28910 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:5165 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:27900:27901 to:122.44.0.133
DNAT tcp -- anywhere 22.44.0.212 tcp dpts:27014:27050 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:27000:27015 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpts:27015:27030 to:22.44.0.133
DNAT udp -- anywhere 22.44.0.212 udp dpt:4380 to:22.44.0.133
TRIGGER 0 -- anywhere 22.44.0.212 TRIGGER type:dnat match:0 relate:0
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
SNAT 0 -- 22.40.0.1/16 anywhere to:22.44.0.212
MASQUERADE 0 -- anywhere anywhere mark match 0x80000000/0x80000000
MASQUERADE 0 -- anywhere anywhere mark match 0xd001
kooper2013
DD-WRT User


Joined: 10 Jan 2013
Posts: 110
Location: DE

PostPosted: Tue May 08, 2018 18:13    Post subject: Asus RT-AC87U Reply with quote
Router/Version: Asus RT-AC87U
Firmware: DD-WRT v3.0-r35898 std (05/07/18 )
Kernel: Linux 4.4.131 #3073 SMP Mon May 7 08:49:26 CEST 2018 armv7l
Mode: Gateway with DHCP (dnsmasq) behind modem.
Issues: See below, but working in general. Uptime 1h10.

No reset.

-still no info of rate, channel, bandwidth graph and numbers of packets on Quantenna (5GHZ, wl1)
-can't adjust channel of wl1 (5GHz), only 'auto' with HT40 and AC/N mixed
-power-cycle required after update (from r35831). Manual reboot seems OK.
-time of syslog is 2 hours behind realtime
-Spamming syslog every 2 minutes: May 8 16:58:01 main user.info : Maybe upnp had died, we need to re-exec it

Happy that wl0 (2.4GHz) is working; it was not working on previous r35874 and I was afraid this would continue.
ntp really seems to work now (required for OpenVPN), without workaround of
Code:
sleep 5; stopservice process_monitor && startservice process_monitor;

or using the IP of the ntp-server.
No special options are used, OpenVPN not tested yet.

_________________
3xBuffalo WLI-H4-D1300
1xBuffalo WZR-D1800H
1xBuffalo WHR-HP-G300N
1xBuffalo WHR-1166D (stock f/w)
1xAsus RT-AC87U
1xAsus RT-AC88U
1xTP710
Steffen M.
DD-WRT User


Joined: 23 Jan 2008
Posts: 50
Location: Ulm, Germany

PostPosted: Tue May 08, 2018 21:13    Post subject: Re: New Build 35898 (BS): 05-07-2018-r35898 Reply with quote
Router/Version: Netgear R7000P
Firmware: DD-WRT v3.0-r35898 std (05/07/18)
Kernel: Linux wl-ap-eg 4.4.131 #3071 SMP Mon May 7 08:35:11 CEST 2018 armv7l DD-WRT
Mode: Client Bridge on 5 GHz, AP on 2.4 GHz, not gateway
Issues: The R7000P came up perfectly, but it unfortunately shows the same problem on its 5 GHz interface which also occurs with the latest Kong build:

I have set up the R7000P in client bridge mode on 5 GHz. The AP it connects to is a Netgear R7000. In this scenario, the R7000P seems to ignore incoming packets to the broadcast address on the 5 GHz device "most of the time". This breaks, e.g. ARP and DHCP. The ARP problem could be worked around by setting static ARP records in all other hosts which want to communicate with the R7000P or any clients behind it. This is not an option. For the DHCP problem I don't see any work-around besides setting up another DHCP or an DHCP forwarder on the R7000P. Nevertheless, both work-arounds do not solve the fundamental problem itself.

I suppose that the driver for "eth2" (wl0: May 1 2017 12:43:53 version 10.10.122.301 (r658909) FWID 01-1ebebd8a) is the cause of the problem. Resetting the R7000P to factory defaults didn't help. It is definitely not a "packet loss" problem caused by bad radio channel conditions.

A more detailed description of the problem can be found here: https://www.dd-wrt.com/forum/viewtopic.php?t=315026.

Kind regards,
Steffen


Last edited by Steffen M. on Wed May 09, 2018 12:22; edited 1 time in total
Therameatelf
DD-WRT User


Joined: 31 Jan 2016
Posts: 74

PostPosted: Wed May 09, 2018 0:49    Post subject: Reply with quote
Router Model: Linksys EA6500
Firmware: DD-WRT v3.0-r35898 giga (05/07/18)
Kernel: Linux 3.10.108-dd #19012 Mon May 7 13:07:46 CEST 2018 mips
Status:: Client Bridge
Previous: DD-WRT v3.0-r35452 giga (03/20/18)
Errors: No wireless connection. Attempt to configure as AP displayed only Diabled and Mixed mode choices.
Channel selection does appear for both 2.4 and 5GHZ.
Wireless status would only display channel unknown.
Reverting to 35452
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 1857
Location: Hung Hom, Hong Kong

PostPosted: Wed May 09, 2018 3:27    Post subject: Asus RT-N18U Reply with quote
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r35898 std (05/07/18)
Kernel: Linux 4.4.131 #3070 Mon May 7 08:29:14 CEST 2018 armv7l
Previous: DD-WRT v3.0-r35874 std (05/04/18)
Mode/Status: Access Point (AP), Wired Working
Reset: NO reset during firmware upgrade
Issues/Errors: no major problems, basic router

1. Running "cat /proc/mtd" in Administration -> Commands still didn't escape special characters properly:
Code:

dev:    size   erasesize  name
mtd0: 00080000 00020000   nameboott;
mtd1: 00180000 00020000   namenvram;
mtd2: 01e00000 00020000   namelinux;
mtd3: 01c80000 00020000   namerootfs
mtd4: 06000000 00020000   nameddwrt;

Running the same command in SSH shell:
Code:

root@RT-N18U:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 01e00000 00020000 "linux"
mtd3: 01c80000 00020000 "rootfs"
mtd4: 06000000 00020000 "ddwrt"


2. Lots of following message:

Code:
May  7 xx:xx:xx DD-WRT daemon.err httpd[1068]: Request Error Code 404: File not found.


Other error messages:
Code:
Jan  1 00:00:13 DD-WRT kern.err kernel: bcmsflash: found no supported devices
Jan  1 00:00:22 DD-WRT daemon.err process_monitor[1034]: cyclic NTP Update failed (servers time.hko.hk)
Jan  1 00:00:22 DD-WRT daemon.err process_monitor[1034]: Last update failed, we need to re-update after 30 seconds


3. No LAN LEDs... all off though there were physical cables.

Miscellaneous:
- Router not using IPv6, VPN nor USB
- Router is NOT working 24/7
- WiFi broken in k3.x editions since build 35531? 5GHz problem?

Old problems:
a. DDNS (inadyn) crashed in build 31722
b. Testing port-forwarding via WAN IP from within LAN not working in builds 34411-34760. Needed external proxy server.
c. NTP client not working in builds 34886-34876,35034 (affecting process_monitor?)
d. The ping to www.google.com increased from 2ms to 13ms after setting a defunct
WINS server in Setup->Basic Setup->DHCP->WINS
e. The "Source Net" field in Port-Forwarding screen displayd blank field as "¸ÖÁv",
from builds 32667 to 32767. Possibly null-pointer assignment?
f. Blank Source Net in Port Forwarding cripped WAN in builds 35831-35874! Needed to be "0.0.0.0/0" or no internet!



speedtest.dd-wrt.35898.asus.rt-n18u.jpg
 Description:
Speedtest.net result for DD-WRT BS 35898 and Asus RT-N18U
 Filesize:  6.02 KB
 Viewed:  5570 Time(s)

speedtest.dd-wrt.35898.asus.rt-n18u.jpg



_________________
Router: Asus RT-N18U (rev. A1)

Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
GitHub: https://github.com/changmw/changmw
Therameatelf
DD-WRT User


Joined: 31 Jan 2016
Posts: 74

PostPosted: Wed May 09, 2018 5:37    Post subject: Reply with quote
Router Model: Linksys E3000
Firmware: DD-WRT v3.0-r35898 mega (05/07/18)
Kernel: Linux 3.10.108-dd #19028 Mon May 7 13:23:03 CEST 2018 mips
Status: AP
Previous: DD-WRT v3.0-r34777 (01/31/18)
Reset: GUI
Errors: Radios not working. Mixed / Disabled only choices.

Radio: Radio is Off
Mode: AP
Network: Mixed
SSID: e3000n
Channel: Unknown
TX Power: 11 mW
Rate: Unknown

Encryption - Interface wl1: Disabled

Wireless Packet Info
Received (RX): 0 OK, no error
Transmitted (TX): 0 OK, no error
flood404
DD-WRT User


Joined: 18 Dec 2013
Posts: 336

PostPosted: Wed May 09, 2018 5:51    Post subject: Netgear 3700v3 Reply with quote
Router/Version: Netgear 3700v3
Firmware: r35898 nv64k version
Kernel: k3.x
Mode: Access Point
Issues: Wifi not working. Only Mixed or Disabled options available.


Reverted back to r35531 to get Wifi working again.
flood404
DD-WRT User


Joined: 18 Dec 2013
Posts: 336

PostPosted: Wed May 09, 2018 13:03    Post subject: Re: Netgear 3700v3 Reply with quote
I would just stay on r35531 since it works well enough for now. No need to be on bleeding edge since the WIFI has been broken for the last 6 releases.
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT 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