Database Users

[Q] Phone keeps waking up - TyphooN CyanogenMod 7 vs. HyperDroidGBX-v12

I've gone from Typhoon CyanogenMod to HyperDroidGBX-v12 and it seems that Hyperdroid keeps connecting to wifi in intervals and waking up the phone which has taken a lot more battery over night than CyanogenMod did. I love the speed of Hyperdroid so I was wondering if there is anything I can do?
When I switched the phone on using Cyanogen I saw him switch off the mobile data connection and switch on wifi. Hyperdroid doesn't seem to manage it like that. Can I customize this?
edit: I found the option under wireless to switch if off when the phone is asleep but I don't think he's doing as he's told (my phone is male, in case you're wondering)...
I've attached a screen of my phone over night with HyperDroid. It kept waking up without the screen being on. I assume that's the root of all evil...
The only app that syncs on my phone atm is the GMail app, no facebook or others.
Any suggestions?
Thanks
edit:
I've searched some more and there were people who's wireless went to sleep when they didn't want it to, the opposite of my problem. I've done a clean install of HyperDroid again and the problem persists, at least the wireless not switching off. Since that worked with CyanogenMod I assume that's the root cause. I'm surprised this hasn't picked up on before, assuming other people have the same problem.
I guess I'd like to know if there are any simple file swaps I can perform like changing drivers between the two mods?
editv2:
Wireless seems to at least switch off now. I tried killing inactive apps. I'll see what happens from here.

Usually it's apps polling for updates.
This includes Facebook, Twitter etc. Are you using Google Latitude? That can wake the device every few minutes.
To check for wakelocks
Code:
cat /proc/wakelocks

It happened again last night that the phone appears awake for quite some time. I've got the wakelocks (which I don't know how to interpret). I'll post them and a screenshot of battery. I'm hoping to either hear a solution or that it's normal.
It seems like he had a much more quiet night tonight. I wish I had paid more attention to it while using Cyanogen. I've installed the battery current widget so that should be interesting as well.
Cheers.
Code:
name count expire_count wake_count active_since total_time sleep_time max_time last_cha
nge
"alarm" 957 0 0 0 23959014779 21546905463 384429936 9723528995498
"wlan_wake" 19027 0 49 0 86119018687 44324798717 1083984373 9683300205212
"main" 17 0 0 0 7736565871862 0 5511280593319 9680620426163
"event4-252" 34973 0 0 0 3475555677 0 6408692 9680155307754
"msmfb_idle_lock" 54032 0 0 0 4743530364 0 278686529 9680154453261
"ds2746-battery" 667 0 0 0 9070099039 8503753803 39886474 9679912631970
"alarm_rtc" 562 8 0 0 63026972383 63025843229 1034118654 8779276859239
"KeyEvents" 35993 0 0 0 4014678958 84869382 86914061 9679667270643
"event3-252" 216 0 0 0 124999996 73455813 16967773 9679666141493
"gpio_input" 52 0 9 0 528106698 122161869 10437012 9679665958387
"event5-252" 284 0 0 0 16235353 0 762939 9675881534557
"usb_mass_storage" 1 0 0 0 229509429930 0 229509429930 9228090579970
"power-supply" 135 0 0 0 70007320 41687016 2685547 9673667392715
"power-supply" 7 0 0 0 6774905 3875733 2532958 9673667209609
"power-supply" 7 0 0 0 10894774 2655028 5859375 9673667087539
"wlan_rx_wake" 1078 1078 0 0 1729369137961 185800921021 21577879641 9670940219862
"qmi" 17 17 0 0 8471907985 1995538327 509357909 9670940189344
"SMD_DATA5" 563 563 120 0 491717996183 412869000741 9329598383 9670940189344
"event0-252" 35776 0 0 0 2916259736 0 3112793 9603342624641
"gpio_kp" 83 0 2 0 14742034892 22491454 1275268561 9585008335097
"AudioHardwareQSDOut" 16 0 0 0 94738861105 704864502 20176086427 8977790592174
"audio_pcm_suspend" 14 0 0 0 211352722187 422058099 35328094487 8977790500621
"audio_pcm_idle" 14 0 0 0 211352630634 0 35328094487 8977790500621
"SMD_RPCCALL" 7382 0 555 0 636077998 468994259 26184081 8977783267956
"rpc_read" 214 0 0 0 6530761 457767 1831054 8977783237438
"ApmCommandThread" 56 0 0 0 1433898924 0 895629880 8825111423477
"radio-interface" 38 0 0 0 41765899679 4004455570 1961944580 8786906162243
"rpc_read" 4429 0 0 0 192779566 184631377 244141 8779275638536
"rpc-interface" 537 0 0 0 889831583 863678015 41290284 8239455598513
"rpc_read" 535 0 0 0 1028228754 170288083 348480225 8239453920046
"AudioHardwareQSDIn" 9 0 0 0 147654846199 0 32158020026 7760196196386
"proximity" 1 1 0 0 3892520753 0 3892520753 5763470148164
"event1-252" 8 0 0 0 274658 0 91552 5734318414763
"mmc_delayed_work" 3 2 0 0 13576922628 0 8541424561 5511892785725
"msm_camera" 2 0 0 0 12680633542 0 10539916988 5504792504962
"msm_camera_wake" 2 0 0 0 12680633542 0 10539916988 5504792504962
"s5k3e2fx" 2 0 0 0 12293823244 0 10387512209 5504791894611
"flashlight" 1 0 0 0 116271973 0 116271973 5472884484944
"rpc_read" 2 0 0 0 70556639 0 41900634 56937371906
"event2-252" 0 0 0 0 0 0 0 0
"SMD_DATA7" 0 0 0 0 0 0 0 0
"SMD_DATA6" 0 0 0 0 0 0 0 0
"port_list" 0 0 0 0 0 0 0 0
"vbus_present" 0 0 0 0 0 0 0 0
"msm_serial_hs_dma" 0 0 0 0 0 0 0 0
"msm_serial_hs_rx" 0 0 0 0 0 0 0 0
"audiojack" 0 0 0 0 0 0 0 0
"headset" 0 0 0 0 0 0 0 0
"microp_i2c_present" 0 0 0 0 0 0 0 0
"rpc_server" 0 0 0 0 0 0 0 0
"rpc_read" 0 0 0 0 0 0 0 0
"vdec_suspend" 0 0 0 0 0 0 0 0
"vdec_idle" 0 0 0 0 0 0 0 0
"i2c" 0 0 0 0 0 0 0 0
"unknown_wakeups" 0 0 0 0 0 0 0 0
"deleted_wake_locks" 193 0 0 0 117065426 0 32287599 0
"kgsl" 2981 0 0 1068695066 4845796179890 688535376655 128397308351 9725263797740
"PowerManagerService" 1061 0 0 52465057371 7525105867782 1338152315208 5239685516362 96738674
65953
"vbus_present" 2 1 0 740221282954 5984945089112 108139678944 5244723806158 8986111270887
"SMD_DS" 176 176 0 0 103807277355 31379227646 1803994144 9680271884899
#

