User:Mantis

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (Bluetooth Networking)
m (Bluetooth Networking)
Line 45: Line 45:
 
   pand[1650]: bnep0 connected
 
   pand[1650]: bnep0 connected
 
#Configure IP of neo's bluetooth network interface (bnep0) as 192.168.0.102:
 
#Configure IP of neo's bluetooth network interface (bnep0) as 192.168.0.102:
root@om-gta02:~# ip a add 192.168.0.102/24 dev bnep0
+
root@om-gta02:~# ifdown usb0
 +
root@om-gta02:~# ifconfig bnep0 192.168.0.102 up
 
</pre>
 
</pre>
  
Line 65: Line 66:
 
root@foosrv:~# scp root@192.168.0.102:/tmp/xx ~/xx    #  transfer files etc
 
root@foosrv:~# scp root@192.168.0.102:/tmp/xx ~/xx    #  transfer files etc
 
</pre>
 
</pre>
 
  
 
----
 
----

Revision as of 18:02, 17 October 2008

Neo Freerunner tips

  • Freerunner Owned since 15 October 2008 (UTC)

SIM: UK O2 Pay-As-You-Go SIM did not work, replaced with Orange PAYG SIM which works fine.

Using FDOM distribution based on Om2008.9

Bluetooth Networking

using LM Technologies USB dongle on OpenSuse 11.0 server (foosrv)

Here's a good article on bluetooth security: [1]


NB. PIN's in Bluetooth can be longer than 4 digit ! Ensure 'passkey' (PIN) settings are consistent in hcid.conf on neo and on server.

On foosrv:

edit /etc/bluetooth/hicd.conf change pscan disable to pscan enable

edit /etc/sysconfig/bluetooth add PAND_START="yes" at the to of the PAND section

Scan should detect neo's bluetooth address eg
foosrv:~ # hcitool scan
  Scanning ...
	00:06:6E:00:99:00	neo(0)
foosrv:~ # /etc/init.d/bluetooth restart
foosrv:~ # ps -ef | grep pand
  root      2210     1  0 00:33 ?        00:00:00 /usr/bin/pand --listen --role NAP
foosrv:~ # tail -f /var/log/messages

- should see hcid messages (eg foosrv hcid[2190]: Default passkey agent (:1.27, /org/kde/kbluetooth_1234) registered)

On neo:

Start bluetooth via Configuration menu

root@om-gta02:~# hcitool scan
Scanning ...
	00:1B:59:01:02:03	Blue-foosrv(0)
root@om-gta02:~# pand --connect 00:1B:59:01:02:03 --role PANU
#see /var/log/messages - see line like
  pand[1650]: Connecting to 00:1B:59:01:02:03 
  pand[1650]: bnep0 connected
#Configure IP of neo's bluetooth network interface (bnep0) as 192.168.0.102:
root@om-gta02:~# ifdown usb0
root@om-gta02:~# ifconfig bnep0 192.168.0.102 up

On foosrv:

If connection successful you should see line in /var/log/messages like pand[17965]: New connection from 00:06:6E:00:99:00 at bnep0

#  list connections to pand daemon:
foosrv:~ # pand --list
  bnep0 00:06:6E:00:99:00 NAP       # shows neo's bd_address
#  set up iptables for forwarding as instructions for [[USB_Networking]]
root@foosrv:~# iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
root@foosrv:~# sysctl -w net.ipv4.ip_forward=1
#  Configure IP of foosrv's bluetooth network interface (bnep0) as 192.168.0.100:
root@foosrv:~# ip addr add 192.168.0.100/24 dev bnep0
#  Network ssh connection:
root@foosrv:~# ssh root@192.168.0.102
root@foosrv:~# scp root@192.168.0.102:/tmp/xx ~/xx     #   transfer files etc

WiFi Networking

to be continued. Hint: Mofi doesn't seem to like punctuation or special characters in the WPA passphrase - if you are having connection failures try setting to simple text phrase 'Mary had a little lamb' or something...



 Le soleil s'est noyé dans son sang qui se fige...  [2]
Personal tools

Neo Freerunner tips

  • Freerunner Owned since 15 October 2008 (UTC)

SIM: UK O2 Pay-As-You-Go SIM did not work, replaced with Orange PAYG SIM which works fine.

Using FDOM distribution based on Om2008.9

Bluetooth Networking

using LM Technologies USB dongle on OpenSuse 11.0 server (foosrv)

Here's a good article on bluetooth security: [1]


NB. PIN's in Bluetooth can be longer than 4 digit ! Ensure 'passkey' (PIN) settings are consistent in hcid.conf on neo and on server.

On foosrv:

edit /etc/bluetooth/hicd.conf change pscan disable to pscan enable

edit /etc/sysconfig/bluetooth add PAND_START="yes" at the to of the PAND section

Scan should detect neo's bluetooth address eg
foosrv:~ # hcitool scan
  Scanning ...
	00:06:6E:00:99:00	neo(0)
foosrv:~ # /etc/init.d/bluetooth restart
foosrv:~ # ps -ef | grep pand
  root      2210     1  0 00:33 ?        00:00:00 /usr/bin/pand --listen --role NAP
foosrv:~ # tail -f /var/log/messages

- should see hcid messages (eg foosrv hcid[2190]: Default passkey agent (:1.27, /org/kde/kbluetooth_1234) registered)

On neo:

Start bluetooth via Configuration menu

root@om-gta02:~# hcitool scan
Scanning ...
	00:1B:59:01:02:03	Blue-foosrv(0)
root@om-gta02:~# pand --connect 00:1B:59:01:02:03 --role PANU
#see /var/log/messages - see line like
  pand[1650]: Connecting to 00:1B:59:01:02:03 
  pand[1650]: bnep0 connected
#Configure IP of neo's bluetooth network interface (bnep0) as 192.168.0.102:
root@om-gta02:~# ip a add 192.168.0.102/24 dev bnep0

On foosrv:

If connection successful you should see line in /var/log/messages like pand[17965]: New connection from 00:06:6E:00:99:00 at bnep0

#  list connections to pand daemon:
foosrv:~ # pand --list
  bnep0 00:06:6E:00:99:00 NAP       # shows neo's bd_address
#  set up iptables for forwarding as instructions for [[USB_Networking]]
root@foosrv:~# iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
root@foosrv:~# sysctl -w net.ipv4.ip_forward=1
#  Configure IP of foosrv's bluetooth network interface (bnep0) as 192.168.0.100:
root@foosrv:~# ip addr add 192.168.0.100/24 dev bnep0
#  Network ssh connection:
root@foosrv:~# ssh root@192.168.0.102
root@foosrv:~# scp root@192.168.0.102:/tmp/xx ~/xx     #   transfer files etc



WiFi Networking

to be continued. Hint: Mofi doesn't seem to like punctuation or special characters in the WPA passphrase - if you are having connection failures try setting to simple text phrase 'Mary had a little lamb' or something...



 Le soleil s'est noyé dans son sang qui se fige...  [2]