WAN Port on Flint 2 Not Detecting Cable

Technical Support for Routers
1

I have a problem with my new Flint 2 router, just setup yesterday (1-Dec-2024). The first port (WAN) doesn’t detect a cable, but if I use the second port (WAN/LAN) instead, it works. Currently, I have cables connected to both ports, but only the second port is detecting the connection.

Also, can you confirm which port is eth0 and which is eth1? Is the first port (WAN) eth0 and the second port (WAN/LAN) eth1?

image
image1000×800 86.2 KB

root@GL-MT6000:~# ethtool eth0
Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  2500baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: yes
root@GL-MT6000:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP AUI BNC MII FIBRE Backplane ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                2500baseX/Full
                                1000baseX/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: no
root@GL-MT6000:~#

GUI eth1

image
image1044×245 7.14 KB

GUI eth2
image
image1041×369 11.6 KB

2

ifconfig to check the network interfaces.

eth0 is the bridge port.
eth1 is the WAN (Ethernet1 in GUI), 2.5G PHY
lan1 is the WAN/LAN (Ethernet 2 in GUI), 2.5G PHY
lan2/3/4/5 is the LAN, all 1G PHY.

If bring the Eth1 interface to LAN mode and connect a client device, how about the situation?

5

I don't quite understand, it said no link detected, but the cable detected in GUI on converted as LAN port?

image
image1045×246 6.57 KB

BusyBox v1.33.2 (2024-10-17 09:43:37 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 21.02-SNAPSHOT
 -----------------------------------------------------
root@GL-MT6000:~# ifconfig
apcli0    Link encap:Ethernet  HWaddr 
          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 (removed)
          inet addr:192.168.8.2  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: (removed)/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1600735 errors:0 dropped:34 overruns:0 frame:0
          TX packets:3416219 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:420382870 (400.9 MiB)  TX bytes:1897641250 (1.7 GiB)

br-lan    Link encap:Ethernet  HWaddr (removed)
          inet addr:192.168.6.1  Bcast:192.168.6.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1563151 errors:0 dropped:2948 overruns:0 frame:0
          TX packets:1461770 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:263625534 (251.4 MiB)  TX bytes:699969747 (667.5 MiB)

eth0      Link encap:Ethernet  HWaddr (removed)
          inet6 addr: (removed)/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1533793 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2193830 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:75526182 (72.0 MiB)  TX bytes:1611074167 (1.5 GiB)
          Interrupt:119

eth1      Link encap:Ethernet  HWaddr (removed)
          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 (removed)
          inet addr:192.168.8.3  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: (removed)64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:372092 errors:0 dropped:66 overruns:0 frame:0
          TX packets:283957 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20586033 (19.6 MiB)  TX bytes:12921965 (12.3 MiB)

lan2      Link encap:Ethernet  HWaddr (removed)
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19866 errors:0 dropped:0 overruns:0 frame:0
          TX packets:295278 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4642925 (4.4 MiB)  TX bytes:18589261 (17.7 MiB)

lan3      Link encap:Ethernet  HWaddr (removed)
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:290116 errors:0 dropped:44 overruns:0 frame:0
          TX packets:441897 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:76831344 (73.2 MiB)  TX bytes:308078398 (293.8 MiB)

lan4      Link encap:Ethernet  HWaddr (removed)
          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)

lan5      Link encap:Ethernet  HWaddr (removed)
          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)

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:16530 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16530 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5176292 (4.9 MiB)  TX bytes:5176292 (4.9 MiB)

ra0       Link encap:Ethernet  HWaddr (removed)
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7948103 errors:7181973 dropped:0 overruns:0 frame:0
          TX packets:353592 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:266884640 (254.5 MiB)  TX bytes:38957076 (37.1 MiB)
          Interrupt:6

rax0      Link encap:Ethernet  HWaddr (removed)
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2652845 errors:140130 dropped:0 overruns:0 frame:0
          TX packets:4137414 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:675229882 (643.9 MiB)  TX bytes:4897871946 (4.5 GiB)

root@GL-MT6000:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: MII
        PHYAD: 1
        Transceiver: external
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: no
root@GL-MT6000:~#
6

Had a similar issue to. After much reading and troubleshooting got there.

Best way to enable wan on Ethernet 1. Connecting a Lan port on internet box/router to Wan on Flint2.Make sure your internet box is in Bridge mode and connect to a normal LAN port. Power off the flint2, connect to Wan from Lan on internet box. wait a few moments then follow connecting using IP address or App on phone. You should notice a connected ethernet 1 cable and trying to do something to get a connection. Options to modify using DHCP / Static may be required but I use IP4 internet or PPoE. The option for using IP6 is in the Network setting on the left. so was required to input Internet details username and password possible other setting may be required. Hope this helps. so LAN to WAN is the rule . Power off flint before connecting.

1 Like
7

Yes, but as soon as you config to WAN it starts expecting its own dhcp server running & router to be in place as the WAN interface wont run on the sane subnet as the LAN....
I WANT a flat network, ONE dhcp server....
Everything running LAN, NO WAN to be seen...

8

TP Link have always been able to be an access point with LAN only connections - Simple out of the box...
Why does FLINT2 need to have constraints?
No need for a WAN to be configured

9

In the settings under networking mentions about dhcp server and LAN . You can change the wan ports to Lan. Think this device is ok for plug and play, there is alot of customisation and familiarity to be made with the Linux OS :slightly_smiling_face: Been a learning curve :slight_smile: get mine working ok with internet and with Berly AX AP. But for me all work great now. Been nice using this compared to the other things In have bought in the past that gave the illusion of plug and play and was not. Fingers crossed you manage to get it working. :slight_smile:

10

Oh, I mean if the ETH1 as LAN port, to see if it can work with the clients like PC, to verify that the physical hardware for this one port is available.

Flint 2 also have a access point (AP) mode, it can find in the GL GUI -> Network -> Network mode.