From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] [PATCH] pand/main.c, restore signals for dev-up script From: Marcel Holtmann To: James Cameron Cc: BlueZ Mailing List In-Reply-To: <20040628101927.GC8871@hp.com> References: <20040627133325.GA23996@hp.com> <1088366793.3774.70.camel@pegasus> <20040627233437.GD28828@hp.com> <1088408656.3774.136.camel@pegasus> <20040628085356.GA8871@hp.com> <1088413518.3774.167.camel@pegasus> <20040628095541.GB8871@hp.com> <1088417629.3774.177.camel@pegasus> <20040628101927.GC8871@hp.com> Content-Type: text/plain Message-Id: <1088419197.3774.183.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 28 Jun 2004 12:39:57 +0200 Hi James, > > > But dev-up is given the peer's Bluetooth device address. net.agent is not > > > given this. Can it be determined from just the interface name? I could > > > do a "hcitool con" if I knew what the right hci device number was, but > > > it seems sensible to have the dev-up script provide the knowledge. > > > > it is the same as the ethernet address of the bnep0 interfaces. > > No, it isn't. You're thinking of the local device address. I'm talking > about the peer's address, which is passed to dev-up by pand. > > While the bnep0 interface on the peer has the address, that doesn't > help the local host get it. sorry. I mixed them up. The remote address is available via "pand -l". Regards Marcel ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel