[wellylug] Odd internet (ip-up?) Problems (was: Problems with fetchmail)

[Leslie Boardman]

Yeah, I thought the nameserver set up looked a bit funny.  I have now
changed it to only be one line.  I figure I'll just add the other one
outside (below) the whereami bit.  I had a look at the script that does
it but I'll need to find my bash guide to follow it.

I have realised that I don't really know what my machine is doing.  Even
with the wrong resolv.conf it connected to the internet ok.  When I
removed whereami and installed a newer version of netenv (this all
started because the debian stable netenv doesn't do dhcp) I could
connect but not resolve any domains, I admit that the resolv.conf file
was still the un-updated one so something was not happening post the
modem connecting but I have no idea what.

In the meantime I have put whereami back and have left my fetchmail and
chrony kludges in place.

Hopefully one of two things will happen:

1) I get time to sit down and really work out what it is doing when it
makes a connection and from there work out why chrony and fetchmail are
having problems or
2) Sarge becomes 'stable', I upgrade and hopefully my problems will go
away.

At this point I am all for 2, nothing like the head-in-sand approach!.

Thanks for the help.

Leslie

On Sun, 2004-04-18 at 20:35, Enkidu wrote:

> Hmm, the NOT CONNECTED nameserver line is supposed to be resolv.conf
> syntax I think that it is wrong. It should be:
> 
> nameserver 203.196.152.4
> nameserver 203.196.152.12
> 
> The man page says :  "Up to MAXNS (currently 3)  name  servers may  be
> listed, one per keyword."
> 
> Don't think that's your problem though.
> 
> Cheers,
> 
> Cliff
-- 
Leslie Boardman, E: elbe at araitanga.com, ICQ:153582540 
PGP Fingerprint:48ED F1C8 5CFF 6819 8958  847F 8F8F 4950 5422 D56B
PGP Key Server: http://www.keyserver.net
"ignorance more frequently begets confidence than does knowledge"-Darwin