From: Marcel Holtmann <marcel@holtmann.org>
To: O Plameras <oscarp@acay.com.au>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Re: rfcommX and ppp
Date: Sat, 09 Oct 2004 15:51:43 +0200 [thread overview]
Message-ID: <1097329902.12972.1.camel@pegasus> (raw)
In-Reply-To: <4167DB4C.6000504@acay.com.au>
Hi,
> > try to use 10.0.0.1: or other way around. Or you can define multiple
> > options.rfcommX files in /etc/ppp/ and use a bridge. There are some ways
> > to get this working.
>
> I learned from PPP lists that ppp0 interface bridging is not supported
> nor is their a patch under 2.6.x or pppd.
>
> When I do this,
> brctl addif br0 ppp0
>
> it returns,
> br_add_interface: Invalid argument
>
> Nobody is doing work on these at the moment is my understanding.
this is a question for the bridge people. Using PPP over RFCOMM is
deprecated by the Bluetooth SIG and using PAN is much more straight
forward how things should be.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-10-09 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 13:05 [Bluez-users] rfcommX and ppp Rafael Vidal Aroca
2004-10-05 15:57 ` Marcel Holtmann
2004-10-05 17:23 ` Rafael Vidal Aroca
2004-10-06 9:44 ` Marcel Holtmann
2004-10-09 12:36 ` O Plameras
2004-10-09 13:51 ` 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=1097329902.12972.1.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=oscarp@acay.com.au \
/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