Discussion Forums > Technology
Routers - which to pick
kitamesume:
ok i just got the Asus RT-N12 rev.C1, the stock firmware is so-so and much better than the current one that i'm still using, im gonna migrate the settings from the old one.
a few questions though.
1) are there any other private IP address for router use other than 192.168.0.0 | 10.0.0.0 | 172.16.0.0?
2) is this the correct dd-wrt firmware for RT-N12 C1 "don't click"?
Pentium100:
--- Quote from: kitamesume on January 05, 2013, 09:45:00 AM ---1) are there any other private IP address for router use other than 192.168.0.0 | 10.0.0.0 | 172.16.0.0?
--- End quote ---
No. These are the only ones for private networks. There is also the link local IP range 169.254.0.0, but you should not use it or it may cause problems.
All others are publicly routable or special (say, multicast) IPs and you should not use them in a private network or you will have problems connecting to the "real" IP.
kitamesume:
ohh well, i just finished loading the firmware and it was the right one, although the settings is much more confusing, or rather complex.
edit:
how do i setup static ip on both wireless and wired clients while maintaining DHCP on other clients with dd-wrt?
http://www.dd-wrt.com/wiki/index.php/Static_DHCP
quite a round-about method =x well it works at least.
also, where the heck is the reboot in this GUI =/ command line "reboot"...
edit2:
anyway i fired up the router, and to my surprise my PC(3500~) total connections is hovering at 3800~ connections with a max connection of 4096... ouch? its pretty close to the max connection which i think is bad...
i found a solution though, lurking in dd-wrt forums.
--- Code: ---
echo "16384" > /sys/module/nf_conntrack/parameters/hashsize
nvram set ip_conntrack_max=16384
[save startup]
--- End code ---
Pentium100:
--- Quote from: kitamesume on January 05, 2013, 12:30:08 PM ---anyway i fired up the router, and to my surprise my PC(3500~) total connections is hovering at 3800~ connections with a max connection of 4096... ouch? its pretty close to the max connection which i think is bad...
i found a solution though, lurking in dd-wrt forums.
--- End quote ---
That is good, but it may still fill up after a few days. he reason is that conntrack by default keeps established TCP connections for 5 days (without any packets going trough) before deciding that the connection is really broken and freeing up the memory. This may be good for some protocols (like telnet) that do not send any packets but you would still like to keep the connection open (though normally all currently used protocols support some kind of keepalive or are just not kept idle for days). However, bittorrent is entirely different - it creates lots of connections and does not tear down a lot of them properly (say the other end lost power or crashed, nobody is sending the FIN or RST packet now), so the conntrack table becomes full of useless entries.
To change that you need to do this:
echo 36000 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
This makes the tcp connection time out in 10 hours if no packet is going trough. You may need to adjust this if you use protocols that idle for a long time and have no keepalive function. On my current router (Windows Server PC with lots of RAM) it is set to 24 hours, but when I had a Linux router with less RAM I used 1 or 2 hours.
Another one is UDP -
/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
You can set this to a few minutes (on my router it is set to 1 minute) since UDP is not supposed to idle for a long time and also since UDP cannot tear down the "connection".
kitamesume:
RT-N12 rev.C1 has 32MB of ram, which i think can handle up to 32K of connections, i won't risk it though.
2Hrs timeout sounds fine, although would this work instead? both are set to 300seconds at the moment, i'm waiting for some dropout connection first and if the 16K connection upperlimit still has enough space to spare.
--- Quote ---IP Filter Settings (adjust these for P2P)
TCP Congestion Control
Maximum Ports
(Default: 4096, Range: 256 - 4096)
TCP Timeout (in seconds)
(Default: 3600, Range: 1 - 86400)
UDP Timeout (in seconds)
(Default: 120, Range: 1 - 86400)
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version