Hello everyone,
I recently changed my network setup to use a router instead of the rp-pppoe setup I used to have running.

The problem I am having is that since I have started using dhcp, localhost does not seem to be resolved correctly anymore. This is really bothersome as many applications seem to try to resolve localhost before starting up and this takes a long while to time out.
When I try to ping the loopback address (127.0.0.1 or localhost) I am getting 100% packet loss. Interesting thing is that pinging my "outside" IP address (193.158.167.136 at the moment) works just fine.

Some other things that might be of interest:
The loopback device is activated (ifconfig -a: [snip]lo Link encap:Local Loopback[/snip]), the router is registered as a DNS (resolv.conf:[snip]nameserver 192.168.1.1[/snip]) and localhost is resolved to 127.0.0.1 (/etc/hosts: 127.0.0.1 localhost). Changing this to my current IP does not have an immediate effect.

Do you have an idea what could be causing this and how to fix it?

Thanks a lot,
- drowstar

First you should do a route print to see what the local host is directed to, possible that it is incorrect, this caused me all sorts of headaches a few weeks ago while hooking up a VPN

Hi jdlcomputers,
thanks for your reply. Unfortunately I am not sure if I understand what you mean. I will try my best.
My best guess at what a route print might be:
This does not seem to include the localhost, right? Is that my problem? Sorry, I feel a bit lost here. I have tried adding my loopback address using an example from the man page (route add -net 127.0.0.1), but that only produces an error (SIOCADDRT: Invalid argument).

I hope this gives you a clue.

Thanks for helping,
- drowstar

EDIT: I just checked on my fedora box. There the same command (route) yields:
The problem this thread is about does not occur there.

Hi Drowstar,
Sorry about the confussion, I let some of my Windows training get the best of me..

Do the following
open a terminal window, type in SU then enter, log into your ROOT (should be a # not a $ you will need whatever you set up as root password to do so..from there simply type in route and press enter.. post your results, I will check back later today

Jerry

Hi Jerry,
thanks for your replies. The output I pasted in my last post is the result of the commands you told me to type in. (Thanks for the detailed instructions. I dont need them quite this exact though.)

Thank you for the routing table hint. It made it possible for me to find out that I can work around the problem when I block the route to 127.0.0.1 (route add -net 127.0.0.1 netmask 255.255.255.255 reject). I am very certain that this is not the appropriate solution, but this ugly hack lets me at least work normally for now.

With that hack in place my routing table looks like this (I used route -n as that seems more to the point to me):
Thank you for your help. Your reply really made it a lot easier to work on this machine. You might be interested in another thread I opened on the topic (sorry, I didn't think you'd reply. I at least should have updated this thread.)

Thanks a bunch again,
- drowstar

I'm glad that worked..
I am used to working with people with the knowlegde of the bathroom wall, so sometimes I get real detailed about the instructions... Sorry

Jerry