My flint 2 doesn't recognize any network cables, so I can't get it to connect to the internet, only the wifi works
Just like that, the only input that has any sign of life is wan2, but my flint2 doesn't recognize it anyway, which means it doesn't have access to the internet.
Hello,
Does May I know the WAN1 (Ethernet1) work properly?
If the WAN2 (Ethernet2) is switched to as LAN mode, and connected to a wired client, is it normal?
Have you tried changing another network cable?
Please share the issue syslog with us to check it out.
wan1 doesn't work, no LAN and WAN ports work, only WAN2 which recognizes that it has a cable can't complete the dhcp and get IP, I've tested several cables, it seems that I have some hardware defect 
I hope it's not this because if it means that my filnt2 has turned into a piece of brick.
logread.tar (270.5 KB)
Guess it could be bad cable?
Might be able to look at command line for status of various things.
There are a few ways to un-brick it. The most simple may be the hard reset.
If that fails might have to go to uboot.
I've already tested various cables and reset them by pressing the button, as well as installing other firmware versions
https://thelinuxcode.com/list-network-interfaces-raspberry-pi/
I would think that one could see state of nic using command line.
Openwrt base might need some programs as it is running BusyBox.
The link should be up if to have connection to another nic I'd think. This assumes connections, plugs and wires along with both sides working.
root@GL-MT6000:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether ee:a2:4e:63:4d:46 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a3:f8:51 brd ff:ff:ff:ff:ff:ff
4: lan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a3:f8:52 brd ff:ff:ff:ff:ff:ff
5: ra0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 4e:0b:1a:64:f5:32 brd ff:ff:ff:ff:ff:ff
6: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a3:f8:53 brd ff:ff:ff:ff:ff:ff
7: ra1: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 96:83:c4:a3:f8:54 brd ff:ff:ff:ff:ff:ff
8: rax0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UNKNOWN mode DEFAULT group default qlen 1000
link/ether ca:cf:ba:46:c0:ae brd ff:ff:ff:ff:ff:ff
9: rax1: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 96:83:c4:a3:f8:55 brd ff:ff:ff:ff:ff:ff
10: apcli0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 92:83:c4:a3:f8:54 brd ff:ff:ff:ff:ff:ff
11: apclix0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 9e:83:c4:a3:f8:54 brd ff:ff:ff:ff:ff:ff
root@GL-MT6000:~# ifconfig
apcli0 Link encap:Ethernet HWaddr 92:83:C4:A3:F8:54
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)
apclix0 Link encap:Ethernet HWaddr 9E:83:C4:A3:F8:54
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)
br-lan Link encap:Ethernet HWaddr 94:83:C4:A3:F8:53
inet addr:192.168.8.1 Bcast:192.168.8.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:660 errors:0 dropped:0 overruns:0 frame:0
TX packets:379 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:56947 (55.6 KiB) TX bytes:48931 (47.7 KiB)
eth0 Link encap:Ethernet HWaddr EE:A2:4E:63:4D:46
inet6 addr: fe80::eca2:4eff:fe63:4d46/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:41306 (40.3 KiB)
Interrupt:119
eth1 Link encap:Ethernet HWaddr 94:83:C4:A3:F8:51
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)
Interrupt:119
lan1 Link encap:Ethernet HWaddr 94:83:C4:A3:F8:52
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:312 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:35084 (34.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:602 errors:0 dropped:0 overruns:0 frame:0
TX packets:602 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:56779 (55.4 KiB) TX bytes:56779 (55.4 KiB)
ra0 Link encap:Ethernet HWaddr 4E:0B:1A:64:F5:32
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1438 errors:306 dropped:0 overruns:0 frame:0
TX packets:331 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130727 (127.6 KiB) TX bytes:41993 (41.0 KiB)
Interrupt:6
rax0 Link encap:Ethernet HWaddr CA:CF:BA:46:C0:AE
UP BROADCAST RUNNING 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)
root@GL-MT6000:~# ls /sys/class/net/
apcli0 apclix0 br-lan eth0 eth1 lan1 lo ra0 ra1 rax0 rax1
from what i see on the logs i don't see much of a issue on the network ports.
Except wan being down, what I do notice is the errors on the ra0 interface, the mtu on the loopback is fine I compared with my own device.
wifi has a higher priority than wire, so if something happens like a high download or a wrong configuration i.e driver failure where lots of packets get lost, it could bring down wired connections.
Can you disable wifi for a bit and check?
if it fails again, I would like to read the output of dmesg if ethtool is present also from ethtool.
from the ip link command i do see a lan ip, so you get dhcp right or not?, it's only the wan part?
If not do you use a switch behind here?, maybe it is EEE this can be problematic on some equipment, the flint 2 mtk sdk may not handle EEE that good, it must be disabled on the switch then.
please post in this format:
```
code
```
Thanks 
I'm on road so I can't compare.
I recall Luci having similar information.
When I see difference between TX and RX numbers like one being zero it makes me think physical over software.
In this log, no WAN (eth1, first port) has plug-in/unplugging, but the WAN/LAN1 (eth0, second port) has plug-in and unplugging.
If you plug and unplug the WAN network cable during the above log, but the log is not printed, there may be hardware problems with the WAN port, you can contact support@gl-inet.com to obtain the more info. Thanks.