Unable to connect properly to local web server from Gentoo - SOLVED
The problem is now fixed. It turns out that the MTU was set to 1500 on the Gentoo box, which is the ethernet default, but the chip only works with MTU set to 1492 (default for PPPoE). I really don't why this is the case, at least it works now though!
Hi there, This is a really weird one, I don't know if anyone could shed any light on it but it's a very *interesting* problem, which I'd love to figure out. It's not desperately important, but is really puzzling! I've tried posting it to the Gentoo forums on a different site, but not had any useful responses. I'm not convinced it's a Gentoo issue, so thought I'd try asking here. I am running a low end web/mail server on my home network. The server itself is set up with Slackware 10.1. There are a number of computers I use, both on the internal network, and externally. For most of these computers, the webserver works fine. However, it doesn't work for my main box on the home network, which runs Gentoo. I'll explain further. When I connect to the webserver, either on https or http, from my work computer or another computer at home, both of which run Ubuntu, the webserver responds just as expected. When I try to connect to it from my Gentoo box, the connection just sits there for certain directories. In Firefox, it just says "Waiting for server.address.com" (address changed from its actual name) in the status bar at the bottom of the Firefox window. This is not a Firefox issue though, as it also fails to connect in links, for example. Now it starts to get really weird:
I read somewhere that having MTU set wrong somewhere can cause something like this, but MTU seems to be set to 1500 on all the computers, which is what I'd expect. Other than that, I really can't understand what's causing this. If anyone has any ideas of other things I could check I'd really appreciate it! If more information on my setup would help, let me know. I'm running Gentoo amd64 with kernel gentoo-2.6.17-r4, but the problem was also occurring when I was using kernel gentoo-2.6.16-r11. The only possibility I can think of is that I missed something when configuring the kernel, but I've no idea what. Thanks! |
Nice to know it got resolved.
|
Which chip is it and which driver did you use please?, for future reference.. :)
|
The chip is a SiS 190, on the (infamous) Asus K8S-MX motherboard. It uses the sis190 driver included in kernel 2.6.14(?) onwards. There's a little more info on this kerneltrap posting.
Maybe this will help someone in future, although my advice would be to avoid that particular motherboard like the plague if you have any choice in the matter! |
All times are GMT -5. The time now is 01:53 PM. |