Choke routing - how to detect and avoid

Discussion in 'Cisco' started by Peter H.M. Brooks, Jul 23, 2003.

  1. Having recently moved to ADSL, I expected much improved performance. SMTP
    and NNTP are indeed much faster - ftp isn't bad either.

    However http is much slower than before on dial up!

    So, I am suspicious that the vendor has some http choke provisions in place.
    To try to circumvent this, I have connected on browser to a local proxy, but
    the problem seems the same. http downloads are particularly slow.

    What should I do to detect if this really is the case?

    If it is, is there any way around it? Are there, for example, proxy routers
    that allow you to tunnel http through some other protocol?
     
    Peter H.M. Brooks, Jul 23, 2003
    #1
    1. Advertisements

  2. That looks OK - I see my IP address.

    However, when I do a traceroute I find that I get lots of 'request timeouts'
    when I go through a particular router - 196.43.10.85, as it happens. Is
    there an easy way to see if this is because it is overloaded or because it
    has some choke applied?
     
    Peter H.M. Brooks, Jul 23, 2003
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.