Version : 1.1
Copyright © 2002-2003 Olivier Berger (oberger [AT/arobase] ouvaton [DOT/point] org)
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; without any Invariant Sections, without any Front-Cover Texts, and without any Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License" (see GNU Free Documentation License).
Abstract
This HOWTO will describe the configuration of a GPRS network connection, both on Windows 2000, GNU/Linux systems, and Palm OS PDA, when using a french Orange GPRS option ("Option PDA/PC") and where the connection uses a Philips Fisio 820 or a Sony-Ericsson mobile phone connected via BlueTooth to the PC or PDA.
Table of Contents
- 1. A bit of history
- 2. About the hardware involved
- 3. Subscribing to the GPRS option at Orange France
- 4. Setting-up for Windows 2000
- 5. Setting-up for Debian GNU/Linux
- 6. Setting-up for Palm-OS on a Sony Clié, with the Sony Bluetooth memorystick
- 7. Miscelleanous
- 8. Reference
- 9. About this document
- GNU Free Documentation License
I had lost my old mobile phone (Siemens S35i) while going to work in the train... Having to buy a new one, I chose to step to the mobile world by choosing to buy a new bluetooth equipped mobile. I chose the Philips Fisio 820, although the Sony-Ericson T38 looked much nicer (IrDa + bluetooth) but this one was too expensive.
One year later, I have again lost (or was robbed) the Fisio, which is not so bad, after all, since this device was not the best I've come to see... and I finally bought a Sony-Ericsson T68i, which after some time, has become much more affordable. I expect it to be much more reliable too. I hope it's OK now for some time... I'm tired to have to rewrite this page each time ;)
The idea is to be ultimately able to connect to the net (send mails, check something onto a web page) with my Clié T625C (nice hires colour screen ;) while going to work on the long 1h train trip away from any net access point. And also to be able to get to the net with my laptop, which is always around when I'm there too ;)
I first tried to get the bluetooth connection running on my laptop. The information was a bit difficult to find, although I managed to connect to my ISP (club-internet) with the bluez stack (recompiled). But that first connection had two drawbacks : first it was slow (only GSM / CSD at 9600 bps) to be usefull anyhow; second it costed me like a regular call, which dissuades to use the connection that much.
I just looked for ways to connect at higher speed with the new GPRS thing... but I then figured out that I had to buy a separate contract with Orange. Ok, I subscribed to the Orange "option PDA/PC"... with other providers or Orange outside of France, your mileage may vary. But then the problems start to add : there was no option for using bluetooth (for any mobile) in the "connection kit" provided by orange (for Windows, of course). And no docs too, of course... a crappy piece of undocumented software is supposed to be much more convenient, of course :(. And the only option available for the Fisio 820 was the USB connection... but at that time, Philips had not started shipping these USB cables for Fisio 820. So I was in a deadlock situation. I then contacted the hotline, which promises to call me back to help solve the problem.
Meanwhile, I tried to gather information on the net to be able to connect manualy both on windows and if possible on GNU/Linux. After many tries, I finally managed to make it, just half an hour before the hotline would finally call me back. I had guessed the right parameters, so everything finally got fine.
One thing is sure, the guys at Orange don't want to publically share their information on the web, and prefer to call people back. Don't inderstand such a strategy, but anyway, who needs them, after all ? ;)
Anyway, I seem to be the first, at the time of first writing of this piece, to have tried to publically document the whole stuff of using Fisio 820 with bluetooth, GPRS on Orange.fr network, so I think this helped some people ;)
I've just bought this new phone, a T68i by Sony-Ericsson, as a replacement for the Fisio. It has two communication devices, that may be used to connect to other devices :
an infrared cell
a bluetooth chip
Now, although Bluetooth support is a bit more widespread than a year ago, still sometimes InfraRed is more easily supported by various tools. Good, the T68i has both
As an example, the tools (running under windows only, of course) shipped with the T68i don't seem to be supporting bluetooth very well from the few experiments I've done.
But there seems to be much interest in bluetooth anyway, and many applications for GNU/Linux seem to be coming these times. And as this phone is one of the standards, I expect to see more uses possible than with the Fisio.
Tell me if you have comments or questions about that configuration steps. I'll be glad to improve this document, although having lost the Fisio, I won't be able any longer to provide much help for this one, I'm afraid.
The Philips Fisio 820 mobile phone embeds a BlueTooth cell.
Here are some details of available services on this bluetooth equipment (log of the commands launched on GNU/Linux) :
liberty:~# hcitool info 00:08:C6:13:6C:4A
Requesting information ...
BD Address: 00:08:C6:13:6C:4A
Device Name: Fisio 820 Olberger
LMP Version: 1.1 (0x1) LMP Subversion: 0x8b40
Manufacturer: Ericsson Mobile Comunications (0)
Features: 0xff 0xf9 0x01 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park mode> <SCO link> <HV2 packets> <HV3 packets>
<u-law log> <A-law log> <CVSD>
liberty:~# sdptool search --service=DUN 00:08:C6:13:6C:4A
Searching for DUN on 00:08:C6:13:6C:4A ...
Service Name: Dial-up networking
Service RecHandle: 0x10008
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 2
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
liberty:~# sdptool browse 00:08:C6:13:6C:4A
Browsing 00:08:C6:13:6C:4A ...
Service RecHandle: 0x10000
Service Name: Serial Port
Service RecHandle: 0x10001
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 5
Service Name: Dial-up networking
Service RecHandle: 0x10002
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 2
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: OBEX Object Push
Service RecHandle: 0x10003
Service Class ID List:
"Obex Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 4
"OBEX" (0x0008)
Profile Descriptor List:
"Obex Object Push" (0x1105)
Version: 0x0100
Service Name: Voice gateway
Service RecHandle: 0x10004
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 1
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Fax
Service RecHandle: 0x10005
Service Class ID List:
"Fax" (0x1111)
"Generic Telephony" (0x1204)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 6
Profile Descriptor List:
"Fax" (0x1111)
Version: 0x0100
The Fisio 820 phone was factory-configured for GPRS on orange.fr (which can be re-configured in one of the empty GPRS accounts slots in case yours wouldn't be. See for details of the parameters). The Wap connection over GPRS should work on the mobile. There is a flag in the display (under the link quality bars) reading "GPRS" whenever you have access to it.
I have a Sony-Ericsson T68i mobile phone, which embeds a BlueTooth cell and an InfraRed cell.
Here are some details of available services on this bluetooth equipment (log of the commands launched on GNU/Linux) :
olivier@gnou:~$ hcitool scan
Scanning ...
00:0A:D9:90:88:0A T68i
gnou:~# hcitool info 00:0A:D9:90:88:0A
Requesting information ...
BD Address: 00:0A:D9:90:88:0A
Device Name: T68i
LMP Version: 1.1 (0x1) LMP Subversion: 0x400
Manufacturer: Ericsson Mobile Comunications (0)
Features: 0x04 0xea 0x31 0x00
<encryption> <RSSI> <SCO link> <HV3 packets>
<u-law log> <A-law log> <CVSD>
gnou:~# sdptool search DUN 00:0A:D9:90:88:0A
Inquiring ...
Searching for DUN on 00:0A:D9:90:88:0A ...
Service Name: Dial-up Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
gnou:~# sdptool browse 00:0A:D9:90:88:0A
Browsing 00:0A:D9:90:88:0A ...
Service Name: Dial-up Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Fax
Service RecHandle: 0x10001
Service Class ID List:
"Fax" (0x1111)
"Generic Telephony" (0x1204)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Profile Descriptor List:
"Fax" (0x1111)
Version: 0x0100
Service Name: Voice gateway
Service RecHandle: 0x10002
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Serial Port 1
Service RecHandle: 0x10003
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Service Name: Serial Port 2
Service RecHandle: 0x10004
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
Service Name: OBEX Object Push
Service RecHandle: 0x10005
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: IrMC Synchronization
Service RecHandle: 0x10006
Service Class ID List:
"IrMCSync" (0x1104)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 11
"OBEX" (0x0008)
Profile Descriptor List:
"IrMCSync" (0x1104)
Version: 0x0100
Service Name: Voice gateway
Service RecHandle: 0x1000f
Service Class ID List:
"" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 6
Profile Descriptor List:
"" (0x111e)
Version: 0x0100
The T68i phone was "factory-configured" for GPRS on orange.fr (which can be re-configured in one of the empty GPRS accounts slots in case yours wouldn't be. See for details of the parameters). The Wap connection over GPRS should work on the mobile. There is a flag like a triangle in the display (over the link quality bars) indicating whenever you have access to GPRS.
Of course you need some Bluetooth equipment on the PC too. I've tried two of them :
TDK USB adapter (works with Windows 2000 and GNU/Linux)
Toshiba PCMCIA card (only works with Windows 2000), which is made by DigiAnswer, and rebranded OEM by Toshiba.
The hardware is rather standard and operates (in theory) with any bluetooth equipment.
I've got a Sony Clié T625C (kind of the same as the T615C, I think, which was sold on the french market only (maybe).
The Blueetooth adapter is a PEGA-MSB1 bluetooth memorystick-based adapter. At the time I bought it, it was only sold on the Japanese market, so I ordered it through a Hong-Kong based company on the Internet. Fortunately, it apparently works allright on the European Clié. At the time of reading, it may be available in other countries too.
At the time of writing, the GPRS isn't activated to every standard customers of Orange in France. You need to subscribe to the "option PDA/PC" contract to activate it.
You should have already configured valid GPRS "accounts" on the phone, but in case you'd need to reconfigure them, here are the parameters.
Thanks to http://www.visanetamoi.com/ for the details. Here is the procedure, in french, sorry :
* Configuration WAP ORANGE
Sélectionnez l' icône Services opérateur puis appuyez sur la touche de validation
Sélectionnez l' icône Wap puis appuyez sur la touche de validation
Sélectionnez l' icône Réglages puis appuyez sur la touche de validation
Sélectionnez l' icône Paramètrages puis appuyez sur la touche de validation
Sélectionnez un profil vide Ex : wap2 puis appuyez sur la touche de validation
Sélectionnez l' icône Changer puis appuyez sur la touche de validation
Sélectionnez l' icône Modifier nom puis appuyez sur la touche de validation
Saisissez le nom de votre profil : orange puis appuyez sur la touche OK
Sélectionnez l' icône Réglages GPRS puis appuyez sur la touche de validation
Sélectionnez l' icône Login puis appuyez sur la touche de validation
Saisissez : orange puis appuyez sur la touche OK
Sélectionnez l' icône Mot de passe puis appuyez sur la touche de validation
Saisissez : orange puis appuyez sur la touche OK
Sélectionnez l' icône Passerelle puis appuyez sur la touche de validation
Sélectionnez l' icône Adresse IP puis appuyez sur la touche de validation
Effacez les quatres 0 en appuyant successivement sur la touche C
Saisissez :192.168.010.100 puis appuyez sur la touche OK
Sélectionnez l' icône Port puis appuyez sur la touche de validation
Vélifiez que le paramètre 9201 est présent sinon modifiez le puis appuyez sur la touche de validation
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône APN puis appuyez sur la touche de validation
Saisissez : orange.fr puis appuyez sur la touche OK
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône Réglages GSM puis appuyez sur la touche de validation
Sélectionnez l' icône Login puis appuyez sur la touche de validation
Saisissez : orange puis appuyez sur la touche OK
Sélectionnez l' icône Mot de passe puis appuyez sur la touche de validation
Saisissez : orange puis appuyez sur la touche OK
Sélectionnez l' icône Passerelle puis appuyez sur la touche de validation
Sélectionnez l' icône Adresse IP puis appuyez sur la touche de validation
Effacez les quatres 0 en appuyant successivement sur la touche C
Saisissez :192.168.010.100 puis appuyez sur la touche OK
Sélectionnez l' icône Port puis appuyez sur la touche de validation
Vérifiez que le paramètre 9201 est présent sinon modifiez le puis appuyez sur la touche de validation
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône Numéro téléphone puis appuyez sur la touche de validation
Sélectionnez l' icône Numéro RNIS puis appuyez sur la touche de validation
Saisissez : +33674501100 (or +33674501200) puis appuyez sur la touche OK
Sélectionnez l' icône Temps d'inactivité puis appuyez sur la touche de validation
Effacez la valeur et saisissez 120 puis appuyez sur la touche OK
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône Réseau puis appuyez sur la touche de validation
Sélectionnez l' icône Réseau GPRS d'abord puis appuyez sur la touche de validation
Sélectionnez l' icône Page d'accueil puis appuyez sur la touche de validation
Saisissez : http://wap.orange.fr puis appuyez sur la touche OK
Appuyez deux fois sur la touche C pour revenir à l'écran Paramètrages
Sélectionnez orange et appuyez sur la touche Activer si vous voulez mettre ce profil par défaut
Appuyez deux fois sur la touche C pour revenir à l'écran Wap
Sélectionnez l' icône Page d'accueil puis appuyez sur la touche de validation
La connexion à Orange est lancée
* Configuration MIB
Appuyez sur la touche Menu
Sélectionnez l' icône Services opérateur puis appuyez sur la touche de validation
Sélectionnez l' icône Wap puis appuyez sur la touche de validation
Sélectionnez l' icône Réglages puis appuyez sur la touche de validation
Sélectionnez l' icône Paramètrages puis appuyez sur la touche de validation
Sélectionnez un profil vide Ex : wap3 puis appuyez sur la touche de validation
Sélectionnez l' icône Changer puis appuyez sur la touche de validation
Sélectionnez l' icône Modifier nom puis appuyez sur la touche de validation
Saisissez le nom de votre profil : mib puis appuyez sur la touche OK
Sélectionnez l' icône Réglages GPRS puis appuyez sur la touche de validation
Sélectionnez l' icône Login puis appuyez sur la touche de validation
Saisissez : mportail puis appuyez sur la touche OK
Sélectionnez l' icône Mot de passe puis appuyez sur la touche de validation
Saisissez : mib puis appuyez sur la touche OK
Sélectionnez l' icône Passerelle puis appuyez sur la touche de validation
Sélectionnez l' icône Adresse IP puis appuyez sur la touche de validation
Effacez les quatres 0 en appuyant successivement sur la touche C
Saisissez :172.016.002.007 puis appuyez sur la touche OK
Sélectionnez l' icône Port puis appuyez sur la touche de validation
Vérifiez que le paramètre 9201 est présent sinon modifiez le puis appuyez sur la touche de validation
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône APN puis appuyez sur la touche de validation
Saisissez : orange-mib puis appuyez sur la touche OK
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône Réglages GSM puis appuyez sur la touche de validation
Sélectionnez l' icône Login puis appuyez sur la touche de validation
Saisissez : mportail puis appuyez sur la touche OK
Sélectionnez l' icône Mot de passe puis appuyez sur la touche de validation
Saisissez : mib puis appuyez sur la touche OK
Sélectionnez l' icône Passerelle puis appuyez sur la touche de validation
Sélectionnez l' icône Adresse IP puis appuyez sur la touche de validation
Effacez les quatres 0 en appuyant successivement sur la touche C
Saisissez :172.016.002.007 puis appuyez sur la touche OK
Sélectionnez l' icône Port puis appuyez sur la touche de validation
Vérifiez que le paramètre 9201 est présent sinon modifiez le puis appuyez sur la touche de validation
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône Numéro téléphone puis appuyez sur la touche de validation
Sélectionnez l' icône Numéro RNIS puis appuyez sur la touche de validation
Saisissez : +33674501800 puis appuyez sur la touche OK
Sélectionnez l' icône Temps d'inactivité puis appuyez sur la touche de validation
Effacez la valeur et saisissez 120 puis appuyez sur la touche OK
Appuyez sur la touche C pour revenir en arrière
Sélectionnez l' icône Réseau puis appuyez sur la touche de validation
Sélectionnez l' icône Réseau GPRS d'abord puis appuyez sur la touche de validation
Sélectionnez l' icône Page d'accueil puis appuyez sur la touche de validation
Saisissez : http://accueil.orangemib.net puis appuyez sur la touche OK
Appuyez deux fois sur la touche C pour revenir à l'écran Paramètrages
Sélectionnez mib et appuyez sur la touche Activé si vous voulez mettre ce profil par défaut
Appuyez deux fois sur la touche C pour revenir à l'écran Wap
Sélectionnez l' icône Page d'accueil puis appuyez sur la touche de validation
La connexion au MIB est lancé Before your Bluetooth devices can communicate, you need to "pair" the devices. First initiate the discovery process on the phone, than search for available Bluetooth devices in the BlueTooth neighbourhood of the PC. When the device get discovered by the other one, you get prompted on the mobile for a PIN (Personal Identification Number). Type a 4 digit number (for example), then validate on the phone, then immediatly type the same PIN on the PC. The devices should now be paired. You may then browse the available services on the phone.
The Fisio 820 will have the following services available:
Serial Port
Fax
Dial-up Networking
Business card
(in french) "Périphérique distant"
Double-click the Dial-up Networking icon
You should see the display change on the Fisio 820, which indicates it has been connected to the computer in Dial-Up Network mode, acting then as a GSM/GPRS modem.
A new virtual serial port was activated (COM 7 in my setup) which corresponds to this Dial-Up Networking bluetooth connection. This serial port will be used as the connection to a modem, to establish Windows dial-up connections to the provider.
You may then test the connection by configuring a regular dial-up connection to your ISP, over GSM.
Just setup a standard Windows Dial-up Network connection just as if you were using some ordinary modem (you will have configured first on that COM 7 port).
For instance, the orange.fr parameters for such a GSM connection used to be :
Phone number : +33 6 74 50 12 00
Login: orange
Password: orange
Internet IP address : allocated by server
DNS: allocated by server (or may work with 10.163.108.209)
You should get access to the net with a VERY slow (9600 bps) connection... and a costly one, too.
You will have to create some special modem connected to the virtual serial port of the BlueTooth connection, and provide specific parameters, in order to get access to the phone's GPRS configuration.
You'll have to create a new modem :
Install new Modem
Select Phone and Modem Options in the Control Panel
Select Modems
Select Add
Select Don't detect my modem ; I will select it from a list, then Next
Select unknown modem with 57600 bps rate
Select the port corresponding to the bluetooth Dial-Up Networking connection (COM 7), press Next, then Yes , then Finish
Select Properties
Select General and select 57600 as the Maximum Port Speed
Select Advanced and enter the GPRS access number : AT+cgdcont=1, "IP", "orange.fr","" press OK twice
The last additional parameters are used to provide access to the orange.fr GPRS APN, which enables access to (almost full) IP networking on french orange network.
Now the virtual modem corresponding to the orange.fr GPRS connection has been setup, you will need to create a Windows DIal-Up Networking connection, to be able to establish a PPP connection over it.
Select Network and Dial-Up Connections, select Make New Connection, click Next
Tick Dial-up to private network, then Next
Tick the modem you created, then Next
Enter the GPRS access number as follow : *99***1#, then Next
Tick For all users, then Next
Enter a name for the connection e.g. Fisio820_GPRS_Orange, then Finish
The Dial-up window Connect Fisio820_GPRS_Orange will appear on your computer screen, tick Properties
Select Networking, double click on Internet Protocol (TCP/IP)
Either Tick "Get automatically DNS addresses" or "Use the following DNS server addresses" and enter : Preferred DNS server : 194.51.3.56 Alternate DNS server : 194.51.3.76 Then OK twice
Select Dial after connectiong your Fisio 820 in dial-mode to your PC.
Type the following connection elements :
Login: orange
Password: orange
Then tick remember the password, then launch the connection.
At the time of writing, the bluetooth stack implemented in the kernel on the Debian stable distribution may not contain a recent bluetooth stack. Thus you will remove every bluetooth support from your kernel, and install the bluez stack from the source. Everything will be found more or less at http://bluez.sourceforge.net.
If you're running a more recent distribution, like Debian testing/unstable, you'll only need to install a set of Debian packages.
You'll need to follow instructions from the bluez documentation.
You'll also need the sdp and other tools. My current installation hosts :
bluez-kernel-2.1.tar.gz
bluez-libs-2.0.tar.gz
bluez-utils-2.0-pre12.tar.gz
bluez-sdp-0.7.tar.gz
bluez-hcidump-1.3.tar.gz
You will also need the Bluetooth rfcomm tool from Marcel Holtmann (http://www.holtmann.org/linux/bluetooth/rfcomm.html)
Test that you can launch the bluepin tool without any error (missing Python-Gtk bindings for instance).
Now you need to have proper modules loaded in the kernel and the hcid daemon running. On my machine (with the TDK USB dongle), I do the following steps to enable the bluetooth interface (hci0) :
modprobe hci_usb
modprobe l2cap
/etc/init.d/bluetooth start
Then I can see the hci0 interface up :
liberty:~# hciconfig hci0: Type: USB BD Address: 00:80:98:24:E0:C2 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:286 acl:6 sco:0 events:23 errors:0 TX bytes:446 acl:3 sco:0 commands:16 errors:0
Debian packages for the Bluez stack and utilities are becoming more and more stable.
Here is a list of installed packages at the time of writing, but this may change in the future : bluez-sdp, bluez-utils, bluez-pan and bluez-hcidump.
Before your Bluetooth devices can communicate, you need to "pair" the devices. First initiate the discovery process on the phone, then launch a discovery through one of the l2ping or hcitool scan tools.
Typical sequence could be to launch hcitool scan, which will report the Fiso 820 bluetooth BADDR (mine is 00:08:C6:13:6C:4A), then you may use sdptool browse BADDR. At that time, the devices should discover each-other.
You will get prompted on the mobile for a PIN (Personal Identification Number). Type a 4 digit number, then validate on the phone. You should then see a popup window appear on the PC, in which you'll type the same PIN. The devices should now be paired.
You may also edit
/etc/bluetooth/pin file to set that PIN
on the PC side.
You may now test the connection with l2ping.
You will need to setup an RFCOMM connection between both devices (serial emulation protocol which will be used to do dial-up networking over Blueetooth).
As you can see if you type "sdptool browse [baddr]", the channel 2 is used for Dial Up Networking on the Fisio 820 :
liberty:~# sdptool browse 00:08:C6:13:6C:4A
Browsing 00:08:C6:13:6C:4A ...
Service RecHandle: 0x10000
[SNIP]
Service Name: Dial-up networking
Service RecHandle: 0x10002
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel/Port: 2
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
[SNIP]
On the T68i, it's on channel 1.
You may then launch rfcomm to establish a virtual serial connection which will be available on the /dev/rfcomm0 port :
liberty:~# rfcomm connect 0 00:08:C6:13:6C:4A 2 Connected /dev/refcomm0 to 00:08:C6:13:6C:4A on channel 2
The serial connection should be established, and the phone's display should reflect connection to the PC.
You may then test the connection by configuring a regular dial-up connection to your ISP, over GSM.
Just setup a standard PPP connection (with pppconfig for instance) just as if you were using some ordinary modem (although connected to the virtual serial port /dev/ttyU0 just initiated before).
For instance, the orange.fr parameters for such a GSM connection are :
Phone number : +33 6 74 50 12 00
Login: orange
Password: orange
Internet IP address : allocated by server
DNS: allocated by server (or may work with 10.163.108.209)
You should get access to the net with a VERY slow (9600 bps) connection, which is also very expensive.
I will present one way to establish a PPP connection to the GPRS account of orange.fr configured in the T68i, using adapted versions of the scripts of Mikko Rapeli available here : http://www.ee.oulu.fi/~mcfrisk/linux/gprs/
To enable the PPP connection over GPRS, just type : pppd file /etc/ppp/gprs
# File: # gprs # # Description: # This file holds the serial cable and IrDA pppd options for GPRS # phones noauth # To give some debug info debug # Serial device to which terminal is connected; # with serial port (COM1 in Windows) use /dev/ttyS0 # and with IrDA use /dev/ircomm0. #/dev/ircomm0 # IrDA #/dev/ttyS0 # serial cable /dev/rfcomm0 # Serial port line speed 115200 # Hardware flow control needs to be used with serial cable. # With IrDA it should be disabled with nocrtscts option. #crtscts # serial cable nocrtscts # IrDA # To keep pppd on the terminal nodetach # Connect script connect /etc/ppp/gprs-connect-chat # IP addresses: # - accept peers idea of our local address and set address peer as # 10.0.0.1 # (any address would do, since IPCP gives 0.0.0.0 to it) # - if you use the 10. network at home or something and pppd rejects # it, # change the address to something else #:10.0.0.1 :192.200.1.21 # pppd must not propose any IP address to the peer! noipdefault # Accept peers idea of our local address ipcp-accept-local # Ignore carrier detect signal from the modem local # No ppp compression novj novjccomp # Disconnect script disconnect /etc/ppp/gprs-disconnect-chat # Add default route defaultroute
#!/bin/sh
#
# File:
# chat-gprs-connect
#
# Description:
# chat script to open Sonera GPRS service with GPRS phones. If ppp
# negotiation stalls, try restarting the phone. To try with other GPRS
# operator setting, change the PDP contex setting. The settings work
#with
# all Ericsson models, but Nokia 8310 does not suppor QoS parameters
#with
# AT commands, so just delete those lines and it'll work.
#
# Set PDP context CID=1, protocol=IP, APN=internet:
# AT+CGDCONT=1,"IP","internet","",0,0
#
# Set CID=1 QoS requirements from the network, not supported by 8310:
# AT+CGQREQ=1,0,0,0,0,0
#
# Set CID=1 minimum acceptable QoS parameters, not supported by 8310:
# AT+CGQMIN=1,0,0,0,0,0
#
# 'Call' CID=1 (activate PDP context one, perform GPRS attach):
# ATD*99***1#
#
# The actual chat script:
exec chat \
TIMEOUT 5 \
ECHO ON \
ABORT '\nBUSY\r' \
ABORT '\nERROR\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rAT \
TIMEOUT 12 \
SAY "Press CTRL-C to close the connection at any
#stage!" \
SAY "\ndefining PDP context...\n" \
OK ATE1 \
OK 'AT+cgdcont=1,"IP","orange.fr","",0,0' \
OK ATD*99***1# \
TIMEOUT 22 \
SAY "\nwaiting for connect...\n" \
CONNECT "" \
SAY "\nConnected." \
SAY "\nIf the following ppp negotiations fail,\n"
#\
SAY "try restarting the phone.\n"
# File: # gprs # # Description: # This file holds the serial cable and IrDA pppd options for GPRS phones hide-password noauth # To give some debug info debug # Serial device to which terminal is connected; # with serial port (COM1 in Windows) use /dev/ttyS0 # and with IrDA use /dev/ircomm0. #/dev/ircomm0 # IrDA #/dev/ttyS0 # serial cable /dev/rfcomm0 # Serial port line speed 115200 # Hardware flow control needs to be used with serial cable. # With IrDA it should be disabled with nocrtscts option. #crtscts # serial cable nocrtscts # IrDA # To keep pppd on the terminal nodetach # Connect script #connect "/usr/sbin/chat -v -f /etc/ppp/gprs-connect-chat" connect /etc/ppp/gprs-connect-chat # IP addresses: # - accept peers idea of our local address and set address peer as 10.0.0.1 # (any address would do, since IPCP gives 0.0.0.0 to it) # - if you use the 10. network at home or something and pppd rejects it, # change the address to something else #:10.0.0.1 #:192.200.1.21 # pppd must not propose any IP address to the peer! noipdefault # Accept peers idea of our local address ipcp-accept-local # Ignore carrier detect signal from the modem local # No ppp compression novj novjccomp # Disconnect script #disconnect "/usr/sbin/chat -v -f /etc/ppp/gprs-disconnect-chat" disconnect /etc/ppp/gprs-disconnect-chat # Add default route defaultroute user "orange" remotename gprs ipparam gprs usepeerdns lcp-echo-failure 0
#!/bin/sh
#
# File:
# chat-gprs-connect
#
# Description:
# chat script to open Sonera GPRS service with GPRS phones. If ppp
# negotiation stalls, try restarting the phone. To try with other GPRS
# operator setting, change the PDP contex setting. The settings work with
# all Ericsson models, but Nokia 8310 does not suppor QoS parameters with
# AT commands, so just delete those lines and it'll work.
#
# Set PDP context CID=1, protocol=IP, APN=internet:
# AT+CGDCONT=1,"IP","internet","",0,0
#
# Set CID=1 QoS requirements from the network, not supported by 8310:
# AT+CGQREQ=1,0,0,0,0,0
#
# Set CID=1 minimum acceptable QoS parameters, not supported by 8310:
# AT+CGQMIN=1,0,0,0,0,0
#
# 'Call' CID=1 (activate PDP context one, perform GPRS attach):
# ATD*99***1#
#
# The actual chat script:
exec chat \
TIMEOUT 5 \
ECHO ON \
ABORT '\nBUSY\r' \
ABORT '\nERROR\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rATZ \
TIMEOUT 12 \
SAY "Press CTRL-C to close the connection at any stage!" \
SAY "\ndefining PDP context...\n" \
OK 'AT&F' \
OK 'ATV1E0S0=0&D2&C1' \
OK AT+CMEE=1 \
OK 'AT+cgdcont=10,"IP","orange.fr"' \
OK-AT-OK ATD*99***10# \
SAY "\nwaiting for connect...\n" \
CONNECT "" \
SAY "\nConnected." \
SAY "\nIf the following ppp negotiations fail,\n" \
SAY "try restarting the phone.\n"
#!/bin/sh # # File: # chat-gprs-disconnect # # send break exec /usr/sbin/chat -V -s -S \ ABORT "BUSY" \ ABORT "ERROR" \ ABORT "NO DIALTONE" \ SAY "\nSending break to the modem\n" \ "" "\K" \ "" "+++ATH" \ SAY "\nPDP context detached\n"
Once having setup asdetailed above, here is the log of a connection :
gnou:/etc/ppp# pppd file gprs Press CTRL-C to close the connection at any stage! defining PDP context... OK AT&F OK ATV1E0S0=0&D2&C1 OK OK OK waiting for connect... CONNECT Connected. If the following ppp negotiations fail, try restarting the phone. Serial connection established. Using interface ppp0 Connect: ppp0 <--> /dev/rfcomm0 kernel does not support PPP filtering LCP: Rcvd Code-Reject for code 9, id 0 Cannot determine ethernet address for proxy ARP local IP address 10.16.4.71 remote IP address 10.16.0.2 primary DNS address 194.51.3.56 secondary DNS address 194.51.3.76 LCP: Rcvd Code-Reject for code 9, id 1 [SNIP] Terminating on signal 2. Connection terminated. Connect time 0.6 minutes. Sent 69 bytes, received 54 bytes. Sending break to the modem PDP context detached Serial link disconnected.
You must pay attention to services that might trouble the establishment of the connections such as :
On GNU/Linux, if a NIS configuration is present on the machine when connected to a wired network, you must be carefull to deactivate NIS (for instance : ifdown eth0; /etc/init.d/nis stop).
If using the same Bluetooth adapter with two different OS (like Windows 2000 and GNU/Linux) with the same mobile phone, you may have problems with pairing. Thus I recommend to use different bluetooth adapters with each OS.
If using two different bluetooth adapters on the PC, you may have to set the default paired device on the mobile phone according to the device in use on the PC, or the connections won't be established succesfully.
I'm using my Sony T625C Clié with a PEGA-MSB1 bluetooth memorystick to connect it to the Bluetooth+GPRS phone, over bluetooth, in order to access the internet (surf the web, send/receive e-mails, etc.).
You need to install the Bluetooth memorystick's drivers first (english versions on the CD, although the kit I ordered was in Japanese).
I suspect that the setup steps described here may be a little specific to the Clié software and nature of the memorystick adapter, although it's probably very close to what would be necessary for other bluetooth devices on other PalmOS based machines, like Palms or Handspring with other kinds of adapters, or for the Cliés with embedded bluetooth chips.
The configuration on the palm is as follow :
In the Preferences application :
In the Bluetooth "tab":
Set Bluetooth to "Enabled"
Define a Device Name, which will help pair the devices
Set Allow Device to be Discovered to Yes
Click the "Trusted Devices" button:
Add devices while the Fisio 820 has bluetooth activated
In the Connection "tab":
Add a New connection :
Name : Orange GPRS
Connect to: PC
Via: Bluetooth
Select a Device and discover the Fisio 820 (and pair it)
Details :
Speed: 38400 bps
Flow Ctl: Automatic
Add a New connection :
Name : Orange GSM
Connect to: Modem
Via: Bluetooth
Select a Device and discover the Fisio 820 (and pair it)
Dialing: TouchTone
Volume: Off
Details :
Speed: 38400 bps
Flow Ctl: Automatic
Init String: "AT"
Now, you may add a Network service using the GPRS connection. Unfortunately, I've no longer the Fisio to confirm these settings. Thanks for any help if you can help complete this document ;).
I used the latest version of the Orange PC/PDA kit to configure the communication elements, which only define the necessary elements for an IrDA connection, then adapted them for Bluetooth connection.
Here are the results :
Insert the Bluetooth memorystick into the Clié
In the Preferences application :
In the Bluetooth "tab":
Set Bluetooth to "Enabled"
Define a Device Name, which will help pair the devices
Set "Allow Device to be Discovered" to Yes
Click the "Trusted Devices" button:
Click "Add device" while the T68i has bluetooth activated and detectable (and maybe while initiating a reception from pairing attemp).
At that time you may launch the Orange application and reinitialize its settings, which will create templates for the IrDA elements we will otherwise manually create from scratch, as specified bellow :
In the "Connection" "tab":
Add a New connection (you may also duplicate the "Orange GPRS" connection created by the Orange kit if it exists, which was created for IrDA) :
Name : "Orange GPRS over BlueTooth"
Select "Connect to:" to "PC" first
Via: Bluetooth
Select a Device and discover the T68i (and pair it if necessary)
Now that the bluetooth device is selected, change the "Connect to:" connection type to "Modem"
Then click the "Details..." button and set :
Speed: 57600 bps
Flow Ctl: Automatic
And in "Init String:", add :
+CGDCONT=10,"IP","orange.fr";z
In te "Network" "tab" :
Add a new "Service:" item (you may also duplicate the "Orange GPRS" service created by the Orange kit if it exists, which was created for the "Orange GPRS" connection over IrDA) :
Service name: "Orange GPRS bluetooth", for instance
Login: orange
Password: orange
In the "Connection:" list, select the "Orange GPRS over BlueTooth" connection that you've setup earlier
In the "Telephone number", type :
*99***10#
Then click on the "Details" button.
In Connexion type, select PPP, in inactivity delay, None, and then check DNS query and Automatic IP address.
Click the Script button, and check that your script will only contain the three lines :
Send: atz
Send CR:
End:
Now click on the "Connect" button.
After a while, you should see that the connection is established : the phone as a double arrow icon next to the Bluetooth indicator (RFCOMM session established), and an earth icon, meaning that GPRS connection to the net is established.
If you go to the Options / Journal menu, from that Network preferences "tab", or issue a /Jtapping, you should enter the network connection debug tool.
You should the see something like the following :
S: atz S: ^M LCP->CfgReq LCP<-CfgReq LCP->CfgAck LCP<-CfgAck LCP Up PAP->CfgReq PAP<-Ack ... [SNIP] ... IPCP Up Service name : Orange GPRS Bluetooth Local IP address : 10.16.13.235 Gateway Address : 10.16.0.2 DNS Addresses : 194.51.3.56 194.51.3.76![[Tip]](images/tip.png)
Tip Now, you may tap to the end of that journal, and type helpin the graffitti area (enter command "help" and a carriage return, with the "/" drawn from upper right to bottom left, or with the mini-keybord carriage-return key).
This will display a list of command, among which is ping.
You may now try and ping the IP address of your gateway, which would normally succeed. The other addresses may not be ping-able... I suspect Orange filters out the ICMP packets :(.
You may now use any internet-aware application, over that GPRS connection : POP/IMAP/SMTP Mail programs, Web/WAP browsers, etc. It seems that SSH is filtered out though.
Don't forget to disconnect the network connection when finished (same button as "Connect" in the preferences tool, or from the applications' menus).
Here are a list of pointers to other elements that may be of use to some of the readers :
If you are a client of SFR France, you may have a look at an article written (in french) by Gérard Blanchet describing his experience with a Zaurus and a Fisio 825 mobile phone.
There are probably interesting elements concerning various parameters for the different french operators in the September 2003 issue (#45) of the french "Team PALMTOPS" magazine.
Vincent Kergonna (
<vincent.k@orange.fr>) wrote me to report success with a Siemens S55 when using the GNU/Linux scripts documented here for the Fisio 820. Thanks for the information.
Reference information was taken from :
A site made by some guys linked somehow to Orange : http://www.gprs92.fr.st/
The documentation of the PDA/PC kits from Orange.fr
The http://www.luxgsm.lu FAQ on GPRS
"Linux, GPRS phones, serial cable and IrDA", at http://www.ee.oulu.fi/~mcfrisk/linux_gprs.html
"Some notes about the Sony Ericsson T68i" at http://larve.net/people/hugo/2003/scratchpad/SonyEricssonT68i.html
Many thanks to the people who have provided so much information in these documents.
The current version you're reading is (CVS id.) : $Revision: 1.1 $ - $Date: 2010-08-10 15:23:57 $
The latest version of this document should be available from http://olivierberger.org/btgprsfisio820orangefr.html.
This document was written using DocBook 4.1.2 XML source, available from http://olivierberger.org/btgprsfisio820orangefr.xml, and transformed to HTML on my Debian GNU/Linux system using the xsltproc XSLT parser and the following XSLT stylesheet (xsltproc --xinclude mystyle.xsl btgprsfisio820orangefr.xml >btgprsfisio820orangefr.html).
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version='1.0'
xmlns="http://www.w3.org/TR/xhtml1/transitional"
exclude-result-prefixes="#default">
<!-- Stylesheet customisation following the documentation from the
"DocBook XSL Stylesheet Documentation"
(http://docbook.sourceforge.net/release/xsl/current/doc/) in
section "Customizing DocBook XSL stylesheets". -->
<!-- <xsl:import href="docbook.xsl"/> -->
<xsl:import href="/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl"/>
<xsl:variable name="toc.section.depth">4</xsl:variable>
<xsl:variable name="chapter.autolabel">1</xsl:variable>
<xsl:variable name="section.autolabel">1</xsl:variable>
<xsl:variable name="generate.section.toc">2</xsl:variable>
<xsl:variable name="generate.section.toc.level">4</xsl:variable>
<xsl:param name="generate.toc">
appendix nop
article/appendix nop
article toc,title
book toc,title,figure,table,example,equation
chapter toc,title
part toc,title
preface toc,title
qandadiv toc
qandaset toc
reference toc,title
sect1 toc
sect2 toc
sect3 toc
sect4 toc
sect5 toc
section toc
set toc,title
</xsl:param>
<xsl:param name="generate.index" select="1"></xsl:param>
<xsl:param name="admon.graphics" select="1"></xsl:param>
<xsl:param name="appendix.autolabel" select="0"></xsl:param>
<xsl:template name="user.head.content">
<xsl:comment> (c) Copyright 2003 Olivier Berger (olberger@club-internet.fr)</xsl:comment>
<!--
<meta http-equiv="Refresh" content="3; URL=http://perso.club-internet.fr/olberger/demo.en.html" />
-->
</xsl:template>
</xsl:stylesheet>
As you've seen in the legal blurb at the beginning, permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; without any Invariant Sections, without any Front-Cover Texts, and without any Back-Cover Texts. A copy of the license is included in the appendix bellow (see GNU Free Documentation License).
I welcome any comments, suggestions or additions on how to
improve this document, of course : write to me at
<oberger [AT/arobase] ouvaton [DOT/point] org>.
GNU Free Documentation License
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you".
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five).
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
In any section entitled "Acknowledgements" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements."
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.