[Q] USB Ethernet problem with Lollipop (GT-I9506)

Hi,
I'm trying to run my USB Ethernet dongle with my S4 LTE+ Lollipop D6, but aplications in the phone and other computers on the network didn't see that connection.
My tryings:
[email protected]:/ # netcfg eth0 up
[email protected]:/ # netcfg eth0 dhcp
[email protected]:/ # netcfg|grep eth0
eth0 UP 10.0.0.12/24 0x00001043 f0:25:b7:20:af:75
[email protected]:/ # ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=1.96 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=2.05 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=1.87 ms
[email protected]:/ # ping www.google.com
ping: unknown host www.google.com
2|[email protected]:/ # nslookup www.google.com
Server: 8.8.4.4
Address 1: 8.8.4.4 google-public-dns-b.google.com
Name: www.google.com
Address 1: 2a00:1450:4013:c01::93 ea-in-x93.1e100.net
Address 2: 74.125.136.104 ea-in-f104.1e100.net
Address 3: 74.125.136.103 ea-in-f103.1e100.net
Address 4: 74.125.136.99 ea-in-f99.1e100.net
Address 5: 74.125.136.105 ea-in-f105.1e100.net
Address 6: 74.125.136.147 ea-in-f147.
I've found this but it doesn't work also:
ndc network create 100
ndc network interface add 100 eth0
ndc network route add 100 eth0 <GATEWAY>/24
ndc network route add 100 eth0 0.0.0.0/0 <DNS1> <DNS2>
ndc resolver setnetdns 100 localdomain <DNS1> <DNS2>
ndc network default set 100
Any suggestions?
Thx

No body knows?

Hi
Have you tried this:
For Lollipop:
ndc resolver setnetdns eth0 "" 8.8.8.8 8.8.4.4​For Kitkat:
ndc resolver setifdns eth0 "" 8.8.8.8 8.8.4.4
ndc resolver setdefaultif eth0​Works for me on 5.1.1 (was able to ping 8.8.8.8 and 8.8.4.4 but not google.com. after typing this in the terminal, the ping worked !)

Android N beta, big cores always sleeping.

There is a bug with the latest android N, only the little cores seems to work. You can check it with cpu-z and a stress test.
Also, more info here: https://code.google.com/p/android/i...porter Opened&groupby=&sort=-opened&id=206819

Do you think this will be a quick patch or stay like it until the next developer preview?

It's stil a beta, maybe there will be a patch or in the next preview...the performance overall isnt that affected. You can also change the kernel .

Enrolled in beta last night did OTA to N will check cpu z see if same battery life still sucks 6am - 1:30pm and 17% left ?
Sent from my Nexus 5X using Tapatalk

i don't have this bug i don't know why
i ceched it with elemental x app

I don't have this issue either. All six cores running properly.

took the OTA from DP2 to DP3 and can confirm its happening to me too. i'll try installing the system image and see if that fixes it.

I'm not sure this is a problem with N but rather a problem with the apps you're using to measure the CPU cores themselves.
There's a command: adb shell cat /proc/stat
Type that in terminal with your phone connected and check it out
Now i'm no wiz at android or anything, but the columns it gives back are readings of how long the cpu cores have spent in certain states.
The meanings of the columns are as follows, from left to right:
user: normal processes executing in user mode
nice: niced processes executing in user mode
system: processes executing in kernel mode
idle: twiddling thumbs
iowait: waiting for I/O to complete
irq: servicing interrupts
softirq: servicing softirqs
Tayos-Mac-Pro:~ TayoOnabule$ adb shell cat /proc/stat
cpu 29779 16626 40322 263858 3638 5754 3666 0 0 0
cpu0 11365 9362 17248 101562 2611 2185 1182 0 0 0
cpu1 6731 3452 9271 30395 319 846 700 0 0 0
cpu2 6258 2891 7887 31142 243 708 572 0 0 0
cpu3 1245 391 3335 33573 216 458 469 0 0 0
cpu4 2344 377 1433 33444 130 1422 299 0 0 0
cpu5 1834 150 1146 33740 116 133 440 0 0 0
intr 2777034 0 3 0 3 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 618895 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 96044 0 0 0 0 0 0 0 343 0 0 136 0 0 0 0 0 2236 2 5 0 0 0 0 0 12538 0 0 0 0 0 0 0 0 0 0 274 0 0 0 0 2 416 2 0 2 0 0 0 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22521 0 0 0 0 0 0 0 0 0 0 0 0 26715 0 0 0 112 12660 0 346 0 25 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 381885 0 0 0 0 0 0 0 1413 0 0 0 0 0 0 1011 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12595 0 6 0 0 0 0 20317 7011 0 0 0 121135 0 0 1141 0 0 0 0 0 0 0 0 1 0 0 14757 619 0 0 0 0 0 548 0 1839 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6983 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9189 0 0 0 0 52677 0 0 0 0 0 0 288 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 529 26 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 94 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 21 0 0 0 0 0 0 0 0 0 0 0 303 0 0 0 0 292 0 2147 3 66 509 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 341 3643 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 131 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 161 0 0 0 0 0 0 0
ctxt 5896731
btime 1463686046
processes 11422
procs_running 1
procs_blocked 0
softirq 1957987 1198 375954 3331 23764 1198 1198 288344 370196 1092 891712
Tayos-Mac-Pro:~ TayoOnabule$
Click to expand...
Click to collapse
Edit: I also can't see the big cores working in CPU-Z, but doing this command it is obvious that they are actually working... apart from anything else N is so buttery smooth they must be working

