> If kppp does it and PPP_TEMP_ENTRY is not set, isn't it right ? kppp doesn't use /etc/ppp/ip-up to write dynamic DNS entries in /etc/resolv.conf
> Otherwise the nameservers would be written two times in there, > wouldn't it ? Yes, because kppp sets itself the dynamic DNS entries and ip-up *never* sets this dynamic DNS entries, while it should be its job, not kppp's. > Why do you think it will never match ? because the # ppp > temp entry is not set in this case ? Because when connection is closed, /etc/ppp/ip-down removes all lines matching"# ppp temp entry". What I wanted to point out it that PPP_TEMP_ENTRY variable is never set, so there no need to use it ... > > For dialup users, with the current ip-up script, only kppp sets > > dynamic DNS in /etc/resolv.conf (it doesn't use the ip-up to do > > that) ... > > Hmmm > Your complain is that for modem use only kppp works ? Roughly speaking, yes. My real complain is that for dialup modem use, only kppp sets dynamic DNS correctly, but it doesn't use ip-up to set them, though I don't know how kppp does it (perhaps it uses /etc/peers/resolv.conf) When others dialers (ppp-on, wvdial) are used, dynamic DNS aren't used, ip-up doesn't write the DNS in /etc/resolv.conf while it should (see my proposed fix) > If drakconnect sets this entry normally in /etc/resolv.conf and > doesn't do that for modem since it is supposed to work with kppp it is > sure a bug. It seems that drakconnect use kppp, when I try to connect with drakconnect, I launchs kppp as root. It's /etc/ppp/ip-up 's job to set the dynamic DNS entries in /etc/resolv.conf, but it is never done because PPP_TEMP_ENTRY is never set. > I have a bit the feeling I don't understand what you want to say, but > thats Ok I guess ;) Sorry, it's a bit hard to explain ;) -- Olivier Blin
