|
Batteries included
-
SumTingWong
- Posts: 24
- Joined: 14 Oct 2015, 13:19
Post
by SumTingWong » 19 Mar 2016, 15:43
Hello.
Android 5.0 Lollipop. SuperSU 2.65 rooted using TWRP.
Modem is connected to external power. Tablet connected with OTG cable.
Everything looks perfectly normal. The connection happens, the light goes blue and stays blue when connected.
However, nothing sees the connection. K9 doesn't work. Play doesn't work. Chrome doesn't work. Even fake WiFi Xposed mod does not change anything.
Code: Select all 18 Mar 2016 20:52:27
Start chat sequence for dialling ...
>
ATE0
<
OK
>
AT+CPIN?
<
+CPIN: READY
OK
>
AT+CFUN?
<
OK
>
AT+CGDCONT=1,"IP","plus"
<
OK
>
ATD*99***1#
<
CONNECT
====
Dialling complete
Now start PPP negotiation ...
>
ff03c021010000140206000000000506f7adb02907020802a565
<
ff03c021010000190206000000000305c22305050600c9128c070208026bb9
>
ff03c021030000080304c023f7d7
<
ff03c021020000140206000000000506f7adb029070208024e0c
<
ff03c021010100180206000000000304c023050600c9128c07020802798c
>
ff03c021020100180206000000000304c023050600c9128c07020802b561
>
c0230101000600003b3f
<
ff03c0210b02000800c9128cae2c
<
c0230201000500fd30
>
802101000016030600000000810600000000830600000000627c
<
80210300001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0e0951
>
80210101002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0efcc6
<
80210301001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0e4103
>
80210102002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0e5906
<
80210302001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0e99f5
>
80210103002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0e3a46
<
80210303001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0ed1a7
>
80210104002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0e028f
<
80210304001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0e3810
>
80210105002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0e61cf
<
80210305001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0e7042
>
80210106002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0ec40f
<
80210306001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0ea8b4
>
80210107002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0ea74f
<
80210307001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0ee0e6
>
80210108002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0ea595
<
80210308001c81060a0b0c0d83060a0b0c0e82060a0b0c0d84060a0b0c0e6bd3
>
80210109002203060000000081060a0b0c0d82060a0b0c0d83060a0b0c0e84060a0b0c0ec6d5
<
80210409001082060a0b0c0d84060a0b0c0ebe83
<
80210100000467c3
>
802102000004aae6
<
802101010004bb99
>
80210201000476bc
(IPCP Timer up, 1000 ms)
>
8021010a001603060000000081060a0b0c0d83060a0b0c0e9a99
<
8021030a001603060a77c6cb8106d40260358306d4026036f087
>
8021010b001603060a77c6cb8106d40260358306d402603637ea
<
8021020b001603060a77c6cb8106d40260358306d4026036c119
Local IP: 10.119.198.203
Peer IP: 10.64.64.64
DNS1: 212.2.96.53
DNS2: 212.2.96.54
Send initial IP packet ...
First IP packet received - we are online
PPP negotiation finished
18 Mar 2016 20:52:00
Device manufacturer string: LENOVO
New device on /dev/bus/usb/001/004
Device ID 12d1:1001
Device top dir: /sys/bus/usb/devices/1-1, active cfg: 1
Device layout (current config) - cl:00 sc:00 pr:00
if:0 as:0 - cl:ff sc:ff pr:ff - ir:81 bi:82 bo:02
if:1 as:0 - cl:ff sc:ff pr:ff - bi:84 bo:04
if:2 as:0 - cl:ff sc:ff pr:ff - bi:85 bo:05
Found vendor-specific interface
Load VendorSpec driver, configuration 0
Device ready for modem initialization, using iface 0
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 19 Mar 2016, 21:47
Let me check this on my own A7-10F. I don't think the modem is to blame, the PPP connection is up.
Maybe it's something with the network routes.
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 19 Mar 2016, 23:31
I just attached my Huawei E173 to the A7-10 with a Vodafone SIM. Works well.
Note that I 'froze' the Tedongle app (with Titanium Backup) and renamed the "dongled" tool in /system/bin to "off.dongled" - which should disable it.
-
SumTingWong
- Posts: 24
- Joined: 14 Oct 2015, 13:19
Post
by SumTingWong » 20 Mar 2016, 00:01
I tried renaming dongle but nothing changes.
Is it perhaps because of IPv6? The ip addr result shows the VPN tunnel not using IPv4 so maybe that's a problem?
Code: Select all u0_a91@Tab2A7-10F:/ $ su
root@Tab2A7-10F:/ # ip route
10.118.202.0/24 dev tun0 proto kernel scope link src 10.118.202.206
root@Tab2A7-10F:/ # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 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
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
link/ether 62:e5:75:af:fc:65 brd ff:ff:ff:ff:ff:ff
3: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
link/ether 0e:eb:b6:7c:5f:a4 brd ff:ff:ff:ff:ff:ff
4: tunl0: <NOARP> mtu 0 qdisc noop state DOWN
link/ipip 0.0.0.0 brd 0.0.0.0
5: sit0: <NOARP,UP,LOWER_UP> mtu 1492 qdisc noqueue state UNKNOWN
link/sit 0.0.0.0 brd 0.0.0.0
inet6 ::10.115.254.56/96 scope global
valid_lft forever preferred_lft forever
inet6 ::127.0.0.1/96 scope host
valid_lft forever preferred_lft forever
6: ip6tnl0: <NOARP> mtu 1452 qdisc noop state DOWN
link/tunnel6 :: brd ::
18: tun0: <POINTOPOINT,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN qlen 500
link/none
inet 10.118.202.206/24 scope global tun0
valid_lft forever preferred_lft forever
root@Tab2A7-10F:/ #
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 20 Mar 2016, 08:31
My "ip addr" output is identical - but what's not is the "ip route" result.
Your's is missing the "default" entry which is most likely the source of the problem. Try to enter
See if that makes a difference.
This is one of the commands that PPP Widget 2 issues to establish the network connection. I am somewhat perplexed that this did not work on your device ...
-
SumTingWong
- Posts: 24
- Joined: 14 Oct 2015, 13:19
Post
by SumTingWong » 20 Mar 2016, 10:16
Entering ip route add default dev tun0 did not fix the issue.
Here is ip monitor results when I tap connect in PPP 2.
Code: Select all root@Tab2A7-10F:/ # ip monitor
7: tun0: <POINTOPOINT,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN
link/none
7: tun0: <POINTOPOINT,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN
link/none
7: tun0: <POINTOPOINT,UP,LOWER_UP> mtu 1500
link/none
7: tun0: <POINTOPOINT,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN
link/none
7: tun0 inet 100.66.173.11/32 scope global tun0
valid_lft forever preferred_lft forever
local 100.66.173.11 dev tun0 table local proto kernel scope host src 100.66.173.11
Deleted 7: tun0 inet 100.66.173.11/32 scope global tun0
valid_lft forever preferred_lft forever
Deleted local 100.66.173.11 dev tun0 table local proto kernel scope host src 100.66.173.11
7: tun0 inet 100.66.173.11/24 scope global tun0
valid_lft forever preferred_lft forever
local 100.66.173.11 dev tun0 table local proto kernel scope host src 100.66.173.11
100.66.173.0/24 dev tun0 proto kernel scope link src 100.66.173.11
broadcast 100.66.173.0 dev tun0 table local proto kernel scope link src 100.66.173.11
broadcast 100.66.173.255 dev tun0 table local proto kernel scope link src 100.66.173.11
5: sit0: <NOARP> mtu 1492 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
5: sit0: <NOARP,UP,LOWER_UP> mtu 1492 qdisc noqueue state UNKNOWN
link/sit 0.0.0.0 brd 0.0.0.0
5: sit0 inet6 ::127.0.0.1/96 scope host
valid_lft forever preferred_lft forever
local ::127.0.0.1 dev lo table local proto none metric 0 5: sit0 inet6 ::100.66.173.11/96 scope global
valid_lft forever preferred_lft forever
local ::100.66.173.11 dev lo table local proto none metric 0
::/96 dev sit0 metric 256
5: sit0: <NOARP,UP,LOWER_UP> mtu 1492
link/sit 0.0.0.0
11000: from all iif tun0 lookup local_network
11000: from all iif tun0 lookup local_network
12000: from all fwmark 0xc0064/0xcffff lookup 1007
12000: from all fwmark 0xc0064/0xcffff lookup 1007
13000: from all fwmark 0x10064/0x1ffff uidrange 0-0 lookup 1007
13000: from all fwmark 0x10064/0x1ffff uidrange 0-0 lookup 1007
10.64.64.64 dev tun0 table 1007 proto static scope link
unreachable default dev lo table 1007 proto static metric 1024 error -101
12000: from all fwmark 0x0/0x20000 uidrange 0-99999 lookup 1007
12000: from all fwmark 0x0/0x20000 uidrange 0-99999 lookup 1007
13000: from all fwmark 0x10064/0x1ffff uidrange 0-99999 lookup 1007
13000: from all fwmark 0x10064/0x1ffff uidrange 0-99999 lookup 1007
14000: from all oif tun0 uidrange 0-99999 lookup 1007
14000: from all oif tun0 uidrange 0-99999 lookup 1007
And the ip route result after adding default route.
Code: Select all root@Tab2A7-10F:/ # ip route add default dev tun0
root@Tab2A7-10F:/ # ip route
default dev tun0 scope link
100.99.132.0/24 dev tun0 proto kernel scope link src 100.99.132.87
root@Tab2A7-10F:/ #
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 20 Mar 2016, 13:53
Ah, the command I recommended was not quite complete. On Lollipop, that should be
Code: Select all # ip route add default dev tun0 table tun0
My output of "ip monitor" when connecting is almost identical to your's - except for the last line:
Code: Select all ...
10.57.90.0/24 dev tun0 proto kernel scope link src 10.57.90.214
broadcast 10.57.90.0 dev tun0 table local proto kernel scope link src 10.57.90.214
broadcast 10.57.90.255 dev tun0 table local proto kernel scope link src 10.57.90.214
default dev tun0 table tun0 scope link
default dev tun0 scope link
11000: from all iif tun0 lookup local_network
11000: from all iif tun0 lookup local_network
12000: from all fwmark 0xc0066/0xcffff lookup 1008
12000: from all fwmark 0xc0066/0xcffff lookup 1008
13000: from all fwmark 0x10066/0x1ffff uidrange 0-0 lookup 1008
13000: from all fwmark 0x10066/0x1ffff uidrange 0-0 lookup 1008
10.64.64.64 dev tun0 table 1008 proto static scope link
unreachable default dev lo table 1008 proto static metric 1024 error -101
12000: from all fwmark 0x0/0x20000 uidrange 0-99999 lookup 1008
12000: from all fwmark 0x0/0x20000 uidrange 0-99999 lookup 1008
13000: from all fwmark 0x10066/0x1ffff uidrange 0-99999 lookup 1008
13000: from all fwmark 0x10066/0x1ffff uidrange 0-99999 lookup 1008
14000: from all oif tun0 uidrange 0-99999 lookup 1008
14000: from all oif tun0 uidrange 0-99999 lookup 1008
default dev tun0 table 1008 scope link
-
SumTingWong
- Posts: 24
- Joined: 14 Oct 2015, 13:19
Post
by SumTingWong » 20 Mar 2016, 15:00
Thank you. With # ip route add default dev tun0 table tun0 the connection works. So what other logs do you need to find what could be causing this bug?
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 20 Mar 2016, 16:56
I'm not sure logs are useful at this level ... Two mostly identical devices, one working (accepting the root commands), one not.
I would very much like to see the same problem on my device. We need to find the difference to yours.
One thing I noted is your SuperSU version. I'm running 2.46 here which is still the official release.
Apart from that, I assume you have the current stock ROM, build
T2-A7-10F_S000054-150801_ROW
(or slightly different ending).
-
SumTingWong
- Posts: 24
- Joined: 14 Oct 2015, 13:19
Post
by SumTingWong » 20 Mar 2016, 19:17
That's very odd. I updated my install using Google Play and the official version there is 2.65 without any mention that it's beta.
My ROM build is T2-A7-10F_S000054_150801_ROW.
I don't have my original stock system partition backed up. I'll just try flashing 2.46 using TWRP then.
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 20 Mar 2016, 19:37
You are correct - the version on Google Play is not announced as "beta" ...
I kept looking at this page:
https://download.chainfire.eu/696/SuperSU/
Maybe that is outdated?
Anyway, before you start to tamper with your system, let me install the latest version from Google Play first.
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 20 Mar 2016, 19:55
O.K., I updated SuperSU to the latest Google Play version level (had to "clean" it in its configuration to be able to update). Afterwards, it said "Have to update the 'su' binary"; I confirmed and got a success message and a recommendation to reboot, which I did.
However, it seems this was not the issue. My route is set as expected.
I remember having seen this issue in other reports. I always put it down to firmware changes by the manufacturer, but maybe the culprit is just annother app or a security setting.
-
SumTingWong
- Posts: 24
- Joined: 14 Oct 2015, 13:19
Post
by SumTingWong » 20 Mar 2016, 20:09
Is there anything I can test to narrow down what's causing this issue?
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 20 Mar 2016, 21:35
Any apps installed that could influence the system/network? Which ones are using root access?
|
|