Hello everybody,
I got a few gadgets for christmas this year, one of which was a router. While I am very glad that I can finally be online with more than one computer at a time, I have a little problem with it.
The internet-connection is working fine. My Fedora box is not having any problems with it. The gentoo box has no problems accessing and surfing the net either. At first it would not start the network at boot, but a little googling helped me solve this problem (
rc-update add net.eth0 boot).
My problem now is that on the gentoo box many (not all!) KDE applications take a very long time to start. For example bringing up kview takes several minutes, while kword starts just as quickly as it always did. KDE itself takes several minutes to get past the second part of the initialisation process ("initialising system services").
There is another curious symptom: kmail starts up as fast as it did before but freezes a second into checking the account for new mail (AFTER it has started downloading mail). After some minutes it displays an error message (
"Could not read file The server terminated the connection.."[sic]) and works normally after that (including checking email).
With dhcpcd deactivated neither of these problems occur.
I have found several posts about similar problems, but the solutions suggested there did not help me.
It might help if I list things I found there and tried unsuccessfully:
-
accidentially i removed the network loopback from my boot-runlevel
Not my problem:
rc-update show
-
If you have two or more nameservers [in /etc/resolv.conf] try commenting one of them out with a # sign.Most likely the first one or your routers nameserver (IP).
Commented my router's nameserver, no effect.
I assume there is indeed some problem with the network (as it first appeared after I replaced the hub with the new router), but I have run out of ideas as to what to do about it.
Can anybody suggest what I might be able to try?
Thanks a whole lot in advance,
- drowstar
Update: After poking around my systems network setup I figured out that there seems to be an issue with the loopback device after all.
ping 127.0.0.1 results in 100% packet loss, same for ping localhost (which seems to be resolved to 127.0.0.1). However when I ping my IP it works just fine.
I will open a new thread as the problem seems to be a lot different from the one I originally reported. Also, I am convinced that this one is too old to be noticed by anyone anymore. I will post another update here if the other thread yields any results.