Why does ppp(8) dial for no reason in -auto mode?
> > > I’ve fought the same irritating issue now and again. As for > > diagnosis, the most useful thing I’ve found is to turn on full > > logging (in ppp.conf), then grep (or tail -f or whatever) the log > > looking for the dial trigger after a spurious dial. I’m not on > > the machine from which I have the misfortune of needing to use a > > modem so I can’t say off-hand the exact string to look for, but > > it’s not any of the four lines you’ve posted. > > full log (if it help you remeber that string, if not when you > are on that machine could you send me the string, please?): Thinking back and looking at the man page a bit, I believe that what you want to log is ‘Filter’. Here’s a bit from the (long!) man page (locate ‘LOGGING’ to find it.): … DNS Log DNS QUERY packets. Filter Log packets permitted by the dial filter and denied by any filter. HDLC Dump HDLC packet in hex. … IIIRC, you can then ‘grep Filter’ to see what triggered the dial. This was sufficient in my case to determi
I’ve fought the same irritating issue now and again. As for diagnosis, the most useful thing I’ve found is to turn on full logging (in ppp.conf), then grep (or tail -f or whatever) the log looking for the dial trigger after a spurious dial. I’m not on the machine from which I have the misfortune of needing to use a modem so I can’t say off-hand the exact string to look for, but it’s not any of the four lines you’ve posted. If you need more info about the nature of the transaction, try ‘tcpdump -i tun0’. I used this recently to determine that various operations on NAT machines behind my gateway were generating spurious (and obviously failing) reverse DNS lookups and thus, an unwanted dial. I never reached a conclusion about how to deal with this other than to set up a cacheing-only DNS server, but I shouldn’t even mention it here since it’s probably not related to a solution for you (…or is it?) BTW, and totally unrelated, does anyone know of a graphical dial utility for ppp(8) (aka,
