I'd be looking around the first error, the missing ';' which is probably building a clientlist or something similar. Can you post the debugger output around that error?
#ClientList_Block_PC a{
background-color:#EFEFEF;
color:#FFF;
font-size:12px;
font-family:Arial, Helvetica, sans-serif;
text-decoration:none;
}
#ClientList_Block_PC div:hover, #ClientList_Block a:hover{
background-color:#3366FF;
color:#FFFFFF;
cursor:default;
}
</style>
<script>
var dhcp_staticlist_array = '<D4:BE:D9:82:16:1D.168.99.100>A5271569ᝰ:25:AE:F7:BF:6F.168.99.169>ឈ:77:03:E2:41:0C.168.99.101>A5271569ᝰ:19:D1:29:B2:F0.168.99.23>STACKERᝰ:90:A9:B1:62:C4.168.99.110>MYBOOKLIVE3Tᝰ:1A:4D:5B:BB:BF.168.99.25>AMD47ɘC:89:10:AF:4F:2E.168.99.75>Samsung TV 1əC:99:4C:38:24:32.168.99.151>Orn's Note3 ';
if(pptpd_support){
var pptpd_clients = '192.168.99.190-199';
var pptpd_clients_subnet = pptpd_clients.split(".")[0]+"."
+pptpd_clients.split(".")[1]+"."
+pptpd_clients.split(".")[2]+".";
var pptpd_clients_start_ip = parseInt(pptpd_clients.split(".")[3].split("-")[0]);
var pptpd_clients_end_ip = parseInt(pptpd_clients.split("-")[1]);
}
var dhcp_enable = '1';
var pool_start = '192.168.99.200';
var pool_end = '192.168.99.254';
var pool_subnet = pool_start.split(".")[0]+"."+pool_start.split(".")[1]+"."+pool_start.split(".")[2]+".";
var pool_start_end = parseInt(pool_start.split(".")[3]);
var pool_end_end = parseInt(pool_end.split(".")[3]);
var static_enable = '1';
var dhcp_staticlists = '<D4:BE:D9:82:16:1D.168.99.100>A5271569ᝰ:25:AE:F7:BF:6F.168.99.169>ឈ:77:03:E2:41:0C.168.99.101>A5271569ᝰ:19:D1:29:B2:F0.168.99.23>STACKERᝰ:90:A9:B1:62:C4.168.99.110>MYBOOKLIVE3Tᝰ:1A:4D:5B:BB:BF.168.99.25>AMD47ɘC:89:10:AF:4F:2E.168.99.75>Samsung TV 1əC:99:4C:38:24:32.168.99.151>Orn's Note3 ';
var staticclist_row = dhcp_staticlists.split('<');
var lan_domain_curr = '';
var dhcp_gateway_curr = '192.168.99.1';
var dhcp_dns1_curr = '';
var dhcp_dns2_curr = '';
var dhcp_wins_curr = '';
if(yadns_support){
var yadns_enable = '0';
var yadns_mode = '1';
}
If you log in to the router via telnet/ssh, the nvram variable to edit is 'dhcp_staticlist'Is there a way to change this setting without using the GUI, so I can fix it?
I just tested it with the same setup as you mention and it's working fine for me.
Keep in mind that DNS lookups get cached both by the OS and by the web browser. You have to either try a different browser, or make sure you do shut down your browser and restart it before testing with a different DNS setup.
If you log in to the router via telnet/ssh, the nvram variable to edit is 'dhcp_staticlist'
do
nvram show | grep dhcp_staticlist
highlight the result with the mouse and then right click to copy it to the command line....insert 'nvram set' (without the quotes) at the beginning of the line and then move the cursor to delete the offending '
EDIT: If you have any spaces in your names you'll also need to enclose the data in double quotes (after the equal sign and at the end of the line)
It's a router, not a computer. You will need to stop running whatever you are running on it that requires so much memory.
/proc/sys/vm/overcommit_memory
echo 1 > /proc/sys/vm/overcommit_memory
echo 400 > /proc/sys/vm/overcommit_ratio
Yes...sorry about that....I forgot about the use of < and > as field separators. Glad you tried the double quotes. Good to hear that it got things running!I had to encapsulate the value in double quotes, even though there were no spaces because I got an error "-sh: syntax error: unexpected redirection" if I did not.
VPN => openVPN clients => Redirect Internet traffic => Rules for routing client traffic through the tunnel
No worries, the fix was straightforward and intuitive once you explained the commands.Yes...sorry about that....I forgot about the use of < and > as field separators. Glad you tried the double quotes. Good to hear that it got things running!
Hi,Turns out the real issue is default setting for= 2, meaning never overcommit memory. Changing this to 1 byCode:/proc/sys/vm/overcommit_memory
lets swap work. 1GB is not too much, since even mkfs.ext3 for a large filesystem (tb's) will need at least 400MB memory.Code:echo 1 > /proc/sys/vm/overcommit_memory
You appear to have some specialized knowledge that the writers of the Asus router code do not? That the Asus setting for overcommit_memory is a mistake?Turns out the real issue is default setting for= 2, meaning never overcommit memory. Changing this to 1 byCode:/proc/sys/vm/overcommit_memory
lets swap work...Code:echo 1 > /proc/sys/vm/overcommit_memory
Hoping Asus would realize their routers have too little ram to even run downloadmaster properly...and ram is cheap...
You appear to have some specialized knowledge that the writers of the Asus router code do not? That the Asus setting for overcommit_memory is a mistake?
@RMerlin I am an Android Kernel developer over at XDA for the Nexus 4 & 5, and I was wondering if you could implement Kernel Same Page Merging as well as zram that will further optimize memory consumption on these routers. Also I wonder how fiops io scheduler would perform on these routers. Let me know what you think, I think we can further optimize the performance on the ARM based routers, and its possible some Android kernel patches may be compatible.
I have policy routing set up where only one client IP goes through the VPN tunnel. It works well. The problem I am having is with DNS. When I set the DNS to "exclusive" it works just as advertised and I have no DNS leak for the client, *but* at this point all my clients start using the DNS of the VPN service (which is not what I want). Note the non-VPN clients do not use the VPN tunnel, they just start using the VPN DNS service. Is this intentional? I would like to have the normal non-vpn clients use the DNS I specify in the WAN settings and have the policy based VPN client use the DNS of the VPN service.
Still, a great release. Love it and good job.
I have policy routing set up where only one client IP goes through the VPN tunnel. It works well. The problem I am having is with DNS. When I set the DNS to "exclusive" it works just as advertised and I have no DNS leak for the client, *but* at this point all my clients start using the DNS of the VPN service (which is not what I want). Note the non-VPN clients do not use the VPN tunnel, they just start using the VPN DNS service. Is this intentional? I would like to have the normal non-vpn clients use the DNS I specify in the WAN settings and have the policy based VPN client use the DNS of the VPN service.
Still, a great release. Love it and good job.
I finally managed to track it down. It's not a bug in the firmware, it's the ovpn config you are importing that's telling the router NOT to run the proper cleanup script at exit time.
Remove the following line from your custom config field:
Code:explicit-exit-notify 1
Should be fine after that.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!