OpenWRT TP-Link router *redirects* default browser IP (so can't login!)

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi there, apologies and help please, for what 'MUST' be incredibly elementary:

Recently (suddenly), I can no longer reach my TP-Link WDR3600 v1 logon page (OpenWRT firmware 23.05.5), at the default IP 192.168.1.1, whether by ethernet or Wi-Fi via LuCI (as by limited knowledge, I only do Terminal/Command...if having no other choice.)

The TP-Link router default IP, is not accessible via Windows 11 Pro or Manjaro 25.0.3 (2 entirely separate boots, on 2 separate internal SSD's, and on 2 DIFFERENT brand laptops), not from any of several Linux 'live' ISO's (from a Ventoy USB), and not with an Android phone. No logon/connection from that router, on 3 different devices, with 5 entirely separate OS installs, and various browsers.

No matter which device or OS is used, the browsers always redirects 192.168.1.1 to 127.0.0.0 OR 0.0.0.0, and does not connect to the router login at those addresses. Or, if via any Linux live ISO, the IP does NOT change, but it can't connect to 192.168.1.1.

As there are at least another 10 residential/local Wi-Fi networks nearby (many modems/routers most likely also using 192.168.1.1 as their default IP), I would think it'd be fairly normal to be asked for their password, but no, regardless from which device or OS, the default IP 'CHANGES' (in the browser) to either 127.0.0.0, or 0.0.0.0, and does not connect to the TP-Link. Same issue, either from my usual Firefox browser (logged into the browser's account, or not), or from different a different browser, such as Chrome.

For a different Arris modem/router (with stock firmware and IP default of 192.168.0.1), there's zero trouble reaching that device's logon page or internet, no matter from which device or OS, ethernet or Wi-Fi, and with no address redirects.

Before resetting, the TP-Link still did function (accessed the internet normally, with same network name and password), with either Wi-Fi or ethernet cable. The only apparent issue,which started this entire mess, was not being able to log in to the router.

After resetting (several times), reaching the internet is still fine for the TP-Link (ethernet ONLY)...but same as above...I cannot reach the default IP (192.168.1.1), on ethernet or Wi-Fi...so can't login that router to reconfigure, etc.

So sorry to ask, but I'm at a total loss, as to how I can't simply reset the TP-Link, to reach the OpenWRT default login page. I just can't access that 192.168.1.1 address, from any of my devices/OS's. I've looked for any mention or solution of this, however I'm able to search, but haven't found anything.

Appreciative, of any help...

2

get putty ssh client

user: root
password: one you set last or empty by default

3

Thanks @brada4, though I don't understand using PuTTY any more than any other 'command line' type interface.

I did however, actually 'try' PuTTY (the best I knew how from Linux), entered the default IP with Port 22, and got nothing (no prompts for user/pass), when it went to the next screen.

So far then, I was now able to entirely disconnect the router (except for power and direct ethernet), and accessed LuCI from the default 192.168.1.1. Then updated to the very latest OpenWRT firmware for the WDR3600 (24.10.1 with NO settings saved), and enabled the very basic AP settings that I use it for.

Reconnected to the modem, It now accesses internet from Linux (Manjaro), but not Windows 11, whereas it worked from both, before this all began (out of nowhere.) And still...no LuCI (from Linux or Windows.)

I know nothing, clearly. But if updating to the latest firmware, with NO settings saved (totally clean upgrade), I had sure hoped it would at least put me back to square one, with a working LuCI (just like a fresh/new install replacing OEM?)

Yeah, I know nothing of any CLI-type usage, so unless anyone is willing to help with step 1, 2, 3, etc. with any of those, then I'm simply out of the loop. Maybe, akin to like 99.5% of all device users?

End goal: I'd really like to have LuCI back, so I could at least login to the default IP and do very basic changes over Wi-Fi/browser, as that's the purpose of LuCI even being developed, I'd hoped.

The LAN IPv4 does say the default is 192.168.1.1, so apparently that's correct, but something else must still be wrong for LuCI to be happy, yes? And still, no internet from Windows either, so that's a step back from 'normal.'

Really, very sorry for the trouble...anyone?

4

Let's try this:

  • Disconnect the WDR3600 from everything except power and a single ethernet connection between one of the WDR3600 lan ports and your computer.
  • Make sure that wifi is disabled on your computer
  • ssh into the WDR3600 and get the following information:

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
  • Then, disconnect the ethernet cable from the WDR3600 and connect your modem (in other words, your computer's ethernet port will be directly connected to the modem).
  • Get the IP address from your computer's ethernet adapter and post just the first to octets here (in bold: aaa.bbb.ccc.ddd)
5

It could be something on your LAN that has an address conflict (i.e. it is also using 192.168.1.1). Connect devices one at a time and confirm proper operation.

2 Likes
6

@mk24: I did try your suggestion thanks, and don't believe I find that there is any IP address conflict among the network devices? The modem/router is 192.168.0.1, but hasn't previously caused any issues, as far as I was ever aware.

@psherman: Hopefully, I've saved (elsewhere) what you've asked for from those SSH commands, but someone has to tell me what are the "to octets" (in bold), that you want, about the "ethernet adapter IP address" (hopefully the capture uploads/pastes below?)

I believe I found (and removed) the Wi-Fi password, but don't know what a "MAC address" or "public IP address" look like...exactly...(in all that stuff)...so they can also be removed?

Ethernet Adapter IP Address 2025-05-31 204348
Ethernet Adapter IP Address 2025-05-31 204348441×250 4.1 KB

7

Sorry... typo. That should have been the first two octets. Specifically, the IPv4 address will have four octets, separated by periods. aaa.bbb.ccc.ddd -- what are aaa.bbb from the computer's adapter (the screenshot is not directly useful, but you can provide the requested information directly in text form, no screenshot needed).

8

To be clear, you're connecting the modem to the WAN/Internet port, correct?

9

@lieachii: You asked about the 'other' modem/router (not the OpenWRT/TP-Link with issues)..."you're connecting the modem to the WAN/Internet port, right"...so yes, that separate device is reached via the WAN/internet port at 192.168.0.1. I had included that info., because a previous post (by @mk24) was to make sure there were no conflicting IP addresses on the network (which I don't believe there are.)

@psherman: I only uploaded the previous image, because I needed to be told exactly 'what' part of that you actually need, so hopefully below now, will be all the info. you've asked for (but without the MAC etc.?) I still have all the command responses, so if I've mistakenly 'redacted' something needed by accident, I can still provide it. I DO appreciate being advised to not include certain things when you said "Remember to redact passwords, MAC addresses and any public IP addresses", but when I don't know what those things are, or look like (in the command responses), I still don't know what should be left out. So mistakenly, I've probably left in things that shouldn't be posted, and removed others that you need?

"kernel": "6.6.86",
        "hostname": "OpenWrt",
        "system": "Atheros AR9344 rev 2",
        "model": "TP-Link TL-WDR3600 v1",
        "board_name": "tplink,tl-wdr3600-v1",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.1",
                "revision": "r28597-0425664679",
                "target": "ath79/generic",
                "description": "OpenWrt 24.10.1 r28597-0425664679",
                "builddate": "1744562312"

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

config globals 'globals'
        option ula_prefix '*removed*'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

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'

config device
        option name 'eth0.2'
        option macaddr '*removed*'

config interface 'wan'
        option device 'eth0.2'
        option proto 'dhcp'

config interface 'wan6'
        option device 'eth0.2'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '2 3 4 5 0t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '1 0t'

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/ahb/18100000.wmac'
        option band '2g'
        option channel 'auto'
        option htmode 'HT40'
        option country 'US'
        option cell_density '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'dd-wrt'
        option encryption '*removed*'
        option key ''
        option ocv '0'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'pci0000:00/0000:00:00.0'
        option band '5g'
        option channel '36'
        option htmode 'HT40'
        option disabled '1'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'none'

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'
        option filter_aaaa '0'
        option filter_a '0'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'server'
        option ra 'server'
        option ra_slaac '1'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

config defaults
        option syn_flood        1
        option input            REJECT
        option output           ACCEPT
        option forward          REJECT
# Uncomment this line to disable ipv6 rules
#       option disable_ipv6     1

config zone
        option name             lan
        list   network          'lan'
        option input            ACCEPT
        option output           ACCEPT
        option forward          ACCEPT

config zone
        option name             wan
        list   network          'wan'
        list   network          'wan6'
        option input            REJECT
        option output           ACCEPT
        option forward          REJECT
        option masq             1
        option mtu_fix          1

config forwarding
        option src              lan
        option dest             wan

# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
        option name             Allow-DHCP-Renew
        option src              wan
        option proto            udp
        option dest_port        68
        option target           ACCEPT
        option family           ipv4

# Allow IPv4 ping
config rule
        option name             Allow-Ping
        option src              wan
        option proto            icmp
        option icmp_type        echo-request
        option family           ipv4
        option target           ACCEPT

config rule
        option name             Allow-IGMP
        option src              wan
        option proto            igmp
        option family           ipv4
        option target           ACCEPT

# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
config rule
        option name             Allow-DHCPv6
        option src              wan
        option proto            udp
        option dest_port        546
        option family           ipv6
        option target           ACCEPT

config rule
        option name             Allow-MLD
        option src              wan
        option proto            icmp
        option src_ip           fe80::/10
        list icmp_type          '130/0'
        list icmp_type          '131/0'
        list icmp_type          '132/0'
        list icmp_type          '143/0'
        option family           ipv6
        option target           ACCEPT

# Allow essential incoming IPv6 ICMP traffic
config rule
        option name             Allow-ICMPv6-Input
        option src              wan
        option proto    icmp
        list icmp_type          echo-request
        list icmp_type          echo-reply
        list icmp_type          destination-unreachable
        list icmp_type          packet-too-big
        list icmp_type          time-exceeded
        list icmp_type          bad-header
        list icmp_type          unknown-header-type
        list icmp_type          router-solicitation
        list icmp_type          neighbour-solicitation
        list icmp_type          router-advertisement
        list icmp_type          neighbour-advertisement
        option limit            1000/sec
        option family           ipv6
        option target           ACCEPT

# Allow essential forwarded IPv6 ICMP traffic
config rule
        option name             Allow-ICMPv6-Forward
        option src              wan
        option dest             *
        option proto            icmp
        list icmp_type          echo-request
        list icmp_type          echo-reply
        list icmp_type          destination-unreachable
        list icmp_type          packet-too-big
        list icmp_type          time-exceeded
        list icmp_type          bad-header
        list icmp_type          unknown-header-type
        option limit            1000/sec
        option family           ipv6
        option target           ACCEPT

config rule
        option name             Allow-IPSec-ESP
        option src              wan
        option dest             lan
        option proto            esp
        option target           ACCEPT

config rule
        option name             Allow-ISAKMP
        option src              wan
        option dest             lan
        option dest_port        500
        option proto            udp
        option target           ACCEPT


### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
#       option src              lan
#       option src_ip   *removed*
#       option dest             wan
#       option proto    tcp
#       option target   REJECT

# block a specific mac on wan
#config rule
#       option dest             wan
#       option src_mac  *removed*
#       option target   REJECT

# block incoming ICMP traffic on a zone
#config rule
#       option src              lan
#       option proto    ICMP
#       option target   DROP

# port redirect port coming in on wan to lan
#config redirect
#       option src                      wan
#       option src_dport        80
#       option dest                     lan
#       option dest_ip          *removed*
#       option dest_port        80
#       option proto            tcp

# port redirect of remapped ssh port (22001) on wan
#config redirect
#       option src              wan
#       option src_dport        22001
#       option dest             lan
#       option dest_port        22
#       option proto            tcp

### FULL CONFIG SECTIONS
#config rule
#       option src              lan
#       option src_ip   '*removed*'
#       option src_mac  *removed*
#       option src_port 80
#       option dest             wan
#       option dest_ip  *removed*
#       option dest_port        120
#       option proto    tcp
#       option target   REJECT

#config redirect
#       option src              lan
#       option src_ip   *removed*
#       option src_mac  *removed*
#       option src_port         1024
#       option src_dport        80
#       option dest_ip  *removed*
#       option dest_port        120
#       option proto    tcp

Ethernet adapter Ethernet:

IPv4 Address. . . . . . . . . . . : 192.168

10

Firewall is in its default state

formatting button acted up
Type 3 backticks
```
before and after copied command lines

11

As long as the next octet is not 1 (192.168.1.x) when you're connected to the upstream router, there should be no issue here.

I don't see any issues with your config at all. There is only one more thing to check:

netstat -plnt
cat /etc/config/uhttpd
12

@brada4: I see your response that "firewall is in its default state" and about the 'backticks' for the format button (but apologies, have no idea what you mean by those.)

@psherman: The next octet is "0", not "1". The result of the next command you've asked "netstat -plnt
cat /etc/config/uhttpd" is:

netstat -plnt

Displays protocol statistics and current TCP/IP network connections.

NETSTAT [-a] [-b] [-e] [-f] [-i] [-n] [-o] [-p proto] [-r] [-s] [-t] [-x] [-y] [interval]

  -a            Displays all connections and listening ports.
  -b            Displays the executable involved in creating each connection or
                listening port. In some cases well-known executables host
                multiple independent components, and in these cases the
                sequence of components involved in creating the connection
                or listening port is displayed. In this case the executable
                name is in [] at the bottom, on top is the component it called,
                and so forth until TCP/IP was reached. Note that this option
                can be time-consuming and will fail unless you have sufficient
                permissions.
  -c            Displays a list of processes sorted by the number of TCP or UDP
                ports currently consumed.
  -d            Displays DSCP value assocated with each connection.
  -e            Displays Ethernet statistics. This may be combined with the -s
                option.
  -f            Displays Fully Qualified Domain Names (FQDN) for foreign
                addresses.
  -i            Displays the time spent by a TCP connection in its current state.
  -n            Displays addresses and port numbers in numerical form.
  -o            Displays the owning process ID associated with each connection.
  -p proto      Shows connections for the protocol specified by proto; proto
                may be any of: TCP, UDP, TCPv6, or UDPv6.  If used with the -s
                option to display per-protocol statistics, proto may be any of:
                IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
  -q            Displays all connections, listening ports, and bound
                nonlistening TCP ports. Bound nonlistening ports may or may not
                be associated with an active connection.
  -r            Displays the routing table.
  -s            Displays per-protocol statistics.  By default, statistics are
                shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
                the -p option may be used to specify a subset of the default.
  -t            Displays the current connection offload state.
  -x            Displays NetworkDirect connections, listeners, and shared
                endpoints.
  -y            Displays the TCP connection template for all connections.
                Cannot be combined with the other options.
  interval      Redisplays selected statistics, pausing interval seconds
                between each display.  Press CTRL+C to stop redisplaying
                statistics.  If omitted, netstat will print the current
                configuration information once.


C:\Windows\System32>cat /etc/config/uhttpd
13

Those commands were supposed to be entered into an ssh session on the OpenWrt router. Can you try again, please?

14

@psherman: Sorry...below now?

netstat -plnt


Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2581/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1367/dropbear
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1776/uhttpd
tcp        0      0 192.168.1.1:53          0.0.0.0:*               LISTEN      2581/dnsmasq
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1776/uhttpd
tcp        0      0 :::22                   :::*                    LISTEN      1367/dropbear
tcp        0      0 :::80                   :::*                    LISTEN      1776/uhttpd
tcp        0      0 :::443                  :::*                    LISTEN      1776/uhttpd
tcp        0      0 ::1:53                  :::*                    LISTEN      2581/dnsmasq
tcp        0      0 fe80::fa1a:67ff:fe32:f430:53 :::*                    LISTEN      2581/dnsmasq
tcp        0      0 fe80::fa1a:67ff:fe32:f430:53 :::*                    LISTEN      2581/dnsmasq
tcp        0      0 fdf1:86d5:af99::1:53    :::*                    LISTEN      2581/dnsmasq
tcp        0      0 fe80::fa1a:67ff:fe32:f431:53 :::*                    LISTEN      2581/dnsmasq

cat /etc/config/uhttpd

config uhttpd 'main'
        list listen_http '0.0.0.0:80'
        list listen_http '[::]:80'
        list listen_https '0.0.0.0:443'
        list listen_https '[::]:443'
        option redirect_https '0'
        option home '/www'
        option rfc1918_filter '1'
        option max_requests '3'
        option max_connections '100'
        option cert '/etc/uhttpd.crt'
        option key '/etc/uhttpd.key'
        option cgi_prefix '/cgi-bin'
        list lua_prefix '/cgi-bin/luci=/usr/lib/lua/luci/sgi/uhttpd.lua'
        option script_timeout '60'
        option network_timeout '30'
        option http_keepalive '20'
        option tcp_keepalive '1'
        option ubus_prefix '/ubus'

config cert 'defaults'
        option days '397'
        option key_type 'ec'
        option bits '2048'
        option ec_curve 'P-256'
        option country 'ZZ'
        option state 'Somewhere'
        option location 'Unknown'
        option commonname 'OpenWrt'

root@OpenWrt:~# [/quote]
-ash: [/quote]: not found
15

I don’t see anything in your configs that could cause the behaviors you have described.

Does the same thing happen with iOS and/or Android?

16

@psherman: Same thing on everything (can't reach LuCI without ethernet.)

Different browsers (logged to Firefox account, or not. Two different brand laptops (each with 2 entirely separate physical SSD's (no shared boot)...Manjaro Linux and Windows 11.) And one Android phone. And, whether or not an OS is actually installed, or just one of several 'live' ISOs, running from a Ventoy USB. I do have one iOS device that's never used. so if it even boots, I haven't tried that (yet.)

It was just fine, until it recently and suddenly wasn't, and as is apparent, all it is...is a super simple 2.4Ghz AP, with a network name and password.

No matter which/what, the browser(s) redirect a 'physically typed' IP of 192.168.1.1 (for the OpenWRT TP-Link)...to either 127.0.0.0...or 0.0.0.0. But the Arris modem/router, with OEM firmware, is easily reachable at 192.168.0.1

Barring any other ideas you may have, and as obtuse as I am, 'why' (do you think) it is so apparently 'absurd', to not just have the router reset...entirely?

First I tried the 'easy' reset button. No LuCI.

Then I tried updating to the latest firmware via ethernet (NO settings saved). No LuCI.

I've downloaded the "KERNEL" for 24.10.1, so maybe can try that...to RESET...from absolute scratch OpenWRT? But LuCI (only via ethernet), says that type of reset requires a "squashfs" file, and I don't understand the implications or process of that...

Forgive me, but is it so bizarre that one can't just easily start over, as if it's an entirely fresh OpenWRT flash, without having to first reinstall the OEM firmware (or some such?)

Thanks so much...for your generous time...

1 Like
17

I am inclined to believe that something else on your network is responsible for this.

Does the same issue occur if you have literally no other connections other than a single ethernet cable from your computer to your TP-Link router (wifi off on your computer, no other network connections at all on the router or the computer).

Can you show a diagram of your topology?

2 Likes
18

3 troubleshooting ideas:

This is the way you typed it, correct?

(Feel free to test that URL.)

I have a few other ideas, but your previous lack of knowledge of certain terms (e.g., MAC - yet oddly, I see a firewall rule that specifies a MAC) lead me to believe those troubleshooting inquires are unnecessary.

  • What are those firewall rules that mention TCP ports 80 and 120 - are they active?

  • You mentioned the rest button, but I'm not sure it was successful from your discussion. You can try the entering on the command line:

firstboot && reboot

19

@lleachii: 1. I type the routers web address as 192.168.1.1 (the way it had always been reached, since owned.) Adding /1 at the end, to test, resulted in "page not found." 2. I don't know anything about (how to answer) the "firewall rules or TCP ports" you question. 3. Previously, I had only tried the router's exterior reset button (several times, and even after updating to the latest OpenWRT firmware), as I didn't/don't (know how) to enter/command "firstboot && reboot."

@psherman: I did test for a network conflict as you last suggested (everything off except the router in question connected by ethernet.) There was still no LUCI, and I don't 'think' there could be any network conflicts (without ANY other devices.) The "topology" of the network is...basically nothing (of any complexity at all.) No added or edited OpenWRT packages, or any other changes to the firmware, except to turn on 2.4Ghz Wi-Fi, and set passwords. The network consists of;

  1. ISP ARRIS modem/Wi-Fi router (192.168.0.1), which ethernets to...
  2. TP-Link WDR3600 Wi-Fi Router (192..168.1.1), which broadcasts to...
    3 A: An Acer laptop with two physically separate SSDs (Windows 11 and Manjaro.) 3 B: A Dell laptop, also with two separate SSDs (Windows 11 and Manjaro.)
    3 C: An OEM OnePlus Android phone.
    3 D: A Roku TV (on an off-location and entirely separate ISP.)

Since last posting, I've done SEVERAL of each, of these THREE...OpenWRT resets with nothing saved (by physical router switch), ethernet connected LuCI Restore (Perform reset), with nothing saved, and re-uploading(s) of the most recent OpenWRT 24.10.1 firmware.

Various 'things' (of some sort), changed each time. First, Linux would be able to access both the network and LuCI (but not Windows.) Then eventually, LuCI was alive on Windows again, as well as Linux, and accessed the network from both OS's as well. Android was the first to regain LuCI again, and so far, hasn't lost it again.

So no 'apparent' further issues...perhaps? LuCI is 'alive.'

Besides the multiple kind of resets (and re-uploading fresh firmware several times)...

The ONLY other thing that, perhaps, had some affect, is that I chose encryption:

WPA2-PSK/WPA3-SAE Mixed Mode (strong security)...instead of...WPA3-SAE (strong security).

I'm sorry to say that I don't know what the encryption was before this issue suddenly appeared, and I don't genuinely know if changing it made any difference at all. The only thing that it 'perhaps' influenced, was that LuCI also works with Windows now, instead of only Manjaro Linux and Android (which was the case for some periods during the day.) Android, after some resets, apparently didn't mind which security protocol, and was the first to act normally again.

I'm truly sorry, as not only have I taken so much of everyone's time (GREATLY appreciated), but I still don't have a clue as to what happened to the router kicking out LuCI...when it was just sitting there for many months, untouched?

Maybe someone else will know whether the type of encryption could've caused any of this?

All I know, for certain, is that if/when anything happens (out of the blue again), I won't beg for everyone's valuable time. Straight in the bin it'll go. I don't 'think' the router itself is defective, nor can I have any opinion about the state of OpenWRT, but regardless...

Thanks again...and my sincere apologies...

20

Not sure why you added /1 - but is this what you saw?

Screenshot_20250602_182826_Firefox Focus
Screenshot_20250602_182826_Firefox Focus316×107 7.66 KB

Then you should reset your device.

Have you done so?

To be clear, you enter it the same location others have asked you to enter commands.