342156 / android-wifi-tether

Automatically exported from code.google.com/p/android-wifi-tether
0 stars 0 forks source link

Can't get ip lease #137

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install
2. Connect to 'G1Tether'
3. No ip lease is given back via DHCP

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
1.52 on HTC Hero

Please provide any additional information below.
I'm using a Linux (Fedora 10) laptop with NetworkManager. Will be happy to
provide any debugging you may need for this.

Original issue reported on code.google.com by hiren.jo...@googlemail.com on 25 Aug 2009 at 10:44

GoogleCodeExporter commented 9 years ago
This happens with Ubuntu 9.04 as well (Jaunty, x64 using Network Manager in 
KDE4) and
now I'm running Slackware64 13 (using Wicd) and cannot connect with and without
access control (no wep). Windows can access it just fine, and I've tried 1.51, 
1.52,
and 1.52-cyanogen fix. I'm running cyanogen stable 4.0.4, but this problem has
persisted since version 3.9x.
Why doesn't dhcpd assign leases to fellow linux clients?? The log on the g1 
doesn't
even show an attempt and linux' logs don't show a response... is it something 
with
the bssid? I tried changing the ssid a few times but no dice...

Please address this as I cannot tether on the road with my otherwise awesome 
Slackbox

Original comment by pel...@gmail.com on 15 Sep 2009 at 1:10

GoogleCodeExporter commented 9 years ago
To further this, I've tried setting wep, changing channel, using static ip 
addresses
on the linux side, and everything else I could think of. It simply refuses to
connect. Please find out why, I'm at a loss!

Original comment by pel...@gmail.com on 15 Sep 2009 at 1:18

GoogleCodeExporter commented 9 years ago
Figured it out!!! This is NOT an app related issue, rather it's a Linux one, 
due to 
Linux' inherent mistrust of ad-hoc wifi and dhcp.
ALL you have to do in linux is run a couple of commands to force the mode PRIOR 
to 
attempting to connect with a network manager. Those commands are:
ifconfig wlan0 down
iwconfig wlan0 mode Ad-Hoc

THAT'S IT! Then you can connect! If you (like me) use wicd, then you'll notice 
it 
doesn't show connection and/or the disconnect button doesn't work. All you need 
to 
know is that it does (try it) and when you want to disconnect, use the 
Disconnect All 
button up top and run the following script to put your wireless card back the 
way it 
belongs:
ifconfig wlan0 down
iwconfig wlan0 mode Managed

Now be reasonable here too. If your wireless card is not wlan0, then substitute 
it. 
Also, if you don't have access to if/iwconfig then add sudo before the lines if 
you're making a script for yourself and you may need to explicitly refer to the 
commands if they're not in your path (/sbin/ifconfig for me). Also, while wicd 
has 
script capabilities for pre and post connections, I found it errored out after 
successfully receiving an IP address, possibly due to the sudo's and me 
attempting to 
run the scripts as a regular user.
Nonetheless my sexy Slackware64 13 box is able to connect through my sexy 
Cyanogen 
G1!

The site that helped me figure this out is here: 
https://bugs.launchpad.net/wicd/+bug/129608

Original comment by pel...@gmail.com on 15 Sep 2009 at 12:40

GoogleCodeExporter commented 9 years ago

Original comment by harald....@gmail.com on 16 Sep 2009 at 1:11