From: Günther Schwarz on
Marc Haber wrote:

> Günther Schwarz <strap(a)gmx.de> wrote:
>>But then this also requires some reachable DNS server. Since my last
>>posting I wrote two lines of scripts for /etc/ppp/ip-up.d/ which copy a
>>working resolv.conf to /etc/.
>
> I would recommend doing so through Debian's resolvconf interface.
>
> echo "nameserver a.b.c.d" | resolvconf -i ppp0 to initialize and
> resolvconf -d ppp0 to restore the previous state.

Thanks a lot.

Günther
From: Günther Schwarz on
Marc Haber wrote:

> echo "nameserver a.b.c.d" | resolvconf -i ppp0 to initialize

resolvconf -a

> and resolvconf -d ppp0 to restore the previous state.

This is already present in /etc/ppp/ip-down.d on Lenny.
It works as intended (I'm posting over 3G network).

Günther
From: Günther Schwarz on
Moe Trin wrote:

> On 16 Mar 2010, in the Usenet newsgroup comp.os.linux.networking, in
> article <80a6vtF7krU2(a)mid.individual.net>, Günther Schwarz wrote:
>
>>Moe Trin wrote:
>
>>> Which version of ppp are you using?
>
>>pppd version 2.4.4 on Debian Lenny
>
> What's new in ppp-2.4.5.
> ************************
>
> * Under Linux, pppd can now operate in a mode where it doesn't request
> the peer's IP address, as some peers refuse to supply an IP address.
> Since Linux supports device routes as well as gateway routes, it's
> possible to have no remote IP address assigned to the ppp interface
> and still route traffic over it.
>
> * Pppd now works better with 3G modems that do strange things such as
> sending IPCP Configure-Naks with the same values over and over again.
>
> 2.4.5 was released back in November. You should be aware that the
> Debian version is significantly altered from what the authors (Paul
> Mackerras of samba.org and James Carlson of Sun) supply.

Thanks for the hint. Though this looks promising Debian stays with
version 2.4.4 even with unstable. It might be too much work to tweak the
source code until it fits to the distribution.
As it is quite common not only with Debian a little patience might
resolve this problem over time.

Günther
From: Marc Haber on
Günther Schwarz <strap(a)gmx.de> wrote:
>Marc Haber wrote:
>> echo "nameserver a.b.c.d" | resolvconf -i ppp0 to initialize
>
>resolvconf -a

Sorry, I always mix up these options. resolvconf desperately needs to
learn long options.

Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
From: Moe Trin on
On Wed, 17 Mar 2010, in the Usenet newsgroup comp.os.linux.networking, in
article <hnqdan$vg9$1(a)news1.tnib.de>, Marc Haber wrote:

>(Moe Trin) wrote:

>>Which version of ppp are you using?

>2.4.4rel-10.1 from Debian unstable, I have been seeing this behavior
>ever since I started using mobile Internet access years ago.

You may want to check with the Debian maintainer, as the ppp package
supplied by Debian is substantially modified from the ANU source from
Mackerras and Carlson. None-the-less, this does appear to be a
problem with the wireless/mobile/UMTS/3g system rather than in pppd.

>Since I have changed over to wvdial, my pppd doesn't log the IPCP/LCP
>conversations any more. I cannot verify this.

You could by adding 'debug' to /etc/ppp/options, but wvdial being a
windoze wanna-be program tries to hide technical stuff like that.

>Since the PPP Peer in this case is the UMTS device and I have seen
>this behavior with a lot of different UTMS devices - is proposing
>10.11.12.13 and 10.11.12.14 an official standard, or just a
>convention among all vendors?

I haven't found any official standards - and it appears to be a
rather unfortunate assumption by the vendors trying to choose a
number that users would _never_ think of using themselves. To bad
the idiots never asked a 6 or 7 year old child.

Old guy