Mailinglist Archive: opensuse-bugs (15135 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=328116

           Summary: Bluetooth DUND not working
           Product: openSUSE 10.3
           Version: RC 1
          Platform: x86-64
        OS/Version: openSUSE 10.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: funtasyspace@xxxxxxxxx
         QAContact: qa@xxxxxxx
                CC: seife@xxxxxxxxxx
          Found By: ---


Created an attachment (id=174560)
 --> (https://bugzilla.novell.com/attachment.cgi?id=174560)
output of hcidump for DUN connection attempt

I can't manage to get the bluetooth dial-up network daemon to work on openSUSE
10.3. I just took my working peer configuration from openSUSE 10.2 and put it
to 

'/etc/ppp/peers/bluetooth-dun'

As before on openSUSE 10.2 I modified '/etc/sysconfig/bluetooth' to start the
DUND automatically with the following parameters: 

DUND_DAEMON_ARGS="--listen --persist call bluetooth-dun"

Next I verified, that dund is running:
# ps ax | grep dund
1865 ?        S<s    0:00 /usr/bin/dund --listen --persist call bluetooth-dun

Now if I try to connect to the dund via my mobile phone or with a second pc and
dund, nothing happens. It seems like dund doesn't react to incoming DUN
requests at all!?
Could it be, that a client tries to lookup the DUN-Service via SDP first? I
recognized, that the SDP daemon (sdpd) is missing (or no longer shiped) with
openSUSE 10.3. [ No SDP deamon -> SDP lookup of DUN-Service fails -> client
doesn't even try to request a DUN connection ]

I attached the output of 'hcidump hci0' on the machine providing the DUN
service, when I try to connect from my mobile phone.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.