Subject: Re: [Bluez-users] Re: pand connection to XP SP2 fails
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
In-Reply-To: <1103113315.4099.118.camel@justakiss>
References: <1103024795.4097.65.camel@justakiss>
	 <1103024932.2143.156.camel@pegasus> <1103025459.4095.68.camel@justakiss>
	 <cpmnro$2p5$1@sea.gmane.org>  <1103036073.4095.101.camel@justakiss>
	 <1103107355.2143.185.camel@pegasus>  <1103110263.4099.109.camel@justakiss>
	 <1103110592.2143.218.camel@pegasus>  <1103113315.4099.118.camel@justakiss>
Content-Type: text/plain
Message-Id: <1103113688.2143.232.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-users-admin@lists.sourceforge.net
Errors-To: bluez-users-admin@lists.sourceforge.net
Reply-To: bluez-users@lists.sourceforge.net
Date: Wed, 15 Dec 2004 13:28:08 +0100

Hi Erwin,

> a simple "pand --connect ..." doesn't work, it results in the 
> "Protocol error(71)" from pand. It seems that pand defaults to remote
> service "NAP", I wonder if there is (or should be) some kind of fallback
> mechanism  that tries GN and PANU as well.

there is no need for a fallback. We should simply use the information
from the SDP search if nothing else is specified on the command line.
Will anyone volunteer to look at this and create a patch?

Regards

Marcel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users