/proc/stat actually shows that the 2 big cores are working. Cpu-z or cpu-x seem slow (or even fail) to update core speed. Try same with Antutu's cpu info (Info > cpu info > more) or tinycore (cpu profil, system info) and run a cpu heavy task that doesn't get low priority or stops when in background. Both should show actual values while on cpu-z/-x the big cores are still marked sleeping/stopped.

Are you sure this isn't thermal throttling? After the image first installed the cores temp was too high so it throttled the large cores off... once temps stabilized the big cores came back online. I think this is just a CPUZ bug to be honest.

It's just CPU-Z.
You can't expect every application to function properly on developer previews.

What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk

DoobyDroid said:
What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I can answer that one! just go back to the enrol page and click unroll device from beta your phone will receive a ota for latest build , unfortunately its a wipe so back up important tack first.........

Yeah my Android N is rooted i use kernel auditor with the stock supersu kernel and it shows cores working.

very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline

meisking1 said:
very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline
Click to expand...
Click to collapse
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.

Joms_US said:
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.
Click to expand...
Click to collapse
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running

meisking1 said:
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running
Click to expand...
Click to collapse
CPU stats does for me.
On stock system thermal throttling kicks in early and big cores are meant as short time boosts not permanent speed up. So you'll see relatively little use anyway

The animations of Android N in slowmotion
http://www.bitfeed.co/page/the-animations-of-android-n-in-slowmotion-video

AdAway - blocking MIUI from calling back home

Most of us don't use Xiaomi phones because of their "superior "software packages, like Mi Cloud, Mi Account, Find, or whatnot. We buy their phones because we get excellent hardware for an affordable price.
So, I decided to snoop around the system and weed out all the domains MIUI uses to report back home to it's chinese overlords. No doubs it sends back a basket of yummy "private user info" gifts
Here is a list of the domains I found about:
# This hosts file contains exported entries from AdAway.
127.0.0.1 market.xiaomi.com
127.0.0.1 api.ad.xiaomi.com
127.0.0.1 notice.game.xiaomi.com
127.0.0.1 api.miui.security.xiaomi.com
127.0.0.1 wifiapi.micloud.xiaomi.net
127.0.0.1 miui.com
127.0.0.1 pdc.micloud.xiaomi.net
127.0.0.1 game.xiaomi.com
127.0.0.1 micloud.xiaomi.net
127.0.0.1 sec-cdn.static.xiaomi.net
127.0.0.1 app.chat.xiaomi.net
127.0.0.1 xiaomi.net
127.0.0.1 xiaomi.com
127.0.0.1 contactapi.micloud.xiaomi.net
127.0.0.1 data.mistat.xiaomi.com
127.0.0.1 api.vip.miui.com
127.0.0.1 connect.rom.miui.com
127.0.0.1 app.market.xiaomi.com
127.0.0.1 account.xiaomi.com
127.0.0.1 miui.net
127.0.0.1 api.account.xiaomi.com
If anyone has any more domains to add, feel free to mention them in your reply.
HOW TO USE:
Root, install AdAway, and add the domains listed above to "Your lists" section in AdAway. See the screenshot for clarification.

Interesting, good job!

No problem. Glad I helped out. Feel free to add more domains to the list, if you know any.

we add that to adaway hosts?
thank you

Do it will block milog too? I always found some logcat in MIUI folder.
If i know how yo disable that logs, tell me...

If I don't mind..... what should we do with this...???
Sry I don't know anything about it...(ofcourse am rooted)

Info on how to block the domains added to the first post.

D-dy said:
Do it will block milog too? I always found some logcat in MIUI folder.
If i know how yo disable that logs, tell me...
Click to expand...
Click to collapse
I solved some of the logcat spam by editing the build.prop file and replacing this:
persist.sys.ssr.enable_ramdumps=1
with this:
persist.sys.ssr.enable_ramdumps=0

Here is an updated list of domains to be blocked:
# This hosts file contains exported entries from AdAway.
127.0.0.1 ad.xiaomi.com
127.0.0.1 game.xiaomi.com
127.0.0.1 pdc.micloud.xiaomi.net
127.0.0.1 223.202.68.86
127.0.0.1 notice.game.xiaomi.com
127.0.0.1 app.chat.xiaomi.net
127.0.0.1 api.miui.security.xiaomi.com
127.0.0.1 api.vip.miui.com
127.0.0.1 contactapi.micloud.xiaomi.net
127.0.0.1 api.ad.xiaomi.com
127.0.0.1 miui.com
127.0.0.1 220.181.47.186
127.0.0.1 sec-cdn.static.xiaomi.net
127.0.0.1 data.mistat.xiaomi.com
127.0.0.1 xiaomi.com
127.0.0.1 micloud.xiaomi.net
127.0.0.1 42.62.94.93
127.0.0.1 resolver.gslb.mi-idc.com
127.0.0.1 account.xiaomi.com
127.0.0.1 chinaunicom.com
127.0.0.1 app.market.xiaomi.com
127.0.0.1 42.62.94.127
127.0.0.1 xiaomi.net
127.0.0.1 api.account.xiaomi.com
127.0.0.1 wifiapi.micloud.xiaomi.net
127.0.0.1 42.62.94.152
127.0.0.1 114.54.23.44
127.0.0.1 connect.rom.miui.com
127.0.0.1 120.134.33.89
127.0.0.1 sdkconfig.ad.xiaomi.com
127.0.0.1 223.202.68.93
127.0.0.1 market.xiaomi.com
127.0.0.1 114.54.23.8
127.0.0.1 miui.net
127.0.0.1 114.54.23.5

Tomo123 said:
Here is an updated list of domains to be blocked:
# This hosts file contains exported entries from AdAway.
127.0.0.1 ad.xiaomi.com
127.0.0.1 game.xiaomi.com
127.0.0.1 pdc.micloud.xiaomi.net
127.0.0.1 223.202.68.86
127.0.0.1 notice.game.xiaomi.com
127.0.0.1 app.chat.xiaomi.net
127.0.0.1 api.miui.security.xiaomi.com
127.0.0.1 api.vip.miui.com
127.0.0.1 contactapi.micloud.xiaomi.net
127.0.0.1 api.ad.xiaomi.com
127.0.0.1 miui.com
127.0.0.1 220.181.47.186
127.0.0.1 sec-cdn.static.xiaomi.net
127.0.0.1 data.mistat.xiaomi.com
127.0.0.1 xiaomi.com
127.0.0.1 micloud.xiaomi.net
127.0.0.1 42.62.94.93
127.0.0.1 resolver.gslb.mi-idc.com
127.0.0.1 account.xiaomi.com
127.0.0.1 chinaunicom.com
127.0.0.1 app.market.xiaomi.com
127.0.0.1 42.62.94.127
127.0.0.1 xiaomi.net
127.0.0.1 api.account.xiaomi.com
127.0.0.1 wifiapi.micloud.xiaomi.net
127.0.0.1 42.62.94.152
127.0.0.1 114.54.23.44
127.0.0.1 connect.rom.miui.com
127.0.0.1 120.134.33.89
127.0.0.1 sdkconfig.ad.xiaomi.com
127.0.0.1 223.202.68.93
127.0.0.1 market.xiaomi.com
127.0.0.1 114.54.23.8
127.0.0.1 miui.net
127.0.0.1 114.54.23.5
Click to expand...
Click to collapse
can u export that list so that we easy can just import ? it is easier .. thanks

I don't think ip redirection is possible in any app, only dns names, other than that, thanks

here's a more thorough list:
Code:
0.0.0.0 a.stat.xiaomi.com
0.0.0.0 abtest.mistat.intl.xiaomi.com
0.0.0.0 abtest.mistat.xiaomi.com
0.0.0.0 ad.mi.com
0.0.0.0 ad.xiaomi.com
0.0.0.0 ad1.xiaomi.com
0.0.0.0 adv.sec.miui.com
0.0.0.0 api.account.xiaomi.com
0.0.0.0 api.ad.xiaomi.com
0.0.0.0 api.admob.xiaomi.com
0.0.0.0 api.chat.xiaomi.net
0.0.0.0 api.comm.miui.com
0.0.0.0 api.cupid.ptqy.gitv.tv
0.0.0.0 api.d.xiaomi.com
0.0.0.0 api.device.xiaomi.net
0.0.0.0 api.io.mi.com
0.0.0.0 api.micloud.xiaomi.net
0.0.0.0 api.miui.security.xiaomi.com
0.0.0.0 api.sec.miui.com
0.0.0.0 api.vip.miui.com
0.0.0.0 api.xiaomi.com
0.0.0.0 api.xmpush.xiaomi.com
0.0.0.0 app.chat.xiaomi.net
0.0.0.0 app.migc.xiaomi.com
0.0.0.0 appstore.cdn.pandora.xiaomi.com
0.0.0.0 appstore.pandora.xiaomi.com
0.0.0.0 assistant.pandora.xiaomi.com
0.0.0.0 auth.be.sec.miui.com
0.0.0.0 awsusor0-cdn.fds-ssl.api.xiaomi.com
0.0.0.0 b.netcheck.gallery.pandora.xiaomi.com
0.0.0.0 bbs.game.xiaomi.com
0.0.0.0 be01.hh.xiaomi.com
0.0.0.0 bgp.fe01.c3.xiaomi.com
0.0.0.0 bk01.hh.xiaomi.com
0.0.0.0 blog.xiaomi.com
0.0.0.0 bss.pandora.xiaomi.com
0.0.0.0 c.id.mi.com
0.0.0.0 cc.sys.intl.xiaomi.com
0.0.0.0 cc.sys.miui.com
0.0.0.0 ccc.sys.intl.xiaomi.com
0.0.0.0 ccc.sys.miui.com
0.0.0.0 cdn.ad.xiaomi.com
0.0.0.0 cdn.fds-ssl.api.xiaomi.com
0.0.0.0 clock.ad.xiaomi.com
0.0.0.0 cnc.fe01.lg.xiaomi.com
0.0.0.0 config.kuyun.com
0.0.0.0 connect.rom.miui.com
0.0.0.0 contactapi.micloud.xiaomi.net
0.0.0.0 ctc.fe01.c3.xiaomi.com
0.0.0.0 ctc.fe02.c3.xiaomi.com
0.0.0.0 d.xiaomi.com
0.0.0.0 data.game.xiaomi.com
0.0.0.0 data.mistat.intl.xiaomi.com
0.0.0.0 data.mistat.xiaomi.com
0.0.0.0 data.sec.miui.com
0.0.0.0 de.pandora.xiaomi.com
0.0.0.0 dvb.pandora.xiaomi.com
0.0.0.0 e.ad.xiaomi.com
0.0.0.0 f1.g.mi.com
0.0.0.0 fcanr.tracking.miui.com
0.0.0.0 fe02.lg.xiaomi.com
0.0.0.0 fe05.lg.xiaomi.com
0.0.0.0 file.market.xiaomi.com
0.0.0.0 file.xmpush.xiaomi.com
0.0.0.0 gallery.cdn.pandora.xiaomi.com
0.0.0.0 gallery.pandora.xiaomi.com
0.0.0.0 game.xiaomi.com
0.0.0.0 geofence.sys.miui.com
0.0.0.0 global.search.xiaomi.net
0.0.0.0 globalapi.ad.xiaomi.com
0.0.0.0 gvod.aiseejapp.atianqi.com
0.0.0.0 hd.xiaomi.com
0.0.0.0 hd02.lg.xiaomi.com
0.0.0.0 heyue.xiaomi.com
0.0.0.0 hk.mibi.xiaomi.com
0.0.0.0 huodong.xiaomi.com
0.0.0.0 huosai.xiaomi.com
0.0.0.0 i.xiaomi.com
0.0.0.0 igame.xiaomi.com
0.0.0.0 image.pandora.xiaomi.com
0.0.0.0 ime.api.xiaomi.com
0.0.0.0 imgg.traffic-media.co
0.0.0.0 iosdl.game.xiaomi.com
0.0.0.0 jellyfish.pandora.xiaomi.com
0.0.0.0 lbs.pandora.xiaomi.com
0.0.0.0 lg-bgp.pandora.xiaomi.com
0.0.0.0 login.game.xiaomi.com
0.0.0.0 logonext.tv.kuyun.com
0.0.0.0 logupdate.avlyun.sec.miui.com
0.0.0.0 m.bss.pandora.xiaomi.com
0.0.0.0 mazu.sec.miui.com
0.0.0.0 meihua.xiaomi.com
0.0.0.0 metok.sys.miui.com
0.0.0.0 mibi.api.xiaomi.com
0.0.0.0 mibi.xiaomi.com
0.0.0.0 micardapi.micloud.xiaomi.net
0.0.0.0 milink.pandora.xiaomi.com
0.0.0.0 mis.migc.xiaomi.com
0.0.0.0 mishop.cdn.pandora.xiaomi.com
0.0.0.0 mishop.pandora.xiaomi.com
0.0.0.0 mitunes.game.xiaomi.com
0.0.0.0 mp.huangye.miui.com
0.0.0.0 new.api.ad.xiaomi.com
0.0.0.0 notice.game.xiaomi.com
0.0.0.0 o2o.api.xiaomi.com
0.0.0.0 order.music.xiaomi.com
0.0.0.0 pdc.micloud.xiaomi.net
0.0.0.0 phonecallapi.micloud.xiaomi.net
0.0.0.0 pmall.migc.xiaomi.com
0.0.0.0 ppurifier.game.xiaomi.com
0.0.0.0 ptmi.gitv.pandora.xiaomi.com
0.0.0.0 qiye.xiaomi.com
0.0.0.0 r.browser.miui.com
0.0.0.0 r.sg.sec.miui.com
0.0.0.0 register.xmpush.xiaomi.com
0.0.0.0 resolver.gslb.mi-idc.com
0.0.0.0 resolver.msg.xiaomi.net
0.0.0.0 sandbox.xmpush.xiaomi.com
0.0.0.0 sdkconfig.ad.intl.xiaomi.com
0.0.0.0 sdkconfig.ad.xiaomi.com
0.0.0.0 secode2.hd.xiaomi.com
0.0.0.0 sfsapi.micloud.xiaomi.net
0.0.0.0 sgpac.account.xiaomi.com
0.0.0.0 shenghuo.xiaomi.com
0.0.0.0 shoes.app-xae.xiaomi.com
0.0.0.0 ssp.ad.xiaomi.com
0.0.0.0 staging.ai.api.xiaomi.com
0.0.0.0 starfish.pandora.xiaomi.com
0.0.0.0 stat.pandora.xiaomi.com
0.0.0.0 static.game.xiaomi.com
0.0.0.0 static.mibi.xiaomi.com
0.0.0.0 statusapi.micloud.xiaomi.net
0.0.0.0 storeconfig.mistat.intl.xiaomi.com
0.0.0.0 t1.g.mi.com
0.0.0.0 tc.hd.xiaomi.com
0.0.0.0 tel.fe01.hh.xiaomi.com
0.0.0.0 test.ad.xiaomi.com
0.0.0.0 test.e.ad.xiaomi.com
0.0.0.0 test.new.api.ad.xiaomi.com
0.0.0.0 tracking.miui.com
0.0.0.0 trial.api.huangye.miui.com
0.0.0.0 tv.app.migc.xiaomi.com
0.0.0.0 update.avlyun.sec.miui.com
0.0.0.0 update.miui.com
0.0.0.0 upgrade.mishop.pandora.xiaomi.com
0.0.0.0 userid.xiaomi.com
0.0.0.0 voip.game.xiaomi.com
0.0.0.0 wallpaper.cdn.pandora.xiaomi.com
0.0.0.0 wallpaper.pandora.xiaomi.com
0.0.0.0 wap.game.xiaomi.com
0.0.0.0 weather.pandora.xiaomi.com
0.0.0.0 xiazai.xiaomi.com
0.0.0.0 xitong.xiaomi.com
0.0.0.0 xlmc.sec.miui.com
0.0.0.0 xshare.api.xiaomi.com
0.0.0.0 zeus.ad.intl.xiaomi.com
0.0.0.0 zx.game.xiaomi.com

One more list:
https://gist.github.com/eboye/ef2f8c3e9e3b32c0980ff1a226770b1c

adaway blocking me tho to access youtube app. just add to whitelist then problem solved

Great idea to start a list here on xda! I took your through list and added it to my adaway. I pasted into a .txt and uploaded it to the internet then added it as a source in Adaway.
I see the git hub link too, I might update my source. Thank you.
One thing has been bugging me is no third party themes on miui 10! So I'm hoping a redirect to an xml with a valid true is needed. Has anyone spoofed the themes auth server?

