# Routing table changes automatically on mangOH yellow **URL:** \ **Category:** General wireless topics\ **Created:** [July 26, 2023, 9:57am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299 "2023-07-26T09:57:05Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ravneet.singh.iitd](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@ravneet.singh.iitd](https://forum.sierrawireless.com/u/ravneet.singh.iitd)\ **Post date:** [July 26, 2023, 9:57am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/1 "2023-07-26T09:57:05Z")
Hi, I am struggling to run wifi properly on my mangOH yellow device. I am able to start wlan0 and connect to wifi and the internet using a static ip (here 192.168.1.26) and setting a default gateway of my router (192.168.1.1) root@swi-mdm9x28-wp:~# wifi client start successfully called start. root@swi-mdm9x28-wp:~# ifconfig wlan0 192.168.1.26 netmask 255.255.255.0 up root@swi-mdm9x28-wp:~# route add default gw 192.168.1.1 wlan0 root@swi-mdm9x28-wp:~# wpa\_supplicant -B -i wlan0 -c /etc/wpa\_supplicant.conf Successfully initialized wpa\_supplicant and then I am able to ping [google.com](http://google.com), so the device connects to the internet via wlan0: root@swi-mdm9x28-wp:~# ping [www.google.com](http://www.google.com) PING [www.google.com](http://www.google.com) (142.250.195.196): 56 data bytes 64 bytes from 142.250.195.196: seq=0 ttl=59 time=46.560 ms 64 bytes from 142.250.195.196: seq=1 ttl=59 time=68.985 ms 64 bytes from 142.250.195.196: seq=2 ttl=59 time=42.266 ms 64 bytes from 142.250.195.196: seq=3 ttl=59 time=61.001 ms 64 bytes from 142.250.195.196: seq=4 ttl=59 time=53.239 ms 64 bytes from 142.250.195.196: seq=5 ttl=59 time=60.138 ms 64 bytes from 142.250.195.196: seq=6 ttl=59 time=50.462 ms 64 bytes from 142.250.195.196: seq=7 ttl=59 time=54.713 ms 64 bytes from 142.250.195.196: seq=8 ttl=59 time=45.096 ms 64 bytes from 142.250.195.196: seq=9 ttl=59 time=52.597 ms 64 bytes from 142.250.195.196: seq=10 ttl=59 time=31.170 ms but then suddenly it stops. After some investigation I figured that the routing table changes automatically (due to some background script or something) and makes the default gateway from rmnet\_data0 instead of from wlan0 which I set manually Before: root@swi-mdm9x28-wp:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 192.168.1.0 \* 255.255.255.0 U 0 0 0 wlan0 192.168.2.0 \* 255.255.255.0 U 0 0 0 ecm0 192.168.225.0 \* 255.255.255.0 U 0 0 0 bridge0 After internet stops working (routing table changed automatically): root@swi-mdm9x28-wp:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.123.88.196 0.0.0.0 UG 0 0 0 rmnet\_data0 10.123.88.192 \* 255.255.255.248 U 0 0 0 rmnet\_data0 192.168.1.0 \* 255.255.255.0 U 0 0 0 wlan0 192.168.2.0 \* 255.255.255.0 U 0 0 0 ecm0 192.168.225.0 \* 255.255.255.0 U 0 0 0 bridge0 Sometimes it just gets back (ping command running, and after a lot of missing packets, it starts responding again): 64 bytes from 142.250.195.196: seq=20 ttl=59 time=54.948 ms 64 bytes from 142.250.195.196: seq=21 ttl=59 time=27.586 ms 64 bytes from 142.250.195.196: seq=22 ttl=59 time=51.768 ms 64 bytes from 142.250.195.196: seq=23 ttl=59 time=29.858 ms 64 bytes from 142.250.195.196: seq=24 ttl=59 time=46.847 ms 64 bytes from 142.250.195.196: seq=131 ttl=59 time=56.453 ms 64 bytes from 142.250.195.196: seq=132 ttl=59 time=22.821 ms 64 bytes from 142.250.195.196: seq=133 ttl=59 time=36.060 ms 64 bytes from 142.250.195.196: seq=134 ttl=59 time=43.583 ms I am not able to figure why this is happening. Can somebody please provide any pointers? Thanks ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [July 26, 2023, 10:00am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/2 "2023-07-26T10:00:13Z")
rmnet\_data0 is from cellular network, is this problem happening when you insert SIM card? you can also compare the “cm data” response before and after the problem happens. BTW, did you establish data connection to cellular network? ---
**Author:** ![ravneet.singh.iitd](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@ravneet.singh.iitd](https://forum.sierrawireless.com/u/ravneet.singh.iitd)\ **Post date:** [July 26, 2023, 10:16am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/3 "2023-07-26T10:16:02Z")
Hi @jyijyi Thank you for your response. No I did not insert any SIM card, but the ifconfig command shows all these interfaces: root@swi-mdm9x28-wp:~# ifconfig -a bridge0 Link encap:Ethernet HWaddr BA:4D:ED:E0:7E:56 inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0 inet6 addr: fe80::b84d:edff:fedd:7b53/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:76 (76.0 B) ecm0 Link encap:Ethernet HWaddr 0E:96:02:C8:43:40 inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::c96:2ff:fec8:4340/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:673 errors:0 dropped:0 overruns:0 frame:0 TX packets:326 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:63947 (62.4 KiB) TX bytes:50440 (49.2 KiB) 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:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:708 (708.0 B) TX bytes:708 (708.0 B) rmnet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:2000 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:3292 (3.2 KiB) rmnet\_data0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 [NO FLAGS] MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:3292 (3.2 KiB) rmnet\_data1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 [NO FLAGS] MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) rmnet\_data2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 [NO FLAGS] MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) rmnet\_data3 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 [NO FLAGS] MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 3C:E1:A1:E8:C1:A2 inet addr:192.168.1.26 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::3ee1:a1ff:fee8:c1a2/64 Scope:Link inet6 addr: 2401:4900:1cb1:7c04:3ee1:a1ff:fee8:c1a2/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5151 (5.0 KiB) TX bytes:3370 (3.2 KiB) I ran the ping command and in another terminal ran the cm data command: root@swi-mdm9x28-wp:~# ping [www.google.com](http://www.google.com) PING [www.google.com](http://www.google.com) (142.250.196.164): 56 data bytes 64 bytes from 142.250.196.164: seq=0 ttl=59 time=49.026 ms 64 bytes from 142.250.196.164: seq=1 ttl=59 time=30.170 ms 64 bytes from 142.250.196.164: seq=2 ttl=59 time=151.451 ms 64 bytes from 142.250.196.164: seq=3 ttl=59 time=52.413 ms 64 bytes from 142.250.196.164: seq=4 ttl=59 time=28.321 ms 64 bytes from 142.250.196.164: seq=5 ttl=59 time=26.692 ms 64 bytes from 142.250.196.164: seq=6 ttl=59 time=33.810 ms 64 bytes from 142.250.196.164: seq=7 ttl=59 time=52.433 ms 64 bytes from 142.250.196.164: seq=8 ttl=59 time=26.257 ms 64 bytes from 142.250.196.164: seq=9 ttl=59 time=107.853 ms 64 bytes from 142.250.196.164: seq=10 ttl=59 time=25.989 ms 64 bytes from 142.250.196.164: seq=11 ttl=59 time=39.774 ms 64 bytes from 142.250.196.164: seq=12 ttl=59 time=32.129 ms 64 bytes from 142.250.196.164: seq=13 ttl=59 time=28.988 ms 64 bytes from 142.250.196.164: seq=14 ttl=59 time=28.511 ms 64 bytes from 142.250.196.164: seq=15 ttl=59 time=83.135 ms 64 bytes from 142.250.196.164: seq=16 ttl=59 time=55.145 ms 64 bytes from 142.250.196.164: seq=17 ttl=59 time=45.145 ms 64 bytes from 142.250.196.164: seq=18 ttl=59 time=53.389 ms 64 bytes from 142.250.196.164: seq=19 ttl=59 time=44.483 ms 64 bytes from 142.250.196.164: seq=20 ttl=59 time=46.227 ms 64 bytes from 142.250.196.164: seq=21 ttl=59 time=25.517 ms 64 bytes from 142.250.196.164: seq=22 ttl=59 time=25.970 ms 64 bytes from 142.250.196.164: seq=23 ttl=59 time=28.367 ms 64 bytes from 142.250.196.164: seq=24 ttl=59 time=49.157 ms 64 bytes from 142.250.196.164: seq=25 ttl=59 time=25.288 ms 64 bytes from 142.250.196.164: seq=26 ttl=59 time=55.143 ms 64 bytes from 142.250.196.164: seq=27 ttl=59 time=75.464 ms 64 bytes from 142.250.196.164: seq=28 ttl=59 time=54.593 ms 64 bytes from 142.250.196.164: seq=29 ttl=59 time=25.300 ms 64 bytes from 142.250.196.164: seq=30 ttl=59 time=28.135 ms 64 bytes from 142.250.196.164: seq=31 ttl=59 time=29.761 ms 64 bytes from 142.250.196.164: seq=32 ttl=59 time=43.752 ms 64 bytes from 142.250.196.164: seq=33 ttl=59 time=41.734 ms 64 bytes from 142.250.196.164: seq=34 ttl=59 time=34.332 ms 64 bytes from 142.250.196.164: seq=35 ttl=59 time=60.858 ms 64 bytes from 142.250.196.164: seq=36 ttl=59 time=36.470 ms 64 bytes from 142.250.196.164: seq=37 ttl=59 time=37.867 ms 64 bytes from 142.250.196.164: seq=38 ttl=59 time=57.375 ms 64 bytes from 142.250.196.164: seq=39 ttl=59 time=33.315 ms 64 bytes from 142.250.196.164: seq=40 ttl=59 time=30.885 ms 64 bytes from 142.250.196.164: seq=41 ttl=59 time=30.237 ms 64 bytes from 142.250.196.164: seq=42 ttl=59 time=29.726 ms 64 bytes from 142.250.196.164: seq=43 ttl=59 time=30.516 ms 64 bytes from 142.250.196.164: seq=44 ttl=59 time=33.814 ms 64 bytes from 142.250.196.164: seq=45 ttl=59 time=30.326 ms 64 bytes from 142.250.196.164: seq=152 ttl=59 time=82.994 ms 64 bytes from 142.250.196.164: seq=153 ttl=59 time=42.926 ms 64 bytes from 142.250.196.164: seq=154 ttl=59 time=28.252 ms 64 bytes from 142.250.196.164: seq=155 ttl=59 time=44.129 ms 64 bytes from 142.250.196.164: seq=156 ttl=59 time=25.783 ms 64 bytes from 142.250.196.164: seq=157 ttl=59 time=112.490 ms 64 bytes from 142.250.196.164: seq=158 ttl=59 time=45.445 ms 64 bytes from 142.250.196.164: seq=159 ttl=59 time=35.856 ms 64 bytes from 142.250.196.164: seq=160 ttl=59 time=56.713 ms 64 bytes from 142.250.196.164: seq=161 ttl=59 time=29.769 ms 64 bytes from 142.250.196.164: seq=162 ttl=59 time=114.034 ms 64 bytes from 142.250.196.164: seq=163 ttl=59 time=25.743 ms 64 bytes from 142.250.196.164: seq=164 ttl=59 time=48.542 ms 64 bytes from 142.250.196.164: seq=165 ttl=59 time=20.366 ms output of cm data command before and after the problem (ran at various times, I see the ip is changing): root@swi-mdm9x28-wp:~# cm data Index: 1 APN: iot.swir PDP Type: IPV4V6 Connected: yes Interface: rmnet\_data0 Family[IPv4]: inet IP[IPv4]: 10.123.197.124 Gateway[IPv4]: 10.123.197.125 Dns1[IPv4]: 8.8.8.8 Dns2[IPv4]: 4.2.2.2 root@swi-mdm9x28-wp:~# cm data Index: 1 APN: iot.swir PDP Type: IPV4V6 Connected: yes Interface: rmnet\_data0 Family[IPv4]: inet IP[IPv4]: 10.123.197.124 Gateway[IPv4]: 10.123.197.125 Dns1[IPv4]: 8.8.8.8 Dns2[IPv4]: 4.2.2.2 root@swi-mdm9x28-wp:~# cm data Index: 1 APN: iot.swir PDP Type: IPV4V6 Connected: yes Interface: rmnet\_data0 Family[IPv4]: inet IP[IPv4]: 10.123.198.243 Gateway[IPv4]: 10.123.198.244 Dns1[IPv4]: 8.8.8.8 Dns2[IPv4]: 4.2.2.2 root@swi-mdm9x28-wp:~# cm data Index: 1 APN: iot.swir PDP Type: IPV4V6 Connected: yes Interface: rmnet\_data0 Family[IPv4]: inet IP[IPv4]: 10.123.200.139 Gateway[IPv4]: 10.123.200.140 Dns1[IPv4]: 8.8.8.8 Dns2[IPv4]: 4.2.2.2 root@swi-mdm9x28-wp:~# Is there any method to disable to rmnet\_data0 interface temporarily? Here is my interfaces file: root@swi-mdm9x28-wp:~# cat /etc/network/interfaces # /etc/network/interfaces – configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # Wired or wireless interfaces auto eth0 iface eth0 inet dhcp # Wireless interfaces iface wlan0 inet manual pre-up /etc/init.d/tiwifi start post-down /etc/init.d/tiwifi stop ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [July 26, 2023, 10:20am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/4 "2023-07-26T10:20:42Z")
If there is no sim card, how can it connect cellular network? ---
**Author:** ![ravneet.singh.iitd](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@ravneet.singh.iitd](https://forum.sierrawireless.com/u/ravneet.singh.iitd)\ **Post date:** [July 26, 2023, 10:39am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/5 "2023-07-26T10:39:50Z")
I am not sure, I have never connected. Also, if I don’t connect to rmnet\_data interface, it will still list in the ifconfig command right? Is there any method to disable to rmnet\_data interface? I will just block it from interfering? ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [July 26, 2023, 10:45am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/6 "2023-07-26T10:45:18Z")
Do you have the cloudinterface app? Not sure if this app will connect network automatically: > **[APN will recover when mangOH Yellow reboot](https://forum.mangoh.io/t/apn-will-recover-when-mangoh-yellow-reboot/4830/11)** > > If you are using Windows 10, be aware that it may configure the APN if it is permitted to manage the connection. ---
**Author:** ![ravneet.singh.iitd](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@ravneet.singh.iitd](https://forum.sierrawireless.com/u/ravneet.singh.iitd)\ **Post date:** [July 26, 2023, 11:09am UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/7 "2023-07-26T11:09:22Z")
Yes I can see an app named cloudinterface in app status. Shall i stop it? ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [July 26, 2023, 12:00pm UTC](https://forum.sierrawireless.com/t/routing-table-changes-automatically-on-mangoh-yellow/30299/8 "2023-07-26T12:00:27Z")
Not sure, but do you have other idea?