[Q] android-wifi-tether also starts up built in wifi tether - G2 and Desire Z Q&A, Help & Troubleshooting

I had the android-wifi-tether app working just fine with Visionary soft root and the original 2.2 build that came with my G2. After updating to the newest build from T-Mobile, hard rooting and setting up Cyanogen 6.1, tether over wifi has stopped working.
When I try to start up a wifi network with the android-wifi-tether app, the built in wifi tether app starts up in the notification bar and the IP Address I get from DHCP is handed out by the built in app (192.168.43.0 range), but I am unable to push any packets through. Checking ifconfig on the phone it seems like my ip address is 192.168.43.1, not 10.3.0.1 which is what I configured in the android-wifi-tether app.
Starting up the built in wifi tether app, I can't even get an IP address through DHCP. Setting a static address I can ping the phone at 192.168.43.1, but I can't push any bits through to the internet.
Any suggestions? I've already removed the android-wifi-tether app and replaced it with a current version. Is there any way I can disable the built in app? Thanks!

Related

Does anyone have VPN Connection running on 2.2

Title says it all.
All of the 2.2 roms and kernels I have tried will connect to the VPN but must screw up the routes as they shut off my data.
Does anyone have this running?
the only issue i have with "VPN Connections" is that is doesn't pass DNS traffic correctly. hence, i must connect via IP Addy not DNS name. other than that it works fine for me. i'm able to establish a vpn connection then use the WYSE rdc/vnc app to connect to my windows or linux servers ... connnectbot for shell access.
I've also been unable to connect to either a PPTP or IPSec VPN over my 3G connection since upgrading to the official release of 2.2 on my EVO 4G. The connection appears to be established just fine, and the VPN server shows that my VPN client is connected, but I cannot ping to or from the device, nor access any internal resources from it. This is a serious bummer considering that things worked fine under 2.1. Will test over WiFi when I get home. Can't test it at work since we're behind a proxy (which is another gripe I have with Android right now... seriously Google, no proxy configuration options?).
i feel i should clarify the name the application i'm using to establish a vpn tunnel is not the stock android vpn application.
it is called "VPN Connection" http://www.appbrain.com/app/org.codeandroid.vpnc_frontend
amw2320 said:
Title says it all.
All of the 2.2 roms and kernels I have tried will connect to the VPN but must screw up the routes as they shut off my data.
Does anyone have this running?
Click to expand...
Click to collapse
I have some interesting info regarding VPN behavior. With 2.1, of course, it did not work. Here's what I experienced: I rooted my 2.1 with Unrevoked (not a full root) and then I installed OMJ's (8/6?) Froyo and lo and behold, my encrypted PPTP VPN to a MS 2003 server was working perfectly. I assumed that 2.2 resolved the vpn issues. Since I thought 2.2 was a fix, I didn't hesitate to install another ROM. This time, though, I also did a NAND root and installed another 2.2 rom; whose, I don't remember. My VPN was gone. What I discovered was that I COULD connect to an unencrypted MS PPTP server, but still not my encrypted VPN server at work. So, here we are today. I'm running Vael-Pak non-sense rom and after I loaded it I had no vpn, but here's the thing...a couple of days ago I was poking around inside some of the Evo's networking files, I didn't change anything, I just opened them and looked at them with Text Editor, and since then my encrypted PPTP VPN has been working great. I'm very hesitant to reboot my phone because I fear that it won't work anymore. Right now I'm happy.
I'm trying in vain to get VPN connections working too. The only ROM that I had it working with no problems was Cyanogenmod's. All the others don't seem to have it supported in the kernel. Now I'm running a ROM based on the stock 2.2 but haven't found a fix yet.
I'm in the same boat - my pptp vpn worked fine in stock 2.1, but not in stock 2.2...
Sent from my PC36100 using Tapatalk
I can't get a pptp (haven't tried l2tp) to connect from my unrooted 2.2 evo with encryption enabled. I'm trying to connect to my server at home running winxp pro with the default winxp vpn server setup.
Works fine if you disable encryption. But what's the point if it's not encrypted, right? It works fine with encryption using a laptop or my old iphone3G. Seems to be a bug with android.
I'd like to know if someone finds a workaround.
This worked in 2.1 - froyo broke it
liamaa said:
I can't get a pptp (haven't tried l2tp) to connect from my unrooted 2.2 evo with encryption enabled. I'm trying to connect to my server at home running winxp pro with the default winxp vpn server setup.
Works fine if you disable encryption. But what's the point if it's not encrypted, right? It works fine with encryption using a laptop or my old iphone3G. Seems to be a bug with android.
I'd like to know if someone finds a workaround.
Click to expand...
Click to collapse
-mark
I am in the same boat. On CM6 VPN works flawlessly, but it is missing a lot, and kept crashing on me.
On every other ROM and kernel with tun.ko, it says it is connected but no connectivity.
AVA V6 is fast, good battery life, everything works (including hulu, and blockbuster) and very stable, but the only single thing I can't get working is Cisco VPN!!
-David
I am curious, does anyone have VPN working on any Froyo ROM besides Cyanogen?
If so what Rom/kernel are you using?
Interesting observation last night - 4g was temporarily working in sf, and my pptp vpn worked over it. I turned off 4g and retested, pptp vpn didn't work over 3g...
-mark

