[SOLVED] ping times with and without the WRT54GS

Discussion in 'Sveasoft Firmware' started by SirDracula, Dec 3, 2004.

  1. SirDracula

    SirDracula Network Guru Member


    I am having a problem, maybe there's an easy explanation for it:

    WRT54GS with Satori-4.0 v2.07.1.7sv

    If I ping a server WITHOUT the WRT54GS (computer connected directly to the DSL modem) I get about 13-14ms replies.

    If I ping the same server WITH the WRT54GS (computer connected via the WRT54GS I get about 28-30ms replies.

    What's going on? Why does the WRT54GS double the ping times?

    I don't have bandwidth mgmt enabled on the router and I am using a wired connection for this test.

    Any setting I am missing somewhere or is it just normal overhead for moving the packets between the private (LAN) and public (WAN) interfaces of the router?

  2. SirDracula

    SirDracula Network Guru Member

    Can someone please try the test above? Please post your results, the router model (WRT54G/GS, version) and any related settings that you may think can make such a difference.

    I would also like to hear from people who run or tried other firmwares too, I just don't want to post this same message all over the place in these forums.

    Thank you.
  3. littlewhoo

    littlewhoo Network Guru Member

    I did try this with a WRT54G running Satori and a WRT54GS running Alchemy. And no matter if I'm pinging from my computer through the router to a remote host, from my computer without the WRT54G(S) directly to the remote host or from the router (logged in via SSH) to the remote host, I'm always getting the same ping times.
    I have a DSL connection without fastpath, so my ping times are always ~60ms.

    The increased ping you are experiencing could be caused by several things. When you are connecting to the internet via the router, all your traffic is sent and received over your ethernet card to the gateway on the router. But when you are connecting the DSL modem directly to the ethernet card, a completely different network interface is being used (pppoe dialup). These interface may have different settings (especially MTU settings), which will result in different ping latencies. You can adjust such settings for each network interface with Tools like DrTCP. http://www.dslreports.com/drtcp

    Or maybe you have a software firewall installed like Zonealarm, Norton Personal Firewall etc., which is handling ICMP traffic on these interface in a different way.
  4. SirDracula

    SirDracula Network Guru Member

    I do NOT use PPPoE (sorry for not mentioning this), I just have a regular always-on DSL connection (Covad) with a *static* IP address.

    As for the software firewall, I have one, but the ping times don't make a difference with it on or off (which is good).

    The MTU is set at its max of 1500 on my computer's ethernet interface. The MTU is set to "Auto" on the router and it seems to default to 1500 from an "ifconfig -a" when logged in to the router via ssh.

    Oh, and I do not have any QoS enabled either on my computer or the router so it's not a problem with traffic priority.

    So, I am still puzzled about this ...
  5. SirDracula

    SirDracula Network Guru Member


    I went option by option and toggled them until I could see a change.

    The guilty option is Administration Tab > Log SubTab (NOT Syslogd), if it's Enabled the ping times suck, if it's Disabled, the ping times are as good as not having the WRT54GS in the picture at all.

    Finally! So for anyone who uses the Sveasoft firmware, don't enable any logging!
  6. pkitester

    pkitester Network Guru Member

    logging can't keep up either

    I guess I could have told you that logging can cause some pretty severe issues. I have written some logging software and during my testing I would swamp the router with many connections per second. The router just completely dies(slows down to the point of not working). CPU pegs, packets are dropped, and even the log messages you do get look like they are getting corrupted.

    So overall it seems there are some serious problems with the logging in this firmware. For the most part it works if you have light loads, and don't mind the extra latency it introduces. But I would think with a 200mhz processor something this simple wouldn't cause such a problem.
  7. none

    none Network Guru Member

    Is the logging feature enabled by default in the Satori and Alchemy firmwares?

  8. SirDracula

    SirDracula Network Guru Member

    To follow up on this topic, I tried HyperWRT 2.0b3 with logging enabled and it doesn't have this issue, the ping times are normal.

    I believe logging is disabled by default in Satori.
  9. pkitester

    pkitester Network Guru Member

    Yes, by default I've always seen logging off.

    But I think this is a feature most people will want to enable. Don't you want to know who's hacking you? Don't you want to know what machines of yours are making outbound connections, and where? I always find it fun to be able to go back a couple of years in my logs and find some software I thought was "ok" has been sending out information on a continual basis, in other words dialing home(EX: APC Powerchute).
  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