mmorciegov / android-wifi-tether

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

No Internet #352

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Which device (manufacturer, type)?

SamSung Moment

Which firmware is installed?

2.1

What version of wireless tether are you using?

2.0.2-pre9

What steps will reproduce the problem?
1.just starting the app client can connect but no Internet.
2.Clients can connect but limited cause no ip address so no Internet.
3.all clients see the wifi but none ever get ip address.

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

Please provide any additional information below.

Here is adb shell out out.

 ./tether start 1
about to run: [/data/data/android.tether/bin/ifconfig eth0 192.168.1.254
netmask 255.255.255.0]
about to run: [/data/data/android.tether/bin/ifconfig eth0 up]
about to run: [/data/data/android.tether/bin/iwconfig eth0 mode ad-hoc]
about to run: [/data/data/android.tether/bin/iwconfig eth0 essid AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig eth0 channel 6]
about to run: [/data/data/android.tether/bin/iwconfig eth0 commit]
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
iptables: Chain already exists
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m
state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s
192.168.1.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j
DROP]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING
-s 192.168.1.0/24 -j MASQUERADE]
about to run: [/data/data/android.tether/bin/dnsmasq -i eth0
--resolv-file=/data/data/android.tether/conf/resolv.conf
--conf-file=/data/data/android.tether/conf/dnsmasq.conf]
about to run: [/data/data/android.tether/bin/iptables -t nat -I PREROUTING
-s 192.168.1.0/24 -j DROP]
script result was []

Original issue reported on code.google.com by vampir...@gmail.com on 23 May 2010 at 9:28

GoogleCodeExporter commented 9 years ago
There is a new test-version of the app online. This new version renames the 
name of
the wireless-interface. No idea if that helps for this issue here but ... give 
it a
shot please and report your results.
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre10.apk

Original comment by harald....@gmail.com on 25 May 2010 at 10:48

GoogleCodeExporter commented 9 years ago
Thanks but didn't make any difference we got it figured out at sdx forums the 
problem
is our firmware didn't allow tethering, so we swap out firmware now it's 
working.

Original comment by vampir...@gmail.com on 27 May 2010 at 2:08

GoogleCodeExporter commented 9 years ago
Oh. Could you please give me link or explain me what you did to make it work? 

Original comment by harald....@gmail.com on 27 May 2010 at 8:19

GoogleCodeExporter commented 9 years ago
Sure we replaced ourrtecdc.bin with the one from Leshak wireless tethering app,
located here
http://forum.samdroid.net/threads/610-Dev-Testing-WiFi-tether-for-i5700-Eclair-u
pd-19.04.

We also had to use his dhd.ko, as ours doesn't support netfilters, our dhd.ko 
caused
the phone to reboot if the kernel had netfilters.

For some reason or other our dhd.ko and rtecdc.bin doesn't allow the 
communication
needed to tether, but Leshak does, and they work great in the moment. 

With these files changed yes I can use any version of your app, however without
changing them I can't.

If you want the files, I can upload them for you, Does this site support 
uploading zip?

Original comment by vampir...@gmail.com on 27 May 2010 at 10:55

GoogleCodeExporter commented 9 years ago
It's now possible to have more than one rtecdc.bin-file on the system and I've 
implemented rules/a new strategy on how to load it.

1) Loading from sdcard: If you put the rtecdc.bin-file (which is needed for 
adhoc) to 
"/sdcard/android.tether/rtcdc.bin" this file is loaded and not the one in 
/system/etc. If this file does not exist ...
2) Loading alternative rtecdc.bin from /system/etc. If the file 
"/system/etc/rtecdc_adhoc.bin" (which can coexist beside the original one) 
exists, it 
will be loaded.
3) If the files for 1) and 2) are missing. The "original" 
("/system/etc/rtecdc.bin") 
is taken.

This should be implemented in the latest -pre-version available here:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre13.apk

I think we are not allowed to distribute the rtcdc.bin (copyright) that's why 
we are 
not going to integrate that file into our app.

Please check above version. Thanks.

Original comment by harald....@gmail.com on 28 May 2010 at 11:37

GoogleCodeExporter commented 9 years ago
Thanks that will do it, I looked over the code and yes it works well, we had 
been
renaming the original rtecdc.bin to rtecdc.bin.bak or rtecdc.org, but your 
ideal is
better using from sdcard or renaming the new rtecdc.bin to rtecdc_adhoc.bin so 
both
rtecdc files can coexist in /system/etc.

Thanks again 
Vampirefo

Original comment by vampir...@gmail.com on 29 May 2010 at 12:42

GoogleCodeExporter commented 9 years ago
Great. Thank you for testing. Will add your name as contributor :-)
http://code.google.com/p/android-wifi-tether/source/diff?
spec=svn444&r=444&format=side&path=/trunk/res/layout/aboutview.xml

Original comment by harald....@gmail.com on 29 May 2010 at 1:11