[Bluez-users] dund and bluez

[Bluez-users] dund and bluez

[Mark S. Townsley]

[-- Attachment #1.1: Type: text/plain, Size: 209 bytes --]

Hi:  I would like to find out more about how DUN profile (and DUND daemon)
works with Bluez.
Is there any config tutorial or programming tutorial about how to integrate
DUN profile with Bluez?

thanks



Mark

[-- Attachment #1.2: Type: text/html, Size: 240 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] dund and bluez

[Stefan Seyfried]

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

On Sun, Dec 17, 2006 at 10:36:31AM -0800, Mark S. Townsley wrote:
> Hi:  I would like to find out more about how DUN profile (and DUND daemon)
> works with Bluez.
> Is there any config tutorial or programming tutorial about how to integrate
> DUN profile with Bluez?

Marcel, these two files are in the SUSE package for quite some time.
Maybe they are good for upstream bluez-utils, too?

-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

[-- Attachment #2: README.dund --]
[-- Type: text/plain, Size: 1928 bytes --]

Problem Description:
====================
If you have some mobile device that is able to make a ppp connection via
bluetooth, and you want to use SUSE LINUX Professional as host to connect with,
you will have to correctly setup the dund.

What to do:
===========

Configuring the dun-daemon on your system:
------------------------------------------
  There's a file named 'dun.example' in this directory. You need to copy it to
/etc/ppp/peers/dun and edit its content. The file contains instructions for
the ppp-daemon regarding connections using dun, most of them are commented.

  Now you should look at the settings of the dun-daemon itself. Start YaST and
select 'bluetooth' from the 'Hardware'-menu.
  In the popup check if Bluetooth is enabled, if not, do so. Aftewrwards click
on the 'Advanced Daemon Configuration'-button. You will now see a list of
available daemons. dund should be listed there, too, otherwise your
installation might be broken.
  The dund is not activated in the default configuration. If you want to use
it, you should enable it now by selecting dund and clicking on 'enable'
afterwards.  With the still selected 'dund'-item click on "edit". A popup
containing the options used for the daemon (not for a single connection as the
ones in the example-file mentioned above!). 
  Change these options to "-listen --persist --msdun call dun" (without the
quotation marks). You can see the valid options by calling 'dund --help' from
a shell.  The 'call dun' is not directly used by dund, but given to the
ppd-daemon. It tells the pppd to use the options found in /etc/ppp/peers/dun. 

Connecting PDA (or whatever device you have) with computer:
-----------------------------------------------------------

  On the mobile device, search for the bluetooth-enabled machine, and connect
to it with ppp. Giving more concrete instructions is hard since the methods
vary from mobile device to mobile device.


[-- Attachment #3: dun.example --]
[-- Type: text/plain, Size: 2000 bytes --]

# Example-file for creating a ppp connection with bluetooth between e.g. a PDA
# and the computer. Move this to /etc/ppp/peers/dun and adapt the following
# options to your needs. The values and options below there are far from
# perfect, but were good in a lot of testcases. They may not be good for you!
#
# Most of the comments were taken from the pppd-manpage for your convenience.
# See there for more information and options

## Enables connection debugging facilities. You should use this if you have problems
#debug

# Baudrate
57600

## Disables the default behaviour when no local IP address is specified,
## which is to determine (if possible) the local IP address from the hostname.
## With this option, the peer will have to supply the local IP address
## during IPCP negotiation (unless it specified explicitly on the command line
## or in an options file).
noipdefault

## Add an entry to this system's ARP [Address Resolution Protocol] table with
## the IP address of the peer and the Ethernet address of this system. This
## will have the effect of making the peer appear to other systems to be on the
## local ethernet.
proxyarp

# IP address of PC : IP address to be assigned to PDA
192.168.1.1:192.168.1.2

# Your DNS server
ms-dns 10.0.0.1

## Enables pppd to alter kernel settings as appropriate. Under Linux, pppd will
## enable IP forwarding (i.e.  set /proc/sys/net/ipv4/ip_forward to 1) if the
## proxyarp option is used, and will enable the dynamic IP address option (i.e.
## set /proc/sys/net/ipv4/ip_dynaddr to 1) in demand mode if the local address
## changes.
ktune

## Do not require the peer to authenticate itself. This option is privileged.
noauth

## Don't use the modem control lines.  With this option, pppd will ignore the
## state of the CD (Carrier Detect) signal from the modem and will not change
## the state of the DTR (Data Terminal Ready) signal.
local

## Disable the defaultroute option.
nodefaultroute

## Disable the IPXCP and IPX protocols. 
noipx

[-- Attachment #4: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #5: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] dund and bluez

[Stefan Seyfried]

On Mon, Dec 18, 2006 at 10:03:05AM +0100, Stefan Seyfried wrote:
> On Sun, Dec 17, 2006 at 10:36:31AM -0800, Mark S. Townsley wrote:
> > Hi:  I would like to find out more about how DUN profile (and DUND daem=
on)
> > works with Bluez.
> > Is there any config tutorial or programming tutorial about how to integ=
rate
> > DUN profile with Bluez?
> =

> Marcel, these two files are in the SUSE package for quite some time.
> Maybe they are good for upstream bluez-utils, too?

Oops. Mentioning YaST does not help too much :-) I'll clean them up a bit
and resend.
-- =

Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg  | "Well, surrounding them's out." =


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] dund and bluez

[Stefan Seyfried]

On Mon, Dec 18, 2006 at 09:18:09AM -0800, Mark S. Townsley wrote:
> Hi Stefan:
> =

> Many thanks for those dund files.  I have followed the steps and seem to =
get

They were most probably already on your machine in
/usr/share/doc/packages/bluez* ;-)

> dund listening just fine.  However, when I minicom over /dev/rfcomm0, I
> still get /dev/rfcomm0 not found.

I think this is an authentication problem. Look in the logs.

> Can I ask you a few stupid questions:

Yes, but better direct them to the list, since there are many knowledgeable
people there that might actually be able to help better than i am :-)

>  1)  I am trying to get my SuSE box to talk to a bluetooth module made by
> Ezurio (attached).  It is sending AT commands to me (and likewise, I can =
AT
> over if I want to interact).  Do I need PPP?  I think I need DUND to hand=
le
> the AT commands but I am not sure if I need PPP.

I have no idea.

>  2)  Can you tell me, programtically (say from C or C++), how can I comma=
nd
> DUND to respond or issue AT commands to a remote host?  Most examples I
> google'ed show it how from some AT scripts living under /etc/ppp/.....

I think that dund just listens for incoming connection and hands those over
to pppd, but to be honest, i have only tried it once.

If you now would mention which version of SUSE you are using (and maybe even
which version of bluez-utils is installed), then even more knowledgeable
people might be able to help you :-)

Have fun,

    Stefan

-- =

Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg  | "Well, surrounding them's out." =


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users