Re: pppd proxyarp broken?

[christos%astron.com@localhost (Christos Zoulas)]

In article <20140228151423.GB16194%homeworld.netbsd.org@localhost>,
Emmanuel Dreyfus  <manu%netbsd.org@localhost> wrote:
>Hi
>
>Today I upgraded a modem remote access system to NetBSD 6.1.2. pppd 
>software changed a bit, for instance I now have to specify the password
>in pap-secrets as @login (I previously used *) if I want to use PAM, 
>otherwise I get "PAP peer authetication failed". This does not seems 
>to be documented (I learnt it reading the sources).
>
>Here is pap-secrets for future refernece if somone has the same problem:
>*       servername     @login  192.0.2.91 192.0.2.92
>
>Another problem is that proyarp seems broken. Using ktrace I can see
>pppd opening the routing socket and writing the entry, but arp -a does
>not list it. pppd does nto check if the result is correct or not. 
>Manually adding the arp entry works aroud the problem, but I wonder if 
>I missed something. here is /etc/ppp/options:
>57600 crtscts
>modem
>nodetach
>proxyarp
>auth login require-pap
>ms-dns 192.0.2.20
>ms-dns 192.0.2.25
>ms-wins 192.0.2.20

IIRC this is a kernel issue fixed in head.

christos