linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Kalle Valo <kalle.valo@canonical.com>
Cc: ofono@ofono.org,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: DUN client for oFono and BlueZ
Date: Tue, 27 Apr 2010 03:35:33 -0300	[thread overview]
Message-ID: <20100427063533.GA30819@vigoh> (raw)
In-Reply-To: <8739yhsa92.fsf@potku.valot.fi>

Hi Kalle,

* Kalle Valo <kalle.valo@canonical.com> [2010-04-27 09:03:05 +0300]:

> "Gustavo F. Padovan" <gustavo@padovan.org> writes:
> 
> > Hi all,
> 
> Hello Gustavo,
> 
> > I'm starting the DUN Client implementation for the Linux Stack. DUN is
> > the Bluetooth dial-up network profile. It makes possible share internet
> > connection between two Bluetooth devices. That is my Google Summer of Code
> > project for this year.
> 
> Excellent, I'm eagerly waiting for this. I hate cables =)
> 
> As soon as you have something working, please do send patches so that
> people can test it.
> 
> > 4. Agent server on BlueZ. This one is very similar to the HFP Agent server. At
> > the end of the DUN agent project I plan to merge the both agent servers. SAP
> > will take advantage of that merge too.
> >
> > 5. oFono DUN agent. Implement the agent handling for DUN.
> 
> Sorry, I'm not familiar with HFP Agent, but what will this agent
> actually do on a DUN connection

The agent can request a RFCOMM connection and receive the RFCOMM channel
via DBus fd-passing. The the DUN plugin can do the handshake.

> 
> > 6. AT command parser and PPP stack integration with DUN. The biggest task,
> > where the core of the project is.
> >
> > 7. ConnMan integration. Setup of the NAT and Internet Connections.
> 
> Why NAT is needed? I guess only for connection sharing.

No idea yet, I guess Denis told me about the NAT, but that will be the last part
of the project, so I'm not caring about it now. I have to check on my
irc logs.


-- 
Gustavo F. Padovan
http://padovan.org

  reply	other threads:[~2010-04-27  6:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  1:20 DUN client for oFono and BlueZ Gustavo F. Padovan
2010-04-27  2:07 ` Marcel Holtmann
2010-04-27  2:12   ` Gustavo F. Padovan
2010-04-27  2:14 ` Zhang, Zhenhua
2010-04-27  2:19   ` Gustavo F. Padovan
2010-04-27  2:40     ` Zhang, Zhenhua
2010-04-27  2:35   ` Denis Kenzior
2010-04-27  6:03 ` Kalle Valo
2010-04-27  6:35   ` Gustavo F. Padovan [this message]
2010-04-27  7:26     ` Kalle Valo
2010-04-27  8:15 ` Bastien Nocera
2010-04-27 15:30   ` Gustavo F. Padovan
2010-04-27 15:40     ` Bastien Nocera

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=20100427063533.GA30819@vigoh \
    --to=gustavo@padovan.org \
    --cc=kalle.valo@canonical.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ofono@ofono.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;
as well as URLs for NNTP newsgroup(s).