Tethering worked for me just once, through wifi. Now, everytime my laptop, or any device connects to my O1 it doesn't detect the internet even if I am able to browse on the phone through my 3G connection.
I can ping the phone's ip address and access shared folders on my laptop through ex file manager so I know the connection is there. Somehow, though, the Internet isn't going through.
My other concern is how this thing manages the sd card. Ever since I bought this, as long as there are no apps installed to the sd, my phone works perfectly fine. Once I move any app to it, though, weird things start happening... like the phone reboots randomly, or freezes, or the sd card unmounts and remounts without loading the apps on it, forcing me to do a manual un/remount or reboot.
I tested this by moving all apps back to internal. 2 days passed with no reboots. Then I moved just one app to the sd and let it sit. No more than 30 mins, the startup sound alerted my attention.
Except flashing custom roms, which I refuse to do until stock works fine, I've already done most of the suggestions I could find floating here on xda and other forums... rooting,unrooting, clearing cache, factory reset, reformatting sd card and so forth... so I was wondering what else I could do to fix these problems.
Phone has been up now for almost a week without rebooting after I took the app out of the card and back to internal. But I don't see the sense of having external memory if the phone goes crazy with apps on it.
Otherwise, it's a perfectly decent phone.
Sent from my LG-P500 using Tapatalk
do you have Data enabled in mobile network settings?
Omnichron said:
do you have Data enabled in mobile network settings?
Click to expand...
Click to collapse
Of course. I can browse on the phone.
Sent from my LG-P500 using Tapatalk
it could be a firewall issue or protocol setting on the laptop nic.
if you have ipv6(NIC Properties) installed remove it and try the connection again.
Omnichron said:
it could be a firewall issue or protocol setting on the laptop nic.
Click to expand...
Click to collapse
If it was, then theoretically, mobile phones should be able to use my data connection, right? I've had my friends connect with their mobiles and tablets... they get the ip address but not the juice.
Sent from my LG-P500 using Tapatalk
try updating or downgrading wifi tether
http://code.google.com/p/android-wifi-tether/downloads/list
Will try it out. Thanks!
Sent from my LG-P500 using Tapatalk
And that worked like a charm without changing any setting on my laptop. although, i noticed that it asked for su on android.tether. What makes this one special?
Sent from my LG-P500 using Tapatalk
I would like to up this post and ask about the initial concern again. Wifi Tether works like a beauty, but I noticed it's an ad-hoc network. Not all devices see my "router".
So back to the original concern of using the built-in Wifi Tethering of this O1... why can't I get any internet on the devices that are able to connect to it? Again, the I.P. address is correct, but there is no Internet connection.
Well, no info here... so. The usual network troubleshooting drill, like...
Code:
ipconfig /all
route print
(on Windows boxes)
Code:
ip address show
ip route print
(on your phone, either via terminal emulator or via adb shell).
doktornotor said:
Well, no info here... so. The usual network troubleshooting drill, like...
Click to expand...
Click to collapse
If by info you mean what kind of phone, it's a rooted stock P500 v10b.
I already mentioned in previous posts that the ip addresses report fine. Again, all devices can connect to the built-in tether, they get correct ip addresses but just no internet. It worked just once when it was new. Never again after that, even after the first factory reset.
But here's what terminal says.
Code:
$ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN
link/ether 9e:4d:23:e2:28:ec brd ff:ff:ff:ff:ff:ff
3: rmnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 76:e2:a8:76:3e:3a brd ff:ff:ff:ff:ff:ff
inet 10.115.27.234/30 brd 10.115.27.235 scope global rmnet0
inet6 fe80::74e2:a8ff:fe76:3e3a/64 scope link
valid_lft forever preferred_lft forever
4: rmnet1: <BROADCAST,MULTICAST> mtu 2000 qdisc noop state DOWN qlen 1000
link/ether a6:b7:7a:3e:5f:00 brd ff:ff:ff:ff:ff:ff
5: rmnet2: <BROADCAST,MULTICAST> mtu 2000 qdisc noop state DOWN qlen 1000
link/ether e6:52:c0:53:21:df brd ff:ff:ff:ff:ff:ff
6: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 96:02:b8:f4:38:65 brd ff:ff:ff:ff:ff:ff
7: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
8: ip6tnl0: <NOARP> mtu 1460 qdisc noop state DOWN
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
23: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 5c:da:d4:79:39:37 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5eda:d4ff:fe79:3937/64 scope link
valid_lft forever preferred_lft forever
24: wl0.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 5c:da:d4:79:39:37 brd ff:ff:ff:ff:ff:ff
inet 192.168.43.1/24 brd 192.168.43.255 scope global wl0.1
inet6 fe80::5eda:d4ff:fe79:3937/64 scope link
valid_lft forever preferred_lft forever
$ip route
202.126.40.5 dev rmnet0
222.127.143.5 dev rmnet0
10.115.27.232/30 dev rmnet0 src 10.115.27.234
192.168.43.0/24 dev wl0.1 src 192.168.43.1
default via 10.115.27.233 dev rmnet0
$
Well, what do you mean by "no internet".
E.g., what does the following produce (on Windows)?
Code:
> tracert www.google.com
> tracert 209.85.143.99
doktornotor said:
Well, what do you mean by "no internet".
Click to expand...
Click to collapse
Doesn't that usually mean that I can't go online the normal way?
On windows, tracert www.google.com doesn't do anything. Surprisingly, it worked for the I.P. address. Browsing using I.P. addresses works, as well.
That being said, I think there's a problem with the way the built-in tethering handles DNS server numbers, which is why none of the devices that connect to it is able to connect through to the internet.
Any ideas on why this is happening? Or how to fix?
androidmeda said:
Doesn't that usually mean that I can't go online the normal way?
On windows, tracert www.google.com doesn't do anything. Surprisingly, it worked for the I.P. address. Browsing using I.P. addresses works, as well.
Click to expand...
Click to collapse
Go online the normal way does not really mean much either, so - no. Internet != web browsing.
Meanwhile, since your DNS is apparently not working properly, stick 8.8.8.8 and 8.8.4.4 (Google public DNS) to the TCP/IP settings on the clients and it will work.
"built-in tethering handles DNS server numbers" - those are IP addresses. If you can ping/traceroute using DNS names (like www.google.com) from the phone, then obviously your clients are not getting the proper DNS servers assigned from the phone via DHCP server.
For further debugging, you need to post which DNS servers are being used on the phone and whether those match the ones assigned to the WiFi clients (or if any are assigned at all). Again, ipconfig /all or whatever similar according to the clients OS.
Using built-in tethering, I checked the DNS server assigned to a windows client, it's the same as the ip address it got from the phone. No browse using urls. Pings are ok, tracert only works if I use the ip address as shown on the ping, and I can browse to a website if I use the ip instead.
Using Wireless Tether, the DNS server is the same as the assigned ip address, but I'm able to browse and tracert using urls.
The only reason I'm trying to get built-in to work is because not all devices can detect Wireless Tether's adhoc network. Even a fellow Optimus One can't see it. (On a side note, I can't detect wireless adhoc networks, either.)
I don't know how to check the DNS assigned to the phone. But looking at ip route, it's probably the first two numbers.
Code:
#ip route
202.126.40.5 dev rmnet0
222.127.143.5 dev rmnet0
10.31.40.196/30 dev rmnet0 src 10.31.40.198
10.10.1.0/24 dev wlan0 src 10.10.1.254
default via 10.31.40.197 dev rmnet0
#
Up until the time Wireless Tether will be able to start as a true access point, I will be wondering what's going on with the built-in.
If assigning a DNS server to a client would work, that still doesn't address the fact that you can't manually assign DNSs on all devices.
Sent from my LG-P500 using Tapatalk
androidmeda said:
Using built-in tethering, I checked the DNS server assigned to a windows client, it's the same as the ip address it got from the phone.
Click to expand...
Click to collapse
I do not understand. Their DNS is set to their local IP address? Well, that obviously cannot work unless you install a DNS server on the computer.
androidmeda said:
Using Wireless Tether, the DNS server is the same as the assigned ip address, but I'm able to browse and tracert using urls.
Click to expand...
Click to collapse
Errr, what? Please post the settings, the above plain does not make sense to me, do not understand what you saying there.
androidmeda said:
I don't know how to check the DNS assigned to the phone.
Click to expand...
Click to collapse
Here:
Code:
$ cat /system/etc/resolv.conf
doktornotor said:
I do not understand. Their DNS is set to their local IP address? Well, that obviously cannot work unless you install a DNS server on the computer.
Click to expand...
Click to collapse
I'm sorry, I meant to say it's the same as the default gateway. Here's how ipconfig /all looks like on my laptop on Wireless Tether. I can browse and do anything online.
Code:
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter
Physical Address. . . . . . . . . : 00-1F-E1-4C-56-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.10.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, May 29, 2011 10:13:47 PM
Lease Expires . . . . . . . . . . : Monday, May 30, 2011 9:59:53 AM
Default Gateway . . . . . . . . . : 10.10.1.254
DNS Servers . . . . . . . . . . . : 10.10.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
And here's how it looked like on built-in tether. No browse.
Code:
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter
Physical Address. . . . . . . . . : 00-1F-E1-4C-56-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.43.25(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, May 29, 2011 10:32:56 PM
Lease Expires . . . . . . . . . . : Sunday, May 29, 2011 11:32:55 PM
Default Gateway . . . . . . . . . : 192.168.43.1
DHCP Server . . . . . . . . . . . : 192.168.43.1
DNS Servers . . . . . . . . . . . : 192.168.43.1
NetBIOS over Tcpip. . . . . . . . : Enabled
I tried putting google's public dns on the wireless network connection's tcp/ip v4 properties, but it still came up with no browse, no ping, tracert ok on ip address.
By the way, cat /system/etc/resolv.conf doesn't exist on the phone according to terminal emulator. I checked with root explorer as well to confirm.
Unless there is a running DNS server/proxy on the default GW, it will not work. Check with nslookup or whatever similar tool.
/system/etc/resolv.conf does not exist? I do not understand how are you able to browse anything from your phone then. It specifies the DNS servers the phone is using.
I tried putting google's public dns on the wireless network connection's tcp/ip v4 properties, but it still came up with no browse, no ping, tracert ok on ip address.
Click to expand...
Click to collapse
Getting totally lost here. Why on wireless? By "built-in" tether you mean you connect the phone via USB cable? Well, that does not use wireless at all, so setting any DNS there will not do any good.
Oh well, to sum this up - if you devices cannot see an ad-hoc wifi network, those are broken, not the phone. Messing with USB cable and internet connection sharing on your PC is just a waste of time, IMHO.
doktornotor said:
/system/etc/resolv.conf does not exist? I do not understand how are you able to browse anything from your phone then. It specifies the DNS servers the phone is using.
Click to expand...
Click to collapse
I don't understand it either.
Getting totally lost here. Why on wireless? By "built-in" tether you mean you connect the phone via USB cable? Well, that does not use wireless at all, so setting any DNS there will not do any good.
Click to expand...
Click to collapse
Froyo has its own wireless tethering, right? That's what I'm trying to get working.. and that's what I'm working on. By the way, USB tethering doesn't work AT ALL.
Oh well, to sum this up - if you devices cannot see an ad-hoc wifi network, those are broken, not the phone. Messing with USB cable and internet connection sharing on your PC is just a waste of time, IMHO.
Click to expand...
Click to collapse
Total of three brand new Optimus Ones, all unable to see different adhoc networks that work on other wireless-capable devices (this laptop and an iProduct)? I'm just not seeing how the adhoc networks are broken.
It might be a waste of time for you, but this is the way I use the internet at home: my laptop tethered to my phone. I'll probably just wait for Wireless Tether to upgrade to access-point capacity.
Thanks for helping me out with this!
Hi everyone,
I have a little problem that I don't know how to solve, nor diagnose as I lack some knowledge.
I have a linksys E3000 router. I installed one of the many Tomato firmware flavors that has bundled VPN server. I managed to configure the server, generated the keys ca,client etc. Everything seems to work fine from a PC. I also run the latest cyanogenmod nightly on my Hero. I managed to solve or let's say find out how to install the certificates onto the system (add the ca.crt, client.crt, client.key into a .pk12 openssl package). Then I used the default CM configuration assitant to configure the connection and it works, or at least it connects and I can see that the conection was succesful on my router GUI.
Now, the problem is that even if it says connected (a small key at status bar), I can't do anything, no web browsing, no android market connection, nothing that involves traffic. I don't know what is the problem, or how to diagnose, log or something. Any help would be apreciated.
Thank you.
My router vpn server configuration:
Interface Type TAP
Protocol UDP
Port 1194
Firewall Automatic
Authorization Mode TLS
Extra HMAC authorization (tls-auth) Disabled
Client address pool DHCP
--------------------------------
Direct clients to redirect Internet traffic (tick)
Encryption cipher Default
Manage Client-Specific Options (tick)
Allow Client<->Client (tick)
My HTC Hero configuration:
-Basic
Name (some i chose)
VPN server (a dyndns host, the router updates the ip automatically)
User authentication (unticked)
CA certificate (the pk12 file i created)
CLIENT certificate (the pk12 file i created)
DNS search domains (unchanged)
-Advanced:
Server port 1194
Protocol to use udp
Device to use tap
LZO compression (unticked)
Redirect gateway (ticked)
Remote Sets Adresses (ticked)
Local IP Adress (faded)
Remote IP Adress (faded)
Chipher algorithm default
Size of cipher key default
Extra arguments unchanged
Hello every body,
This is my first post here
I had rooted my Xperia S two days ago and since then I am exploring my root capabilities.
I wrote a script to hook my Xperia S to my LAN Via USB.
Here is what I did.
1-connect Xperia S to PC in Regular USB Tethering mode.
2-bridge the network adapter form the phone with PC LAN Adapter and set IPv4 Settings Manually.
3-Run the following script on the phone.
Code:
ifconfig rndis0 192.168.1.99
ip route add 0.0.0.0/0 via 192.168.1.1 dev rndis0
ip route add 0.0.0.0/0 via 192.168.1.1 dev rndis0 metric 213
ip route del 192.168.1.0/24
ip route add 192.168.1.0/24 via default dev rndis0 proto kernel scope link src 192.168.1.99 metric 213
ip route add 192.168.1.1 via default dev rndis0 scope link
setprop net.nds1 8.8.8.8
setprop net.nds2 8.8.4.4
here I tried to mimic the same routing table form regular WIFI connection.
And it WORKS!!
but with a strange behavior.
After these steps I try to ping PC (form phone) and it is Unreachable, and the gateway is the same.
But after I reverse the operation and ping the phone from PC and from the gateway, the network operates normally , and phone pings through the gateway to the internet. also , I can receive streams from my PC and Access my mobile's FTP server , stock browser works.
But the Market cannot download apps , Maps cannot load.
I wonder why This is happening?
If you have an answer , I would be delighted to know it.
Thank You.
Maps cannot load.
Click to expand...
Click to collapse
It did load after some time , it needed patience , although it popped up "Data Connection not Available".
After these steps I try to ping PC (form phone) and it is Unreachable, and the gateway is the same.
But after I reverse the operation and ping the phone from PC and from the gateway, the network operates normally , and phone pings through the gateway to the internet.
Click to expand...
Click to collapse
Since it worked after it was pinged and learned MAC addresses.
I think there is a problem in layer 2, for some reason it cannot send ARP requests.
Success
After Upgrading to Windows 8 , The same script works as it should.
My Xperia S can now ping all network devices directly.
It seems that there was some thing wrong with My previous Win7.
But still there are some applications that can't deal with USB internet.
Google Play can navigate and search but can't download apps.
I think this topic was moved to inappropriate sub-forum (> Sony Xperia P, U, Sola, Go > Xperia P, U, Sola, Go General ) , it is related to Xperia S Please move it there.
Thank You.
In a browser google resolves to an address in the 208.54.0.0/16 IP address block (example 208.54.38.51). This range is not owned by Google as far I know and actually resolves to tmodns.net, which is owned by T-Mobile.
Looking through Afwall+ firewall logs shows that before connecting to any Google services, for example downloading an app through the play store, the phone connects with an IP in the same 208.54.0.0/16 range. Using IPTABLES to block this range prevents me from being able to do things like access Google in the browser and download apps through the play store.
If I start transparent proxying through Tor I can connect to Google correctly as well as download apps with no problems.
Can anyone confirm that this happens on their T-Mobile phone? Is there anyway I can prevent this without having to go through Tor? Perhaps by using IPTABLES to redirect any connections to the 208.54.0.0/16 block to an IP owned by Google.
I also have my DNS set to use Google's DNS servers so that shouldn't be the issue. It seems like it's happening inside of T-Mobile's internal 10.*.*.* network before the phone connects to the outside Internet.
Code:
[email protected]:/ $ nslookup google.com
Server: 8.8.4.4
Address 1: 8.8.4.4 google-public-dns-b.google.com
Name: google.com
Address 1: 2404:6800:4005:c00::64
Address 2: 208.54.38.49 m312636d0.tmodns.net
Address 3: 208.54.38.48 m302636d0.tmodns.net
Address 4: 208.54.38.53 m352636d0.tmodns.net
Address 5: 208.54.38.57 m392636d0.tmodns.net
Address 6: 208.54.38.51 m332636d0.tmodns.net
Address 7: 208.54.38.54 m362636d0.tmodns.net
Address 8: 208.54.38.50 m322636d0.tmodns.net
Address 9: 208.54.38.59 m3b2636d0.tmodns.net
Address 10: 208.54.38.55 m372636d0.tmodns.net
Address 11: 208.54.38.52 m342636d0.tmodns.net
Address 12: 208.54.38.56 m382636d0.tmodns.net
Address 13: 208.54.38.58 m3a2636d0.tmodns.net
[email protected]:/ $ nslookup google.com 66.244.95.20
Server: 66.244.95.20
Address 1: 66.244.95.20 brian-vm.suso.org
Name: google.com
Address 1: 2404:6800:400a:803::1008
Address 2: 208.54.38.49 m312636d0.tmodns.net
Address 3: 208.54.38.48 m302636d0.tmodns.net
Address 4: 208.54.38.53 m352636d0.tmodns.net
Address 5: 208.54.38.57 m392636d0.tmodns.net
Address 6: 208.54.38.51 m332636d0.tmodns.net
Address 7: 208.54.38.54 m362636d0.tmodns.net
Address 8: 208.54.38.50 m322636d0.tmodns.net
Address 9: 208.54.38.59 m3b2636d0.tmodns.net
Address 10: 208.54.38.55 m372636d0.tmodns.net
Address 11: 208.54.38.52 m342636d0.tmodns.net
Address 12: 208.54.38.56 m382636d0.tmodns.net
Address 13: 208.54.38.58 m3a2636d0.tmodns.net
Because I'm blocking the 208.54.0.0/16 IP range in the iptables I can't connect to Google unless I use a direct IP like 74.125.228.3 for example.
Earlier today it started working correctly but soon went back to the way described in my first post.
I did a nslookup using two different DDNS servers.
When I run a traceroute, with or without the firewall enabled, it hops through T-Mobile's network then dies before even reach the T-Mobile tmodns.net Google server.
I'm just curious this of ordinary behavior for T-Mobile. I would rather directly connect to Google owned IP addresses.
Code:
[email protected]:/ $ su
traceroute -v google.com
traceroute to google.com (208.54.38.52), 30 hops max, 38 byte packets
1 10.170.227.192 (10.170.227.192) 36 bytes to (null) 236.960 ms 286.452 ms 269.902 ms
2 10.170.227.137 (10.170.227.137) 76 bytes to (null) 279.829 ms 319.824 ms 329.807 ms
3 10.162.37.124 (10.162.37.124) 36 bytes to (null) 269.846 ms 249.833 ms 259.821 ms
4 10.162.37.113 (10.162.37.113) 76 bytes to (null) 259.902 ms 279.785 ms 259.878 ms
5 10.170.205.11 (10.170.205.11) 76 bytes to (null) 659.813 ms 269.880 ms 259.800 ms
6 10.177.17.125 (10.177.17.125) 76 bytes to (null) 629.853 ms 269.756 ms 369.844 ms
7 10.177.26.106 (10.177.26.106) 36 bytes to (null) 329.907 ms 539.814 ms 683.135 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *