No Internet Connection! Find a network to reconnect. GL-MT2500A

Confucius · September 30, 2024, 2:36pm

I have a usb hard drive attached. Which I can access via wired-LAN. So all good there.

But the GL-MT2500a from the NETWORK tab tells me "No Internet Connection! Find a network to reconnect."
While I don't really need access to the internet via it, it will not be able to find any updates it needs. It has a static ip address.

So what am I missing here?
Why can it not find it's way out to the internet?

Edit to add this from the system log.
Mon Sep 30 15:56:50 2024 user.notice AdGuardHome[5765]: 2024/09/30 15:56:50.750295 [error] dnsproxy: upstream 9.9.9.9:53 failed to exchange ;1.openwrt.pool.ntp.org. IN AAAA in 180.692µs: dialing 9.9.9.9:53 over udp: dial udp 9.9.9.9:53: connect: network is unreachable

admon · September 30, 2024, 5:28pm

DNS does not work, that's why it tells you that you don't have internet.
Seems like your upstream network blocks DNS to 9.9.9.9

Try to use the provided DNS of your upstream network or change AdGuard Home to use DNS-over-HTTPS or DNS-over-TLS.

Confucius · September 30, 2024, 6:21pm

I had not done anything with AdGuard. It's now disabled.
Still no internet.
All i've done is change it's ip to a static one and enabled the network storage part for the usb hard drive.
Is there something else that needs doing?
I'll look for where I can enter the DNS stuff.

Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.682558] fuse: init (API version 7.31)
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.691716] usbcore: registered new interface driver cdc_acm
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.697427] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.708466] usbcore: registered new interface driver cdc_wdm
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.718528] usbcore: registered new interface driver ipheth
Mon Sep 30 19:00:28 2024 kern.debug kernel: [    9.728761] -->mtfwd_init(ver:2.0)
Mon Sep 30 19:00:28 2024 kern.debug kernel: [    9.728802] <--
Mon Sep 30 19:00:28 2024 kern.debug kernel: [    9.733135] -->mtqos_init(), mtqos ver:1.0
Mon Sep 30 19:00:28 2024 kern.debug kernel: [    9.734952] <--
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.752156] usbcore: registered new interface driver usbserial_generic
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.758820] usbserial: USB Serial support registered for generic
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.786501] xt_time: kernel timezone is -0000
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.792045] usbcore: registered new interface driver cdc_ether
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.799393] usbcore: registered new interface driver cdc_ncm
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.807079] usbcore: registered new interface driver huawei_cdc_ncm
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.817082] PPP generic driver version 2.4.2
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.822552] NET: Registered protocol family 24
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.828209] usbcore: registered new interface driver qmi_wwan
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.835269] usbcore: registered new interface driver rndis_host
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.845217] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.853071] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.863716] usbcore: registered new interface driver option
Mon Sep 30 19:00:28 2024 kern.info kernel: [    9.869417] usbserial: USB Serial support registered for GSM modem (1-port)
Mon Sep 30 19:00:28 2024 user.info kernel: [    9.878320] kmodloader: done loading kernel modules from /etc/modules.d/*
Mon Sep 30 19:00:29 2024 daemon.notice procd: /etc/rc.d/S18vpnpolicy: uci: Entry not found
Mon Sep 30 19:00:29 2024 daemon.notice procd: /etc/rc.d/S18vpnpolicy: uci: Entry not found
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: Connected to system UBus
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: started, version 2.85 cachesize 150
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: DNS service limited to local subnets
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: UBus support enabled: connected to system bus
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain test
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain onion
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain localhost
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain local
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain invalid
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain bind
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: using only locally-known addresses for domain lan
Mon Sep 30 19:00:29 2024 daemon.warn dnsmasq[2401]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: read /etc/hosts - 4 addresses
Mon Sep 30 19:00:29 2024 daemon.info dnsmasq[2401]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Sep 30 19:00:29 2024 authpriv.info dropbear[2464]: Not backgrounding
Mon Sep 30 19:00:30 2024 daemon.err rmmod: module is not loaded
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: bonding
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: 8021ad
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: 8021q
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: macvlan
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: veth
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: bridge
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: Network device
Mon Sep 30 19:00:30 2024 user.notice : Added device handler type: tunnel
Mon Sep 30 19:00:30 2024 user.notice kmwan: config json str={ "op": 0, "data": { "sensitivity": 5000, "mode": "failover" } }
Mon Sep 30 19:00:30 2024 kern.debug kernel: [   13.817671] kmwan: sensitivity and mode are set.
Mon Sep 30 19:00:30 2024 kern.info kernel: [   14.253774] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Mon Sep 30 19:00:30 2024 kern.info kernel: [   14.282157] MediaTek MT7981 PHY mdio-bus:00: TX-VCM SW cal result: 0x2
Mon Sep 30 19:00:30 2024 kern.info kernel: [   14.289806] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:00] driver [MediaTek MT7981 PHY]
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.302313] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/gmii link mode
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.312259] br-lan: port 1(eth1) entered blocking state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.317548] br-lan: port 1(eth1) entered disabled state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.323076] device eth1 entered promiscuous mode
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.329029] br-lan: port 1(eth1) entered blocking state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.334277] br-lan: port 1(eth1) entered forwarding state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.342521] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.351103] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'lan' is enabled
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'lan' is setting up now
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'lan' is now up
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.357495] br-lan: port 2(eth0) entered blocking state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.364780] br-lan: port 2(eth0) entered disabled state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.370240] device eth0 entered promiscuous mode
Mon Sep 30 19:00:31 2024 daemon.notice netifd: bridge 'br-lan' link is up
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'loopback' is enabled
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'loopback' is setting up now
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'loopback' is now up
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Network device 'eth0' link is up
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Network device 'lo' link is up
Mon Sep 30 19:00:31 2024 daemon.notice netifd: Interface 'loopback' has link connectivity
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.386901] br-lan: port 2(eth0) entered blocking state
Mon Sep 30 19:00:31 2024 kern.info kernel: [   14.392148] br-lan: port 2(eth0) entered forwarding state
Mon Sep 30 19:00:31 2024 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Sep 30 19:00:31 2024 daemon.notice procd: /etc/rc.d/S40gl_nas_diskmanager: start app = /usr/bin/gl_nas_diskmanager
Mon Sep 30 19:00:31 2024 user.notice firewall: Reloading firewall due to ifup of loopback (lo)
Mon Sep 30 19:00:31 2024 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Mon Sep 30 19:00:31 2024 kern.info kernel: [   15.274148] br-lan: port 1(eth1) entered disabled state
Mon Sep 30 19:00:32 2024 kern.info kernel: [   15.912594] tertf: br-lan registered, add it
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Successfully dropped root privileges.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: avahi-daemon 0.8 starting up.
Mon Sep 30 19:00:33 2024 daemon.warn avahi-daemon[4059]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: No service file found in /etc/avahi/services.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.0.100.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: New relevant interface br-lan.IPv4 for mDNS.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: New relevant interface lo.IPv6 for mDNS.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: New relevant interface lo.IPv4 for mDNS.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Network interface enumeration completed.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Registering new address record for 192.168.0.100 on br-lan.IPv4.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Registering new address record for ::1 on lo.*.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Registering HINFO record with values 'AARCH64'/'LINUX'.
Mon Sep 30 19:00:33 2024 daemon.info avahi-daemon[4059]: Server startup complete. Host name is GL-MT2500.local. Local service cookie is 3705410089.
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]: [2024/09/30 19:00:33.991372,  0] ../../lib/util/become_daemon.c:136(daemon_ready)
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]: [2024/09/30 19:00:33.992708,  0] ../../source3/nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast)
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]:   become_domain_master_browser_bcast:
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]:   Attempting to become domain master browser on workgroup WORKGROUP on subnet 192.168.0.100
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]: [2024/09/30 19:00:33.993139,  0] ../../source3/nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast)
Mon Sep 30 19:00:33 2024 daemon.err nmbd[3770]:   become_domain_master_browser_bcast: querying subnet 192.168.0.100 for domain master browser on workgroup WORKGROUP
Mon Sep 30 19:00:34 2024 daemon.err smbd[3768]: [2024/09/30 19:00:34.555576,  0] ../../lib/util/become_daemon.c:136(daemon_ready)
Mon Sep 30 19:00:34 2024 daemon.err smbd[3768]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dhcp
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/wireless reload dependency on /etc/config/network
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/luci-splash
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/qos
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/miniupnpd
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/odhcpd
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
Mon Sep 30 19:00:36 2024 user.notice ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
Mon Sep 30 19:00:37 2024 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/luci_statistics
Mon Sep 30 19:00:37 2024 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/dhcp
Mon Sep 30 19:00:37 2024 daemon.notice ntfs-3g[4656]: Version 2017.3.23 integrated FUSE 27
Mon Sep 30 19:00:37 2024 daemon.notice ntfs-3g[4656]: Mounted /dev/sda4 (Read-Write, label "WINDOWS", NTFS 3.1)
Mon Sep 30 19:00:37 2024 daemon.notice ntfs-3g[4656]: Cmdline options: noatime,big_writes,async,force
Mon Sep 30 19:00:37 2024 daemon.notice ntfs-3g[4656]: Mount options: async,force,allow_other,nonempty,noatime,fsname=/dev/sda4,blkdev,blksize=4096
Mon Sep 30 19:00:37 2024 daemon.notice ntfs-3g[4656]: Ownership and permissions disabled, configuration type 1
Mon Sep 30 19:00:37 2024 daemon.notice procd: /etc/rc.d/S90zerotier: disabled in config
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S97gl_nas_sys:  3768 root     35036 S    /usr/sbin/smbd -F
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S97gl_nas_sys:  4289 root     33468 S    {smbd-notifyd} /usr/sbin/smbd -F
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S97gl_nas_sys:  4290 root     33460 S    {cleanupd} /usr/sbin/smbd -F
Mon Sep 30 19:00:38 2024 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S99disk_manage: start app = /usr/bin/disk_manage
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S99gl_nas_sys_dl: start app = /usr/bin/gl_nas_sys
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S99gl_nas_sys_dl: === nas enable
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S99gl_nas_sys_up: start app = /usr/bin/gl_nas_sys
Mon Sep 30 19:00:38 2024 daemon.notice procd: /etc/rc.d/S99gl_nas_sys_up: === nas enable
Mon Sep 30 19:00:39 2024 daemon.notice procd: /etc/rc.d/S99webdav_ser: start app = /usr/bin/webdav_ser
Mon Sep 30 19:00:39 2024 daemon.info procd: - init complete -
Mon Sep 30 19:00:39 2024 daemon.notice ntfs-3g[6136]: Version 2017.3.23 integrated FUSE 27
Mon Sep 30 19:00:39 2024 daemon.notice ntfs-3g[6136]: Mounted /dev/sda5 (Read-Write, label "RECOVERY", NTFS 3.1)
Mon Sep 30 19:00:39 2024 daemon.notice ntfs-3g[6136]: Cmdline options: noatime,big_writes,async,force
Mon Sep 30 19:00:39 2024 daemon.notice ntfs-3g[6136]: Mount options: async,force,allow_other,nonempty,noatime,fsname=/dev/sda5,blkdev,blksize=4096
Mon Sep 30 19:00:39 2024 daemon.notice ntfs-3g[6136]: Ownership and permissions disabled, configuration type 1
Mon Sep 30 19:00:41 2024 daemon.err nmbd[3770]: [2024/09/30 19:00:41.313992,  0] ../../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
Mon Sep 30 19:00:41 2024 daemon.err nmbd[3770]:   *****
Mon Sep 30 19:00:41 2024 daemon.err nmbd[3770]:
Mon Sep 30 19:00:41 2024 daemon.err nmbd[3770]:   Samba server GL-MT2500 is now a domain master browser for workgroup WORKGROUP on subnet 192.168.0.100
Mon Sep 30 19:00:41 2024 daemon.err nmbd[3770]:
Mon Sep 30 19:00:41 2024 daemon.err nmbd[3770]:   *****
Mon Sep 30 19:00:55 2024 daemon.err nmbd[3770]: [2024/09/30 19:00:55.341008,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Mon Sep 30 19:00:55 2024 daemon.err nmbd[3770]:   *****
Mon Sep 30 19:00:55 2024 daemon.err nmbd[3770]:
Mon Sep 30 19:00:55 2024 daemon.err nmbd[3770]:   Samba name server GL-MT2500 is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.100
Mon Sep 30 19:00:55 2024 daemon.err nmbd[3770]:
Mon Sep 30 19:00:55 2024 daemon.err nmbd[3770]:   *****
Mon Sep 30 19:00:57 2024 daemon.err usbmuxd[6458]: [19:00:57.681][3] usbmuxd v1.1.1 starting up
Mon Sep 30 19:00:57 2024 daemon.err usbmuxd[6458]: [19:00:57.682][3] Using libusb 1.0.24
Mon Sep 30 19:00:57 2024 daemon.err usbmuxd[6458]: [19:00:57.682][3] Initialization complete
Mon Sep 30 19:00:57 2024 daemon.err usbmuxd[6458]: [19:00:57.682][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with "--exit" to trigger.
Mon Sep 30 19:00:59 2024 daemon.err usbmuxd[6458]: [19:00:59.653][3] Caught signal 15, exiting
Mon Sep 30 19:00:59 2024 daemon.err usbmuxd[6458]: [19:00:59.653][3] usbmuxd shutting down
Mon Sep 30 19:00:59 2024 daemon.err usbmuxd[6458]: [19:00:59.753][3] Shutdown complete

admon · September 30, 2024, 6:43pm

Did you set the correct gateway and DNS server as well?
Just setting static won't work if the information are wrong.

Confucius · September 30, 2024, 6:59pm

Haven't found where to put all these yet.
I see DNS under LAN on the left. I've put in the DNS servers as supplied by my isp.
The place for the gateway has alluded me so far.

admon · September 30, 2024, 7:01pm

Could you please provide a screenshot where you set the static IP?

Confucius · September 30, 2024, 7:03pm

admon · October 1, 2024, 4:54am

Please create a screenshot of the „Internet“ page as well.

Confucius · October 1, 2024, 1:26pm

OK,

admon · October 1, 2024, 1:52pm

Why did you change the port to LAN instead of WAN?

Confucius · October 1, 2024, 1:57pm

I don't remember doing it. I've been going round in circles this past week. Should it be WAN then?

admon · October 1, 2024, 5:18pm

Totally. Always WAN.

Confucius · October 1, 2024, 6:37pm

OK, now I can not login into it. It doesn't show up in network places, I can not see the usb hard disk.

Confucius · October 1, 2024, 7:25pm

I have now reset it to factory defaults, changed its IP address, to match my network, in applications added the network storage.
I can now see the usb hard drive on the network.
I have changed nothing else what so ever.
From the network on the left all the option below eg multi-lan, lan, dns, etc. it tells me there is no internet "No Internet Connection! Find a network to reconnect."
Where to now?
Thanks

alzhao · October 2, 2024, 7:07am

Did you plug a cable to the WAN port of MT2500?

I suppose you do but better ask.

Can you export the log from MT2500's admin panel->system->log after you plug the cable.

Confucius · October 2, 2024, 11:21am

So now I have plugged the cable into the WAN port.

I can no longer get into it to get the logs.

I've got its IP from my ISP router and tried its new IP, not the one I set it to. So no longer a static IP address.

I can not connect to it.

It no longer shows up on the network.

The USB hard disk attached is no longer reachable.

Confucius · October 2, 2024, 1:59pm

I took this to mean, I should plug the network cable into the WAN socket, then export the log. Is this correct?

As I've already stated, I can't export the log now.

So what do I now do?

Confucius · October 2, 2024, 10:16pm

It seems to me that I have three options open to me.

Return the GL-MT2500A.
Leave as is and it will never update.
Someone tells me what the heck to do to make this thing work.

Because I'm just going round in circles. The only way I have found to get to the Config pages is via the IP I set it to and from the LAN, not the WAN.

What I have done so far (many times, as have started afresh many times), is to change my PC's IP (192.168.8.2) to match the MT2500 (192.168.8.1). Then go to the LAN part of the setup below the Network option on the left side of the web page. Where I change the MT2500 IP Address to 192.168.0.100. All my stuff is in the range of 192.168.0.*** and all but the wireless stuff have a unique static IP address.

So if I must use the WAN port as a WAN port as the users here keep telling me. How do I configure the MT2500, when it disappears from the network, when I plug in the network cable into the WAN port? Which I will need to do when I attach a USB hard drive. And when a different hard drive is attached you will need to find out what the MT2500 has named it, etc. so you can get to the new USB hard drive.

It seems to me that it doesn't know where to look for the route to the WWW. Nor is there anywhere that I can find, to tell it to go through my ISP's router (192.168.0.1).

I have a second router of my own (just in case the ISPs router fails, and they do!), this one sits in the shed at the bottom of the garden and it is configured to go via the ISP's router via a wired connection and all the stuff attached to this router sees the WWW with no problem. All that this little grey box of yours needs to do is replicate this. Which on the face of it, it should be able to do. I/It Just needs to know how!

So there you have it, will some very nice knowledgeable person please step forward, tell me if this box can give me a working USB hard networked AND keep its self updated and then tell me how to do it.
logread.tar (131 KB)

Confucius · October 3, 2024, 12:06am

UPDATE...
I should also add that if I try to change the "Network Mode" to Bridge. I get the popup message "To set up Bridge mode, you need to connect an Ethernet cable to the WAN port first."

There is a cable in the WAN!

I didn't go down that route as a warning "When you use Bridge mode, you will not be able to connect to this UI again." tells me I will lose the web page. Which I took to mean I wouldn't be able to configure a new USB hard disk or even get to the MT2500 via the web pages.

Anyway a change of heart, what would another reset cost my sanity.

So I've persisted down this route now and it seems that if I connect both ports, I can still reach the MT2500 and change it to bridge mode, with no warnings. So after removing one of the network cables (Had to, you probably know why!). It looks better, I can still get to the MT2500 web pages and still setup the USB hard disk. So the warning about losing access to the web pages was misleading to me.

The only thing to be proven is, will it still keep it self updated. There are no warnings about internet access, the LED isn't flashing, it looks whitish, so may be it can? Yes or No?

Only problem now is that I have to go to my routers admin page or the ISPs router to look up it's IP address to gain access. If you have been paying attention, you will have notice I like static IPs. So is there anyway to get this now other than reserving an IP address with my ISP router.

Confucius · October 3, 2024, 2:01pm

A new day and an old & new problem.

Old first.

It's disappeared again.

I can't see the USB hard disk in my network places.

Everything was shut down last night and on booting up this morning, it's gone. I can get to the MT2500 web pages. I can see that the USB hard disk is attached. And I've established that it can see the internet too.

New.

From the Network Storage page, it does show that it's there. But going to "Action" to get the shared link, I get "\undefined\disk". It seems to have mounted the hard disk as "/tmp/mountd/disk1_part1" in "/dev/sda4".

What are my options?

Update.
I've enabled DLNA, it showed up straight away, but nothing else.