Open GoogleCodeExporter opened 9 years ago
Which device-profile (app settings) did you select?
Original comment by harald....@gmail.com
on 23 Aug 2011 at 1:39
I tried using specified settings for "Droid 2" and also left the settings on
"Auto" and neither worked. However the old version works PERFECT right "out of
the box". Fantastic software by the way!!! Much faster online then I had ever
anticipated! If you have some suggestions on settings please let me know.
Original comment by Supercha...@gmail.com
on 23 Aug 2011 at 9:20
I'm having the same problem on a Droid 2 Global, using Fission 2.4.3. I tried
changing several settings, such as ad-hoc vs. master, to no effect. (Actually,
ad-hoc reported an error).
As with the reporter, 2.0.7 version works perfectly for me.
I've attached a log (via alogcat) of starting WiFi Tether, and for comparison a
log of starting the older Wireless Tether.
Original comment by fastcat@gmail.com
on 25 Aug 2011 at 4:04
Attachments:
Droid Global 2 same issue as with others 2.0.7 version works
Original comment by Runt.Pac...@gmail.com
on 30 Aug 2011 at 5:49
I need some additional info for debugging ...
1) Install the latest beta.
2) Start/stop tethering (via gui) at least once.
3) Connect to your phone via adb
adb shell
4) Change directory ...
cd /data/data/com.googlecode.android.wifi.tether/bin
5) Start from tether from command-line:
./tether start
6) You will see some additional output. Please post it here.
And ...
Please update the generated config-file (start/stop tethering at least once to
make sure the file was updated) - it's located ...
/data/data/com.googlecode.android.wifi.tether/conf/tether.conf
Thanks.
Original comment by harald....@gmail.com
on 30 Aug 2011 at 6:51
Original comment by harald....@gmail.com
on 30 Aug 2011 at 6:52
Same issue with D2G and 2.0.7 and Beta6. Will try to generate debugging info.
Original comment by jbierl...@gmail.com
on 1 Sep 2011 at 1:34
# ./tether start
./tether start
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -N wir
eless-tether]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -F wir
eless-tether]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -F FOR
WARD]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat
-F PREROUTING]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat
-F POSTROUTING]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat
-F]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wir
eless-tether -m state --state ESTABLISHED,RELATED -j ACCEPT]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wir
eless-tether -s 192.168.2.0/24 -j ACCEPT]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wir
eless-tether -p 47 -j ACCEPT]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wir
eless-tether -j DROP]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A FOR
WARD -m state --state INVALID -j DROP]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A FOR
WARD -j wireless-tether]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat
-I POSTROUTING -s 192.168.2.0/24 -j MASQUERADE]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/dnsmasq -i tiwl
an0 --dhcp-authoritative --no-negcache --user=root --no-resolv --no-hosts --serv
er=8.8.8.8 --server=8.8.4.4 --dhcp-range=192.168.2.100,192.168.2.108,12h --dhcp-
leasefile=/data/data/com.googlecode.android.wifi.tether/var/dnsmasq.leases --pid
-file=/data/data/com.googlecode.android.wifi.tether/var/dnsmasq.pid]
script result was []
Original comment by josh3...@gmail.com
on 9 Sep 2011 at 7:30
I have the same problem (droid 2 froyo 2.3). I turn it on with settings for
droid 2 and nothing can detect the tether. I've tried all beta and the new
download and still nothing. The 2.0.7 also works the best for me right now.
Original comment by xthebegi...@gmail.com
on 2 Nov 2011 at 3:51
Same issue here. I'm running gingerbread on the Droid 2 Global and heard the
new betas get around Verizon's tether detection. It isn't transmitting with the
betas though and only transmits with my 2.0.7 version...which directs me to
verizon's tethering page.
Original comment by vincetl...@gmail.com
on 10 Nov 2011 at 3:47
The beta11 is working for mine ! Is it working for everyone?
Original comment by xthebegi...@gmail.com
on 21 Jan 2012 at 11:49
I'm posting this from my D2G tethered to a Win7 laptop, working for me, hooray!
FWIW, I installed beta 11 fresh (had previously uninstalled it, so no settings
carried over), and the only settings I changed were the SSID name and enabling
encryption.
Original comment by fastcat@gmail.com
on 6 Feb 2012 at 4:42
Access control does not seem to work ... Once I add my laptop to the access
control list, the next time I enable tethering, I get an error, but all it says
in "show log" is that it failed to enable access control.
Running "tether start" through a shell, the final bit of startup is what seems
to fail:
...tether/bin/iptables -t nat -I PREROUTING -s 192.168.2.0/24 -j DROP
getsockopt for multiport...<x4>
iptables: No chain/target/match by that name
Running that iptables command manually doesn't produce any errors, however
running the iptables command used to whitelist a mac address (iptables -t nat
-I PREROUTING -m mac --mac-source xx:xx:xx:xx:xx:xx -j ACCEPT) does fail with
that iptables error.
Original comment by fastcat@gmail.com
on 6 Feb 2012 at 5:06
Original issue reported on code.google.com by
Supercha...@gmail.com
on 23 Aug 2011 at 3:51