![]() ![]() Here is what you need to do each time you reboot the machine and you want your Access Point to be functional: (copy the IP addresses from your /etc/nf if you are not sure what to use, the above addresses won’t work for you)Īll the above is needed to be done once. Around line 15-20, add your DNS info, e.g. # Automatically bind the device at startupĮdit the /etc/bluetooth/nf (this is optional, but useful) and change the name line fromįile with a text editor and change the “auth” with “noauth” (somewhere around line 25-30). Start by installing the BlueZ Bluetooth and other needed packages (all as root): pacman -S bluez-libs bluez-utils iptables pppĮdit your /etc/bluetooth/pin file and enter some digits: 12345 (remove the “BlueZ” word, some devices only pair with numerical pins).Įdit your /etc/bluetooth/nf file and make it look like this instead of the default values: In any case, any Class Bluetooth module will work anyway. Most integrated BT modules on laptops/PDAs are Class II, up to 10 meters, so if you want the best performance for the Access Point we will try to create here, buy a Linux-supported Class I dongle (about $35). Class I means that the device can send/receive up to 100 meters, Class II means 10 meters and Class III, 1 meter. ![]() I am using the AIPTEK BTuoi USB-based Bluetooth dongle, which is Class I. ![]() You will need two Bluetooth-enabled devices to start with, and some patience as setting up Bluetooth is problematic on all OSes (each one with its own quirks). Following my earlier article about creating a Bluetooth access point with your OS, here is my quick guide how to do just that with Arch Linux. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |