Summary: | elinks often can't connect to server | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cedar McKay <gentoo.3.ohthetrees> |
Component: | Current packages | Assignee: | Michal Januszewski (RETIRED) <spock> |
Status: | RESOLVED UPSTREAM | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
tcpdump- links session
tcpdump- elinks session |
Description
Cedar McKay
2004-03-04 11:36:28 UTC
1) Are you using a proxy? 2) On the bottom of the elinks window there a 'status-line' which shows msgs like "Making connection", "Request sent", "Transferring", etc. At which of these states does the page loading stop? 1)I'm not using a proxy. I am behind a lynksys router. But considering that every other browser, from firefox to links works fine (and out of the box) on that machine, I think it has to be an issue with elinks. 2) Today I'm not able to hit any websites at all. If I type "g" to bring up the "go to url" window, then enter a url, (e.g. http://google.com) there is a brief flash of the words "Looking up host" followed 1/4 second later with "Error Host not found". As I said, doing the exact same procedure with links works fine. thanks, Cedar Ok, here's an idea of what to do. Install a packet sniffer like tcpdump or ethereal. Make sure no confidental informations are transferred to/from your computer when you'll be using the sniffer. It would be best if you could stop all other unnecessary traffic (fetchmail, irc, p2p programs, etc). Then start the sniffer and make sure the promiscuous mode is _disabled_. After you have started the sniffer, go to your console and start elinks. Try to visit one or two pages. Then end your sniffing session and save the results in a sane format (tcpdump's format will do fine). Then repeat those steps for a different browser (links, mozilla, whatever). And finally send me the two saved files for analysis. I hope to be able to either find some differences between how elinks and <any browser> tries to load a webpage or reproduce the problem here, on my computer. Please remember that it's important you make sure no confidental data like passwords, personal conversations is transferred at the time you will be making the traffic-snapshots. Thanks in advance for your work on this issue :) might take me a day or two to get to that, but I will. Great, I hope it gets us somewhere. I'll be AFK 11th - 14th Mar, so please be patient ;) Ok, I'm back. Any progress on this one? Created attachment 27352 [details]
tcpdump- links session
Created attachment 27353 [details]
tcpdump- elinks session
OK, I attached a links session and and elinks session in the tcpdump format. Links session: went to google, then nyt.com worked fine Elinks session: went to google and it worked, then tried nyt.com, seattlepi.com, espn.com all gave the "host not found error" hope that helps, Cedar Do you have the 'async_dns' option enabled in your elinks config file? Could you change this option's state (ie. enable it if it's disabled and disable it if it's enabled) and check if this changes anything? just to be clear, my config file was totally default, I hadn't modified it at all. Anytway, async_dns was set to 1 by default, and changing that to 0 caused the problem to disapear. Everything is working super now. Thanks! Mind explaining what was going on, and whose fault it is? thanks, Cedar Well, when the async_dns option is enabled every time you want to load a page a separate thread is started for the DNS query. When it's disabled, the queries are done from the main browser thread. async_dns is enabled by default in both elinks and links (AFAIK). For some reason the async dns queries in elinks didn't work for you, I don't know why exactly as I was not able to reproduce this problem on my system. Do you have async_dns enabled in links? If you do, and it works, you might consider reporting a bug about async_dns to the elinks authors. Perhaps they will be able to find and fix it then. Ok, I'm closing this one as there isn't much more that can be done about it. |