New Build 36698 (BS): 08-22-2018-r36698

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


Joined: 25 Oct 2013
Posts: 2576
Location: Indy

PostPosted: Wed Aug 22, 2018 19:38    Post subject: New Build 36698 (BS): 08-22-2018-r36698 Reply with quote
Downloads at:
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/08-22-2018-r36698/
ftp://ftp.dd-wrt.com/betas/2018/08-22-2018-r36698/
Also: alternate DD-WRT website link.

Changelogs:
SVN Changelog: Since last build (36645)
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 r33678, including k26 (33655) & k24 (33656); use build 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issue #4 below).
4. Micro builds were broken from 36410 to 36596.

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. Trendnet 81*DRU models are missing factory-to-flash/color]
3. [color=darkred]DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:

http://svn.dd-wrt.com/ticket/6246
4. WDS does not work on ARM devices (only MIPS<->MIPS)
5. VAPs not working at boot (k3.10?); workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas

Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put into 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 issues, be sure to include the mode in use (gateway, AP, CB, etc.):
Code:
[b]Router/Version: [/b]
[b]File: [/b]
[b]Kernel: [/b]
[b]Mode: [/b]
[b]Status: [/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 #
x64 OPNsense 20.7.1|FT2020.5: EA6900v1.1@1GHz, F7D8302@532|DD 44294: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4


Last edited by jwh7 on Thu Aug 23, 2018 12:10; edited 2 times in total
Sponsor
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2576
Location: Indy

PostPosted: Wed Aug 22, 2018 22:02    Post subject: Reply with quote
Router/Version: Netgear WNDR4500v2
File: .bin
Kernel: Linux 3.10.108-d5 #20620 Wed Aug 22 16:02:29 CEST 2018 mips
Mode: CB+[AP+VAP]
Status: No VAP at boot; BSSID/SSID show up but can't connect. Works after restarting wlconf and nas.

Router/Version: Netgear WNDR4000
File: k3x nv64k
Mode: CB+[AP+VAP]
Status: No VAP at boot; no BSSID/SSID at boot. Works after restarting wlconf and nas.

Router/Version: Linksys WRT54GLv1.1
File: nokaid_special_generic
Kernel: Linux 2.4.37 #50361 Wed Aug 22 08:02:04 CEST 2018 mips
Mode: CB
Status: Not tested much, but no problems.

Router/Version: Linksys WRT54GSv6
File: micro generic
Kernel: Linux 2.4.37 #50369 Wed Aug 22 08:12:26 CEST 2018 mips
Mode: CB
Status: Fine, though the WRT's are getting an ego from being tested so much lately. Cool

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.1|FT2020.5: EA6900v1.1@1GHz, F7D8302@532|DD 44294: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
flyzipper
DD-WRT User


Joined: 21 Feb 2016
Posts: 409

PostPosted: Wed Aug 22, 2018 23:14    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r36698M std ( 08/22/18 )
Kernel: Linux 4.4.151-rc1 #3732 SMP Wed Aug 22 09:38:43 CEST 2018 armv7l
Previous: r36645
Mode/Status: Gateway / working
Reset: no (then yes)
Issues/Errors: None so far, but upgrade continues to fail via web UI (finally tried a reset and manual reconfig after so many recent failed upgrades... fingers crossed for the next release).

Uptime: 1 hour 21 minutes
Temperatures: CPU 68.6 °C / WL0 48.0 °C / WL1 51.5 °C



Last edited by flyzipper on Thu Aug 23, 2018 2:09; edited 1 time in total
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5324
Location: Texas

PostPosted: Wed Aug 22, 2018 23:50    Post subject: Reply with quote
WRT54G v5
DD-WRT v3.0-r36698 micro 08/22/18
Linux 2.4.37 #50369 Wed Aug 22 08:12:26 CEST 2018 mips
GUI install over r36645
[dd-wrt.v24_micro_generic.bin]
Defaults on the WRT54Gv5 ...all I could get accross this ol' dogs WAN ---
Code:
mrjcd@Deb:~$ iperf3 -c bigdeb.mrjcd.com
Connecting to host bigdeb.mrjcd.com, port 5201
[  5] local 192.168.1.137 port 41610 connected to 10.72.28.10 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  5.58 MBytes  46.8 Mbits/sec    0    253 KBytes       
[  5]   1.00-2.00   sec  4.78 MBytes  40.1 Mbits/sec  260    188 KBytes       
[  5]   2.00-3.00   sec  4.47 MBytes  37.5 Mbits/sec    0    208 KBytes       
[  5]   3.00-4.00   sec  4.47 MBytes  37.5 Mbits/sec    0    221 KBytes       
[  5]   4.00-5.00   sec  5.22 MBytes  43.8 Mbits/sec    0    236 KBytes       
[  5]   5.00-6.00   sec  4.47 MBytes  37.5 Mbits/sec    0    252 KBytes       
[  5]   6.00-7.00   sec  5.22 MBytes  43.8 Mbits/sec    0    266 KBytes       
[  5]   7.00-8.00   sec  4.47 MBytes  37.5 Mbits/sec    0    279 KBytes       
[  5]   8.00-9.00   sec  4.47 MBytes  37.5 Mbits/sec    0    291 KBytes       
[  5]   9.00-10.00  sec  4.47 MBytes  37.5 Mbits/sec    0    303 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  47.7 MBytes  40.0 Mbits/sec  260             sender
[  5]   0.00-10.04  sec  46.3 MBytes  38.7 Mbits/sec                  receiver

iperf Done.
mrjcd@Deb:~$ iperf3 -c bigdeb.mrjcd.com -R
Connecting to host bigdeb.mrjcd.com, port 5201
Reverse mode, remote host bigdeb.mrjcd.com is sending
[  5] local 192.168.1.137 port 41614 connected to 10.72.28.10 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  4.50 MBytes  37.8 Mbits/sec                 
[  5]   1.00-2.00   sec  4.55 MBytes  38.1 Mbits/sec                 
[  5]   2.00-3.00   sec  4.62 MBytes  38.8 Mbits/sec                 
[  5]   3.00-4.00   sec  4.58 MBytes  38.4 Mbits/sec                 
[  5]   4.00-5.00   sec  4.31 MBytes  36.1 Mbits/sec                 
[  5]   5.00-6.00   sec  4.58 MBytes  38.4 Mbits/sec                 
[  5]   6.00-7.00   sec  4.65 MBytes  39.0 Mbits/sec                 
[  5]   7.00-8.00   sec  4.62 MBytes  38.8 Mbits/sec                 
[  5]   8.00-9.00   sec  4.55 MBytes  38.1 Mbits/sec                 
[  5]   9.00-10.00  sec  4.55 MBytes  38.2 Mbits/sec                 
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.07  sec  46.8 MBytes  39.0 Mbits/sec   36             sender
[  5]   0.00-10.00  sec  45.5 MBytes  38.2 Mbits/sec                  receiver

iperf Done.
Cool
Mile-Lile
DD-WRT Guru


Joined: 24 Feb 2013
Posts: 1516
Location: Belgrade

PostPosted: Thu Aug 23, 2018 7:10    Post subject: Reply with quote
Router Model Netgear R6250
Firmware Version DD-WRT v3.0-r36698M std (08/22/1Cool
Kernel Version Linux 4.4.151-rc1 #3732 SMP Wed Aug 22 09:38:43 CEST 2018 armv7l


Status: Working (basic features + hotspotsystem on guest VAP)
Reset: No. Updated remotely from WAN (http)
Errors: None
mwchang
DD-WRT Guru


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

PostPosted: Thu Aug 23, 2018 9:50    Post subject: Asus RT-N18U and DD-WRT BS Build 36698M Reply with quote
This build was reported as "DD-WRT v3.0-r36698M std (08/22/18)". The "M" reminded me of Kong's build. Though everything works, is this really the BS build?

Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r36698M std (08/22/18)
Kernel: Linux 4.4.151-rc1 #3736 Wed Aug 22 10:05:10 CEST 2018 armv7l
Previous: DD-WRT v3.0-r36596 std (08/14/18)
Mode: Access Point (AP, not using IPv6, VAP, VPN, NAS nor USB)
Status: Working, no major problems
Reset: NO reset during firmware upgrade

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

2. Error(s) logged:
Code:
grep -i err /var/log/messages

Aug 23 09:42:43 DD-WRT daemon.err httpd[956]: Request Error Code 404: File style/elegant/logo.png not found.
Aug 23 09:42:45 DD-WRT daemon.err httpd[956]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Aug 23 09:42:50 DD-WRT daemon.err httpd[956]: Request Error Code 404: File style/elegant/logo.png not found.


3. Warning(s) logged:
Code:
grep -i warn /var/log/messages | grep -v DROP

Aug 23 09:27:58 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1904 to 0x1006: channel 1 used by exiting BSSs
Aug 23 09:34:28 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1904 to 0x1006: channel 1 used by exiting BSSs
Aug 23 09:34:28 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Aug 23 09:43:08 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1904 to 0x1006: channel 1 used by exiting BSSs


Other users' comments:
- WiFi broken in k3.x editions since build 35531 for modes other than AP?
- 5GHz problem can be solved by adding delay (boot wait?) in init process?
- Setting WPA re-key interval if not 99999 and rebooting router daily fixed nas (network authentication service) crash problems?
- Setting WPA re-key interval to 0 could prevent wifi clients from disconnecting?
- VAP still not fixed by this build 36333, adding a VAP might disable the real AP
- Command `lsmod` displayed only one line starting with build 36330 if not older builds!- Command `lsmod` displayed only one line starting with build 36330 if not older builds!
- Change security mode of Virtual Interface wl0.1 to WPA personal, and after successfull connect change it back to WPA2 Personal.
- Manually install the kmod utilities package from the OpenWRT repository
- Anything but "auto" set in advanced wl1 settings for authentication type and are using WPA / WPA2, 5GHz NOT going to work
- Restarting nas and all wireless interfaces (wl0, wl1) could fix VAP issues.

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 (also something related to blank Source Net?)
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!
g. Running "cat /proc/mtd" in Administration -> Commands for builds before 35916 didn't escape HTML special characters.
h. K3X BS Builds 36233 and 36242 might brick your routers (Kernel CPU patch went kaboom?). And VAP was not working. Bypass them!
i. lsmod listed only one module in some 36xxx builds




speedtest.net result for DD-WRT BS build 36698 and Asus RT-N18U.png
 Description:
speedtest.net result for DD-WRT BS build 36698 and Asus RT-N18U
 Filesize:  12.94 KB
 Viewed:  6157 Time(s)

speedtest.net result for DD-WRT BS build 36698 and Asus RT-N18U.png



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

May the Force and farces be with you! Live long and proper!

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
mwchang
DD-WRT Guru


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

PostPosted: Thu Aug 23, 2018 9:56    Post subject: FTP server reported "550 Failed to Change directory& Reply with quote
"ftp://ftp.dd-wrt.com/betas/2018/08-21-2018-r36696/" reported error "550 Failed to Change directory"!

update: problem solved


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

May the Force and farces be with you! Live long and proper!

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


Last edited by mwchang on Fri Aug 24, 2018 12:00; edited 1 time in total
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Aug 23, 2018 11:40    Post subject: Re: Asus RT-N18U and DD-WRT BS Build 36698M Reply with quote
mwchang wrote:
This build was reported as "DD-WRT v3.0-r36698M std (08/22/1Cool". The "M" reminded me of Kong's build. Though everything works, is this really the BS build?


I tried to point out the "M" in the other thread Mile-Lile had created by mistake to no avail. This is a BS build AFAIK. Kong don't support my device anymore, hasn't for years.
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Aug 23, 2018 11:47    Post subject: Reply with quote
For those who may or may not have figured out a workaround for DISABLING wireless webGUI access, I figured out how to get it to disable with default configuration of the radios and ethernet ports bridged:

https://svn.dd-wrt.com/ticket/3544#comment:26

You can also apply the same principle to disable telnet, ssh, https access to the wireless LAN side of the router. I know this has been discussed in the forum, but I haven't really read any threads that may pertain (because I was hoping the problem would've already been fixed!)
wicket
DD-WRT Novice


Joined: 18 Jul 2017
Posts: 41
Location: Wisconsin, USA

PostPosted: Thu Aug 23, 2018 12:26    Post subject: Unable to upgrade VIA webui Reply with quote
Router/Version: Linksys EA6500 v1
Firmware:DD-WRT v3.0-r36698 giga ( 08/22/18 )
Kernel: Linux 3.10.108-d5 #20620 Wed Aug 22 16:02:29 CEST 2018 mips
Previous: DD-WRT v3.0-r36596 giga ( 08-14-18 )
Mode/Status: Gateway/AP
Setup: Using IPv6 via DNSMasq, DDNS, & Port Range Forward.
Reset: No
Issues/Errors: I was unable to update to this firmware via the web-ui. I had to use telnet to upgrade. Everything else seems to be working fine.

_________________
Bernadoe
DD-WRT User


Joined: 03 Dec 2014
Posts: 215

PostPosted: Thu Aug 23, 2018 13:48    Post subject: Reply with quote
Router: Netgear R7000
Firmware: DD-WRT v3.0-r36698M std (08/22/2018)
Kernel: Linux 4.4.151-rc1 #3732 SMP Wed Aug 22 09:38:43 CEST 2018 armv7l
Status: Working
Reset: No
Previous: 36645
Errors: No

Temperatures : CPU 58.0 °C / WL0 49.4 °C / WL1 51.4 °C

Working very well :
Router mode : DHCP
SFE Enable
STP Enable
DNSMasq
Encrypt DNS
Cache DNSSEC data
Validate DNS Replies (DNSSEC)
Local DNS
No DNS Rebind
Query DNS in Strict Order
Usb
Nas, Samba, JFFS2, MiniDLNA
wl0, wl1
Vpn (OpenVPN Client)
New :
library versions: OpenSSL 1.1.0i 14 Aug 2018 LZO 2.09

Kong and BS: Thanks for all your good work!

without VPN



with VPN
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Aug 23, 2018 16:09    Post subject: Cisco Linksys E4200 v1 Reply with quote
Router/Version:  Linksys E4200 v1
Firmware:  DD-WRT v3.0-r36698 mega ( 08/22/18 )
Kernel:  Linux 3.10.108-d5 #20636 Wed Aug 22 16:19:45 CEST 2018 mips
Previous: DD-WRT v3.0-r36645 mega ( 08/19/18 )
Firmware file used: dd-wrt.v24-36698_NEWD-2_K3.x_mega-e4200.bin
Reset; Yes; Reset via webUI (reboot), Firmware upgrade (without checking reset to defaults!), Reset via webUI (reboot), configured settings manually (reboot) x2, iptables test rules didn’t copy and paste correctly* EDIT: Took a few more reboots to figure out which modules were needed to get ebtables to work since iptables does not work for what I was testing (see below)
Mode: Gateway/AP
Uptime: ~4:30
Status: OK
Issues/Errors: I didn't capture and save serial log data during figuring out iptables / ebtables to disable wireless access to webGUI, ssh, telnet, BUT it appears that a single set of rules gets multiplied. I am guessing due to the vif / vap fixes that have things being initialized 98435794578 times on boot. Rolling Eyes

kernel-panic69 wrote:
For those who may or may not have figured out a workaround for DISABLING wireless webGUI access, I figured out how to get it to disable with default configuration of the radios and ethernet ports bridged:

https://svn.dd-wrt.com/ticket/3544#comment:26

You can also apply the same principle to disable telnet, ssh, https access to the wireless LAN side of the router. I know this has been discussed in the forum, but I haven't really read any threads that may pertain (because I was hoping the problem would've already been fixed!)


