On Fri, Mar 6, 2009 at 4:19 PM, Thomas Bohn <thomas@xxxxxxxxxxx> wrote: > On 2009-03-06 16:11 -0600, Aaron Griffin wrote: > >> Ok, well... if you shut off your network AFTERWARDS, does it block >> your connection attempts too? Does /etc/hosts have "localhost" in >> there? > > When I shutdown the connection it doesn't work, the loop interface stays the > same all the way. > > lo when connected: > ---snip--- > % ifconfig lo > lo Link encap:Local Loopback inet addr:127.0.0.1 > Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:23 errors:0 dropped:0 overruns:0 frame:0 > TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2167 (2.1 Kb) TX > bytes:2167 (2.1 Kb) > ---snip--- > > when disconnected: > ---snip--- > % ifconfig lo > lo Link encap:Local Loopback inet addr:127.0.0.1 > Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:23 errors:0 dropped:0 overruns:0 frame:0 > TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2167 (2.1 Kb) TX > bytes:2167 (2.1 Kb) > ---snip--- > > When I try to run ncmpcpp, when I'm disconnected: > ---snip--- > % ncmpcpp > Cannot connect to mpd: host "localhost" not found: Temporary failure in name > resolution > % ncmpcpp > Cannot connect to mpd: host "127.0.0.1" not found: Address family for > hostname not supported > ---snip--- > > It is just weird. Agreed... how about running "route -nv" before and after lo is borked?