|
|
2010-04-19
, 15:03
|
|
Banned |
Posts: 388 |
Thanked: 57 times |
Joined on Mar 2010
|
#52
|
|
|
2010-04-19
, 15:10
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#53
|
Any idea for the name of that widget? I am not sure how to setup the router to use static DHCP mode. I guess might be easier to use the widget for the time being.
|
|
2010-04-19
, 15:51
|
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#54
|
|
|
2010-04-19
, 18:23
|
|
Banned |
Posts: 388 |
Thanked: 57 times |
Joined on Mar 2010
|
#55
|
About PAND in F12:
Does ifconfig now show you have a bnep0 device up at least?
HWADDR=My BT MAC TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes IPV6INIT=no NAME=bnep0 UUID=some number ONBOOT=yes PEERDNS=yes PEERROUTES=yes
What does route show about routes or both ends?
I think it is only a routing problem anymore for you.
|
|
2010-04-19
, 18:39
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#56
|
/etc/sysconfig/network-scripts shown as:
Later when I query:Code:HWADDR=My BT MAC TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes IPV6INIT=no NAME=bnep0 UUID=some number ONBOOT=yes PEERDNS=yes PEERROUTES=yes
ifup bnep0
Device has different MAC address than expected, ignoring.
# cat /etc/sysconfig/network-scripts/ifcfg-bnep0 HWADDR=00:14:35:00:XX:XX TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes IPV6INIT=no NAME="bnep0" ONBOOT=yes IPADDR=192.168.3.14 NETMASK=255.255.255.0 DEVICE=bnep0 NM_CONTROLLED=yes USERCTL=yes PREFIX=24 IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes
|
|
2010-04-19
, 19:19
|
|
Banned |
Posts: 388 |
Thanked: 57 times |
Joined on Mar 2010
|
#57
|
Your PC should get bnep0 device when N900 has made a PAND connection to it.Code:# cat /etc/sysconfig/network-scripts/ifcfg-bnep0 HWADDR=00:14:35:00:XX:XX TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes IPV6INIT=no NAME="bnep0" ONBOOT=yes IPADDR=192.168.3.14 NETMASK=255.255.255.0 DEVICE=bnep0 NM_CONTROLLED=yes USERCTL=yes PREFIX=24 IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes
I don't think N900 has DHCPD, so BOOTPROTO=none and manual IP address.

|
|
2010-04-19
, 21:01
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#58
|
|
|
2010-04-19
, 22:05
|
|
Banned |
Posts: 388 |
Thanked: 57 times |
Joined on Mar 2010
|
#59
|
[gsever@ccn Desktop]$ ssh root@N900 Nokia-N900-42-11:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.XX.XX.XX * 255.255.252.0 U 0 0 0 wlan0 default 172.XX.XX.XX 0.0.0.0 UG 0 0 0 wlan0
Also ping usually is the first protocol which is good to try. Also ´tcpdump -i bnep0´ may reveal what is wrong.

[root@ccn network-scripts]# tcpdump -i bnep0 tcpdump: bnep0: No such device exists (SIOCGIFHWADDR: No such device)
Does hciconfig show there is data going in and out?
"BT tethering is soo difficult" :-)
Nokia-N900-42-11:~# hciconfig hci0: Type: UART BD Address: EC:9B:XX:XX:XX:XX ACL MTU: 1017:4 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:19850 acl:408 sco:0 events:470 errors:0 TX bytes:27240 acl:451 sco:0 commands:98 errors:0 Nokia-N900-42-11:~# hcitool scan Scanning ... 00:XX:XX:XX:XX:XX ccn
|
|
2010-04-20
, 17:28
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#60
|
However still isn't working
ssh root@192.168.3.15
ssh: connect to host 192.168.3.15 port 22: No route to host
From N900 ->Settings -> PC-Connectivity Manager I activated bluetooth. In advanced tab:
Bluetooth enabled
DHCP server checked
IP address: 192.168.3.15
Gateway: 192.168.3.14
Network mask: 255.255.255.0
Bluetooth address search successfully discover and pair with my FC12 laptop. Settings are all applied.
pand -c EC:9B:5B:01:XX:XX -S -E -e bnep0
pand -l # This responds after the restart
bnep0 EC:9B:5B:01:XX:XX PANU
# Guessing the last should be the IP of N900
ifconfig bnep0 192.168.3.14 netmask 255.255.255.0 dstaddr 192.168.3.15
However still isn't working
ssh root@192.168.3.15
ssh: connect to host 192.168.3.15 port 22: No route to host
It should be close I know. I sometimes get similar messages trying to ssh other Redhat and Fedora machines.
We hijacked the topic but we are getting useful responses for everybody (ok especially for FC12 users