<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Tethering in Fedora &#8211; Using your mobile phone with NetworkManager to surf the web</title>
	<atom:link href="http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/</link>
	<description>About open source, education and random other Stuff</description>
	<lastBuildDate>Fri, 09 Jul 2010 23:37:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Peter</title>
		<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/comment-page-1/#comment-50</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 25 Sep 2009 23:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://fetzig.org/?p=42#comment-50</guid>
		<description>In the previous post, I had rebooted before testing. Now after a shutdown and turn on, it is working. :-) How can I create a trigger to start your script when the bluetooth engine detects my phone? Thanks!</description>
		<content:encoded><![CDATA[<p>In the previous post, I had rebooted before testing. Now after a shutdown and turn on, it is working. <img src='http://fetzig.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  How can I create a trigger to start your script when the bluetooth engine detects my phone? Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/comment-page-1/#comment-49</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 25 Sep 2009 22:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://fetzig.org/?p=42#comment-49</guid>
		<description>Hey,

did not work here with my N95 8GB. See:
[root@notepeter tmp]# python dialup-bluetooth.py 
no device specified.  Searching all nearby bluetooth devices for the dialup service
Searching for dialup service on 00:21:FE:C5:49:F9
couldn&#039;t find the dialup service =(

But check Channel 4...

[root@notepeter tmp]# sdptool browse 00:21:FE:C5:49:F9
Browsing 00:21:FE:C5:49:F9 ...
Service Name: AVRCP Target
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10000
Service Class ID List:
  &quot;AV Remote Target&quot; (0x110c)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
    PSM: 23
  &quot;AVCTP&quot; (0x0017)
    uint16: 0x100
Profile Descriptor List:
  &quot;AV Remote&quot; (0x110e)
    Version: 0x0100

Service Name: Audio Source
Service RecHandle: 0x10003
Service Class ID List:
  &quot;Audio Source&quot; (0x110a)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
    PSM: 25
  &quot;AVDTP&quot; (0x0019)
    uint16: 0x100
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;Advanced Audio&quot; (0x110d)
    Version: 0x0100

Service Name: Hands-Free Audio Gateway
Service RecHandle: 0x10004
Service Class ID List:
  &quot;Handsfree Audio Gateway&quot; (0x111f)
  &quot;Generic Audio&quot; (0x1203)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;Handsfree&quot; (0x111e)
    Version: 0x0105

Service Name: Headset Audio Gateway
Service RecHandle: 0x10005
Service Class ID List:
  &quot;Headset Audio Gateway&quot; (0x1112)
  &quot;Generic Audio&quot; (0x1203)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 2
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;Headset&quot; (0x1108)
    Version: 0x0100

Service Name: AVRCP Controller
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10006
Service Class ID List:
  &quot;AV Remote&quot; (0x110e)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
    PSM: 23
  &quot;AVCTP&quot; (0x0017)
    uint16: 0x100
Profile Descriptor List:
  &quot;AV Remote&quot; (0x110e)
    Version: 0x0100

Service Name: SyncMLClient
Service RecHandle: 0x10007
Service Class ID List:
  UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 10
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;&quot; (0x00000002-0000-1000-8000-0002ee000002)
    Version: 0x0100

Service Name: OBEX File Transfer
Service RecHandle: 0x10008
Service Class ID List:
  &quot;OBEX File Transfer&quot; (0x1106)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 11
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;OBEX File Transfer&quot; (0x1106)
    Version: 0x0100

Service Name: Nokia OBEX PC Suite Services
Service RecHandle: 0x10009
Service Class ID List:
  UUID 128: 00005005-0000-1000-8000-0002ee000001
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 12
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;&quot; (0x00005005-0000-1000-8000-0002ee000001)
    Version: 0x0100

Service Name: SyncML DM Client
Service RecHandle: 0x1000a
Service Class ID List:
  UUID 128: 00000004-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 13
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;&quot; (0x00000004-0000-1000-8000-0002ee000002)
    Version: 0x0100

Service Name: Nokia SyncML Server
Service RecHandle: 0x1000c
Service Class ID List:
  UUID 128: 00005601-0000-1000-8000-0002ee000001
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 14
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;&quot; (0x00005601-0000-1000-8000-0002ee000001)
    Version: 0x0100

Service Name: OBEX Object Push
Service RecHandle: 0x1000d
Service Class ID List:
  &quot;OBEX Object Push&quot; (0x1105)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 9
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;OBEX Object Push&quot; (0x1105)
    Version: 0x0100

Service RecHandle: 0x1000e
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 3

Service Name: Dial-Up Networking
Service RecHandle: 0x1000f
Service Class ID List:
  &quot;Dialup Networking&quot; (0x1103)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 4
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;Dialup Networking&quot; (0x1103)
    Version: 0x0100

Service Name: Imaging
Service RecHandle: 0x10010
Service Class ID List:
  &quot;Imaging Responder&quot; (0x111b)
Protocol Descriptor List:
  &quot;L2CAP&quot; (0x0100)
  &quot;RFCOMM&quot; (0x0003)
    Channel: 15
  &quot;OBEX&quot; (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  &quot;Imaging&quot; (0x111a)
    Version: 0x0100

How can I help?</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>did not work here with my N95 8GB. See:<br />
[root@notepeter tmp]# python dialup-bluetooth.py<br />
no device specified.  Searching all nearby bluetooth devices for the dialup service<br />
Searching for dialup service on 00:21:FE:C5:49:F9<br />
couldn&#8217;t find the dialup service =(</p>
<p>But check Channel 4&#8230;</p>
<p>[root@notepeter tmp]# sdptool browse 00:21:FE:C5:49:F9<br />
Browsing 00:21:FE:C5:49:F9 &#8230;<br />
Service Name: AVRCP Target<br />
Service Description: Audio Video Remote Control<br />
Service Provider: Symbian Software Ltd.<br />
Service RecHandle: 0&#215;10000<br />
Service Class ID List:<br />
  &#8220;AV Remote Target&#8221; (0x110c)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
    PSM: 23<br />
  &#8220;AVCTP&#8221; (0&#215;0017)<br />
    uint16: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;AV Remote&#8221; (0x110e)<br />
    Version: 0&#215;0100</p>
<p>Service Name: Audio Source<br />
Service RecHandle: 0&#215;10003<br />
Service Class ID List:<br />
  &#8220;Audio Source&#8221; (0x110a)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
    PSM: 25<br />
  &#8220;AVDTP&#8221; (0&#215;0019)<br />
    uint16: 0&#215;100<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;Advanced Audio&#8221; (0x110d)<br />
    Version: 0&#215;0100</p>
<p>Service Name: Hands-Free Audio Gateway<br />
Service RecHandle: 0&#215;10004<br />
Service Class ID List:<br />
  &#8220;Handsfree Audio Gateway&#8221; (0x111f)<br />
  &#8220;Generic Audio&#8221; (0&#215;1203)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 1<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;Handsfree&#8221; (0x111e)<br />
    Version: 0&#215;0105</p>
<p>Service Name: Headset Audio Gateway<br />
Service RecHandle: 0&#215;10005<br />
Service Class ID List:<br />
  &#8220;Headset Audio Gateway&#8221; (0&#215;1112)<br />
  &#8220;Generic Audio&#8221; (0&#215;1203)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 2<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;Headset&#8221; (0&#215;1108)<br />
    Version: 0&#215;0100</p>
<p>Service Name: AVRCP Controller<br />
Service Description: Audio Video Remote Control<br />
Service Provider: Symbian Software Ltd.<br />
Service RecHandle: 0&#215;10006<br />
Service Class ID List:<br />
  &#8220;AV Remote&#8221; (0x110e)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
    PSM: 23<br />
  &#8220;AVCTP&#8221; (0&#215;0017)<br />
    uint16: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;AV Remote&#8221; (0x110e)<br />
    Version: 0&#215;0100</p>
<p>Service Name: SyncMLClient<br />
Service RecHandle: 0&#215;10007<br />
Service Class ID List:<br />
  UUID 128: 00000002-0000-1000-8000-0002ee000002<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 10<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;&#8221; (0&#215;00000002-0000-1000-8000-0002ee000002)<br />
    Version: 0&#215;0100</p>
<p>Service Name: OBEX File Transfer<br />
Service RecHandle: 0&#215;10008<br />
Service Class ID List:<br />
  &#8220;OBEX File Transfer&#8221; (0&#215;1106)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 11<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;OBEX File Transfer&#8221; (0&#215;1106)<br />
    Version: 0&#215;0100</p>
<p>Service Name: Nokia OBEX PC Suite Services<br />
Service RecHandle: 0&#215;10009<br />
Service Class ID List:<br />
  UUID 128: 00005005-0000-1000-8000-0002ee000001<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 12<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;&#8221; (0&#215;00005005-0000-1000-8000-0002ee000001)<br />
    Version: 0&#215;0100</p>
<p>Service Name: SyncML DM Client<br />
Service RecHandle: 0x1000a<br />
Service Class ID List:<br />
  UUID 128: 00000004-0000-1000-8000-0002ee000002<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 13<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;&#8221; (0&#215;00000004-0000-1000-8000-0002ee000002)<br />
    Version: 0&#215;0100</p>
<p>Service Name: Nokia SyncML Server<br />
Service RecHandle: 0x1000c<br />
Service Class ID List:<br />
  UUID 128: 00005601-0000-1000-8000-0002ee000001<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 14<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;&#8221; (0&#215;00005601-0000-1000-8000-0002ee000001)<br />
    Version: 0&#215;0100</p>
<p>Service Name: OBEX Object Push<br />
Service RecHandle: 0x1000d<br />
Service Class ID List:<br />
  &#8220;OBEX Object Push&#8221; (0&#215;1105)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 9<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;OBEX Object Push&#8221; (0&#215;1105)<br />
    Version: 0&#215;0100</p>
<p>Service RecHandle: 0x1000e<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 3</p>
<p>Service Name: Dial-Up Networking<br />
Service RecHandle: 0x1000f<br />
Service Class ID List:<br />
  &#8220;Dialup Networking&#8221; (0&#215;1103)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 4<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;Dialup Networking&#8221; (0&#215;1103)<br />
    Version: 0&#215;0100</p>
<p>Service Name: Imaging<br />
Service RecHandle: 0&#215;10010<br />
Service Class ID List:<br />
  &#8220;Imaging Responder&#8221; (0x111b)<br />
Protocol Descriptor List:<br />
  &#8220;L2CAP&#8221; (0&#215;0100)<br />
  &#8220;RFCOMM&#8221; (0&#215;0003)<br />
    Channel: 15<br />
  &#8220;OBEX&#8221; (0&#215;0008)<br />
Language Base Attr List:<br />
  code_ISO639: 0x454e<br />
  encoding:    0x6a<br />
  base_offset: 0&#215;100<br />
Profile Descriptor List:<br />
  &#8220;Imaging&#8221; (0x111a)<br />
    Version: 0&#215;0100</p>
<p>How can I help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mehrdad</title>
		<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/comment-page-1/#comment-47</link>
		<dc:creator>mehrdad</dc:creator>
		<pubDate>Thu, 17 Sep 2009 04:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://fetzig.org/?p=42#comment-47</guid>
		<description>Dear Nushio
I have a Problem with NetworkManager on Fedora 11 , i installed Blueman and also Bluez but Can`t connect to a PAN true my OMINA SmartPhone but i did connected with a Windows XP when i had on my laptop, please tell me how to?
I add my phone with the blueman and then click the &quot;Network Access&quot; and blueman says that &quot;You are connected to phone...&quot; but nothing happens to NetworkManager but I expect it to recognize a Network . What is my problem? please answer me in my email: 
m.mirsamie @ gmail .com
Tanx</description>
		<content:encoded><![CDATA[<p>Dear Nushio<br />
I have a Problem with NetworkManager on Fedora 11 , i installed Blueman and also Bluez but Can`t connect to a PAN true my OMINA SmartPhone but i did connected with a Windows XP when i had on my laptop, please tell me how to?<br />
I add my phone with the blueman and then click the &#8220;Network Access&#8221; and blueman says that &#8220;You are connected to phone&#8230;&#8221; but nothing happens to NetworkManager but I expect it to recognize a Network . What is my problem? please answer me in my email:<br />
m.mirsamie @ gmail .com<br />
Tanx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Felix Kaechele</title>
		<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/comment-page-1/#comment-44</link>
		<dc:creator>Felix Kaechele</dc:creator>
		<pubDate>Sat, 08 Aug 2009 07:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://fetzig.org/?p=42#comment-44</guid>
		<description>Well I have an option to approve my computer within my bluetooth settings. Thus it can connect without asking me to approve the connection. And if it is connected it shows a little icon.
However I don&#039;t use this method anymore because I bought a real mobile broadband ExpressCard for my Laptop.</description>
		<content:encoded><![CDATA[<p>Well I have an option to approve my computer within my bluetooth settings. Thus it can connect without asking me to approve the connection. And if it is connected it shows a little icon.<br />
However I don&#8217;t use this method anymore because I bought a real mobile broadband ExpressCard for my Laptop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily </title>
		<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/comment-page-1/#comment-43</link>
		<dc:creator>Emily </dc:creator>
		<pubDate>Sat, 08 Aug 2009 07:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://fetzig.org/?p=42#comment-43</guid>
		<description>Sounds like more on the Bluetooth side, of course. Does your phone do
anything when NM tries to bring the connection up? Mine usually asks me
whether I want to allow the computer to connect, or it&#039;ll show an icon
saying a computer is connected. In any case, this is exactly why this
method is a hack, and why we want the real solution.</description>
		<content:encoded><![CDATA[<p>Sounds like more on the Bluetooth side, of course. Does your phone do<br />
anything when NM tries to bring the connection up? Mine usually asks me<br />
whether I want to allow the computer to connect, or it&#8217;ll show an icon<br />
saying a computer is connected. In any case, this is exactly why this<br />
method is a hack, and why we want the real solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nushio</title>
		<link>http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/comment-page-1/#comment-40</link>
		<dc:creator>Nushio</dc:creator>
		<pubDate>Sat, 04 Jul 2009 18:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://fetzig.org/?p=42#comment-40</guid>
		<description>I can confirm that Blueman works for bluetooth tethering. 

You can install it from Fedora 10 and 11, its currently in updates-testing and should land regular packages soon. 

If you had any issues with blueman, let me know so I can report them back to the package maintainer. 

Thanks.</description>
		<content:encoded><![CDATA[<p>I can confirm that Blueman works for bluetooth tethering. </p>
<p>You can install it from Fedora 10 and 11, its currently in updates-testing and should land regular packages soon. </p>
<p>If you had any issues with blueman, let me know so I can report them back to the package maintainer. </p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
