Linux bluetooth development
 help / color / mirror / Atom feed
From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] DUND pre-pppd script
Date: Thu, 29 May 2008 20:10:40 -0600	[thread overview]
Message-ID: <d89ddf300805291910n15430303r71fc22c0a1c689ca@mail.gmail.com> (raw)
In-Reply-To: <483F3DE8.5040807@magtech.com.au>

Aras

> I think that I can solve this problem by configuring dund to call a pppd
> wrapper which calculates the correct, non-colliding, subnet and then
> passed on the arguments to pppd.

although there is no way to coax dund to pass the remote btaddr
address on to a wrapper script, we should be able to figure it out.

tell dund to use the wrapper:
dund --pppd=mypppd ...

in the mypppd wrapper:
#!/bin/sh
BTADDR=`rfcomm show $2 | cut -d ' ' -f2`
# set LOCAL, REMOTE based on the BTADDR
pppd LOCAL:REMOTE $*

if dund were changed then the tty might no longer be on $2.
in my scenario at least, LOCAL would always be 0.0.0.0 and something
like /etc/ppp/ip-up.d/bridge would bridge pppX:

#!/bin/sh
# $2 is the ppp interface name
brctl addif pan0 $2

should be fun to see if any of this works :)

-- 
Brad

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-05-30  2:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  3:04 [Bluez-users] DUND pre-pppd script arasv
2008-05-29 11:01 ` Raymond Ingles
2008-05-29 23:36   ` Aras Vaichas
2008-05-30  2:10     ` Brad Midgley [this message]
2008-05-30 15:51       ` Brad Midgley
2008-05-29 12:39 ` Brad Midgley
2008-06-04  7:08   ` Aras Vaichas

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=d89ddf300805291910n15430303r71fc22c0a1c689ca@mail.gmail.com \
    --to=bmidgley@gmail.com \
    --cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox