I have a Blu Dash 4.5 Android version 4.2.1 Kernel version 3.4.5. It has the tether plus bluetooth WI-FI hotspot all
there. Linux lite see it but does not get ff to work. What do I need to do to get it to work?
$ ifconfig -a
eth0 Link encap:Ethernet HWaddr bc:ae:c5:d9:b7:ca
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::beae:c5ff:fed9:b7ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3691 errors:0 dropped:0 overruns:0 frame:0
TX packets:2970 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3380406 (3.3 MB) TX bytes:422360 (422.3 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:833 errors:0 dropped:0 overruns:0 frame:0
TX packets:833 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:71508 (71.5 KB) TX bytes:71508 (71.5 KB)
usb0 Link encap:Ethernet HWaddr 82:68:04:d8:56:3f
inet6 addr: fe80::8068:4ff:fed8:563f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:6179 (6.1 KB)
Posts: 1,149
Threads: 22
Joined: Feb 2014
Reputation:
0
Hello!
Your phone COULD be 'timing out' the cellular data connection to save power. On MY phone, I have to use an app called Battery Booster to set the phone to 'Basic Saving Mode'. This keeps the data connection alive.
I have a similar phone (BLU Advance 4.0), and I tether (and hotspot!) on it using LL from time to time without issues - even on Net10.
NB: On Net10/StraightTalk phones bought from retail outlets, these features are disabled in the ROM by the carrier - another reason to Bring Your Own Phone to Net10, StraightTalk, etc.
On the phone, I have USB debugging enabled, disable WiFi, go to System Settings > More (under Data Usage) > Tethering & Portable Hotspot, and check 'USB tethering'. In LL on MY PCs, this shows up as 'Wired Connection 1'.
Since Linux and Android use the same default TTL (time-to-live) for IP packets (64ms), it shouldn't be giving you a problem. In this case, cellular carriers can't tell whether you're on the PC or on the phone, since the IP packets share the same TTL.
Another little tidbit: if you change your default TTL in Windows from 128ms to 64ms, you can ALSO tether to a Windows PC with an Android phone. Google it to see exactly how, but it involves adding a registry entry to specify the DefaultTTL to be 64ms on the Windows box. Again, they think you're on the phone.
I wouldn't be caught dead owning one, but I imagine this would also work on a FruitPhone (iPhone) but setting the default TTL to that of a FruitPhone, but not sure how to do that in Linux...
73 DE N4RPS
Rob
A gun in your hand is worth more than a whole police force on the phone.
It shows up like you said but can't get the firefox to run off it. As you can see above it sees it.
Posts: 1,149
Threads: 22
Joined: Feb 2014
Reputation:
0
Hello!
Under your usb0 (your phone), I see it returning an IPv6 address for the phone, but no IPv4 address. (I don't use IPv6 here at all, but I see an IPv4 address for your LAN connection.)
Here's MY usb0, which, when the tethering cable is connected, spins the network indicator in a circle as soon as I select 'USB tethering' on the phone, then connects as 'Wired connection 2', and shows up that way on the menu that comes up when the network icon is left-clicked:
usb0 Link encap:Ethernet HWaddr ae:c5:84:f8:38:5d
inet addr:192.168.42.64 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::acc5:84ff:fef8:385d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1930 (1.9 KB) TX bytes:14003 (14.0 KB)
Right-click on the network icon on the taskbar and select 'Edit connections'. Select the connection for your phone. Is the 'Available to all users' box checked? It COULD be THAT, but I doubt it.
I use 32-bit LL on this laptop; I'll try things out with the 64-bit version. My BLU is software-rooted (Framaroot), but that shouldn't make a difference, as all this worked for me before I rooted the phone.
Unless someone else steps in with more insight than I have, I THINK this pretty much covers all the bases, as RNDIS support is built into the kernel, UIAM...
73 DE N4RPS
Rob
A gun in your hand is worth more than a whole police force on the phone.
usb0 Link encap:Ethernet HWaddr 82:68:04:d8:56:3f
inet6 addr: fe80::8068:4ff:fed8:563f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:6179 (6.1 KB)
You have:
inet addr:192.168.42.64 Bcast:192.168.42.255 Mask:255.255.255.0
as you can see I do not. Would that make a difference?
I do not know what I did but I got it to work:
:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr bc:ae:c5:d9:b7:ca
inet6 addr: fe80::beae:c5ff:fed9:b7ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:833073 errors:0 dropped:0 overruns:0 frame:0
TX packets:446630 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1185635451 (1.1 GB) TX bytes:38942686 (38.9 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:5739 errors:0 dropped:0 overruns:0 frame:0
TX packets:5739 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:519216 (519.2 KB) TX bytes:519216 (519.2 KB)
usb0 Link encap:Ethernet HWaddr 16:3c:2c:8a:14:c0
inet addr:192.168.42.118 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::143c:2cff:fe8a:14c0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4461 errors:1 dropped:0 overruns:0 frame:1
TX packets:3704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4224926 (4.2 MB) TX bytes:786727 (786.7 KB)
It has this in there now;
inet addr:192.168.42.118 Bcast:192.168.42.255 Mask:255.255.255.0
I just noticed that it was using my phones WIFI for the tethering.
So not yet solved
Posts: 1,149
Threads: 22
Joined: Feb 2014
Reputation:
0
Hello!
Since you're able to set up SOME KIND connection through the phone, you're almost there. Just turn off WiFi on the phone, make sure the phone's cellular data connection is enabled, and you SHOULD be 'good to go'.
Once you make it all the way there, I hope your sister enjoys it!
73 DE N4RPS
Rob
A gun in your hand is worth more than a whole police force on the phone.