On Thu, Mar 20, 2014 at 01:43:59PM +0900, YASUOKA Masahiko wrote:
On Wed, 19 Mar 2014 21:05:35 -0700
Paul B. Henson hen...@acm.org wrote:
On Thu, Mar 20, 2014 at 10:22:51AM +0900, YASUOKA Masahiko wrote:
pppx will be fixed.
Great :). This is a known bug then?
It's new for me. I had
From: YASUOKA Masahiko
Sent: Wednesday, March 19, 2014 9:44 PM
Should I just keep an eye on the changelog for mention of pppx
changes to tell when it's safe to try again?
Sorry I cannot understand the point of this question.
Sorry to be confusing; I switched to tun because of this bug,
From: Jonathan Gray
Sent: Thursday, March 20, 2014 3:36 AM
The following diff prevents the panic here:
Interesting, given the XXX, it seems somebody was already a little
suspicious of this section :).
From a cursory glance, it seems pppx_dev_lookup is supposed to return data
about a
On Wed, 19 Mar 2014 16:45:46 -0700
Paul B. Henson hen...@acm.org wrote:
After successfully setting up an L2TP VPN with npppd and pppx, I tried
to add a second VPN subnet with a different authentication base. I was
working remotely, and after starting npppd in debug mode:
pppx will be fixed.
On Thu, Mar 20, 2014 at 10:22:51AM +0900, YASUOKA Masahiko wrote:
pppx will be fixed.
Great :). This is a known bug then? Should I just keep an eye on the
changelog for mention of pppx changes to tell when it's safe to try
again?
You can use tun(4) instead if you want to use multiple
On Wed, 19 Mar 2014 21:05:35 -0700
Paul B. Henson hen...@acm.org wrote:
On Thu, Mar 20, 2014 at 10:22:51AM +0900, YASUOKA Masahiko wrote:
pppx will be fixed.
Great :). This is a known bug then?
It's new for me. I had not even try MAKEDEV pppx1 yet.
Should I just keep an eye on the
6 matches
Mail list logo