Code:
root@DD-WRT:/sbin# ebtables -L
Bridge table: filter

Bridge chain: INPUT, entries: 24, policy: ACCEPT
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 23 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 23 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 22 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 22 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 443 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 443 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 80 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 80 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 23 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 23 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 22 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 22 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 443 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 443 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 80 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 80 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 23 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 23 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 22 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 22 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 443 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 443 -j DROP
-p IPv4 -i eth2 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 80 -j DROP
-p IPv4 -i eth1 --ip-src 192.168.1.0/24 --ip-dst 192.168.1.1 --ip-proto tcp --ip-dport 80 -j DROP

Bridge chain: FORWARD, entries: 0, policy: ACCEPT

Bridge chain: OUTPUT, entries: 0, policy: ACCEPT


I do believe there are some persistent errors noted in my serial logs, I will have to go back through. One related to udev comes to mind. Not sure if all the ones I saw during troubleshooting ebtables / iptables rules to secure wireless access to router management are in the attached serial log or not, but I will go back through later and check. Logs attached, as usual Cool



r36698.syslog.txt
 Description:

Download
 Filename:  r36698.syslog.txt
 Filesize:  24.86 KB
 Downloaded:  416 Time(s)


r36645_r36698.serial.txt
 Description:

Download
 Filename:  r36645_r36698.serial.txt
 Filesize:  150.36 KB
 Downloaded:  437 Time(s)

mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5324
Location: Texas

PostPosted: Thu Aug 23, 2018 16:56    Post subject: Reply with quote
E2500
DD-WRT v3.0-r36698 mega 08/22/18
Linux 3.10.108-d5 #20636 Wed Aug 22 16:19:45 CEST 2018 mips
[dd-wrt.v24-36698_NEWD-2_K3.x_mega.bin]
GUI install over r36104
No Reset.
'Repeater Bridge' to a WNDR3700v4.
Everything good --- connecting to VAP works perfect.

GUI reset to defaults and config 'repeater bridge' to main router (EA8500).
Could never get DHCP connected to the EA8500 main 2.4 or its guest 2.4.
Wireless status showed on both units as connected but just won't work.
Config RB back to the WNDR3700v4 (WAP) and works perfectly. The really weird thing is I still had
the E2500 LAN IP set to subnet of EA8500 guest network but when I config RB back to the WNDR3700v4 (WAP on main network)
I got DHCP IP from main router (E8500) subnet....of course I had to set static IP to subnet of E2500 LAN
before I could access its webif --- set back to main subnet IP and RB is working good ---- just won't work RB to EA8500.


GUI reset to defaults (regular gateway) and config guest network.... unbridged in Wieless setting.
Mutiple DHCP in 'Networking' for wl0.1
Cannot connect to VAP.

