18777 is the last best build that you can use on that router. I've reopened the concerned ticket several times http://svn.dd-wrt.com/ticket/4015 , but BrainSlayer won't fix it, unfortunately. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
18777 is the last best build that you can use on that router. I've reopened the concerned ticket several times http://svn.dd-wrt.com/ticket/4015 , but BrainSlayer won't fix it, unfortunately.
thank you sir , you r the only one who replay in timely manner and very helpful.
but what I mean can you advise which build is best for eap3660:-
13064
or
14986
or
18777
or other?
I know 18777 is the latest but is it the best to use?
I hope BB find a time to fix it for eap3660
and found a way for eap9550 and eap350
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Apr 18, 2015 4:30 Post subject:
they are all buggy..but 18777 is the best up to it, i remember using it on my wndr3700 v1 & dir-825 b1 it was noticeably better than priors. been using ddwrt since r136xx i think it was when i started, & every single build between that & current, the nasty "WAN RX hang" & qos memory leaks were the biggest offenders in early builds _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
@ ][No_Way
See, I'm not the only one who replies in a timely manner and is very helpful ! _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
they are all buggy..but 18777 is the best up to it, i remember using it on my wndr3700 v1 & dir-825 b1 it was noticeably better than priors. been using ddwrt since r136xx i think it was when i started, & every single build between that & current, the nasty "WAN RX hang" & qos memory leaks were the biggest offenders in early builds
thank you dear.
Im also old user but not advanced starting from my wrt54gs v2 on 2008
just for intrest which is the best build for your opinon regardless it fit my EAP3660 or not.
@][No_Way Indeed you ARE confused. Be more attentive next time. Also, check your Inbox, you have a message from me since yesterday. Haven't you noticed ? _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
@][No_Way Indeed you ARE confused. Be more attentive next time. Also, check your Inbox, you have a message from me since yesterday. Haven't you noticed ?
Now I'm using b18777 but i have 2 problem
first: router reboot some time once a day and some time much more frequent, this looks with high cpu consuming
2nd:
I have eap3660 with build 1877
and I made 3 ssid and separate it so I want to restrict address on br1 with ip 192.168.2.x Br1
based on ip range and deny access for specific time.
my firewall iptables:-
iptables -t nat -I POSTROUTING -o br0 -j SNAT --to `nvram get lan_ipaddr`
iptables -I FORWARD -i br1 -d `nvram get lan_ipaddr`/`nvram get lan_netmask` -m state --state NEW -j DROP
iptables -I FORWARD -i br2 -d `nvram get lan_ipaddr`/`nvram get lan_netmask` -m state --state NEW -j DROP
iptables -I INPUT -i br1 -p tcp --dport telnet -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br2 -p tcp --dport telnet -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br1 -p tcp --dport ssh -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br2 -p tcp --dport ssh -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br1 -p tcp --dport www -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br2 -p tcp --dport www -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br1 -p tcp --dport https -j REJECT --reject-with tcp-reset
iptables -I INPUT -i br2 -p tcp --dport https -j REJECT --reject-with tcp-reset
iptables -t nat -I PREROUTING -i br1 -s 192.168.2.1/24 -p udp --dport 53 -j DNAT --to 208.67.222.222
iptables -t nat -I PREROUTING -i br1 -s 192.168.2.1/24 -p tcp --dport 53 -j DNAT --to 208.67.222.222
iptables -D FORWARD -j lan2wan
iptables -I FORWARD -j lan2wan
insmod xt_mark
insmod xt_mac
insmod imq
insmod ipt_IMQ
tc qdisc del dev br2 root
tc qdisc add dev br2 root handle 1: htb
tc class add dev br2 parent 1: classid 1:1 htb rate 2048kbit
tc qdisc add dev br2 parent 1:1 handle 10: sfq perturb 10
tc filter add dev br2 parent 1:0 prio 5 protocol ip u32 match ip dst 192.168.3.0/24 flowid 1:1
ip link set imq0 up
tc qdisc del dev imq0 root
tc qdisc add dev imq0 root handle 1: htb
tc class add dev imq0 parent 1: classid 1:1 htb rate 512kbit
tc qdisc add dev imq0 parent 1:1 handle 10: sfq perturb 10
tc filter add dev imq0 parent 1:0 prio 5 protocol ip u32 match ip src 192.168.3.0/24 flowid 1:1
iptables -t mangle -I PREROUTING -i br1 -j IMQ --todev 0
ip link set imq0 up
and iptables -vnL :-
Chain INPUT (policy ACCEPT 42637 packets, 2827K bytes)
pkts bytes target prot opt in out source destination
0 0 REJECT tcp -- br2 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 reject-with tcp-reset
0 0 REJECT tcp -- br1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 reject-with tcp-reset
0 0 REJECT tcp -- br2 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 reject-with tcp-reset
0 0 REJECT tcp -- br1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 reject-with tcp-reset
0 0 REJECT tcp -- br2 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 reject-with tcp-reset
0 0 REJECT tcp -- br1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 reject-with tcp-reset
0 0 REJECT tcp -- br2 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:23 reject-with tcp-reset
0 0 REJECT tcp -- br1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:23 reject-with tcp-reset
Chain FORWARD (policy ACCEPT 15722 packets, 6752K bytes)
pkts bytes target prot opt in out source destination
15722 6752K lan2wan 0 -- * * 0.0.0.0/0 0.0.0.0/0
0 0 DROP 0 -- br2 * 0.0.0.0/0 192.168.1.0/24 state NEW
0 0 DROP 0 -- br1 * 0.0.0.0/0 192.168.1.0/24 state NEW
Chain OUTPUT (policy ACCEPT 13480 packets, 4202K bytes)
pkts bytes target prot opt in out source destination
Chain advgrp_1 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_10 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_2 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_3 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_4 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_5 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_6 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_7 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_8 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_9 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_1 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_10 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_2 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_3 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_4 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_5 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_6 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_7 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_8 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_9 (0 references)
pkts bytes target prot opt in out source destination
Chain lan2wan (1 references)
pkts bytes target prot opt in out source destination
Chain logaccept (0 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT 0 -- * * 0.0.0.0/0 0.0.0.0/0
Chain logbrute (0 references)
pkts bytes target prot opt in out source destination
0 0 0 -- * * 0.0.0.0/0 0.0.0.0/0 recent: SET name: BRUTEFORCE side: source
0 0 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0 !recent: UPDATE seconds: 60 hit_count: 4 name: BRUTEFORCE side: source
0 0 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 1/min burst 1
0 0 DROP 0 -- * * 0.0.0.0/0 0.0.0.0/0
Chain logdrop (0 references)
pkts bytes target prot opt in out source destination
0 0 DROP 0 -- * * 0.0.0.0/0 0.0.0.0/0
Chain logreject (0 references)
pkts bytes target prot opt in out source destination
0 0 REJECT tcp -- * * 0.0.0.0/0 0.0.0.0/0 reject-with tcp-reset
Chain trigger_out (0 references)
pkts bytes target prot opt in out source destination