1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

dd-wrt one-button control to limit "damage" done b

Discussion in 'DD-WRT Firmware' started by Yalla-One, Jul 15, 2005.

?

Would P2P flow control from GUI be a good idea?

  1. Yes

    100.0%
  2. No

    0 vote(s)
    0.0%
  3. I'm clueless...

    0 vote(s)
    0.0%
  1. Yalla-One

    Yalla-One Network Guru Member

    Hi all,

    First of all, allow me to join the others in taking my (virtual) hat off for BrainSlayer and a very very well done job.

    I was wondering if there are plans to include in the new GUI a menu-setting to limit the number of concurrent Peer2Peer half-open connection which currently kill both the line and the Linksys box itself.

    I'm keeping an old computer running only P2P 24x7, and it kills my Linksys appr. every 24 hours, so it needs hard reset. This is according to people more skilled than I, happening because the connection slots on the Linksys fill up and while this is happening, even though P2P utilize only 40% of the bandwidth, it ties up so many connection slots that I'm unable to use IP telephony or any other QoS aware application successfully, because the packets don't get through.

    I noticed elsewhere on this forum that there's a line that can be configured using open-wrt so that this is limited, but for those of us not sufficienly technical to run open-wrt, wouldn't it be a great idea if this feature was included in dd-wrt so it can be turned on and turned off there?

    Thanks BrainSlayer!

    -Y1
     
  2. Lazybones

    Lazybones Network Guru Member

    It's a good feature Idea, but you can almost completely prevent this by changing the settings in your P2P app to use fewer connections at once..

    What P2P app is it? If its one for a common network that does not include this feature I am sure we can suggest one that does.
     
  3. Yalla-One

    Yalla-One Network Guru Member

    I know that most applications allow these settings on the application level, but from a networking and policing point of view, I have a strong preference from being able to control this on the network, so that one "un-thoughtful" user cannot tweak his/her settings and ruin the day for others. I for one use a slight derivative from mldonkey as a daemon on linux, and even though I've programmed it to be "nice", it still leaves behind old embryonic connections when analyzing the network with a packet sniffer.
    Some neighbours use Shareaza, others emule.
    This is why I *REALLY* want to see this in the network.

    On the QoS page, imagine setting the maximum number of embryonic connections, total connections etc, maybe in total, and one for each IP address (client). I see it's possible from openwrt.

    Problem with current solution is (a) that the box hangs every 25 hours and (b) that nobody can use IP Telephony. The bandwidth is controlled perfectly, but the sheer number of connections make impossible.

    What is your take on this, BrainSlayer ?

    Thanks for reading

    -Y1
     
  4. Lazybones

    Lazybones Network Guru Member

    True, but from your first post it just sounded like you had a dedicated box sitting on your network.

    Shareaza is VERY bad for creating too many connections, there are many suggestions in the Shareaza forums on how to solve this.. It tends to blow up most makes of router as well as some older windows systems.

    I still use Shareaza my self, but not as my primary download tool.

    DD-WRT has a built in Reboot timer if you want a dirty workaround for now.. I think BrainSlayer is rather busy with other issues.
     
  5. Yalla-One

    Yalla-One Network Guru Member

    Hi again,

    I have a dedicated box on my network running mldonkey (Linux). However, my neightbour(s) use other programs and I they're rather hard to police...

    I know Brainslayer is rather busy with multiple super issues, but if I don't mention it, it might never happen, so I figured this might be a good way to bring it to his attention and then he's obviously free to decide if/when to include such a feature.

    From the number of posts I've read about this in different forums from different Linksys-OS'es, it seems to be a common problem for across the board that the box freezes with too many concurrent sessions. Policing this in the box is IMHO the only way to go as it takes away from the (clueless) end-user the possibility of misconfiguring his own client and thus bringing down the entire network.

    It's for that reason I'm happy with running firewall in the Linksys as well - simply because the end-user often is too ignorant to update his/her own firewall. The more control centrally, the better.

    Thanks for listening.
     
  6. Yalla-One

    Yalla-One Network Guru Member

    Startup control code

    I found this info in another thread for HyperWRT. Will DD-WRT support this in the startup-script? Supposedly this is all it takes to fix/control the use of P2P software in a network behind a Linksys router.

    echo 4096 > /proc/sys/net/ipv4/ip_conntrack_max
    echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
    echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
    echo 512 > /proc/sys/net/ipv4/neigh/default/gc_thresh1
    echo 2048 > /proc/sys/net/ipv4/neigh/default/gc_thresh2
    echo 4096 > /proc/sys/net/ipv4/neigh/default/gc_thresh3
    echo "600 1800 120 60 120 120 10 60 30 120" > /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts

    Does this make sense to anyone?
    And - does DD-WRT use the same format, so I can insert these lines in the startup script? If so, how do I do that, and save it so it "sticks" ?

    Thanks again

    -Y1
     

Share This Page