GUI reset to defaults (regular gateway) just create VAP --- no security on wl0 or wl0.1 -- cannot connect to the VAP.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2576
Location: Indy

PostPosted: Thu Aug 23, 2018 17:27    Post subject: Reply with quote
mrjcd wrote:
GUI reset to defaults (regular gateway) and config guest network.... unbridged in Wieless setting.
Mutiple DHCP in 'Networking' for wl0.1
Cannot connect to VAP.

GUI reset to defaults (regular gateway) just create VAP --- no security on wl0 or wl0.1 -- cannot connect to the VAP.
Did you test if the OP workaround fixes the VAP, or are you just providing another report that it is broken by default?
Quote:
5. VAPs not working at boot (k3.10?); workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
I sent BS a bunch of stuff yest about this...no reply.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.1|FT2020.5: EA6900v1.1@1GHz, F7D8302@532|DD 44294: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.3: RT-ACRH13, R6220, WNDR3700v4
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5324
Location: Texas

PostPosted: Thu Aug 23, 2018 18:13    Post subject: Reply with quote
jwh7 wrote:
mrjcd wrote:
GUI reset to defaults (regular gateway) and config guest network.... unbridged in Wieless setting.
Mutiple DHCP in 'Networking' for wl0.1
Cannot connect to VAP.

GUI reset to defaults (regular gateway) just create VAP --- no security on wl0 or wl0.1 -- cannot connect to the VAP.
Did you test if the OP workaround fixes the VAP, or are you just providing another report that it is broken by default?
Quote:
5. VAPs not working at boot (k3.10?); workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
I sent BS a bunch of stuff yest about this...no reply.

On the E2500 the VAP (guest network unbridged in wireless settings) multiple DHCP server
set for wl0.1 in 'Networking' and using Net Isolation and also different WPA2-AES for wl0/wl0.1
Everything works fine if:
Code:
sleep 10
stopservice nas
stopservice wlconf
startservice wlconf
startservice nas

saved as startup. VAP won't broadcast otherwise.
Goto page 1, 2, 3  Next Display posts from previous:    Page 1 of 3
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