Do you require VLAN id 2 access to the management port on 172.16.2.250 from 172.16.2.254 < which needs to be your GL router, this needs to be set up in the firewall in the GL router.
To re-flash the DM200 I had my PC directly connected to the it's ethernet port. After the reflash I configured my PC's network interface to the 172.16.2.x subnet. I tried a fixed IP of either 172.16.2.2 or 172.16.2.254 on the PC, but neither let me access the modem's management interface. Maybe I needed to be using a VLAN tag at this point? (VLANs are not something i've used before).
Anyway, now the modem+router combo is up and running it would be nice to be able to get to the modem admin interfaces. Hopefully the required configuration for the router is documented somwhere. I'm guessing this woudl require some combination of firewall rules and a routing rule? (to have the modem address routed over the WAN port at TCP/IP level rather than just forwarded to the ISP over WAN).
mt6000:8080/cgi-bin/luci/admin/network/network
add network interface
Name Management
Protocol Static Address
Device eth0.2 < so WAN port and Vlan ID 2
Create interface
edit interface, set address of 172.16.2.254 and default gateway 172.16.2.250
Hi,
I have a very similar problem (even the same ISP - Utility Warehouse) I have been migrating from a Netgear D7000, to a Flint 2. I can use the D7000 as my modem if I leave it as a full router and connect it to the WAN port of the Flint, configured for DHCP. That works OK, but I was hoping to use as little of the D7000 as possible as it has become quite unreliable. I also need port forwarding so I have to set that up to leapfrog through both routers (which actually works!).
The D7000 has a modem only mode but get the same issue as @incans . I changed my WAN port to PPPoE with VLAN ID 101 but get the same log messages as far as I can tell.
I was using lan1 set as a second WAN port, to make it easier to revert to my working setup. Log was:
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.620857] device lan1 left promiscuous mode
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.626897] mt7530 mdio-bus:1f lan1: Link is Down
Sun Jan 5 13:57:23 2025 daemon.info avahi-daemon[5073]: Interface lan1.IPv6 no longer relevant for mDNS.
Sun Jan 5 13:57:23 2025 daemon.info avahi-daemon[5073]: Leaving mDNS multicast group on interface lan1.IPv6 with address fe80::50aa:b5ff:fe3d:65a2.
Sun Jan 5 13:57:23 2025 daemon.info avahi-daemon[5073]: Withdrawing address record for fe80::50aa:b5ff:fe3d:65a2 on lan1.
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' is disabled
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.640998] mt7530 mdio-bus:1f lan1: configuring for phy/sgmii link mode
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.648080] 8021q: adding VLAN 0 to HW filter on device lan1
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' is enabled
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' is setting up now
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.661863] device lan1 entered promiscuous mode
Sun Jan 5 13:57:23 2025 daemon.notice netifd: VLAN 'lan1.101' link is down
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' has link connectivity loss
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Network device 'lan1' link is down
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' is now down
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.744364] device lan1 left promiscuous mode
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' is disabled
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.755642] mt7530 mdio-bus:1f lan1: configuring for phy/sgmii link mode
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.762873] 8021q: adding VLAN 0 to HW filter on device lan1
Sun Jan 5 13:57:23 2025 daemon.notice netifd: Interface 'secondwan' is enabled
Sun Jan 5 13:57:23 2025 kern.info kernel: [ 890.774672] device lan1 entered promiscuous mode
Sun Jan 5 13:57:23 2025 user.notice firewall: Reloading firewall due to ifdown of secondwan ()
Sun Jan 5 13:57:24 2025 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "secondwan" ] } }
Sun Jan 5 13:57:27 2025 kern.info kernel: [ 894.263117] mt7530 mdio-bus:1f lan1: Link is Up - 1Gbps/Full - flow control rx/tx
Sun Jan 5 13:57:27 2025 kern.info kernel: [ 894.270630] IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
Sun Jan 5 13:57:27 2025 daemon.notice netifd: Network device 'lan1' link is up
Sun Jan 5 13:57:27 2025 daemon.notice netifd: VLAN 'lan1.101' link is up
Sun Jan 5 13:57:27 2025 daemon.notice netifd: Interface 'secondwan' has link connectivity
Sun Jan 5 13:57:27 2025 daemon.notice netifd: Interface 'secondwan' is setting up now
Sun Jan 5 13:57:29 2025 daemon.info avahi-daemon[5073]: Joining mDNS multicast group on interface lan1.IPv6 with address fe80::50aa:b5ff:fe3d:65a2.
Sun Jan 5 13:57:29 2025 daemon.info avahi-daemon[5073]: New relevant interface lan1.IPv6 for mDNS.
Sun Jan 5 13:57:29 2025 daemon.info avahi-daemon[5073]: Registering new address record for fe80::50aa:b5ff:fe3d:65a2 on lan1.*.
Sun Jan 5 13:57:57 2025 daemon.err insmod: module is already loaded - slhc
Sun Jan 5 13:57:57 2025 daemon.err insmod: module is already loaded - ppp_generic
Sun Jan 5 13:57:57 2025 daemon.err insmod: module is already loaded - pppox
Sun Jan 5 13:57:57 2025 daemon.err insmod: module is already loaded - pppoe
Sun Jan 5 13:57:57 2025 daemon.info pppd[21053]: Plugin rp-pppoe.so loaded.
Sun Jan 5 13:57:57 2025 daemon.info pppd[21053]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Sun Jan 5 13:57:57 2025 daemon.notice pppd[21053]: pppd 2.4.8 started by root, uid 0
Sun Jan 5 13:58:12 2025 daemon.warn pppd[21053]: Timeout waiting for PADO packets
Sun Jan 5 13:58:12 2025 daemon.err pppd[21053]: Unable to complete PPPoE Discovery
Sun Jan 5 13:58:12 2025 daemon.info pppd[21053]: Exit.
Sun Jan 5 13:58:12 2025 daemon.notice netifd: Interface 'secondwan' is now down
It does sound as if you have the same problem that i did, which is that when manufacturers say they have a "VDSL Modem mode", that does not necessarily mean the same thing to different vendors.
In my case I was able, after some false starts, to re-flash my Netgear DM200 with a "Pure bridge" version of OpenWRT that did work. I don't know if this is an option for your D7000, but if it is, it should work although obvously there is always some risk re-flashing a firmware device, and once installed it's not easy to get at to install updates, so it's likely to stay on one firmware version forever.
The most assured, but also most expensive, option is to go buy a device that works as a bridge out of the box. A lot of people recommend the Draytek devices. I had a V130 which was resonably easy to set up and worked well for years until a lightning strike killed it. The current equivalent is the V167 I believe.
There are a ton of old basic routers lying around these days on eBay and FB, or even in your or a relatives loft. I suspect there will be forums (maybe including this one) where people can recommend devices that are easy to re-purpose, ideally routers that have proper "pure bridge" mods than can just be selected from the standard user interface.
Thanks for the tips. My Draytek V167 arrived today and is now working nicely.
It gave me a bit of a scare - I had to remove the vlan id = 101 which seemed to be required for my V7000 to log in but now seems to be required to be not set for my Flint 2 to login via the v167.