[Q] Wireless tethering via bluetooth

I've got an EVO running CM6 stable with android-wireless-tether (pre7). I am able to pair/connect to my home PC by setting up a bluetooth PAN in Windows 7. I right click on my device, choose "Connect > Access Point" and it says "Connection Successful". The only thing I get now is "Identifying..." until I am stuck with the good ol' 169.xx... IP address.
I checked the log for the wireless tether app, and it shows:
Enabling NAT rules... done
Enabling IP forwarding... done
Tethering now running... done
error: SIOCSIFFLAGS (Cannot assign requested address)
I've done a little research on the error and tried a few suggestions (rebuild binary/config files, changing the default LAN IP in awt settings) to no avail.
I also tried disabling WiFi and just attempting to share the 3G connection which still isn't working out (same error). Can anyone help me out with this one? I've also tried awt pre8 with the same results.
I had same setup and problem. Started the supper user app and quit app. Powered down phone restarted phone. After restart WiFi tether worked fine. Don't know why .
Sent from my PC36100 using XDA App
Just turn on wireless teather and the go to access conections fine androidap and connect to that. Why do you have to use blue tooth am I missing something? Wireless teather is in the settings with CM6 so you dont need an extra app for teather?
Thanks for the suggestions. I tried opening/closing SU app and rebooting, got the same result.
The reason why I am doing it this way is because I have a PC with only a network card (not WiFi). It's about 30/40 ft. from my router. Rather than buying a wireless card or some cable, I'm connecting via bluetooth and sharing my phones WiFi connection.
I understand if I had a WiFi adapter I could just use the built in Hotspot feature, but if I had WiFi, I would rather connect directly to the router.
I'm definitely interested in this too. At work, we have a no-wireless router policy, and I don't really feel like firing it up and have a guy holding a Fluke wireless network analyzer come and find me.
Bluetooth is alright for what I need. Seems to almost be a kernel issue or something. Worked *perfectly* with my N1, even with pre8. The EVO with CM6 stable isnt working. Just as a note, the wifi portion works correctly.
Actually let me rephrase : The bluetooth section does work, I believe there might be an issue related to the dnsmasq dhcp server not being able to serve IPs. The 'Upload' section of the information panel changes, the Green Download section stays 0.00. The client never receives an IP address, and thats about it.
Logcat didnt really show me much of anything critical error-wise, I'm really hoping that I can downgrade/upgrade a kernel in order to support whatever hardware changes there were between the N1 and the EVO.
I checked the wireless router wifi mode, and it no longer works either. 'Started with errors' is what I get now when in the wifi mode. The built-android wireless tether works fine, but I either wish I could hide the ESSID or have a bluetooth option available.
It *seems* related to the kernel, but logcat doesnt mention anything about not being able to load a module, and the wifi-tether app doesnt have a txt log, or does it?

Running Salvage 1.1 GB - Wireless Tether application error

It keeps telling me that my tethering has been started but with errors. Just installed the Salvage 1.1 mod and it works pretty good - but I really need the wireless tethering app. Of course before I installed this new ROM it worked but now it does not. What can I do to fix this??
My error log
Activating WiFi interface
failed
Setting ad-hoc mode
failed
Setting essid
failed
Setting Channel
failed
Enabling NAT rules
done
Enabling IP forwarding
done
Enabling access control
done
Tethering now running
done
Oh, and also the Portable Wi-FI hotspot option under my Wireless & Networks settings also says error
Wireless tether won't work with the gingerbread roms. You need to use barnacle tether or the native hotspot. And to fix your wifi, just reboot and it'll be fine. Anytime you run the wireless tether app it'll mess up your wifi, and you have to reboot to fix it.

