P2P and disconnects

Discussion in 'Sveasoft Firmware' started by tobias2k, Aug 17, 2004.

  1. tobias2k

    tobias2k Network Guru Member

    I'm using Satori-4.0 v2.07.1.7sv on my W54g and receive disconnects when running p2p software for a couple of hours.
    At the sveasoft forums this problem was already discussed but no solution was found until sveasoft becomes non-public.
    Has anybody found a solution in the meantime ?
  2. zaphod

    zaphod Network Guru Member


    got the same problem when i tested this firmware.. Its not a good firmware for using p2p-software cause you get many disconnects..

    have changed to hyperwrt 1.3 and no more disconnects... emule runs with full downloadspeed after a while :)

    a bug in the connection-tracking-module causes the disconnects but theres no solution i know...

    change the firmware !!


  3. tobias2k

    tobias2k Network Guru Member

    thx 4 info, i will do so.
  4. pkitester

    pkitester Network Guru Member

  5. pkitester

    pkitester Network Guru Member

    One more thing. I don't understand the logic behind this at all, but check out /proc/sys/net/ipv4/ip_local_port_range

    For whatever reason it is set from 1024 4999. I see the same crazyness is done in windows, and other unixes. This pretty much means the router can only have ~4000 connections total, granted by default it can only track ~500 nat connections until you make the changes above. The problem is that connections don't die right away, so a p2p program, or a game might make thousands of "ping" type checks and get to this limit pretty fast. Running a netstat -an should give you an idea if this is a problem for you.

    If you have 65536 ports available why not use them all!? Oh because it might save a few bytes of ram...Well I'd rather have a working device, than a bunch of free ram. :)
  6. zaphod

    zaphod Network Guru Member

    hi pkitester, (hehe, are you testing vpns???)

    thats not the point i think.... the wrt54g v1.0 - 1.1 and some 2.0 models only got 16 MB of Ram available for the system, few models got 32 MB Ram but theres no firmware which can use it...

    P2P-Software normally only uses about 200-400 Conns at the same time more is not good for the internal mechanism the soft use....

    The Standard conntrack value from hyperwrt 1.3 is 1024 thats pretty enough for p2p-software, http-browsing, scp-copys and uploading a iso-file to my ps2 at the same time... So to put up this value is not the real goal... i think there is a bug in satoris release in the module conntrack itself cause in other firmware editions the p2p-soft didnt disconnect after days...

    sorry for my bad english... lot time ago learning it :)


  7. pkitester

    pkitester Network Guru Member

    Given my line of work, I test tons of different things, but it is also a hobby too.

    By default the linksys stuff was set to track around 500 connections. But even with it set to 4096 I don't think it is unreasonable. I guess it all depends on what you are doing. But with really long timeouts as the default, it doesn't take very much to fill the tables and have things start dropping.

    I've seen it happen on my home network when just doing something simple like playing Unreal on the internet. Just looking for a server to play on can fill the linksys's tables up and it will start dropping my IM connections.

    The couple hundred bytes it takes to track connections, or give you the ability to use all of the available ports is well worth it. Most of my devices here have 16mb-32mb of ram. Even with alternative firmware loaded I still have between 10-22mb free.

    I would not be surprized if there were bugs, but I'd certainly want to try out some of the more obvious things first myself. If you open your p2p up for file sharing, isn't it entirely possible you'll get thousands of people hitting your server to download? That would also fill up the table in an instant as well. That is why I suggested looking at your netstat when you are seeing a problem. It should be pretty obvious there what is going on. You could also look at all your current connections too.

    For me, nothing is good enough. I've written some network monitoring software I would like to use and none of the devices seem to be able to handle the load it can generate. I can easily generate hundreds of connections per second on a single machine, but this pretty much kills any device in the blink of an eye. :( Some due to network setting limitations, some due to cpu limitations, some due to bugs... I've even tried removing all network devices and just tested it through a DSL modem. In that case, the DSL modem croaks even though all it should be doing anything but sending the packets to my machine.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice