On Mon, Oct 13, 2003 at 10:01:57AM -0800, J Y wrote: > Hi, After getting grub to work and booting with the k7 kernel rather > than the bf2.4 the DNS problem returned..or that's what I think I'm > seeing-basically a conection that doesn't work. So I ran plog, I got an > exit status 1; I put exit 0 in the 6 scripts in /etc/ppp/ip-up.d > > Oct 13 12:34:57 deblnx pppd[1328]: not replacing existing default route > to tap0 [0.0.0.0] > Oct 13 12:34:57 deblnx pppd[1328]: Cannot determine ethernet address for > proxy ARP > Oct 13 12:34:57 deblnx pppd[1328]: local IP address 67.75.63.145 > Oct 13 12:34:57 deblnx pppd[1328]: remote IP address 63.215.27.35 > Oct 13 12:34:57 deblnx pppd[1328]: primary DNS address 209.244.0.3 > Oct 13 12:34:57 deblnx pppd[1328]: secondary DNS address 209.244.0.4 > Oct 13 12:34:57 deblnx pppd[1328]: Script /etc/ppp/ip-up started (pid 1369) > Oct 13 12:34:58 deblnx pppd[1328]: Script /etc/ppp/ip-up finished (pid > 1369), status = 0x0 > deblnx:/home/john# > > deblnx:/home/john# ls -l /etc/ppp/ip-up.d > total 24 > -rwxr-xr-x 1 root root 969 Oct 13 12:26 000usepeerdns > -rwxr-xr-x 1 root root 2466 Oct 13 12:27 0dns-up > -rwxr-xr-x 1 root root 831 Oct 13 12:30 1wwwoffle > -rwxr-xr-x 1 root root 92 Oct 13 12:33 exim > -rwxr-xr-x 1 root root 246 Oct 13 12:33 fetchmail > -rwxr-xr-x 1 root root 230 Oct 13 12:34 leafnode > > after removing the 'exit 0' from exim (this time I did it in the order > of ls -l ) I got a: > > deblnx:/home/john# plog > Oct 13 12:45:55 deblnx pppd[1739]: not replacing existing default route > to tap0 [0.0.0.0] > Oct 13 12:45:55 deblnx pppd[1739]: Cannot determine ethernet address for > proxy ARP > Oct 13 12:45:55 deblnx pppd[1739]: local IP address 67.75.62.176 > Oct 13 12:45:55 deblnx pppd[1739]: remote IP address 63.215.27.33 > Oct 13 12:45:55 deblnx pppd[1739]: primary DNS address 209.244.0.3 > Oct 13 12:45:55 deblnx pppd[1739]: secondary DNS address 209.244.0.4 > Oct 13 12:45:55 deblnx pppd[1739]: Script /etc/ppp/ip-up started (pid 1780) > Oct 13 12:45:55 deblnx pppd[1739]: Script /etc/ppp/ip-up finished (pid > 1780), status = 0x1 > > This is what's in exim: > #!/bin/sh > > # Flush exim queue > if [ -x /usr/sbin/exim ]; then > /usr/sbin/exim -qf > fi > > I'm just doing what I remembered from the help I got before. Yet the > symptom and results seem the same.Thanks
Well, if the symptoms are the same, the first thing to check is if the cause is the same. We eventually determined that the cause was that /etc/resolv.conf was a directory instead of a file, and cured it by making sure that /etc/resolv.conf was a file. So, the first thing to check is: has /etc/resolv.conf mysteriously turned back into a directory again? ls -ld /etc/resolv.conf By the time the exim script is run, DNS has already been set up. Failure of the exim script would result in your outgoing mail not being sent, but you'd still be able to use your browser etc. You can run exim -qf (as root) by hand after bringing the connection up to see if exim does have a problem. (Your kernel must be supporting PPP, otherwise you wouldn't be getting this far at all. Don't worry about that.) -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F
pgp00000.pgp
Description: PGP signature