[Q] Wifi tether won't work, rooted Evo 4G and Kindle Fire

I've searched several threads, and tried asking the KF forum, but had no luck figuring out what's wrong.
Both devices definitely 100% rooted with superuser working fine, permissions granted for all apps.
I installed wifi_tether_v3_1-beta14.apk on the phone. Here are the settings:
Device Profile: Evo 4G
Setup-Method: Initially I tried Softap (master).
That's the same as infrastructure mode, correct?
Default SSID (AndroidTether)
MSS Clamping checked
Routing Fix checked​
If I try to run it with these settings, I get a popup informing me the wifi hotspot started, but with errors. No devices (PC, kindle, etc.) can see it.
If I switch Setup-Method to Ad-hoc, it runs fine, no errors, PC can see it and connect to it. But KF can't connect to Ad-hoc... so lame.
So, I got ZT-180 Adhoc Switcher.apk for the kindle fire, to switch it to ad-hoc mode. Went to settings, told it to connect to AndroidTether. Switched to Ad-Hoc mode. It says "attempting to connect" ... after a minute it gives up and keeps retrying. The hotspot shows in the list of wifi networks, but it's hanging at "Obtaining IP address".
So, what's the issue? Infrastructure mode not working? Need to flash a custom rom? I read something about maybe needing a non-stock kernel? Upgrade or downgrade my radio?
I finally found a method that works, barely.
Wifi Tether (app listed above) failed.
Adhoc Switcher failed.
Wifi Hotspot Widget failed.
Elixir2's hotspot widget failed (connected but no surf).
The one that worked is free and doesn't even need root apparently: Foxfi.
I say it "barely" worked because even this has issues.
When I tried to create a password, it wouldn't connect.
But if I leave the password blank (no password) it does work.
http://foxfi.com/bin/
I just told it to start running, and left the SSID at the default (FoxFi98 I believe).
CreeDo said:
I finally found a method that works, barely.
Wifi Tether (app listed above) failed.
Adhoc Switcher failed.
Wifi Hotspot Widget failed.
Elixir2's hotspot widget failed (connected but no surf).
The one that worked is free and doesn't even need root apparently: Foxfi.
I say it "barely" worked because even this has issues.
When I tried to create a password, it wouldn't connect.
But if I leave the password blank (no password) it does work.
http://foxfi.com/bin/
I just told it to start running, and left the SSID at the default (FoxFi98 I believe).
Click to expand...
Click to collapse
Most f those other apps are using adhoc s which the kindle fire so t notice. What worked for me was to use the built in features of a custom ROM cm9 worked well for me using WiFi tethering and Bluetooth. In fact when I was using CM9 the data speeds were pretty much the same on the tablet and phone. It was real easy too just pulled down the notification tray and presses the toggle for WiFi AP every time after the initial setup.
Sent from my Nexus 7 using xda app-developers app
FoxFI won't work on HTC phones
CreeDo said:
I finally found a method that works, barely.
Wifi Tether (app listed above) failed.
Adhoc Switcher failed.
Wifi Hotspot Widget failed.
Elixir2's hotspot widget failed (connected but no surf).
The one that worked is free and doesn't even need root apparently: Foxfi.
I say it "barely" worked because even this has issues.
When I tried to create a password, it wouldn't connect.
But if I leave the password blank (no password) it does work.
I just told it to start running, and left the SSID at the default (FoxFi98 I believe).
Click to expand...
Click to collapse
Installed FoxFi from their website on my HTC EVO 3d. When I ran it, it told me that it was unable to run on HTC phones due to a Hotspot lock and advised me to use bluetooth instead. There is no bluetooth option on my Kindle Fire. I have tried several WIFI tethering apps all with no luck.:crying:

[Q] Lollipop Wifi Policy

Ive searched the web and read about countless issues about lollipop wifi. but im looking for something specific which i cannot find elsewhere:
on KitKat when connecting to a hotspot (or any wifi for that matter) it would instantly connect to wifi and switch to that connection, regardless if the connection gave internet access or not.
on LP it seems to remain connected to mobile data and wifi does not give an IP address until a hotspot is logged in (using the sign in to wifi notification)
the problem is it doesnt always show, is there a way to switch the wifi policy to not perform a soft handover? or does this need to be baked into a rom?
I have an app that auto-logs into wifi hotspots for me, but because it does not get an IP address and apps are not able to use that connection, it does not work as intended.
FYI i am NOT talking about wifi to mobile data handover, its the other way around

Categories

Resources