MTCDT-LEU1-247A not being assigned default gateway

[some_dev]

I have a MTCDT-LEU1-247A with Firmware1.6.4.
I have eth0 configured as DHCP client on a 192.168.88.x network but it does not appear to have connectivity outside of the network. I tried pinging the gateway and 8.8.8.8. I can reach the former but not later.

What is puzzling is that I have a MTCDT-246A also with Firmware1.6.4 with exact same config (however, MTCDT-LEU1-247A has more interfaces) and no such issues.

running route -n:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.88.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

ANy ideas anyone?

[Jeff Hatch]

some_dev,

Your device appears to have obtained an IP, but not a gateway from DHCP. It is possible that there is a bug and the default gateway is not getting set, but if it is getting set on the other device I am not so sure about that.

Has the Ethernet eth0 interface been configured as a LAN or WAN on the device that is not getting a default route?

For the device that is working, what additional interfaces does it have and how are they configured?

Jeff

[some_dev]

Jeff Hatch,

Thanks for getting back so quick.
It is the device that is not being assigned the gateway that has the extra interfaces.
Overview of device in question(Note, WIFI is off):

eth0–> LAN; ETHER; DHCP Client; 192.168.88.58/24; Bridge: —
ppp0–> WAN; PPP; PPP
wlan0–> WAN; WIFI_AS_WAN; DHCP Client; IP Addr: <blank>; Bridge: —
wlan1–> LAN; WIFI_AP; IP Mode: DHCP Client; IP Addr:<blank>; Bridge:br0
br0–> LAN, BRIDGE, Static, IP Addr: 0.0.0.0/24, Bridge: br0

Working device:
eth0–> LAN; ETHER; DHCP Client; 192.168.88.71/24; Bridge: —
br0–> LAN; BRIDGE; IP Mode:<blank>; IP Addr: <blank>; Bridge: br0

All WANs are disabled on both devices.
What is weird to me is that all the wifi and PPP interfaces are displayed despite being disabled.

Let me know if you require more details.

• This reply was modified 5 years, 11 months ago by some_dev.
• This reply was modified 5 years, 11 months ago by some_dev.
• This reply was modified 5 years, 11 months ago by some_dev.
• This reply was modified 5 years, 11 months ago by some_dev.
• This reply was modified 5 years, 11 months ago by some_dev.
• This reply was modified 5 years, 11 months ago by some_dev. Reason: Clarity

[Jeff Hatch]

Does the device that is working have a default route? On the device with issues, is ppp/Cellular enabled? If Cellular is enabled, but it is not getting a connection and not getting an IP, default route, and DNS servers, that might be part of the problem. pppd is what tells the kernel to create the ppp0 interface and configures that interface with the IP and gateway from the provider.

If ppp/Cellular is not enabled, can you provide the “route -n” on both devices along with “ifconfig -a”? There may be more configuration information needed to get to the bottom of this.

Jeff

[some_dev]

Working device::
route -n:
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.88.1 0.0.0.0 UG 0 0 0 eth0
192.168.88.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

I’ll include the (ifconfig -a)s in a seperate post

Device in question::
route -n:
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
192.168.88.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

For the device in question, cellular is not enabled.
Looks like this could take a while alright.

• This reply was modified 5 years, 11 months ago by some_dev.
• This reply was modified 5 years, 11 months ago by some_dev.

[some_dev]

Working device ifconfig -a
admin@localhost:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:08:00:4A:45:35
inet addr:192.168.88.71 Bcast:192.168.88.255 Mask:255.255.255.0
inet6 addr: fe80::208:ff:fe4a:4535%3069057744/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:94210 errors:0 dropped:891 overruns:0 frame:0
TX packets:38462 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7410119 (7.0 MiB) TX bytes:12882785 (12.2 MiB)
Interrupt:23 Base address:0xc000

gre0 Link encap:UNSPEC HWaddr 00-00-00-00-35-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1476 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)

gretap0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1462 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)

ip_vti0 Link encap:UNSPEC HWaddr 00-00-00-00-35-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1364 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)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%3069057744/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:87544 errors:0 dropped:0 overruns:0 frame:0
TX packets:87544 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17471915 (16.6 MiB) TX bytes:17471915 (16.6 MiB)

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)

tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-35-00-00-00-00-00-00-00-00-00-00-00
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)

[some_dev]

Device in question ifconfig -a
admin@mtcdt:~# ifconfig -a
br0 Link encap:Ethernet HWaddr AA:D4:35:0F:3E:D2
inet addr:127.0.0.1 Bcast:127.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::a8d4:35ff:fe0f:3ed2%3069557456/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:648 (648.0 B)

eth0 Link encap:Ethernet HWaddr 00:08:00:4A:44:13
inet addr:192.168.88.58 Bcast:192.168.88.255 Mask:255.255.255.0
inet6 addr: fe80::208:ff:fe4a:4413%3069557456/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22524 errors:0 dropped:690 overruns:0 frame:0
TX packets:4233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1915359 (1.8 MiB) TX bytes:2511665 (2.3 MiB)
Interrupt:23 Base address:0xc000

gre0 Link encap:UNSPEC HWaddr 00-00-00-00-33-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1476 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)

gretap0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1462 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)

ip_vti0 Link encap:UNSPEC HWaddr 00-00-00-00-33-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1364 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)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%3069557456/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:37007 errors:0 dropped:0 overruns:0 frame:0
TX packets:37007 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5709876 (5.4 MiB) TX bytes:5709876 (5.4 MiB)

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)

tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-33-00-00-00-00-00-00-00-00-00-00-00
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)

wwan0 Link encap:Ethernet HWaddr BA:48:ED:41:9C:81
BROADCAST MULTICAST 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)

[some_dev]

Quick update;
Setting static IP and gateway configs for eth0 has worked as a work around.

[Jeff Hatch]

The device that has a gateway has to be getting the gateway from DHCP if that is how the eth0 is configured, so that appears to be working. The non-working device has something strange: It has a br0 (bridge) interface with localhost set for it’s address.

Check on the br0 configuration on the non-working device. If it is explicitly set to localhost for it’s info try clearing that out. I am not sure that is causing any issues, but it is odd.

It may be possible that with the bridge configured it is somehow messing with the routing. Make sure that eth0 is not configured “under the bridge”. I’ve had the bridge configured with nothing assigned to it in the past and things worked find, but not with the localhost address.

Jeff

[some_dev]

Jeff,

I shoudl ahve mentioned that I configured those settings on br0 whilst changing from another setting for testing. Was a matter of not being allowed to leave it blank.

I’ll probably have to contact support directly on this one.

[Author]

Posts