MT-6000/Flint 2 2.5Gbe ports

I recently got an MT-6000 and I got everything all set up how I wanted besides being unable to remap the "eth1" WAN 2.5Gbe port to the lan bridge and using "lan 5" as my WAN port. I would like 2x2.5Gbe ports if possible.
These are the steps I took (config attached too)

  1. Changed the WAN and WAN6 interfaces to LAN5
  2. Removed LAN5 from the br-lan and added eth1
  3. Save and apply.
    It applies fine but I cannot get my ISP to give it an IP address. There is no MAC address restriction or anything but even after rebooting the router and modem multiple times, letting it sit for about 20 min the other night etc... It just refuses to connect. The only thing I can think of is that the eth1 port is handled differently by openwrt (the second 2.5Gbe port is called lan1) but I am just spitballing on that one.
    I have talked to someone who had the stock firmware/openwrt install and was able to do it so it doesn't appear to be a hardware limitation but I am clearly not configuring something properly.

Appreciate the help in advance, network config is below:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdea:dc29:6e61::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth1'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'

config device
        option name 'lan1'
        option macaddr '94:83:c4:a4:7e:72'

config device
        option name 'lan2'
        option macaddr '94:83:c4:a4:7e:72'

config device
        option name 'lan3'
        option macaddr '94:83:c4:a4:7e:72'

config device
        option name 'lan4'
        option macaddr '94:83:c4:a4:7e:72'

config device
        option name 'lan5'
        option macaddr '94:83:c4:a4:7e:72'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        list dns '192.168.1.151'
        list dns '8.8.8.8'

config device
        option name 'eth1'
        option macaddr '94:83:c4:a4:7e:70'

config interface 'wan'
        option device 'lan5'
        option proto 'dhcp'

config interface 'wan6'
        option device 'lan5'
        option proto 'dhcpv6'
        option reqaddress 'try'
        option reqprefix 'auto'

IIRC the reason for the default config on this device was due to the internal switch linkage

1 Like

yeah it lists an eth0 as an ethernet switch (which is not explicitly used as far as I can tell. I am sure it is used but not in the config file) so I think there is something to that. It also looks like the SoC has 2x 2.5Gbe links and it talks about splitting one in to multiple 1Gbe ports so there is a good chance it only has a total of 5Gb of bandwidth available.
The guy I talked to said he had to change a setting for that first port in the stock firmware and then change the layout in the "advanced" standard Luci interface. Not sure if that was necessary and if so, whether it is possible via openwrt but mucked around about as much as I could without worrying I might nuke the router and take my internet down (and have an unhappy family as a result).

Maybe take a look at this thread: Configure LAN port as WAN

Were you able to get it to work just by swapping LAN5 to the WAN/WAN6 interface and moving eth1 to the br-lan? Or did you decide against it since that 2.5Gbe port isn't switched? If you got it to work, I may give it another go to see if I can because I have given up trying that as of now since it isn't behaving like any other device I have switched the ports around on using openwrt.
I've tried that a handful of times but can't get it to connect to the internet/get an IP from my modem when I do that no matter how long I wait or how many times I restart one or both devices.
Appreciate the response!

I can't remember if I got it to work as suggested. It worked at least partly.
In hindsight it seemed not a good idea as explained in this (Configure LAN port as WAN - #21 by Jack007) post.

Yeah the fact that the one runs through the CPU makes me think it's not worth the trouble. Can get a good 2.5Gbe & SFP+ switch for so cheap now it doesn't make sense to fight with it when the throughput will also be bad or cause crazy high CPU usage.
I think I will just grab a switch and make it simple. Can run my network off that out of the 2.5Gbe lan port and have the mt6000 as the wifi AP and manage SQM and such.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.