public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: klaus@encephalon.dk (Klaus Holst)
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dund never activates pppd
Date: Tue, 24 Feb 2004 09:53:51 +0100	[thread overview]
Message-ID: <20040224085351.GA3782@encephalon.dk> (raw)
In-Reply-To: <1077573810.2791.161.camel@pegasus>

* Marcel Holtmann <marcel@holtmann.org> [2004-02-23 23:03:30 +0100]:

> Hi Klaus,
> 
> > I have just installed bluez with partial success. I am using a belkin usb adaptor
> > and linux 2.4.25 with the latest bluez installed. The adaptor is recognized and 
> > I am able to connect a Pocket PC (WM2003) to the linux-machine using "Network Access Service". 
> > However pppd is never started and I am not able to transmit any packets from the PPC.
> > 
> > Starting pand,dund etc:
> > Feb 23 18:51:28 mini hcid[5972]: HCI daemon ver 2.4 started
> > Feb 23 18:51:28 mini hcid[5972]: Starting security manager 0
> > Feb 23 18:51:28 mini bluetooth: hcid startup succeeded
> > Feb 23 18:51:28 mini sdpd[5978]: sdpd v1.5 started
> > Feb 23 18:51:28 mini bluetooth: sdpd startup succeeded
> > Feb 23 18:51:34 mini pand[5986]: PAN daemon ver 1.1
> > Feb 23 18:51:34 mini pan: pand startup succeeded
> > Feb 23 18:51:34 mini dund[5990]: DUN daemon ver 1.1
> > Feb 23 18:51:34 mini pan: dund startup succeeded
> > Feb 23 18:52:13 mini hcid[5972]: link_key_request (sba=00:03:C9:2E:6C:F6, dba=00:04:3E:A2:2D:C9)
> > Feb 23 18:52:16 mini pand[5997]: New connection from 00:04:3E:A2:2D:C9 bnep0
> > 
> > And pppd is never started as I suppose it should?
> 
> your new connection is a PAN connection and so you don't need pppd. Set
> up your new bnep0 device with ifconfig etc. and go ahead.
> 
> Regards
> 
> Marcel
> 

Thanks for the quick reply. I tried to set up bnep0:
 
bnep0     Link encap:Ethernet  HWaddr 00:03:C9:2E:6C:F6  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2182 (2.1 Kb)  TX bytes:319 (319.0 b)

But I am still not able to ping anything from the pocket pc (using vxUtils). The pocket pc
has been assigned the ip adr:169.254.121.94 and subnet mask: 255.255.0.0 - probably assigned by
itself because of timeout.

I guess I am missing a step or two in the setup-process?

Best regards
Klaus

  reply	other threads:[~2004-02-24  8:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 21:36 [Bluez-users] dund never activates pppd Klaus Holst
2004-02-23 22:03 ` Marcel Holtmann
2004-02-24  8:53   ` Klaus Holst [this message]
2004-02-24 12:14     ` Marcel Holtmann
2004-02-24 21:54       ` Klaus Holst
2004-02-24 21:59         ` Marcel Holtmann
     [not found]           ` <20040224223520.GA2241@encephalon.dk>
2004-02-24 22:41             ` Marcel Holtmann
2004-02-25 11:38       ` Klaus Holst
2004-02-25 13:34         ` Marcel Holtmann
2004-02-25 18:00           ` Klaus Holst
2004-02-25 18:37             ` Marcel Holtmann

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=20040224085351.GA3782@encephalon.dk \
    --to=klaus@encephalon.dk \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.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