More:
Code:
0.0.0.0 fr.app.chat.global.xiaomi.net
0.0.0.0 resolver.msg.global.xiaomi.net
0.0.0.0 relocationapi.micloud.xiaomi.net
0.0.0.0 api.en.miui.com
0.0.0.0 feedback.intl.miui.com
0.0.0.0 us.statusapi.micloud.xiaomi.net
0.0.0.0 i.mi.com
0.0.0.0 global.market.xiaomi.com
0.0.0.0 find.api.micloud.xiaomi.net
0.0.0.0 us.find.api.micloud.xiaomi.net
0.0.0.0 controller.intl.xiaomi.com
0.0.0.0 api.ad.intl.xiaomi.com
0.0.0.0 authbe.sec.intl.miui.com
0.0.0.0 video.intl.xiaomi.com
0.0.0.0 metok-ccc.intl.xiaomi.com
0.0.0.0 weatherapi.market.xiaomi.com
0.0.0.0 us.galleryapi.micloud.xiaomi.net
0.0.0.0 api.sec.intl.miui.com
0.0.0.0 api.developer.xiaomi.com
0.0.0.0 www.miui.com
0.0.0.0 api.hybrid.intl.xiaomi.com
0.0.0.0 tracking.intl.miui.com
0.0.0.0 adv.sec.intl.miui.com
0.0.0.0 fr-app-chat-global-xiaomi-net-1516654448.eu-central-1.elb.amazonaws.com
0.0.0.0 mcc.intl.inf.miui.com
https://github.com/Sunybyjava/KillADHosts/blob/master/Hosts_Miui

Does the Mi Account still works with these in hosts file?

ne0t said:
Does the Mi Account still works with these in hosts file?
Click to expand...
Click to collapse
Hi!
I dont know, i disabled the MiAccount after successful bootloader opening. May you must try it, if it works or not, let us to know. Thank you.

Updated List
Thanks to all for the contributions... I found few more host names from internet and included all in one file with duplicates removed.
Also addressed to 0.0.0. in place of 127.0.0.1 as that seems to be better.
PS: Not yet tested
Code:
0.0.0.0 10.235.124.13
0.0.0.0 10.99.168.145
0.0.0.0 10.99.184.96
0.0.0.0 a.stat.xiaomi.com
0.0.0.0 abtest.mistat.intl.xiaomi.com
0.0.0.0 abtest.mistat.xiaomi.com
0.0.0.0 account.jetbrains.com
0.0.0.0 account.preview.n.xiaomi.net
0.0.0.0 account.xiaomi.com
0.0.0.0 ad.mi.com
0.0.0.0 ad.xiaomi.com
0.0.0.0 ad1.xiaomi.com
0.0.0.0 adinfo.ra1.xlmc.sec.miui.com
0.0.0.0 adv.sec.intl.miui.com
0.0.0.0 adv.sec.miui.com
0.0.0.0 api.account.preview.n.xiaomi.net
0.0.0.0 api.account.xiaomi.com
0.0.0.0 api.ad.intl.xiaomi.com
0.0.0.0 api.ad.xiaomi.com
0.0.0.0 api.admob.xiaomi.com
0.0.0.0 api.chat.xiaomi.net
0.0.0.0 api.comm.miui.com
0.0.0.0 api.cupid.ptqy.gitv.tv
0.0.0.0 api.d.xiaomi.com
0.0.0.0 api.developer.xiaomi.com
0.0.0.0 api.device.xiaomi.net
0.0.0.0 api.en.miui.com
0.0.0.0 api.hybrid.intl.xiaomi.com
0.0.0.0 api.hybrid.xiaomi.com
0.0.0.0 api.io.mi.com
0.0.0.0 api.micloud.xiaomi.net
0.0.0.0 api.miui.security.xiaomi.com
0.0.0.0 api.ra2.xlmc.sec.miui.com
0.0.0.0 api.sec.intl.miui.com
0.0.0.0 api.sec.miui.com
0.0.0.0 api.setting.intl.miui.com
0.0.0.0 api.tw06.xlmc.sec.miui.com
0.0.0.0 api.vip.miui.com
0.0.0.0 api.xiaomi.com
0.0.0.0 api.xmpush.xiaomi.com
0.0.0.0 api.zhuti.xiaomi.com
0.0.0.0 app.chat.xiaomi.net
0.0.0.0 app.market.xiaomi.com
0.0.0.0 app.mibi.xiaomi.com
0.0.0.0 app.migc.xiaomi.com
0.0.0.0 app.xiaomi.com
0.0.0.0 app01.nodes.gslb.mi-idc.com
0.0.0.0 app02.nodes.gslb.mi-idc.com
0.0.0.0 appstore.cdn.pandora.xiaomi.com
0.0.0.0 appstore.pandora.xiaomi.com
0.0.0.0 assistant.pandora.xiaomi.com
0.0.0.0 auth.be.sec.miui.com
0.0.0.0 authbe.sec.intl.miui.com
0.0.0.0 awsusor0-cdn.fds-ssl.api.xiaomi.com
0.0.0.0 b.netcheck.gallery.pandora.xiaomi.com
0.0.0.0 bbs.game.xiaomi.com
0.0.0.0 be01.hh.xiaomi.com
0.0.0.0 bgp.fe01.c3.xiaomi.com
0.0.0.0 bk01.hh.xiaomi.com
0.0.0.0 blog.xiaomi.com
0.0.0.0 bss.pandora.xiaomi.com
0.0.0.0 c.id.mi.com
0.0.0.0 calopenupdate.comm.miui.com
0.0.0.0 cc.sys.intl.xiaomi.com
0.0.0.0 cc.sys.miui.com
0.0.0.0 cc2.sys.intl.xiaomi.com
0.0.0.0 cc2.sys.miui.com
0.0.0.0 ccc.sys.intl.xiaomi.com
0.0.0.0 ccc.sys.miui.com
0.0.0.0 cdn.ad.xiaomi.com
0.0.0.0 cdn.fds-ssl.api.xiaomi.com
0.0.0.0 clock.ad.xiaomi.com
0.0.0.0 cnc.fe01.lg.xiaomi.com
0.0.0.0 config.kuyun.com
0.0.0.0 connect.rom.miui.com
0.0.0.0 contactapi.micloud.xiaomi.net
0.0.0.0 controller.intl.xiaomi.com
0.0.0.0 ctc.fe01.c3.xiaomi.com
0.0.0.0 ctc.fe02.c3.xiaomi.com
0.0.0.0 d.xiaomi.com
0.0.0.0 data.game.xiaomi.com
0.0.0.0 data.mistat.intl.xiaomi.com
0.0.0.0 data.mistat.xiaomi.com
0.0.0.0 data.sec.miui.com
0.0.0.0 de.pandora.xiaomi.com
0.0.0.0 dev.api.zhuti.n.xiaomi.com
0.0.0.0 dev.market.n.xiaomi.com
0.0.0.0 dev.staging.api.developer.n.xiaomi.com
0.0.0.0 drm.market.xiaomi.com
0.0.0.0 dvb.pandora.xiaomi.com
0.0.0.0 e.ad.xiaomi.com
0.0.0.0 f1.g.mi.com
0.0.0.0 fcanr.tracking.miui.com
0.0.0.0 fe02.lg.xiaomi.com
0.0.0.0 fe05.lg.xiaomi.com
0.0.0.0 feedback.intl.miui.com
0.0.0.0 feedback.miui.com
0.0.0.0 file.market.xiaomi.com
0.0.0.0 file.xmpush.xiaomi.com
0.0.0.0 find.api.micloud.xiaomi.net
0.0.0.0 flash.sec.intl.miui.com
0.0.0.0 fr-app-chat-global-xiaomi-net-1516654448.eu-central-1.elb.amazonaws.com
0.0.0.0 fr.app.chat.global.xiaomi.net
0.0.0.0 gallery.cdn.pandora.xiaomi.com
0.0.0.0 gallery.pandora.xiaomi.com
0.0.0.0 game.xiaomi.com
0.0.0.0 geofence.sys.miui.com
0.0.0.0 global.market.xiaomi.com
0.0.0.0 global.preview.app.market.pt.xiaomi.com
0.0.0.0 global.search.xiaomi.net
0.0.0.0 globalapi.ad.xiaomi.com
0.0.0.0 gvod.aiseejapp.atianqi.com
0.0.0.0 hd.xiaomi.com
0.0.0.0 hd02.lg.xiaomi.com
0.0.0.0 heyue.xiaomi.com
0.0.0.0 hk.mibi.xiaomi.com
0.0.0.0 hm.xiaomi.com
0.0.0.0 huodong.xiaomi.com
0.0.0.0 huosai.xiaomi.com
0.0.0.0 i.mi.com
0.0.0.0 i.xiaomi.com
0.0.0.0 igame.xiaomi.com
0.0.0.0 image.box.xiaomi.com
0.0.0.0 image.cdn.mvideo.xiaomi.com
0.0.0.0 image.pandora.xiaomi.com
0.0.0.0 ime.api.xiaomi.com
0.0.0.0 imgg.traffic-media.co
0.0.0.0 info.analysis.kp.sec.miui.com
0.0.0.0 info.sec.miui.com
0.0.0.0 iosdl.game.xiaomi.com
0.0.0.0 jellyfish.pandora.xiaomi.com
0.0.0.0 lbs.pandora.xiaomi.com
0.0.0.0 lg-bgp.pandora.xiaomi.com
0.0.0.0 log.ad.xiaomi.com
0.0.0.0 login.game.xiaomi.com
0.0.0.0 logonext.tv.kuyun.com
0.0.0.0 logupdate.avlyun.sec.miui.com
0.0.0.0 m.bss.pandora.xiaomi.com
0.0.0.0 m.zhuti.xiaomi.com
0.0.0.0 market.xiaomi.com
0.0.0.0 mazu.sec.miui.com
0.0.0.0 mcc.intl.inf.miui.com
0.0.0.0 meihua.xiaomi.com
0.0.0.0 metok-ccc.intl.xiaomi.com
0.0.0.0 metok.sys.miui.com
0.0.0.0 mibi.api.xiaomi.com
0.0.0.0 mibi.xiaomi.com
0.0.0.0 micardapi.micloud.xiaomi.net
0.0.0.0 micloud.xiaomi.net
0.0.0.0 migrate.driveapi.micloud.xiaomi.net
0.0.0.0 milink.pandora.xiaomi.com
0.0.0.0 mis.migc.xiaomi.com
0.0.0.0 mishop.cdn.pandora.xiaomi.com
0.0.0.0 mishop.pandora.xiaomi.com
0.0.0.0 mitunes.game.xiaomi.com
0.0.0.0 miui.com
0.0.0.0 miui.net
0.0.0.0 mlog.search.xiaomi.net
0.0.0.0 mp.huangye.miui.com
0.0.0.0 new.api.ad.xiaomi.com
0.0.0.0 notice.game.xiaomi.com
0.0.0.0 o2o.api.xiaomi.com
0.0.0.0 onebox.api.zhuti.n.xiaomi.com
0.0.0.0 onebox.market.n.xiaomi.com
0.0.0.0 order.music.xiaomi.com
0.0.0.0 pdc.micloud.xiaomi.net
0.0.0.0 phonecallapi.micloud.xiaomi.net
0.0.0.0 pmall.migc.xiaomi.com
0.0.0.0 ppurifier.game.xiaomi.com
0.0.0.0 ptmi.gitv.pandora.xiaomi.com
0.0.0.0 qiye.xiaomi.com
0.0.0.0 r.browser.miui.com
0.0.0.0 r.sg.sec.miui.com
0.0.0.0 reader.browser.miui.com
0.0.0.0 register.xmpush.global.xiaomi.com
0.0.0.0 register.xmpush.xiaomi.com
0.0.0.0 relocationapi.micloud.xiaomi.net
0.0.0.0 resolver.gslb.mi-idc.com
0.0.0.0 resolver.msg.global.xiaomi.net
0.0.0.0 resolver.msg.xiaomi.net
0.0.0.0 ruac.account.xiaomi.com
0.0.0.0 sandbox.xmpush.xiaomi.com
0.0.0.0 sdkconfig.ad.intl.xiaomi.com
0.0.0.0 sdkconfig.ad.xiaomi.com
0.0.0.0 sec-cdn.static.xiaomi.net
0.0.0.0 sec.resource.xiaomi.net
0.0.0.0 secode2.hd.xiaomi.com
0.0.0.0 sfsapi.micloud.xiaomi.net
0.0.0.0 sgpac.account.xiaomi.com
0.0.0.0 shenghuo.xiaomi.com
0.0.0.0 shoes.app-xae.xiaomi.com
0.0.0.0 ssp.ad.xiaomi.com
0.0.0.0 staging.ai.api.xiaomi.com
0.0.0.0 staging.api.zhuti.n.xiaomi.com
0.0.0.0 staging.appapi.n.xiaomi.com
0.0.0.0 staging.market.n.xiaomi.com
0.0.0.0 starfish.pandora.xiaomi.com
0.0.0.0 stat.pandora.xiaomi.com
0.0.0.0 stat.xiaomi.com
0.0.0.0 static.game.xiaomi.com
0.0.0.0 static.mibi.xiaomi.com
0.0.0.0 statusapi.micloud.xiaomi.net
0.0.0.0 storeconfig.mistat.intl.xiaomi.com
0.0.0.0 t1.g.mi.com
0.0.0.0 tc.hd.xiaomi.com
0.0.0.0 tel.fe01.hh.xiaomi.com
0.0.0.0 test.ad.xiaomi.com
0.0.0.0 test.e.ad.xiaomi.com
0.0.0.0 test.log.ad.xiaomi.com
0.0.0.0 test.new.api.ad.xiaomi.com
0.0.0.0 test.xiaomi.com
0.0.0.0 test.zeus.ad.xiaomi.com
0.0.0.0 thm.market.xiaomi.com
0.0.0.0 tracking.intl.miui.com
0.0.0.0 tracking.miui.com
0.0.0.0 trial.api.huangye.miui.com
0.0.0.0 tv.app.migc.xiaomi.com
0.0.0.0 update.avlyun.sec.miui.com
0.0.0.0 update.intl.miui.com
0.0.0.0 update.miui.com
0.0.0.0 upgrade.mishop.pandora.xiaomi.com
0.0.0.0 us.find.api.micloud.xiaomi.net
0.0.0.0 us.galleryapi.micloud.xiaomi.net
0.0.0.0 us.statusapi.micloud.xiaomi.net
0.0.0.0 userid.xiaomi.com
0.0.0.0 video.intl.xiaomi.com
0.0.0.0 video.xiaomi.com
0.0.0.0 voip.game.xiaomi.com
0.0.0.0 wallpaper.cdn.pandora.xiaomi.com
0.0.0.0 wallpaper.pandora.xiaomi.com
0.0.0.0 wap.game.xiaomi.com
0.0.0.0 weather.pandora.xiaomi.com
0.0.0.0 weatherapi.market.xiaomi.com
0.0.0.0 wifiapi.micloud.xiaomi.net
0.0.0.0 www.miui.com
0.0.0.0 www.xiaomi.com
0.0.0.0 xiaomi.com
0.0.0.0 xiaomi.net
0.0.0.0 xiazai.xiaomi.com
0.0.0.0 xitong.xiaomi.com
0.0.0.0 xlmc.sec.miui.com
0.0.0.0 xshare.api.xiaomi.com
0.0.0.0 zeus.ad.intl.xiaomi.com
0.0.0.0 zeus.ad.xiaomi.com
0.0.0.0 zhuti.xiaomi.com
0.0.0.0 zx.game.xiaomi.com

Does this list^ also work with Adguard?

How to forward traffic from eth0 to ppp0 (AOSP embedded project)

I am using Android 10 on a custom device (Variscite imx8). The Android image has been generated by AOSP.
I need to forward the traffico from the eth0 to the ppp0 (Quectel LTE module) interface.
I've managed to enable the ppp0 interface by using the pppd script (i.e.: pppd call my-connection-info) and I can see that I receive the two DNS server addresses and my public IPv4 successfully.
Now the first weird thing: If I ping to 8.8.8.8 I receive "connect: Network is unreachable" meanwhile if I specify the ppp0 interface with ping -I ppp0 8.8.8.8 I can successfully ping the target. I've added the following routing table with priority 25000 so that I'm able to ping 8.8.8.8 without specifying the interface:
Code:
ip rule add prio 250000 from all lookup 25000
ip rule add table 25000 default via <my-public-ip> dev ppp0
Now I want to forward the eth0 traffic to the ppp0, to do so I've tried the following commands:
Code:
$ echo 1 > /proc/sys/net/ipv4/ip_forward
$ iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
But the PC on the other end of the eth0 interfce still prompts "From 192.168.10.1 icmp_seq=xxx Destination Net Unreachable" where 192.168.10.1 address is the Android device (which acts like a gateway).
This is the content of netstat -rn command:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.64.64.64 0.0.0.0 UG 0 0 0 ppp0
10.64.64.64 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
This is the output of netstat -rn:
Code:
default via 10.64.64.64 dev ppp0
10.64.64.64 dev ppp0 proto kernel scope link src <my-public-ip>
192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.1
This is the output of iptables -L (which I've flushed with iptables -F, iptables -X and iptables -t nat -F):
Code:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Which is the issue here? Thank you.