[Xastir] Xastir and Mobilinkd Tnc 1 Bluetooth tnc

Bryan Irwin kf5tot at outlook.com
Fri Nov 7 09:09:11 EST 2014



> Date: Fri, 7 Nov 2014 08:07:11 -0500
> From: kevin at kevinratcliff.com
> To: xastir at lists.xastir.org
> Subject: Re: [Xastir] Xastir and Mobilinkd Tnc 1 Bluetooth tnc

> 
> In 2009 I wrote a wiki article for bluetooth and Ubuntu 9.10:
> http://xastir.org/index.php/HowTo:BluetoothTNC. Some of it probably
> still applies?

I read and followed your wiki article first thing.  It was a great help in getting me as far as I am.  



> You may have run into one of these longstanding bugs:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570692
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1014992
> 
> First I would make sure your user account is in the 'dialout' group on
> your box. My understanding is that this is used to control access to
> serial devices in linux, not just modems. So I think you need to be in
> this group to access /dev/rfcomm0 (which is a bluetooth serial port,
> thus considered a 'modem').

When I run the command 'ls -l /dev/rfcomm*'  it returns 'crw-rw---- 1 root dialout 216, 0 Nov 6 19:38 /dev/rfcomm0

> Exit xastir (or maybe just disable/stop the rfcomm0 interface on the
> xastir Interfaces menu if you don't want to shut down xastir
> completely for some reason).
> 
> Then run your 'sudo rfcomm connect 0' command again if the bluetooth
> link isn't still connected. I think that in theory you wouldn't need
> to run this with sudo but maybe that's what the Ubuntu bugs are about?
When I run sudo rfcomm connect 0 after exiting xastir I get 'Can't create RFCOMM TTY: Address already in use'
I can release the port using sudo rfcomm release 0 and then reconnect to it using connect again
> I didn't read the bug reports very carefully.
> 
> Next I'd try opening /dev/rfcomm0 in a serial terminal program like
> gtkterm or minicom (but don't use sudo for these) to see if you still
> get a permissions error. If you can open the device that way, you
> should be able to open it in xastir.

I've tried minicom and haven't had any luck connecting to rfcomm, I get a permission denied message but I may be doing it incorrectly.  I'm not real sure on minicom.

> If the serial terminal programs still won't open the rfcomm0 device
> after your account is a member of dialout I'm afraid I'm out of ideas
> right now, and I don't have an Ubuntu box to experiment with in front
> of me. I don't think it's an issue with xastir, but rather some sort
> of issue with system permissions.
> 
> > Any help would be greatly appreciated.
> 
Thank you for all your help.  I'm off to read some bug reports now.
BryanKF5TOT 		 	   		  


More information about the Xastir mailing list