Related
Hi,
Last week I received my Archos 101. In general it is great. Even better is this forum
I installed urukdroid (thanks to the project-team!). I tried to use openvpn but it failed and I am not sure about the reason.
The server-configuration is
...
ifconfig-pool 10.10.10.120 10.10.10.130
push "route 10.10.10.1"
route 10.10.10.0 255.255.255.0
ifconfig 10.10.10.1 255.255.255.0
push "route-gateway 10.10.10.1"
push "route 10.10.10.0 255.255.255.0"
...
As the Archos is the only device it would get IP 10.10.10.120.
BUT: ifconfig shows:
inet addr.: 10.10.10.255 Bcast: 10.255.255.255 Mask 255.0.0.0
That did (and cannot) work. No ping to home network possible.
When I called route it looked fine (I used redirect-gateway).
When I send the command
ifconfig tap0 10.10.10.120 broadcast 10.10.10.1 netmask 255.255.255.0
from Archos Terminal I had at least access to my home network. But all route entries are gone.
Who has an idea what I am doing wrong? I checked it in the last day again and again... If there is no solution: is it possible to 'save' the entries from route and restore it after my manual change of ifconfig? I would like to do it via script, as my home network I only reachable via dyndns.
Thanks and best regards!
I used the OpenVPN Howto Quickstart and had no problems.
macemoneta said:
I used the OpenVPN Howto Quickstart and had no problems.
Click to expand...
Click to collapse
Yes, I know the guide. I did the same with my ubuntu-netbook and it works directly.
And I think, it would work also on the Archos, if the openvpn/ifconfig on Archos accept the 10.10.10.120. But the IP is changed to 10.10.10.255 and that did not fit.
Where the h*** did the 255 instead of 120 come from?
I noticed the same problem...
No idea where it comes from, but as a workaround, you can put a script somewhere containing a suitable "ip addr add x.x.x.x/y dev z" statement, and reference that in the .conf file as "up scriptname".
Note that you need to add "--script-security 2" to the openvpn commandline to make that work. I added that to the OPENVPN_CFG variable in /etc/uruk.conf/openvpn.
regards
Patrick
This is the openvpn configuration I use for my Archos 101 (on the server). I'm not having any problems, using openvpn 2.1.1:
Code:
port 1194
dev tun
tls-server
ca /etc/openvpn/keys/ca.crt
cert /etc/openvpn/keys/[COLOR="Blue"]<my host>[/COLOR].crt
key /etc/openvpn/keys/[COLOR="blue"]<my host>[/COLOR].key
dh /etc/openvpn/keys/dh1024.pem
mode server
ifconfig 10.8.0.1 10.8.0.2
ifconfig-pool 10.8.0.4 10.8.0.255
push "route 10.8.0.1 255.255.255.255"
client-config-dir ccd
push "redirect-gateway def1"
push "dhcp-option DOMAIN [COLOR="Blue"]<my domain>[/COLOR]"
push "dhcp-option DNS [COLOR="blue"]<my dns server>[/COLOR]"
keepalive 10 60
inactive 3600
route 10.8.0.0 255.255.255.0
user openvpn
group openvpn
persist-tun
persist-key
verb 4
I examined the situation a bit further.
The problem comes from the ifconfig command that openvpn calls itself:
Code:
/system/bin/ifconfig myvpn \
192.168.x.41 \
netmask 255.255.255.0 \
mtu 1500 \
broadcast 192.168.x.255
This is only used when tap interfaces are involved, which is the case in my setup, but not in the setup macemoneta is showing. caesar68: do you also use tap interfaces?
I can reproduce the problem by just using that ifconfig command again.
When I list the IP-address-to-set as the last argument, instead, it works, i.e.
Code:
/system/bin/ifconfig myvpn \
netmask 255.255.255.0 \
mtu 1500 \
broadcast 192.168.x.255 \
192.168.x.41
A quick scanning of the openvpn manpage, does not suggest a way to override the ifconfig command that is used, but it does give an option --ifconfig-noexec which suppresses its calling.
Unfortuntely, when I just pack the is-working-after-the-interface-is-up ifconfig command into an up script with this option, it just gives me an error SIOCSIFNETMASK (Cannot assign requested address) - even if the same commandline works when I run it over an already upped interface... Probably because the interface then already had an IP address...
No problem, though, ifconfig is obsolete anyway, let us just use ip link and ip addr, which are fortunately available under Uruk.
So, caesar68, the clean solution would be to have
--script-security 2 on the openvpn commandline, e.g. via OPENVPN_CFG in /etc/uruk.conf/openvpn
in your myvpn.conf file:
Code:
ifconfig-noexec
up-delay
up-restart
up /etc/openvpn/myvpn-on-up
a corresponding script /etc/openvpn/myvpn-on-up, executable, with content
Code:
#! /system/bin/sh
ip link set $dev mtu $tun_mtu up
ip addr add $ifconfig_local/$ifconfig_netmask \
broadcast $ifconfig_broadcast \
dev $dev
Works For Me
Thanks for the explanation and the workaround, brian_o'fish. Why are you using tap though? Tap provides an Ethernet bridge, so you'll be transporting packets that really don't need to be sent to your Archos (reducing available bandwidth). Tun is layer 3 routed, so only traffic destined for either endpoint goes over the VPN connection.
macemoneta said:
Why are you using tap though?
Click to expand...
Click to collapse
That's what the server I'm using, is configured to do, as it provides transparant bridged LAN access via VPN, and that is what I want, as I am the admin of said LAN and VPN.
If the low level of broadcasts we have, ever increases or appears to be a problem to me, I'll set up an additional tun server, but for now it is simply not an issue.
Anyway, good hint in general!
Hi all!
Thanks a lot for your comments. Yes I am using tap. I would like to have access to my home network (storage etc.). Therefore I want to use the brigde functionality. And that works only when I changed the ifconfig manually afterwards. But the route is distroyed then and packages to the internet are not routed secure thru my home-network.
@ brian_o'fish: Thanks for the advise. I will try that the next days. In the moment I am happy to read, that I am not the only one with the problem (and maybe to stupid to use openvpn - but on the netbook it works).
I have never worked with tun. Maybe I could check, if that is also a workaround.
I will keep you informed, but I am on a trip the next days.
Thanks again!
*** Update ***:
I didn't work neither with tap nor with tun. Meanwhile I tried to run VPNC. I had some trouble, but it works now.
caesar68 said:
I didn't work neither with tap nor with tun.
Click to expand...
Click to collapse
Did you try the approach I described with tap, and can tell where / how it failed?
(The procedures can be found at post #4)
It is apparent that prior to ICS, ad hoc wireless networks are not supported: h t t p:// code. google.com/p/android/issues/detail?id=82
Does anyone know if ad hoc wireless is supported under ICS? I can't seem to find ad hoc wireless networks on my U9GT 2 tablet, running Android 4.0.3.
Anyone???
Saw this useful thread: http://szym.net/2010/12/adhoc-wifi-in-android/
Source Code to wpa_supplicant (ICS): https://github.com/jhonxie/android_external_wpa_supplicant_6/tree/ics
But I still can't get it to work. HELP!
After ploughing through the materials on the Internet, I finally got it to work! I believe this method works for any Android device, of any Android version. However, this method is tedious as I couldn't get the system to accept the adhoc configuration in wpa_supplicant.conf.
Here are the steps:
Ignore the first character of my example command-lines as it represents the prompt (i.e. $, #, >)
Run Terminal Emulator and elevate to root privileges / be the superuser. Then run "wpa_cli", the software interface to the wireless stack:
Code:
$ su
# wpa_cli
>
Now that you're in wpa_cli, the first command is to add a network:
Code:
> add_network
5
Take note as the system would output a number. That is the number that represents your adhoc network. In my example, the number is "5".
Next, type the following commands to set (configure) network "5" (be sure to fill in the respective SSID and BSSID):
Code:
> set_network 5 mode 1
OK
> set_network 5 ssid "MyAdHocWiFi"
OK
> set_network 5 bssid aa:BB:cc:DD:ee:FF
OK
> set_network 5 key_mgmt NONE
OK
> enable_network 5
OK
> ap_scan 2
OK
> select_network 5
OK
If you don't know your bssid, run WiFi Analyzer from the Android Market. The system would reply an "OK" after every successfully executed command. If you get a "FAIL", check your syntax - is the an extra / missing quote?
At this point, you should see a bunch of system messages. There might be some error messages but that might not mean the adhoc wireless connection had failed. Check if your device has successfully obtained an IP configuration:
Code:
# busybox ifconfig
Now, you might think this is a hell lot of work... You're right! It should be able to read the configuration file (e.g. /data/misc/wifi/wpa_supplicant.conf) and connect automatically, but I couldn't get wpa_supplicant to accept my adhoc configuration! I'll update this thread when I got it sorted out.
Finally, I am able to tether to my Nokia phone with JoikuSpot!
References:
- http://szym.net/2010/12/adhoc-wifi-in-android/
- http://www.olsr.org/?q=olsr_on_android
Do you have something that would work with wpa_supplicant v0.8.x?
The wpa_cli command is failing because it cannot be found. Should it be in my system/bin folder? I've since installed busybox and would love to connect to my adhoc network. Suggestions?
wendal has kindly compiled the wpa_supplicant that works with adhoc wireless networks (IBSS). For more info, refer here: http://www.slatedroid.com/topic/286...licant-source/page__view__findpost__p__304667
Has anyone got that file to work? I always try it but my wireless stays frozen. I've changed the ownership and permissions and still nothing!!!
megabiteg said:
Has anyone got that file to work? I always try it but my wireless stays frozen. I've changed the ownership and permissions and still nothing!!!
Click to expand...
Click to collapse
It didn't work for me on my ICS kindle-fire.. According to the log it seems like it doesn't recognize the kindle-fire wireless interface. I am wondering at this point whether each device uses its own wpa_supplicant that works with its own driver or what else. I am going to find out more about it and see if I can get my own wpa_supplicant patched with IBSS and compiled.
Code:
I/ActivityManager( 1400): No longer want com.android.vending (pid 2307): hidden #16
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1400): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
D/CommandListener( 1296): Setting iface cfg
D/CommandListener( 1296): Trying to bring down tiwlan0
D/CommandListener( 1296): broadcast flag ignored
D/CommandListener( 1296): multicast flag ignored
D/NetworkManagementService( 1400): rsp <213 f0:a2:25:77:b3:22 0.0.0.0 0 [down broadcast multicast]>
D/NetworkManagementService( 1400): flags <[down broadcast multicast]>
E/wpa_supplicant( 2457): Unsupported driver 'tiwlan0'.
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant
Not working on hidden WPA2 AES Wigi
Hi there, I have a rooted stock ICS Google Nexus. On my workplace, the wifi has hidden SSID with WPA2-Personal and AES. When I try to connect with it, nothing happens. It's does not save on the wpa_supplicant.conf also.
I've tried the compiled wpa_supplicant mentioned on the post, but the same thing happens... I've even tried to edit manually the wpa_supplicant.conf but the wifi crashed after that (thankfully I had a backup).
So any ideas on how to get this thing connected? On my later Atrix with stock 2.3.6 it connected just fine...
Thanks.
Hello i tried many adhoc fixes and now i can connect to adhoc network but after 1-2 minutes connection get lost. Does anybody know how to solve the problem?
i use Htc Sensation with ICS
I have ICS CM9 on my HTC legend and can't recognise the wirelss network at my office. At home no problem.
If I launch wpa_cli I get:
Using interface 'tiwlan0'
Inteactive mode
>
<2>CTRL-EVENT-SCAN-RESULTS
and the last line continues to loop.
Is it correct? What should I do then and to let this wi fi network accessible?
Try this
Hello,
I just got a new Idolian tablet and couldn't connect to my hidden home SSID. I just thought I'd try something really quick and it worked..! I added network in manually but it said not in range. Try temporarily turning the SSID broadcast back on then connect. Mine was successful. I then turned off the SSID broadcast on the router and the wifi off and on again on the tablet and it connected perfectly.
I've been reading this forums for almost a year but this is my 1st post so hopefully it will help someone out as these forums have for me.
Has anyone got it to connect and not get the obtaining IP address loop? My device finds the Ad Hoc network for my cars ODB2 wifi adapter but will never connect.
Good day friends, I really need to enable ad-hoc on my HTC One X, to use my Brookstone Rover, more'm not getting my wpa_supplicant is v8.
I have a doubt, this command set_network 5 bssid aa: BB: CC: DD: ee: FF, this is the bssid mac network card from my smartphone or mac card that will connect my smartphone?
thank you very much
Edit wpa_supplicant.conf instead of wpa_supplicant
I changed data/misc/wifi/wpa_supplicant.conf instead of /system/bin/wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander. If you're doing this from device itself, use some Root Explorer and Terminal Emulator.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=1
mode=1
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb/Terminal Emulator
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Ok, done! Now you can turn on wifi and if the specified adhoc network is nearby, your device'll automatically connect to it. Don't scan for new networks. If you do, adhoc support will be lost and you'll have to start over again!
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other known networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.
For more details refer
http://forum.xda-developers.com/showthread.php?t=1591207
error adhoc network
Hello,
I have android 4.2.2 ,Nexus 4
I did the same steps but I can not connect to adhoc network
I receive the output below:
> OK
<3>CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<4>Failed to initiate AP scan
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
<3>CTRL-EVENT-STATE-CHANGE id=4 state=0 BSSID=1a:79:c3:0c:b1:bd
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
have you any idea about why doesn't work with me.
---------- Post added at 10:28 AM ---------- Previous post was at 10:24 AM ----------
Hello,
I have android 4.2.2 ,Nexus 4
I did the same steps but I can not connect to adhoc network
I receive the output below:
> OK
<3>CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<4>Failed to initiate AP scan
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
<3>CTRL-EVENT-STATE-CHANGE id=4 state=0 BSSID=1a:79:c3:0c:b1:bd
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
have you any idea about why doesn't work with me.
fyresg said:
After ploughing through the materials on the Internet, I finally got it to work! I believe this method works for any Android device, of any Android version. However, this method is tedious as I couldn't get the system to accept the adhoc configuration in wpa_supplicant.conf.
Here are the steps:
Ignore the first character of my example command-lines as it represents the prompt (i.e. $, #, >)
Run Terminal Emulator and elevate to root privileges / be the superuser. Then run "wpa_cli", the software interface to the wireless stack:
Code:
$ su
# wpa_cli
>
Now that you're in wpa_cli, the first command is to add a network:
Code:
> add_network
5
Take note as the system would output a number. That is the number that represents your adhoc network. In my example, the number is "5".
Next, type the following commands to set (configure) network "5" (be sure to fill in the respective SSID and BSSID):
Code:
> set_network 5 mode 1
OK
> set_network 5 ssid "MyAdHocWiFi"
OK
> set_network 5 bssid aa:BB:cc:DD:ee:FF
OK
> set_network 5 key_mgmt NONE
OK
> enable_network 5
OK
> ap_scan 2
OK
> select_network 5
OK
If you don't know your bssid, run WiFi Analyzer from the Android Market. The system would reply an "OK" after every successfully executed command. If you get a "FAIL", check your syntax - is the an extra / missing quote?
At this point, you should see a bunch of system messages. There might be some error messages but that might not mean the adhoc wireless connection had failed. Check if your device has successfully obtained an IP configuration:
Code:
# busybox ifconfig
Now, you might think this is a hell lot of work... You're right! It should be able to read the configuration file (e.g. /data/misc/wifi/wpa_supplicant.conf) and connect automatically, but I couldn't get wpa_supplicant to accept my adhoc configuration! I'll update this thread when I got it sorted out.
Finally, I am able to tether to my Nokia phone with JoikuSpot!
References:
- http://szym.net/2010/12/adhoc-wifi-in-android/
- http://www.olsr.org/?q=olsr_on_android
Click to expand...
Click to collapse
Thanks brother! This was what I was looking for everywhere!
The wpa_supplicant method did not work for Me and this did! Thanks a lot!
After realising the player won't connect to my Skype Phone S2 to nick the internet, I did a bit of "hacking":
1) Rooted the device
2) Installed Nook Color Bluetooth Tether from Google Play
3) After realising Nook Color is not working, tried running pand --connect, got "Failed to open control socket: Protocol not supported" error message
4) Dowloaded the Samsung kernel source and cross-compiled it to get the missing bnep.ko module for my kernel version.
5) Successfully inserted the mod (lsmod reports live). However pand --connect [address] does not return anything, neither does pand -l
I am running out of ideas how to get the player to connect to the skypephone. Any ideas?
I bought the player as a replacement of hx4700 (released in 2004), which was able to tether with my skypephone easily. I still can not believe that this modern device is lacking the feature.
a.fiodorov said:
After realising the player won't connect to my Skype Phone S2 to nick the internet, I did a bit of "hacking":
1) Rooted the device
2) Installed Nook Color Bluetooth Tether from Google Play
3) After realising Nook Color is not working, tried running pand --connect, got "Failed to open control socket: Protocol not supported" error message
4) Dowloaded the Samsung kernel source and cross-compiled it to get the missing bnep.ko module for my kernel version.
5) Successfully inserted the mod (lsmod reports live). However pand --connect [address] does not return anything, neither does pand -l
I am running out of ideas how to get the player to connect to the skypephone. Any ideas?
I bought the player as a replacement of hx4700 (released in 2004), which was able to tether with my skypephone easily. I still can not believe that this modern device is lacking the feature.
Click to expand...
Click to collapse
Are you running pand from the Player? What does logcat show after? Are you running stock rom? Does "netcfg" show a bnep0 device?
If you have a 5.0, I can confirm that I've gotten bluetooth networking working using the CM7 ROM in the development section.
Thank you for informing me about CM7, but current alpha is not good for me though. I ll keep checking the progress.
logcat showed:
"E/pand (22197): Connect to 00:12:40:53:AC:A4 failed. No route to host(113)"
bnep0 is missing from netcfg output.
You think that uploading the compiled kernel, with bnep.ko might solve it?
a.fiodorov said:
Thank you for informing me about CM7, but current alpha is not good for me though. I ll keep checking the progress.
logcat showed:
"E/pand (22197): Connect to 00:12:40:53:AC:A4 failed. No route to host(113)"
bnep0 is missing from netcfg output.
You think that uploading the compiled kernel, with bnep.ko might solve it?
Click to expand...
Click to collapse
I could be wrong, but I didn't think stock gingerbread android bluetooth stack supported networking. I know ICS does. But then again if pand is available..
Is hciconfig there? What does hciconfig -a show?
BlueZ
BlueZ (hciconfig) is not installed.
pand is from /system/bin, so it's not from BusyBox, which is in /system/xbin in my case.
How can I test that the bnep module is functioning?
P.S. might be easer to go for CM7, but I am running exactly the same kernel CM requires: rj13 (for international).
a.fiodorov said:
BlueZ is not installed.
pand is from /system/bin, so it's not from BusyBox, which is in /system/xbin in my case.
How can I test that the bnep module is functioning?
P.S. might be easer to go for CM, but I am running exactly the same kernel CM requires: rj13 (for international). So I am not convinced other rom is necessarily.
Click to expand...
Click to collapse
There's more to it than just loading the bnep module. It will be pretty tough to figure out what's going on without hciconfig/hcitool/l2ping. You could try
Code:
cat /sys/class/bluetooth/hci0/class
With CM7 bluetoothd this shows 0x5a020c on my player. The third byte (0x5a) shows the service classes supported, and the second bit is whether Networking is supported.
@ambrice,
Just realised that it's you who ported CM7. Kudos!
I am very tempted to try bluetooth tethering from CM7, could you address my concern that I will be running the same kernel (rj13), so how will ROM be able to fix my (possibly) not working bnep0?
>>cat /sys/class/bluetooth/hci0/class
cat: can't open '/sys/class/bluetooth/hci0/class': No such file or directory
a.fiodorov said:
@ambrice,
Just realised that it's you who ported CM7. Kudos!
I am very tempted to try bluetooth tethering from CM7, could you address my concern that I will be running the same kernel (rj13), so how will ROM be able to fix my (possibly) not working bnep0?
>>cat /sys/class/bluetooth/hci0/class
cat: can't open '/sys/class/bluetooth/hci0/class': No such file or directory
Click to expand...
Click to collapse
There is a userspace component to setting up bluetooth networking. It's not all done by the bnep module.
It's weird that you have no hci0. Is your bluetooth turned on? Is there anything in /sys/class/bluetooth?
rj13 kernel is incompatible with CM7. However, the kernel that comes with the CM7 ROMs has bnep turned on, and I have been using it to do reverse bluetooth tethering.
Sorry did not realise the kernel for CM7 is different.
I am now running CM7 and still looking for tethering settings in GUI.
EDIT: Still can not find it
a.fiodorov said:
Sorry did not realise the kernel for CM7 is different.
I am now running CM7 and still looking for tethering settings in GUI.
EDIT: Still can not find it
Click to expand...
Click to collapse
There isn't an easy gui setting to do that, the normal way to do bluetooth tethering is to run the pand connect from another device such as a PC, and CyanogenMod has a pand listening for connections and shares its internet, because the normal case is for a laptop to connect to a phone's cell network.
But running pand from the player should work now and give you a bnep0 device that you can configure. Easiest way is to put the steps in a script and run it to connect.
The bluetooth won't come on: says it's in airplane mode. Wifi ignores it though.
So should I fire up pand -c [address] from the player and I am ready to go?
Did not work when bluetooth was still on.
a.fiodorov said:
The bluetooth won't come on: says it's in airplane mode. Wifi ignores it though.
So should I fire up pand -c [address] from the player and I am ready to go?
Did not work when bluetooth was still on.
Click to expand...
Click to collapse
pand will get the bnep0 network device to show up. Then you need to use dhcpcd or ifconfig to configure the network device.
# pand -c 00:12:40:53:AC:A4
# netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
tunl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080
ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
Click to expand...
Click to collapse
Still no bnep0 . The bluetooth is on.
After some googling found a command:
# sdptool search dun
Inquiring ...
Searching for dun on 00:12:40:53:AC:A4 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10009
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 8
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Click to expand...
Click to collapse
What am I missing?
CM
for people who found this thread, here's a potentially very useful link:
http://forum.cyanogenmod.com/topic/...r-blackberry-phone-via-bluetooth/#entry268658
I will see what I can make of it
CM7
I tried the above guide with CM7, and that's the error I got: "Couldn't set tty to PPP discipline: Invalid argument". pptpclient.sourceforge.net says it's just a matter of ppp_async module. I will see if I can get ambrice to include it into the kernel.
any progress or info on this?
I have tried entropy512 as well as rj's kernel and not found the beep module. I also loaded CM7 Rom and got a boot loop. I updated to CM9 and it booted but still no beep module.
Any info would be appreciated.
Thanks.
Try ambrice's ppp_async kernel module with his latest CM7. Use the guide above to get the reverse tethering. That's the only solution I found so far.
Here's the module: http://www.2shared.com/file/PTXe8_Y-/ppp_async.html
Does anyone have a working solution for PPTP VPN on custom O1 roms? I've tried a lot of ROMs and even CMs don't seem to have it.
It's an important feature so I'm a little bit disappointed that it's not yet properly implemented in these ROMs.
Sadly I'm not a Linux programmer so I couldn't fix it myself, but I hope some devs will see this post and tell me whether it would be possible to implement it in the feuture releases.
I'd be happy to assist in debugging if someone would try to fix the PPTP VPN module.
Here is the log (the error is always the same - Socket() Address family not supported by protocol) :
07-18 15:09:00.469: I/Vpn(198): Switched from [Legacy VPN] to [Legacy VPN]
07-18 15:09:00.479: V/LegacyVpnRunner(198): Waiting
07-18 15:09:00.479: V/LegacyVpnRunner(198): Executing
07-18 15:09:00.559: D/mtpd(5449): Waiting for control socket
07-18 15:09:00.719: D/mtpd(5449): Received 20 arguments
07-18 15:09:00.719: I/mtpd(5449): Using protocol pptp
07-18 15:09:00.719: I/mtpd(5449): Connecting to vpn.[my vpn host].com port 1723 via wlan0
07-18 15:09:00.789: I/mtpd(5449): Connection established (socket = 11)
07-18 15:09:00.789: D/mtpd(5449): Sending SCCRQ
07-18 15:09:00.809: D/mtpd(5449): Received SCCRP -> Sending OCRQ (local = 54508)
07-18 15:09:00.809: I/mtpd(5449): Tunnel established
07-18 15:09:00.829: D/mtpd(5449): Received OCRQ (remote = 27834)
07-18 15:09:00.829: I/mtpd(5449): Session established
07-18 15:09:00.829: I/mtpd(5449): Creating PPPoX socket
07-18 15:09:00.829: A/mtpd(5449): Socket() Address family not supported by protocol
07-18 15:09:00.919: I/LegacyVpnRunner(198): Aborting
07-18 15:09:00.919: I/LegacyVpnRunner(198): java.lang.IllegalStateException: mtpd is dead
07-18 15:09:00.919: I/LegacyVpnRunner(198): at com.android.server.connectivity.Vpn$LegacyVpnRunner.execute(Vpn.java:569)
07-18 15:09:00.919: I/LegacyVpnRunner(198): at com.android.server.connectivity.Vpn$LegacyVpnRunner.run(Vpn.java:447)
Try flashing DjnoxD's kernel
http://forum.xda-developers.com/showthread.php?p=24560941
sent from xda app. it's all good. flash a custom rom. you will thank yourself.
mrcorey said:
Try flashing DjnoxD's kernel
http://forum.xda-developers.com/showthread.php?p=24560941
sent from xda app. it's all good. flash a custom rom. you will thank yourself.
Click to expand...
Click to collapse
Thx. I'm going to try that.
[Edit]
Unfortunately it still doesn't work . DJNoXD's shows exactly the same error with hephappy's ICS.
I've enclosed the working VPN log with stock GB kernel and ROM (works only with encryption OFF).
I really hope developers can fix this problem in the next kernels / roms.
Hi all,
I recently purchased a SGS3 and ran the stock ROM for approx 30mins before flashing a CM10 nightly build (i9300 intl). Because of this I am unable to verify if the wifi was working on my home router prior to flashing a custom ROM.
At work I am able to connect to our wifi connection without problemson 2.4ghz or 5ghz. At home I've got a D-Link DSL-G604T wireless router which I am unable to connect to. I've tried changing the wifi channel, password, removing protection, factory reset and installed a seperate CM10 nightly build without any help.
When trying to connect to the WIFI connection I get the following output in adb logcat.
Anyone have any ideas what may be stopping me from connecting ot my wifi?
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
I/wpa_supplicant( 5841): wlan0: Trying to associate with 00:1e:58:80:a2:e2 (SSID
='HOMEWIFI' freq=2452 MHz)
D/CommandListener( 1913): Clearing all IP addresses on wlan0
I/wpa_supplicant( 5841): wlan0: Associated with 00:1e:58:80:a2:e2
I/wpa_supplicant( 5841): wlan0: Authentication with 00:1e:58:80:a2:e2 timed out.
I/wpa_supplicant( 5841): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00
reason=0
More info of my phone (kernel, build etc): i.imgur.com/PRaEx.png
Cheers
You could try install the latest Siyah kernel, which contains the updated Wifi driver which could help. I used to have my Wifi absolutely fine with my ICS stock ROM. When I upgraded to CM 10 Jelly Bean, my Wifi works but very unstable. Two solutions that worked for me. 1- Use Wifi fixer app 2- Upgrade Siyah 1.7b4 kernel.
And now I can enjoy CM10 and AOKP at the same time without Wifi problems
Hope this helps
this is also happening on the verizon cm10 builds to for the gs3.