Linux PPP protocol development
 help / color / mirror / Atom feed
From: tony.chamberlain@lemko.com
To: linux-ppp@vger.kernel.org
Subject: Re:  Banyan Vines
Date: Tue, 28 Oct 2008 14:25:09 +0000	[thread overview]
Message-ID: <W381217436184361225203909@webmail20> (raw)
In-Reply-To: <W9913123352266171225199214@webmail4>



-----Original Message-----
From: James Carlson [mailto:carlsonj@workingcode.com]
Sent: Tuesday, October 28, 2008 09:02 AM
To: tony.chamberlain@lemko.com
Cc: linux-ppp@vger.kernel.org
Subject: Re: Banyan Vines

tony.chamberlain@lemko.com writes:
> Does anyone know what it means if you are running pptp and in
> /var/log/messages you get a message "unsupported protocol Banyan Vines"
> (along with a lot of unsupported protocol messages which are just
> hex values), or what to do about it?

It means you're getting garbled packets from the peer.

If it's persistent and doesn't correct itself over time, the most
plausible reason (I think) would be that you're using MPPE (MS
proprietary packet encryption) and there's a bug in that code.

If it just happens intermittently and then fixes itself, I'd ignore
it.  The cause would be dropped or corrupted packets and recovery by
the encryption code.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>


It appeared to be happening every couple minutes and causing
the VPN to go down (even though pppd was still running) so I had
to kill pppd and let it restart. That fixed it till the next time.
So probably like you say it is mppe.

Thanks




  parent reply	other threads:[~2008-10-28 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 13:06 Banyan Vines tony.chamberlain
2008-10-28 14:02 ` James Carlson
2008-10-28 14:25 ` tony.chamberlain [this message]
2008-10-30 19:40 ` Michael St. Laurent
2008-10-30 20:09 ` James Carlson
2008-10-30 22:35 ` tony.chamberlain
2008-10-31 13:06 ` James Carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=W381217436184361225203909@webmail20 \
    --to=tony.chamberlain@lemko.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox