around 5pm PST, i added the QoS suggestion found at the end of this thread: https://community.ubnt.com/t5/EdgeMAX/EdgeRouter-X-Losing-Speed/m-p/1801659#U1801659
it worked quite well improving upload speed 800-900 kbs to more like 1400kbs. I left and came back 6 hours later and the router was locked up hard. no one was home during that time. I went back to vanilla 1.7 config I saved after running WAN+2LAN2 wizard. then added back in the QoS. that's what's running now with no openDNS config.
So to summarize:
1) run WAN+2LAN2 wizard on 1.7 firmare. that stayed up for a couple days
2) added in openDNS config.
3) a day later added in QoS as per thread above and ERX locked up in 6 hours.
here's the current config:
ubnt@ubnt:~$ cat /config/config.boot
firewall {
all-ping enable
broadcast-ping disable
ipv6-receive-redirects disable
ipv6-src-route disable
ip-src-route disable
log-martians enable
name WAN_IN {
default-action drop
description "WAN to internal"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid state"
state {
invalid enable
}
}
}
name WAN_LOCAL {
default-action drop
description "WAN to router"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid state"
state {
invalid enable
}
}
}
receive-redirects disable
send-redirects enable
source-validation disable
syn-cookies enable
}
interfaces {
ethernet eth0 {
address dhcp
description Internet
duplex auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
speed auto
}
ethernet eth1 {
description Local
duplex auto
speed auto
}
ethernet eth2 {
description Local
duplex auto
speed auto
}
ethernet eth3 {
description Local
duplex auto
speed auto
}
ethernet eth4 {
description Local
duplex auto
speed auto
}
loopback lo {
}
switch switch0 {
address 192.168.0.1/24
description Local
mtu 1500
switch-port {
interface eth1
interface eth2
interface eth3
interface eth4
}
}
}
service {
dhcp-server {
disabled false
hostfile-update disable
shared-network-name LAN {
authoritative enable
subnet 192.168.0.0/24 {
default-router 192.168.0.1
dns-server 192.168.0.1
lease 86400
start 192.168.0.38 {
stop 192.168.0.99
}
}
}
}
dns {
forwarding {
cache-size 150
listen-on switch0
}
}
gui {
https-port 443
}
nat {
rule 5010 {
description "masquerade for WAN"
outbound-interface eth0
type masquerade
}
}
ssh {
port 22
protocol-version v2
}
}
system {
host-name ubnt
login {
user ubnt {
authentication {
encrypted-password *
}
level admin
}
}
ntp {
server 0.ubnt.pool.ntp.org {
}
server 1.ubnt.pool.ntp.org {
}
server 2.ubnt.pool.ntp.org {
}
server 3.ubnt.pool.ntp.org {
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone UTC
}
traffic-control {
smart-queue sq1 {
upload {
ecn disable
flows 1024
fq-quantum 300
htb-quantum 1500
limit 1024
rate 1.5mbit
target 15ms
}
wan-interface eth0
}
}
/* Warning: Do not remove the following line. */
/* === vyatta-config-version: "config-management@1:conntrack@1:cron@1:dhcp-relay@1:dhcp-server@4:firewall@5:ipsec@4:nat@3:qos@1:quagga@2:system@4:ubnt-pptp@1:ubnt-util@1:vrrp@1:webgui@1:webproxy@1:zone-policy@1" === */
/* Release version: v1.7.0.4783374.150622.1533 */can anyone shed light why 1.7 with QoS and/or using openDNS as domain name servers (not currently running this bit to test all the options) would be unstable? i really need the QoS to defeat bufferbloat...
thanks.