From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] PAND + DUND
Date: Fri, 09 Sep 2005 14:21:47 +0200 [thread overview]
Message-ID: <1126268507.5227.83.camel@blade> (raw)
In-Reply-To: <1126266637.4171.178.camel@baythorne.infradead.org>
Hi David,
> > you might not wanna hear it, but the DUN profile is deprecated (even by
> > the Bluetooth SIG). However to integrate it into your bridge you need to
> > play some tricks with pppd. It is all about pppd and this is not going
> > to be very easy.
>
> That's sad. DUN allows for compression; Unless I'm mistaken, PAN does
> not.
>
> I keep intending to write a pppd plugin and kernel module to do
> ppp-over-rfcomm directly instead of using the tty. Haven't quite got
> round to it yet though :)
the bluez-utils package still contains ppporc, but the kernel PPP and
pppd sucks and so PPP over RFCOMM socket directly is almost impossible
without tricks.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-09 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 23:21 [Bluez-devel] PAND + DUND Gavin Glynn
2005-09-08 23:34 ` Marcel Holtmann
2005-09-09 11:50 ` David Woodhouse
2005-09-09 12:21 ` Marcel Holtmann [this message]
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=1126268507.5227.83.camel@blade \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.