From: Kalle Valo <kalle.valo@canonical.com>
To: ofono@ofono.org
Subject: Re: DUN client for oFono and BlueZ
Date: Tue, 27 Apr 2010 09:03:05 +0300 [thread overview]
Message-ID: <8739yhsa92.fsf@potku.valot.fi> (raw)
In-Reply-To: <20100427012059.GG12813@vigoh>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
"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?
> 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.
--
Kalle Valo
next prev parent reply other threads:[~2010-04-27 6:03 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 [this message]
2010-04-27 6:35 ` Gustavo F. Padovan
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=8739yhsa92.fsf@potku.valot.fi \
--to=kalle.valo@canonical.com \
--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