I'm attempting to set up a bluetooth network on my Linux desktop to connect my Honeycomb tablet to for internet access.
I want to use bluetooth because my university does not allow creating WiFi networks in your room, and there isn't a public one in range from my room.
My tablet is an Acer Iconia A500 (unrooted, but willing to root if needed) and I'm running Arch Linux on my desktop. I've successfully paired the two, but I con't work out how to set up a NAP.
This is going to take installing a few packages, and a little bit of config'ing stuff, so I'll avoid giving a man the proverbial fish, and hopefully set you in the right direction:
You'll need to install the 'bluez' package, and the 'blueman' bluetooth manager (assuming you're going for GTK).
You'll likely, but optionally, want to install a dhcp server on your Arch system and then configure that...
Once you've got blueman running right, you'll be able to right-click on the applet and go to 'local services', and there configure the DUN service.
Beyond that, there may be some bridging of network interfaces and stuff, but I'm not sure (that'll be covered in the Arch wiki, as most of this is). Best of luck.
-Dan
Related
Hi,
I tried several tools (aNetShare, tetherBlu, Wifi tether) but I can't tether my MacBook to my Hero!
Bluetooth: my Mac is telling me, that no additional BT-service is available except the speakers. I.e. no PAN is available.
Wifi: my Mac shows me the Hero as an access point. But connecting to it has no effect, neither on the Hero neither on my MacBook (except the wifi-icon on the mac is changing to a small console, but greyed out).
Of course, I have rooted my Hero and it's working (tried with several tools). Is tethering Hero and MacBook an impossible mission?
Android doesn't support PAN, only HFP and A2DP.
I haven't tried the apps you mention. DO any of them specifically say that they add PAN to the device?
I'm not familiar with this bluetooth stuff, but with other phones, my MacBook tethers over bluetooth with PAN connection. That's why I assumed that type of connection here, too.
No, not possible with Android.
Like i said, the Android OS only supports HFP and A2DP. If those apps do not specifically add the PAN profile to the hero, and i very much doubt that they do, then you're not gonna get anywhere.
If you need to use the phone as a modem with your mac, you're S.O.L with android!
I have messed around trying to tether my Hero with my Mac book air for a couple of weeks and tried pretty much everthing without any sucess. All the wifi tether apps out there dont seem to like macs and bluetooth failed too.
In the end I found a working solution but its not ideal - however it does work.
Installed Pararellls desktop ( Vmware would probably work too if it has good USB support - never tried it)
Installed windows XP as virtual OS
Installed PDAnet for windows ( mac version doesnt exist )
Installed Phone drivers under windows virtual machine
So now I run windows as virtual machine to tether my HTC hero with my Mac, it works well most of the time, unless the connection is dropped then Pdanet cant see the internet connection any more and requires an OS reboot.
I hope this saves some of you guys the time I lost
naaa.. get the modaco custom rom.
the android-wifi-tether app issue is present for macs and pcs, it is actually do to the hero itself and not your computer, you need to get the custom rom (awifiteth comes pre-installed) and that works perfectly on my macbook!
the custom rom adds iptable support and so it now works..
Is it not possible to make an app that injects this code into the official firmware running Hero's ?
Also, I guess the telco's are helping ensure the manufactures disable any possible way to tether as they have no current mechanism to charge for it unless you buy one of their dongles and pay though the nose for another contract
joemax said:
Is it not possible to make an app that injects this code into the official firmware running Hero's ?
Click to expand...
Click to collapse
No, the official firmware is "non-rooted," meaning that you and your downloaded apps won't be able to access the Linux system on a read-write basis, which is necessary for tethering apps, as they likely all need to change the iptables to alter the way network routing occurs within the phone.
But possible once someone works out how to root the latest firmware ?
If someone does this, I would pay gladly for the app if it allowed me to use the Hero as a 3G/HSDPA modem.
I didn't get much response on my previous question about proxy support for the stock rom, so I was wondering if any of the alternate roms include it. I would very much like to have access to the internet at work, but the school district requires loggon through a proxy server (content filter) before you can access the WiFi network. I realize that port restrictions that the district places on the network will likely prevent me from accessing the market, gmail, or voice search. But at school, I would most like to just access flash based educational website for kids.
Any thoughts on this? The district is moving toward ipads as the tablet platform of choice because of the lack of proxy support with Android. But the ipads lack of support for flash really hinders what I want a tablet to be able to do for me. (Yes, I want my cake and eat it too!) Is this too much to ask?
I connect my gtab to my schools wirelesss that is using 802.1x EAP for wireless security. I had to install a mod that changed the settings app and allowed advanced wireless settings. That allowed me to put in the authentication type, domain name, password, etc. Once connected, I ran a mod that set it back to the original settings apps. I asked in your previous post as to whether you are having problems actually getting on the wireless or once on, you can't bet by the web filter. We use websense here. Once I got on the wireless, there was an websense authentication dialog that popped up. Once I put my domain\username and password in, it works fine.
It won't even let me connect to the district network because I don't have anywhere to enter the proxy settings in the wifi set up box.
Assuming you have Pershoot's or Clemsyn's Kernel (or one of the better ROMs), you need something like ASProxy. I use it at work all the time and it does the job. There is a free program called TransParentProxy which is more limited but does allow you to quickly test settings without spending any money.
I do not see a proxy settings in the wpa_supplicant.conf file. My understanding of this file is it lists all possible settings settings available for Wi-Fi configurations.
# This file describes configuration file format and lists all available option.
Click to expand...
Click to collapse
Previously I've only needed to access a proxy after connecting to the network. Perhaps you have run into a problem getting connected to your network using the tablets Wi-Fi settings manager. So connecting to the network might be your first step and then connecting to the proxy your 2nd.
I found the free Wifi Advanced Config Editor (WifiACE on the Android Market) to have a GUI to easily configure advanced Wi-Fi settings not found in the tablet's settings. I realized when trying to set up an advanced configuration I needed to create a new connection in the tablets WiFi Settings with the security of NONE to avoid having some of the wrong settings configured by default. Then using the information from the my network admin I manually set the options via the WifACE GUI, un-checking NONE, and bingo I got connected.
I recommend WiFiACe with one caveat: make sure you have a way (like adb) working and know how to backup, delete, and restore files and that you make a back up of all wpa_supplicant.conf files on your tablet.
My caveat comes because my first reboot after I got connected to the Enterprise network at work the Wifi would not start or run. It would only display "error" and do nothing. Several reboots later it still wouldn't start and without Wi-Fi running there is no way to make configuration changes either through WifiACE or the tablets Wi-Fi Settings. I had to use the adb shell to delete the newly configured wap_supplicant.conf and create a new connection via the tablets Wi-Fi Settings and then make the necessary changes through WifiACE. Once that was done it ran and connected. Now after multiple reboots it still works and connects. Without the ability to delete the file I'm afraid I would have had to re-flash my tablet to get Wi-Fi to work again.
I don't think you've ever mentioned what ROM you're running. If you're running stock, you will have a very difficult time, in fact it may be impossible. If you're running a different mod, there's hope. Now, assuming that you got ClockWordMod (CWM) installed, you can probably be successful in at least connecting to the wireless. If you don't have CWM installed, here's a good place to start:
http://forum.xda-developers.com/showthread.php?t=865245
Once you have CWM installed, go to this thread:
http://forum.xda-developers.com/showthread.php?t=857939
This will give you the zips for installing a differernt wireless config tool that will allow you to put in the 802.1x EAP config. Once you can successfully connect, you back out the the tool you installed.
One of the corner cases it seems HP did not design into webOS is the ability to auto negotiate a full 802.11X connection. I managed to fix this though and my touchpad is happily connected to our office wi-fi and I figure anyone else trying this might want to check out the workaround I managed.
When I attempted to configure my touchpad to connect to an office/enterprise access point, I hit a brick wall where after completing all the required steps. It was able to use the current user credentials and get to the access point itself, but failed out with a "warning, no certificate is found for this network, please contact your network administrator" type of message.
Well of course no one in our IT group had ever so much as seen WebOS and ultimately I was left to fend for myself.
The goal here is to successfully transfer the (normally auto-retrieved) 802.11X signing certificate to the touchpad so that it can properly connect to your corporate/enterprise wireless network. On other devices such as android this seems to all be automated, but on the touchpad a significant amount of manual arm-wringing was needed to get it to all work together.
Step 1: Getting a root security certificate for your company.
There are a few guides out there for various operating systems/devices which you can use. Since my office machine was windows 7, thats what I have direct experience with.
Win7 Has a built in certificate management tool, but it is not listed in any of the menus. To get to it, enter certmgr.msc into the run panel and it will open up this handy dandy little tool.
Once you have that tool open, look into the root certificate authority folder and find your company's enterprise certificate. Hopefully it will be fairly easy to spot, i.e. if you work at company with domain X, you should see something like "X Enterprise CA".
Right click this certificate and select "All Tasks->Export" which will bring up a wizard with a few different certificate formats. After much trial and error, I found that the only one the touchpad seemed to natively understand was the "Base-64 encoded X.509". Finish the export with a file name and you can find it in your default user folder.
Step 2: Transfer this file to your touchpad
This one is a no brainer, just connect the touchpad via usb to your machine where you have this file, and drag it over.
Step 3: Importing the new certificate
All you need here is any webos file manager capable of opening a file. I used Gemini File Manager, but several free ones are also available and should work.
Open the file manager app on your touchpad, and run that certificate file. This will open a certificate manager tool on the touchpad and prompt you to trust this new certificate. Once you select to trust it, it will be brought into the system and available to use for 802.11x authentication.
Step 4: Connecting to the network
At this point all you should have to do is connect to the office wireless that was giving you trouble before, and now after giving all your authentication info it should successfully connect and offer full connectivity
It seems a little convoluted but it is awfully nice to have the touchpad be fully on-line and available around the office and you only have to do it the one time, successive connections should all just work.
I've tried this at my University, but it doesn't work for my exact situation. Hopefully it will work for others too. Kudos for figuring it out! As for me, apparently WPA2 Enterprise PEAP MSCHAPV2 is a no go until the WebOS team will update/fix it....
I managed to get connected to my MS corp wireless, but will actually see if I have network connectivity a bit later (and update this thread).
its given me full connectivity here (I'm writing this on my touchpad on the enterprise WiFi right now). Its also worked for several other people here lucky enough to score one as well.
the biggest sticking point was getting the right certificate in the right (touchpad working ) format. Once I managed to get that file simply sending it around helped everyone else here get going in a couple minutes vs a couple hours it took when I was trying to sort it all out.
We use 802.1x at work without server certs. Just peap and mschap v2. I haven't had any luck connecting though. Anyone else been able to?
Looks like PEAP support is a major sticking point.
There's a tutorial here: http://www.webos-internals.org/wiki/Advanced_Wifi
(I changed some of the script as per the thread I got the link from here: http://forums.precentral.net/hp-touchpad/288229-wifi-enterprise-802-1x.html)
I tracked down the ARM wpa_supplicant package here: http://packages.debian.org/squeeze/armel/wpasupplicant/download
And the libreadline.so.6 package here:
http://packages.debian.org/squeeze/armel/libreadline6/download
.DEB packages just have .TAR files inside them so I extracted what I needed using 7Zip and used WebOSQuickInstall to copy the files to the TP.
Even after following the other directions though, I consistantly get an error saying:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Not having much luck...
what's odd is our network looks like it does have peap set but with this certificate its working on the touchpad just fine.
it uses our exchange login info with a slightly off domain but even that has not thrown it.
The exact network configuration visible in the windows properties for the wireless link here is as follows:
Security: WPA2-Enterprise
Encryption: AES
Network Authentication: PEAP
Validate Server Certificate
Secured Password (EAP-MSCHAPv2) (Automatically use windows login/pass/domain)
Fast Reconnect
I haven't had luck with anything so far.
Is anyone willing to make a patch to fix the MSCHAPv2 problems? I'm willing to donate to your cause if I can my TouchPad to connect to my school's wireless, as it's essentially useless right now.
The network here uses WPA-Enterprise (not WPA2), and PEAP with password authentication only (no cert needed - as far as I'm aware it doesn't issue one to the phone).
I managed to get the TP to say "no network with that name and security method" found when I had the protocol set to IEEE801X, it doesn't do it when I set it to WPA-EAP though.
Essentially, using (what I believe to be) the exact same settings that work with my SGS2, doesn't work with the TouchPad.
It looks like at best the enterprise stuff is kinda half baked. If you need a certificate, webos is capable of *using* one, but not generating it. If its non certificate based, it seems to just fail out entirely.
Have you guys who are having the failures had luck with other devices like laptops etc? if so, what are the settings used to establish that successful connection? It seems like the touchpads are *capable* of mantaining peap/mschapv2 connections, as that is the setup my office uses, but for some reason without the certificate requirement it just is glitching out and won't establish the connection in the first place
eltee said:
It looks like at best the enterprise stuff is kinda half baked. If you need a certificate, webos is capable of *using* one, but not generating it. If its non certificate based, it seems to just fail out entirely.
Have you guys who are having the failures had luck with other devices like laptops etc? if so, what are the settings used to establish that successful connection? It seems like the touchpads are *capable* of mantaining peap/mschapv2 connections, as that is the setup my office uses, but for some reason without the certificate requirement it just is glitching out and won't establish the connection in the first place
Click to expand...
Click to collapse
My Windows7 laptop and my WP7 Samsung Focus both securely connect to the network fine. My TouchPad is the first device I've ever heard of having issues connecting.
Hell, my roommate even has his PS3 and XBOX connected.
Thanks OP! Method works on Swansea University Eduroam.
bump now that we have a 3.03/04 update
anyone know if it worked?
Installed the WiFi Certificate but still no luck.
Any other workarounds out there?
Just updated (manually) to the leaked 3.0.3 version and it's resolved the Enterprise Wifi connection issue.
Confirmed, my WiFi works. Enterprise mschapv2 PEAP without certificate. 3.0.3. Now I can leave my laptop at home and use splashtop if I need anything.. *rock on*
I can also confirm that the certificate issue has been solved in 3.03, but now I can't set a proxy, has anyone been able to?
PEAP/MSCHAPv2 fixed with "official" 3.04 OTA too
PEAP/MSCHAPv2 authentication has stayed fixed with the official 3.04 OTA update.
I've just checked that I can connect to an eduroam connection configured this way at a UK university, which the TouchPad couldn't do before.
professordes said:
PEAP/MSCHAPv2 authentication has stayed fixed with the official 3.04 OTA update.
I've just checked that I can connect to an eduroam connection configured this way at a UK university, which the TouchPad couldn't do before.
Click to expand...
Click to collapse
awesome news, I will be testing mine out today when I get to school.
update: I was able to connect at my school, but I had to uncheck the cert box to get it to work.
Yup, i removed my custom certificate on 3.04 and re-joined the access point. It had some new options about authentication built in and sure enough just worked, no issues.
Looks like the little crazy work-around won't be needed anymore
Hello,
First I am able to use simple port forwarding on my router to access each IP cam individually. This is an unsecure method and is exactly the solution I a trying to get away from.
I am a Linux professional. I can handle my own on the Ubuntu side. I am not so much technically savvy on the Android side. I've spent a good amount of time trying various methods mentioned below. The primary problem is that I just don't have beaucoup amount of time debugging to get this to work. Hence my post.
I am looking for the simplest solution to achieve my requirement. I want to securely access multiple services from my Android phone over 4G/3G on my natted home network using my Ubuntu server as the gateway. When i I say securely I mean, using an encrypted protocol to connect to my Ubuntu server, using multiple levels of authentication reaching my final end point application such as my IP webcam.
My phone is a HTC One M8 running Android 4.4.2 rooted using Weaksauce. The server on my internal network is Ubuntu 14.04.
I've unsuccessfully tried using Openvpn v2.3.2 on ubuntu and OpenVPN on my Android. This method and the other listed below I've spent hours trying get it to work. Way too many permutations of configuration and application choices to even attempt to list hear.
I've tried PPTP v1.3.4 on Ubuntu with the Android VPN client unsuccessfully
Again I am looking for the quickest way for my requirements to be met. I am open to the above methods but thinking below is the way to go.
The solution I am leaning towards is using ProxyDroid and SSH Autotunnel on my Android to port forward port 3128 to reach squid v3.3.8 on my Ubuntu.
The current problem I am running into is that SSH Autotunnel complains that it cannot create the port forward because port 3128 is already opened by squid. I've used this solution years ago using Putty on Windows and squid on my Linux system. Technically I am doing the same thing with SSH Autotunnel so I do not understand why I am getting this error this time.
I really appreciate anybody who has a few minutes to help me get up and running.
--Thanks, Chris
I have a Nexus 7 (2013) WiFi tablet flashed with Ubuntu touch, there is much unfamiliar to me as a regular Linux user with this distro.
I have been trying to get the tablet to connect to the Nokai N900(Maemo5 Linux) app QT Mobile Hotspot via wifi, it associates but doesn’t grab from an IP from the DHCP as my Ubuntu laptop does. If I run dhclient in the tablet's terminal it just hangs. Any ideas?
The N900 running QT Mobile Hotspot uses ad-hoc mode to make the connection.
Working in shell with the tablet is a bit of a pain as the replacement touch screen makes typing difficult and SSH apparently doesn't work without tweaking.
I see the same with UT on a MX4 and the n900.
Android out of the box disables connecting to ad-hoc networks. I wonder if UT does the same via a driver inheritance?
What issues do you have with ssh?
"Sent from Ubuntu Touch MX using the Forum Browser app"
handaxe said:
I see the same with UT on a MX4 and the n900.
Android out of the box disables connecting to ad-hoc networks. I wonder if UT does the same via a driver inheritance?
What issues do you have with ssh?"
Click to expand...
Click to collapse
Hey handaxe, same from TMO?
From my research Android can go ad-hoc when rooted, in fact my nexus associates in ad-hoc mode with the N900, just that grabbing an IP address fails. Not sure if the tablet uses dhclient, but that fails when I try it in shell.
I got ssh working askubuntu.com/questions/348714/how-can-i-access-my-ubuntu-phone-over-ssh but it is using public key verification, I go through wipes so often and have such low security needs a password is enough and I hate having to worry about key management, I assume a machine will be compromised and just use crypto on private data. Getting the tablet moved to password verification is probably what I need to bootstrap myself into the next step. There is no good gedit like app and I cant very well VI without having Esc, and Ctrl keys.
As an aside if you know how to get a VNC server running, I had been hoping to use the tablet as a big screen for N900/Maemo apps, especially GPS until the Ubuntu Touch selection expands.
biketool said:
Hey handaxe, same from TMO?
...
As an aside if you know how to get a VNC server running, I had been hoping to use the tablet as a big screen for N900/Maemo apps, especially GPS until the Ubuntu Touch selection expands.
Click to expand...
Click to collapse
The same handaxe....
http://www.unixarea.de/bq/bq-aquaris-e45-ubuntu.txt
Item no 7.
Useful info in that page overall. Installing VNC requires setting the filesystem to rw, thus allowing use of apt-get and .deb installation as opposed to clicks. This disables OTA updates.
I test-ran dhclient as root via ssh whilst connected to a WPA AP, and it did not hang, so I assume that ad-hoc is not supported.
But to get back to the most important topic,
has anyone successfully used tethering from an Ubuntu Touch wifi tablet to any phone with an ad-hoc network link?
Just an update, my research shows that it is possible for a rooted android Nexus 7(flo) to connect via ad-hoc just as the Ubuntu Touch flashed Nexus 7 also already can,
I do get a wifi associate on my Ubuntu N7 and can see the MAC address of the Nokia phone on the other side of the connection.
this problem is only an ubuntu touch DCHP hang issue, the connection to the N900 works automaticly and perfectly when I use my Ubuntu laptop.
I do not see a way to post a bug for core OS issues only official Ubuntu Touch apps.
biketool said:
I do not see a way to post a bug for core OS issues only official Ubuntu Touch apps.
Click to expand...
Click to collapse
Bugs go here.
Actually, they go under the app concerned, it this case I imagine network-manager, but bug admin seems to take care of that.
I searched around on ad-hoc and WEP but found nada.