MTCDT-LEU1-247A Firmware 6.3.0 network issues

[Ian Bester]

Hi All

I have limited technical skills, but I hope someone can help me. I upgraded my older conduit from V5.0.1 to 6.3.0, but it doesn’t connect to the internet since the update.

It is currently connected to my local network via eth0 (and I can access it via the webUI), but I cannot ping out, and I get an error when checking the connection to my AWS MQTT endpoint (Temporary failure in name resolution).

Can anyone please help me with the next steps to troubleshoot? Many thanks.
Ian

[Jason Reiss]

Do you have eth0 on the Conduit setup as WAN?
Is it setup as DHCP client?
Does it show gateway and dns server addresses? See Setup > Network Interfaces.

[Jason Reiss]

Other commands to look at.

admin@mtcdt:~$ sudo ifconfig
admin@mtcdt:~$ nslookup google.com
Server:         127.0.0.1
Address:        127.0.0.1:53

Non-authoritative answer:
Name:   google.com
Address: 172.217.4.46

Non-authoritative answer:
Name:   google.com
Address: 2607:f8b0:4009:804::200e

admin@mtcdt:~$ sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         172.16.0.1      0.0.0.0         UG    0      0        0 eth0
172.16.0.0      *               255.255.0.0     U     0      0        0 eth0
192.168.2.0     *               255.255.255.0   U     0      0        0 br0

[Ian Bester]

ifconfig output:

eth0      Link encap:Ethernet  HWaddr 00:08:00:4A:28:7D  
          inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6243 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6341 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:847621 (827.7 KiB)  TX bytes:4304898 (4.1 MiB)
          Interrupt:24 Base address:0xc000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:110284 errors:0 dropped:0 overruns:0 frame:0
          TX packets:110284 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:13330938 (12.7 MiB)  TX bytes:13330938 (12.7 MiB)

wlan0     Link encap:Ethernet  HWaddr 00:23:A7:C6:A6:90  
          UP 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)

nslookup google.com output:

Server:		127.0.0.1
Address:	127.0.0.1:53

** server can't find google.com: REFUSED

** server can't find google.com: REFUSED

[Ian Bester]

Current eth0 set-up:

LAN, DHCP enabled

[Steve Kovarik]

Ian,
And what are the results if you try and ping an IP address like 8.8.8.8

[Jason Reiss]

You will want to setup eth0 as WAN to reach the Internet.

[Jason Reiss]

Or the route is not set.

admin@mtcdt:~$ sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         172.16.0.1      0.0.0.0         UG    0      0        0 eth0
172.16.0.0      *               255.255.0.0     U     0      0        0 eth0
192.168.2.0     *               255.255.255.0   U     0      0        0 br0

[Jason Reiss]

When configured as WAN the DNS server will be configured in this file automatically.

admin@mtcdt:/var/run$ cat /var/run/wan_resolv.conf
domain mts.test
nameserver 172.16.0.20

[Author]

Posts