Challenges adding second Router Client

I am having challenges trying to add a second client router to my existing two router configuration using OpenWrt 23.05.5. The existing two router configuration has been working just fine for number of years. I will provide a high level overview of the working two router configuration, then explain what i have tried.

RouterUpstairs

WRT1900ACV2

Radio0 Marvell 88W8864 802.11ac/n
max # scan SSIDs: 4
Disabled

Radio 1 Marvell 88W8864 802.11b/g/n
max # scan SSIDs: 4
Master: SSID Upstairs N/Chan09

10.10.12.10/24
Lan1-Lan4 not connected
WAN Ethernet connected to ISP Modem

RouterDownstairs

WRT1900ACV2

Radio0 Marvell 88W8864 802.11ac/n
max # scan SSIDs: 4
Disabled

Radio 1 Marvell 88W8864 802.11b/g/n
max # scan SSIDs: 4
Master: SSID Downstairs N/Chan09
Client: SSID Upstairs N/Chan09

10.10.10.250/24
Lan1-Lan4 connected to 3 systems and 16 port Ethernet switch
WAN port not connected

Again the above configuration has worked fine for years across many prior releases of OpenWRT.

I would like to add a second client router to RouterDownstairs. This second router is a mini router that is suitable for the task at hand. It is a GL.iNet GL-A1300. I installed OpenWrt 23.05.5 just fine and of course did not keep the configuration not to mention the GL iNet version of OpenWRT was DSA.

First try:

SeismicRouter

GL.iNet GL-A1300

Radio0 Qualcomm Atheros IPQ4019 802.11ac/n
max # scan SSIDs: 16
Disabled

Radio 1Qualcomm Atheros IPQ4019 802.11b/g/n
max # scan SSIDs: 16
Master: SSID SeismicR N/Chan09

10.10.20.10/24
Lan1 would be connected to Seismic SBC

RouterDownstairs

WRT1900ACV2

max # scan SSIDs: 4

Radio0 Marvell 88W8864 802.11ac/n
max # scan SSIDs: 4
Disabled

Radio 1 Marvell 88W8864 802.11b/g/n
max # scan SSIDs: 4
Master: SSID Downstairs N/Chan09
Client: SSID SeismicR N/Chan09

10.10.10.250/24
Lan1-Lan4 connected to 3 systems and 16 port Ethernet switch
WAN port not connected

Does not work as desired. SeismicR causes RouterDownstairs to disconnect Client and Master so RouterDownstairs disconnects from RouterUpstairs and unable to connect to SeismicR.

Second try:

SeismicRouter

GL.iNet GL-A1300

Radio0 Qualcomm Atheros IPQ4019 802.11ac/n
max # scan SSIDs: 16
Disabled

Radio 1Qualcomm Atheros IPQ4019 802.11b/g/n
max # scan SSIDs: 16
Master: SSID SeismicR N/Chan10

10.10.20.10/24
Lan1 would be connected to Seismic SBC

RouterDownstairs

WRT1900ACV2

Radio0 Marvell 88W8864 802.11ac/n
max # scan SSIDs: 4
Disabled

Radio 1 Marvell 88W8864 802.11b/g/n
max # scan SSIDs: 4
Master: SSID Downstairs N/Chan09
Client: SSID SeismicR N/Chan10

10.10.10.250/24
Lan1-Lan4 connected to 3 systems and 16 port Ethernet switch
WAN port not connected

Does not work as desired. SeismicR causes RouterDownstairs to disconnect Client and Master so RouterDownstairs disconnects from RouterUpstairs and unable to connect to SeismicR.

Third try:

SeismicRouter

GL.iNet GL-A1300

Radio0 Qualcomm Atheros IPQ4019 802.11ac/n
max # scan SSIDs: 16
Master: SSID SeismicR N/Chan36

Radio 1Qualcomm Atheros IPQ4019 802.11b/g/n
max # scan SSIDs: 16
Disabled

10.10.20.10/24
Lan1 would be connected to Seismic SBC

RouterDownstairs

WRT1900ACV2

Radio0 Marvell 88W8864 802.11ac/n
max # scan SSIDs: 4
Client: SSID SeismicR N/Chan36

Radio 1 Marvell 88W8864 802.11b/g/n
max # scan SSIDs: 4
Master: SSID Downstairs N/Chan09
10.10.10.250/24
Lan1-Lan4 connected to 3 systems and 16 port Ethernet switch
WAN port not connected

Does not work as desired. SeismicR causes RouterDownstairs to disconnect Client and Master so RouterDownstairs disconnects from RouterUpstairs and unable to connect to SeismicR.

Fourth try:

SeismicRouter

GL.iNet GL-A1300

Radio0 Qualcomm Atheros IPQ4019 802.11ac/n
max # scan SSIDs: 16
Master: SSID SeismicR AC/Chan36

Radio 1Qualcomm Atheros IPQ4019 802.11b/g/n
max # scan SSIDs: 16
Disabled

10.10.20.10/24
Lan1 would be connected to Seismic SBC

RouterDownstairs

WRT1900ACV2

Radio0 Marvell 88W8864 802.11ac/n
max # scan SSIDs: 4
Client: SSID SeismicR AC/Chan36

Radio 1 Marvell 88W8864 802.11b/g/n
max # scan SSIDs: 4
Master: SSID Downstairs N/Chan09
10.10.10.250/24
Lan1-Lan4 connected to 3 systems and 16 port Ethernet switch
WAN port not connected

Does not work as desired. SeismicR causes RouterDownstairs to disconnect Client and Master so RouterDownstairs disconnects from RouterUpstairs and unable to connect to SeismicR.

What am I missing?

There is a lot of detail here that is largely irrelevant, while the things we need to know seem to have been omitted.

I can’t understand what you are doing for each “try” and it’s not clear what is different between each one.

Let’s start with some basics:

  • do you have the option to connect each device via Ethernet?
  • Do you actually want or need to have each router forming its own network/subnet?
  • please provide a network topology diagram so that we can better understand the context.
  • let’s see the configs from each device:

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

The routers were configured via LuCI, hence I showed the key elements of the challenges to configure second router client SeismicR for the RouterDownstairs. I showed first the years long working LuCI configuration for RouterUpstairs and RouterDownstairs first. This means from firewall and configuration point of view configuration works just fine across many prior OpenWRT releases for years.

I choose to show each "try" configuration for adding a second wireless DHCP client to RouterDownstairs for the new router of working configuration to DownstairsRouter rather than listing only the changes made to avoid people having to look up and down the posting(s) to merge the tries made to add in the second wireless client configuration for SeismicR in their mind. You will note for each try that UpstairsRouter is not listed as there were no changes.

Note that both RouterDownstairs and SeismicR work on own just fine, but when both clients are enabled on DownstairsRouter the client connection to UpstairsRouter is lost no matter if use same or different channel on the B/G/N radio, or use the A/C radio instead for AC or N.

I can provide the CLI information has been requested, but frankly it will be far far more information than I provided. Hence in my opinion far more difficult to understand the key issue of a second client added to same radio or add second client to other radio not being used in my years long configuration.

The key issue is once the second wireless client is enabled to DownstairsRouter the client connection to UpstairsRadio is lost. Once the second client (SeismicR) configuration on DownstairsRouter is disabled one has to go though various efforts to restore the client connection of UpstairsRouter on the DownstairsRouter. I have skipped those steps have to go through to restore the client wireless connection for UpstairsRouter to DownstairsRouter. At no point in any of these tries does anything occur to UpstairsRadio that needs attention no reboot of UpstairsRouter.

As FYI I do not have physical access to UpstairsRouter. As indicated in mt initial posting the only Ethernet connection for UpstairsRouter is for WAN to the ISP modem. I own UpstairsRouter and I am solely responsible for configuration of UpstairsRouter. That means I am the only one with the passwords to UpstairsRouter as is also the case for DownstairsRouter and SeismicR router. If there is some special situation where I need to physically have UpstairsRouter I can request so. To date I have been able to effect firmware updates and configuration tuning just fine via LuCI via client connection from Downstairs router. This also means I have ssh access to UpstairsRouter via the wireless client connection from DownstairsRouter.

The downstairs router is configuration is accessed via Ethernet.

The SeismicR router in final end configuration would only have wireless LuCI or ssh access, but I can disconnect the SeismicR router and connect to my system via Ethernet If I need to at any time I choose. Testing for the various tried for SeismicR has been done without need to place where the Seismic SBC is located on opposite side of grade level I live. In fact the UpstairsRouter was configured and tested the configuration in same manner as I am doing with the SeismicR router. As can be deduced the UpstairsRouter has run without my need to have physical access to and knowing I do not have physical access to UpstairsRouter for years. Ergo the approach I use to configure and test configuration UpstairsRouter at my desk before is placed where I have no access to the UpstairsRouter is proven approach.

In essence the same configuration and testing approach is being used for the second client router trying to add to the DownstairsRouter configuration. This means once I have working DownstairsRouter/SeismicR router configuration then I can place/connect the SeismicR router to the Seismic SBC via Ethernet and access the SeismicR router configuration via wireless DHCP using ssh or LuCI as I have been doing for years with UpstairsRouter.

A routed client, which is what you are trying to do with the 1300, really doesn't make any more demand on its AP than an endpoint client like a phone or laptop. Thus the routed client is popular for connecting (with permission) to networks that you don't own, such as hotels or neighbors. No configuration changes in the AP are needed. It should not break anything in the AP.

With that said, watch out for duplicate MAC or IP addresses and network loops (e.g. trying to connect by wifi and wired at the same time). The open source driver for the Marvell wifi chip in the 1900 is known to have problems. Is the link upstairs to downstairs WDS or regular client?

Please clarify what you mean by both clients...

Any given radio can only be used for one instance of STA (client) mode. If you have two radios in the same device operating in STA mode, there would be additional considerations regarding the routing tables (mwan3 or PBR).

If you're talking about 2 distinct devices both connecting in STA mode to a single upstream AP, that should be fine, provided you've configured things properly.

Maybe so, but you've provided a ton of information that is not at all relevant, and we can filter out the irrelevant things as we read through a configuration as we find the relevant items.

Also, we cannot rule out that you don't have other misconfigured items.

1 Like

Understand very clearly loop issues that can occur with duplicate IP or MAC addresses. For sure not factor in what I have tried. Each router has own unique subnet, ie 10.10.12.10, 10.10.10.250, and 10.10.20.10. Netmask of entire system is 255.255.255.0 Always use the real MAC address of device and never define MAC address for any router or system I am using. The GL-A1300 was set in master not client and is using stock OpenWRT 23.05.5 I flashed last week onto the GL-A1300 and not older GL.iNet custom OpenWRT 4.5.19 (OpenWRT 21.02 currently GL.iNet uses) arrived as new in sealed box.

I did not note in my posting I tried the GL-A1300 in client. I need to access the GL-A1300 configuration via wireless and I could not figure out how to do so. Therefore if there is a way to configure the GL-A1300 as client and not master where I can access he GL-A1300 configuration and allow me to set static or DHCP static address for the Seismic SBC I would connect to the GL-A1300 I am open to that.

The issue thus far in essence of being able to connect the GL-A1300 via the DownstairsRouter (10.10.10.250) as second client. For example the UpstairsRouter (10.10.12.10) is running as Master Wireless that the DownstairsRouter connects to via client configuration on DownstairsRouter. This allows me to access the UpstairsRouter via ssh or LuCI, and even allows me to access the ISP modem that is at 192.168.1.1 via the DownstairsRouter (10.10.10.250) via UpstairsRouter (10.10.12.10). Again all via my 10.10.10/24 network. I do not have password access to the ISP modem as is ISP of person my UpstairsRouter is connected to, but point is using client access from DownstairsRouter at my desk works to access to the ISP modem. Hence why I want to use client access via DownstairsRouter to SeismicR router.

As much as I like to connect the Seismic SBC via Ethernet to the DownstairsRouter I cannot. The Seismic SBC to date has been connected via DHCP to DownstairsRouter using USB wireless adapter on SeismicSBC. The reason for wanting to use wireless router based connection to the Seismic SBC is because USB based wireless connection is adding significant delays outside the NTPD calculations. This means the 200 samples per second sampling used by the Seismic SBC is missing several samples which causes some seismic software to complain of missing data and hence will not process the seismic data to graphs, et al. I know the ADC application works fine related to samples per second as I ensured the code keeps to samples per second via various time based calculations as I wrote using CLOCK_REALTIME via clock_gettime and have used for years (I do not do simple dump sleep of 5ms and never have) and tested it via Ethernet when tested code. I wrote the entire code for the ADC in C. I have ran Ethernet cable across floor from one end of house to opposite side of house to recheck that source of large NTPD varience is due to USB wireless interface. This affter many different attempts at different NTPD configurations to solve the NTPD varying often >100ms where unsuccessful. For 200 samples per second means NTPD needs to be > +-2.5 ms. The 200 samples per second was 100% stable using Ethernet, hence the USB wireless based connection is introducing alot of jitter outside the NTPD ability to calculate for. NTPD means have used ntpd, ntpdsec, and chrony all with same problem of unable to account for the wireless adapter USB based interface wide and random jitter/delay times.

As an aside the ADC code I wrote is not hard coded for 200 samples per second, but any sample rate can be specified. Ego the calculations for delay work correctly at any sample per second specified, where 100 SPS is another common used sample rate. To repeat the ADC code does not use simple/dump delay where the sample rate would drift only longer not shorter (USB based wireless causes large drifts forward and backward) at known and constant time (time to read/process each sample, that the calculations in my code completely zero out).

Do want me to post one post for each of three routers or one post with all three routers per your:

ubus call system board cat /etc/config/network cat /etc/config/wireless cat /etc/config/dhcp cat /etc/config/firewall

information request?

Yes... along with a physical topology diagram so we can understand how these devices relate to each other.

The whole ADC/sampling discussion is not relevant here... we just need to know what your topology looks like as well as the device configurations.

Umm, no idea why CR/LF did not take in prior post of </>

it doesn't really matter... as long as your configs are readable when you post those.

I mean two things.

First, if I try two clients on the B/G/N radio, each to different intended master does not work in what I have tried. I tried using same channel for both clients and using different channel for client to SeismicR.

Second, if I try the SeismicR client on the AC radio does not work on the N channel nor AC channel.

In all cases does not work means the years long working B/G/N radio for client to JLM002 stops working (forced to disabled when add SeismicR client) and some interesting effort is needed to restore the JLM002 client connection.

To start is this (ASCII) physical topology diagram acceptable?:

    JLM002Host          +---- LAN 1 No Connection
   WRT1900ACV2          |---- LAN 2 No Connection
  10.10.12.10/24        |---- LAN 3 No Connection
        |               |---- LAN 4 No Connection
        |               +---- WAN (not bridged to LAN) ISP Modem
        |
WLAN (Master JLM002 Radio B/G/N)  N Chan 09
        .
        .
        .
        .
        .
        .
(Client JLM002 Radio B/G/N) N Chan 09 DHCP
        |
frttseedmitjherasxmykf  +---- LAN 1 PC
     WRT1900ACV2        |---- LAN 2 16 port Ethernet Switch
   10.10.10.250/24      |---- LAN 3 PC
 (hkhuytehkholjioytdh)  |---- LAN 4 GPS App SBC
        |               +---- WAN (not bridged to LAN) No Connection
        |
(Master Radio B/G/N) Chan 09
::::::::::Working for Years above this Marker ::::::::::
(Client SeismicR Radio B/G/N)  N Chan 09 DHCP (Tried not current)
(Client SeismicR Radio B/G/N)  N Chan 10 DHCP (Tried not current)
(Client SeismicR Radio AC)     N Chan 36 DHCP (Tried not current)
(Client SeismicR Radio AC)    AC Chan 36 DHCP (current disabled)
        .
        .
        .
        .
        .
        .
(Master SeismicR Radio AC)    Chan 36 DHCP (current, causes Client JLM002 Radio B/G/N N Chan 09 DHCP to disconnect)
(Master SeismicR Radio B/G/N) Chan 09 DHCP (Tried not current, causes Client JLM002 Radio B/G/N N Chan 09 DHCP to disconnect)
    SeismicRHost        ----- LAN 1 Seismic SBC
  GL.Inet GL-A1300      ----- LAN 2 Not Connected
 10.10.20.10/24         ----- WAN (not bridged to LAN) No Connection
(Client hkhuytehkholjioytdh Radio B/G/N)  N Chan 09 DHCP (Tried works, not current as does not meet need to access router configuration via ssh or LuCI)

As FYI I have personal appointment 10 January 2025 such that I will not be able to reply for most of or all of day. Best case will be able to reply evening of EST+0500.

Will you be posting your config files? We need those to review.

I can once I know the physical topology diagram acceptable is what requested. The diagram took me a couple hours to create.

TBH, a photo of a hand drawn diagram (pencil on paper) would probably be more clear.

But nothing can really happen until you share your configs. Those of us who are frequent contributors can read a config and understand the whole picture pretty quickly.

Sorry for delay in posting. It took me a while to sanitize MAC addresses. I do not need to sanitize any IP Addresses as all are internal use IP addresses only. I changed passwords to password comments that match router wireless access point referencing so can follow and verify passwords match up (was never an issue). The longest part of delay of over 90 minutes was OS yet again going off in never-land. I have replacement OS mostly ready, but few rough edges to sort out that have been taking some time.

This represent the last configuration attempt, i.e. try 4 for [frttseedmitjherasxmykf] and [SeismicRHost].

End goal is to be able to access [SeismicRHost] via ssh and LuCI and of course allocate via DHCP IP for Seismic SBC. Later I will likey want static IP for Seismic SBC. Later means in about 6-12 months when I upgrade the Seismic SBC hardware to better SBC (means fresh OS install) for Seismic code I am writing, ADC upgrades I am working on (hardware and code for) and complete first and second Force Balanced Seismometers (time consuming as takes months of complex metal work doing by hand and electronics) I am building.

UpstairsRouter [JLM002Host] (No issues)

2025-01-09 23:13:06 +0000 UTC : 1736464386  user@unix 665EF506 tty0 ~ $ ssh root@10.10.12.10
root@10.10.12.10's password:


BusyBox v1.36.1 (2024-09-23 12:34:46 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.5, r24106-10cc5fcd00
 -----------------------------------------------------
root@JLM002Host:~# date
Thu Jan  9 23:15:10 UTC 2025
root@JLM002Host:~# ubus call system board
{
	"kernel": "5.15.167",
	"hostname": "JLM002Host",
	"system": "ARMv7 Processor rev 1 (v7l)",
	"model": "Linksys WRT1900AC v2",
	"board_name": "linksys,wrt1900ac-v2",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.5",
		"revision": "r24106-10cc5fcd00",
		"target": "mvebu/cortexa9",
		"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
	}
}
root@JLM002Host:~# cat /etc/config/network

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 'fd66:38be:768b::/48'

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

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '10.10.12.10'
	option netmask '255.255.255.0'
	option ip6assign '60'
	list dns '9.9.9.9'
	list dns '149.112.112.112'
	list dns '2620:fe::fe'
	list dns '2620:fe::9'

config device
	option name 'wan'
	option macaddr '00:00:00:00:00:01'

config interface 'wan'
	option device 'wan'
	option proto 'dhcp'
	option type 'bridge'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'
	option type 'bridge'

config interface 'wwan'
	option proto 'dhcp'

root@JLM002Host:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
	option channel 'auto'
	option band '5g'
	option htmode 'VHT80'
	option country 'CA'
	option cell_density '0'
	option disabled '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
	option channel '9'
	option band '2g'
	option htmode 'HT20'
	option country 'CA'
	option cell_density '0'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'JLM002'
	option encryption 'psk2'
	option macaddr '00:00:00:00:00:02'
	option key 'Password_JLM002'
	option short_preamble '0'
	option disassoc_low_ack '0'

root@JLM002Host:~# cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'remote'
	option expandhosts '1'
	option cachesize '1000'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option localservice '1'
	option ednspacket_max '1232'

config dhcp 'lan'
	option interface 'lan'
	option start '20'
	option limit '4'
	option leasetime '1h'
	option dhcpv4 'server'
	option dhcpv6 'server'
	option ra 'server'
	list ra_flags 'managed-config'
	list ra_flags 'other-config'
	option ra_useleasetime '1'

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

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

config host
	option name 'frttseedmitjherasxmykf'
	option ip '10.10.12.23'
	option mac '00:00:00:00:00:05'

root@JLM002Host:~# cat /etc/config/firewall

config defaults
	option input 'DROP'
	option output 'DROP'
	option forward 'DROP'
	option synflood_protect '1'
	option drop_invalid '1'

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

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

config forwarding
	option src 'lan'
	option dest 'wan'

config rule
	option name 'Allow-DHCP-Renew'
	option src 'wan'
	option proto 'udp'
	option dest_port '68'
	option target 'ACCEPT'
	option family 'ipv4'

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'

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'

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'

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'

config ipset
	option name 'bflixAdLinksIPv4'
	option comment 'Banned IPs Also Covers Many Dynamically Changing Web Site Names IP4'
	option family 'ipv4'
	list entry '172.240.108.68'
	list entry '172.240.127.234'
	list entry '192.243.59.12'
	list entry '192.243.61.227'
	list entry '192.243.59.20'
	list entry '192.243.59.13'
	list entry '192.243.61.225'
	list entry '172.240.108.84'
	list entry '172.240.108.76'
	list entry '172.240.253.132'
	list match 'ip'

config ipset
	option name 'bflixAdLinksIPv6'
	option family 'ipv6'
	option comment 'Banned IPs Also Covers Many Dynamically Changing Web Site Names IP6'
	list entry '2606:4700:3037::ac43:8368'
	list entry '2606:4700:3033::6815:402'
	list match 'ip'

config ipset
	option name 'stake.tld'
	option comment 'Any TLD'
	option family 'ipv4'
	list entry '172.64.144.31'
	list entry '104.18.43.225'
	list entry '104.18.37.229'
	list entry '172.64.150.27'
	list match 'ip'

config ipset
	option name 'betrivers'
	option family 'ipv4'
	list entry '104.18.35.53'
	list entry '172.64.152.203'
	list match 'ip'

config ipset
	option name 'bluffbet.com'
	option family 'ipv4'
	list entry '52.84.52.29'
	list entry '52.84.52.46'
	list entry '52.84.52.122'
	list entry '52.84.52.19'
	list match 'ip'

config ipset
	option name 'deviceconnectnetwork.co.in'
	option comment 'IP4 and any subdomain'
	option family 'ipv4'
	list match 'ip'
	list entry '172.67.186.240'
	list entry '104.21.2.87'
	list entry '108.62.60.42'

config ipset
	option name 'blowbuyhow'
	option family 'ipv4'
	list match 'ip'
	list entry '172.234.26.93'

config ipset
	option name 'bemobtrcksAndgojktrIPv4'
	option comment 'IP4'
	option family 'ipv4'
	list match 'ip'
	list entry '3.220.51.12'
	list entry '52.204.19.219'

config ipset
	option name 'bemobtrcksAndgojktrIPv6'
	option comment 'IP6'
	option family 'ipv6'
	list match 'ip'
	list entry '2600:1f18:43d1:2a02:b6ee:327b:545e:e578'
	list entry '2600:1f18:43d1:2a02:c6f9:e151:e2e1:732d'

config ipset
	option name 'betanoIPv4'
	option comment 'Any Subdomain'
	option family 'ipv4'
	list match 'ip'
	list entry '104.18.10.72'
	list entry '104.18.11.72'

config ipset
	option name 'betanoIPv6'
	option comment 'Any Subdomain'
	option family 'ipv6'
	list match 'ip'
	list entry '2606:4700::6812:a48'
	list entry '2606:4700::6812:b48'

config ipset
	option name 'chaturbateIPv4'
	option family 'ipv4'
	list match 'ip'
	list entry '104.18.101.40'
	list entry '104.18.100.40'

config ipset
	option name 'chaturbateIPv6'
	option family 'ipv6'
	list match 'ip'
	list entry '2606:4700::6812:6528'
	list entry '2606:4700::6812:6428'

config rule
	option name 'bflixIPv4'
	option src '*'
	option ipset 'bflixAdLinksIPv4'
	option target 'DROP'
	option dest '*'

config rule
	option name 'bflixIPv6'
	option src '*'
	option ipset 'bflixAdLinksIPv6'
	option target 'DROP'
	option dest '*'

config rule
	option name 'test'
	option src '*'
	option dest '*'
	option target 'DROP'
	list src_ip '172.240.127.234'
	list dest_ip '172.240.127.234'

root@JLM002Host:~# exit
Connection to 10.10.12.10 closed.

Downstairs Router [frttseedmitjherasxmykf] (No issues except adding SeismicR)

2025-01-09 23:15:56 +0000 UTC : 1736464556  user@unix 665EF506 tty0 ~ $ ssh root@10.10.10.250
root@10.10.10.250's password:


BusyBox v1.36.1 (2024-09-23 12:34:46 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.5, r24106-10cc5fcd00
 -----------------------------------------------------
root@frttseedmitjherasxmykf:~# date
Thu Jan  9 23:16:40 UTC 2025
root@frttseedmitjherasxmykf:~# ubus call system board
{
	"kernel": "5.15.167",
	"hostname": "frttseedmitjherasxmykf",
	"system": "ARMv7 Processor rev 1 (v7l)",
	"model": "Linksys WRT1900AC v2",
	"board_name": "linksys,wrt1900ac-v2",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.5",
		"revision": "r24106-10cc5fcd00",
		"target": "mvebu/cortexa9",
		"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
	}
}
root@frttseedmitjherasxmykf:~# cat /etc/config/network

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 'fd61:27b5:453a::/48'

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

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '10.10.10.250'
	option netmask '255.255.255.0'
	option ip6assign '60'
	list dns '10.10.12.10'

config device
	option name 'wan'
	option macaddr '00:00:00:00:00:03'

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

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'

config interface 'wwan'
	option proto 'dhcp'

root@frttseedmitjherasxmykf:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
	option channel '36'
	option band '5g'
	option htmode 'VHT20'
	option country 'CA'
	option txpower '23'
	option cell_density '1'
	option disabled '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
	option channel '9'
	option band '2g'
	option htmode 'HT20'
	option country 'CA'
	option txpower '20'
	option cell_density '1'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'hkhuytehkholjioytdh'
	option encryption 'psk2'
	option macaddr '00:00:00:00:00:04'
	option key 'Password_hkhuytehkholjioytdh'

config wifi-iface 'wifinet5'
	option device 'radio0'
	option mode 'sta'
	option network 'wwan'
	option ssid 'Seismic01Rx'
	option encryption 'psk2'
	option key 'Password_SeismicR'
	option disabled '1'

config wifi-iface 'wifinet3'
	option device 'radio1'
	option mode 'sta'
	option network 'wwan'
	option ssid 'JLM002'
	option encryption 'psk2'
	option key 'Password_JLM002'

config wifi-iface 'wifinet6'
	option device 'radio0'
	option mode 'sta'
	option network 'wwan'
	option ssid 'Seismic01R'
	option encryption 'psk2'
	option key 'Password_SeismicR'
	option disabled '1'

root@frttseedmitjherasxmykf:~# cat /etc/config/dhcp

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

config dhcp 'lan'
	option interface 'lan'
	option start '100'
	option limit '35'
	option leasetime '5m'
	option dhcpv4 'server'
	option dhcpv6 'server'
	option ra 'server'
	list ra_flags 'managed-config'
	list ra_flags 'other-config'
	option ra_useleasetime '1'

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 domain
	option name 'sensors02'
	option ip '10.10.10.195'

config host
	option name 'Audio'
	option ip '10.10.10.194'
	option leasetime '5m'

config host
	option name 'GPS01A'
	option ip '10.10.10.193'
	option leasetime '5m'

config host
	option name 'SeismicGeophone'
	option ip '10.10.10.192'
	option leasetime '5m'

config host
	option name 'S0002'
	option ip '10.10.10.200'
	option leasetime '5m'

config host
	option name 'N0001'
	list mac '00:00:00:00:00:06'
	option ip '10.10.10.201'
	option leasetime '5m'

config host
	option name 'N0001'
	list mac '00:00:00:00:00:07'
	option ip '10.10.10.202'
	option leasetime '5m'

root@frttseedmitjherasxmykf:~# cat /etc/config/firewall

config defaults
	option syn_flood '1'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'

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

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

config forwarding
	option src 'lan'
	option dest 'wan'

config rule
	option name 'Allow-DHCP-Renew'
	option src 'wan'
	option proto 'udp'
	option dest_port '68'
	option target 'ACCEPT'
	option family 'ipv4'

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'

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'

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'

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'

root@frttseedmitjherasxmykf:~# exit
Connection to 10.10.10.250 closed.

Seismic Router [SeismicRHost] (No issues) (some on purpose disabled Clients)

2025-01-09 23:27:47 +0000 UTC : 1736465267  user@unix 665EF506 tty0 ~ $ ssh root@10.10.20.10
root@10.10.20.10's password:


BusyBox v1.36.1 (2024-09-23 12:34:46 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.5, r24106-10cc5fcd00
 -----------------------------------------------------
root@Seismic01RHost:~# date
Tue Jan  7 19:53:46 UTC 2025
root@Seismic01RHost:~# ubus call system board
{
	"kernel": "5.15.167",
	"hostname": "Seismic01RHost",
	"system": "ARMv7 Processor rev 5 (v7l)",
	"model": "GL.iNet GL-A1300",
	"board_name": "glinet,gl-a1300",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.5",
		"revision": "r24106-10cc5fcd00",
		"target": "ipq40xx/generic",
		"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
	}
}
root@Seismic01RHost:~# cat /etc/config/network

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 'fdcd:8c8c:e553::/48'

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

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '10.10.20.10'
	option netmask '255.255.255.0'
	option ip6assign '60'

config interface 'wan'
	option device 'wan'
	option proto 'dhcp'
	option type 'bridge'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'
	option type 'bridge'

config interface 'wwan'
	option proto 'dhcp'

root@Seismic01RHost:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc/a000000.wifi'
	option channel '9'
	option band '2g'
	option htmode 'HT20'
	option cell_density '1'
	option country 'CA'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc/a800000.wifi'
	option channel '36'
	option band '5g'
	option htmode 'VHT40'
	option country 'CA'
	option cell_density '1'
	option txpower '23'
	option disabled '1'

config wifi-iface 'wifinet1'
	option device 'radio0'
	option mode 'ap'
	option ssid 'Seismic01R'
	option encryption 'psk2'
	option key 'Password_SeismicR'
	option network 'lan'
	option disabled '1'

config wifi-iface 'wifinet3'
	option device 'radio1'
	option mode 'ap'
	option ssid 'Seismic01R'
	option encryption 'psk2'
	option key 'Password_SeismicR'
	option network 'lan'
	option disabled '1'

config wifi-iface 'wifinet2'
	option device 'radio0'
	option mode 'sta'
	option network 'wwan'
	option ssid 'JLM002'
	option encryption 'psk2'
	option key 'Password_JLM002'
	option disabled '1'

root@Seismic01RHost:~# cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option cachesize '1000'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option localservice '1'
	option ednspacket_max '1232'
	option dhcpleasemax '5'

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

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'

root@Seismic01RHost:~# cat /etc/config/firewall

config defaults
	option syn_flood '1'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'

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

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

config forwarding
	option src 'lan'
	option dest 'wan'

config rule
	option name 'Allow-DHCP-Renew'
	option src 'wan'
	option proto 'udp'
	option dest_port '68'
	option target 'ACCEPT'
	option family 'ipv4'

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'

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'

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'

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'

root@Seismic01RHost:~# exit
Connection to 10.10.20.10 closed.

Based on your configs, it appears you're trying to setup 2 STA-mode connections on the "Downstairs Router." Is that correct? If so, why?? You can only have one STA-mode connection per radio, and if you have multiple STA-mode connections in general, you need to account for it with PBR or mwan3.

If you must connect via wireless between the "Downstairs Router" and "Seismic", it should be setup such that Seismic is operating a STA-mode connection, with "Downstairs Router" setup an AP to which Seismic connects.

Meanwhile, let's clean up some stuff:

Starting from upstairs router...
You can delete all the DNS entries here. They don't actually anything here:

Delete the bridge lines from both of these:

Delete this:

Delete wwan from here:

Now onto Downstairs Router:
Delete the dns here (again, does nothing):

Delete this:

and this:

Consider longer DHCP leases... 5m is unnecessarily short:

Same is true with all of your static hosts. Usually, the lease time is omitted entirely for static hosts as it'll just use the standard lease time (one example):

Finally, "Seismic":

Delete the bridge lines from both of these:

Enable this STA mode connection with the SSID and passphrase from "Downstairs Router's" AP mode config:

And you can enable these:

Reboot the "Downstairs Router" as well as "Seismic" and then things should hopefully work for you.

Thanks for your very detailed reply for changes. I am going to gave some questions or comments. I will likely break these into different replies.

I had a much longer day for my appointment than I had expected.

I initially tried setting up SeismicR as client on same radio (B/G/N) as client for JLM002 (UpstairsRouter) using same channel using for UpstairsRouter and DownstairsRouter. This resulted as previously noted in only one or the other client working. What this means is that when the SeismicR client was created on DownstairsRouter the client for UpstairsRouter (JLM002) on DownstairsRouter stopped working. When I disabled the SeismicR client on DownstairsRouter and enabled the JLM002 client on DownstairsRouter the client for JLM002 would not work, so I would disable again and rename JLM002 client to JLM002x. When I created new jlm002 client via B/G/N radio then the JLM002 client connection on downstairs radio would work again. When I enabled the SeismicR client again on the B/G/N radio it would not work and JLM002 continued to work. When I scanned via B/G/N radio to create SeismicR client again the client to SeismicR worked again, but JLM002 client stopped working. The same patter occured even when I decided to use the AC/N radio for SeismicR client on the downstairs router no matter if for AC or N on the AC/N radio. This means no matter what I attempted in using same or different radio for SeismicR client the same problem of only being able to use one client and to restore use of other client meant having to delete or rename prior client name before creating client via scanning via the respective radio being used for the client.

For for example this SeismicRx client configuration was one of last times I renamed SeismicR client on DownstairsRouter before creating again via scanning using respective radio of time. My intent was to delete, but kept as reference for possible bug report information that re-enabing when had worked would not work on re-enabled, but had to rescan respective radio to be active again with of course other client on DownstairsRouter stop working. Therefore your catching SeismicRx definition to delete makes sense from a cleanup point and I would have deleted at some point.

One key question for your various changes is can I just effect the changes for DownstairsRouter and SeismicR first and see if that addresses the goal of your changes? I ask as I do not have physical access to the UpstairsRouter. If any changes made cause loss of internet connection because the DownstairsRouter looses connection to UpstairsRouter there is manual process where I have to ask to have UpstairsRouter disconnected and placed on stairs for me. This Request process can take hour or two, at times longer before effected. Then I would try to fix via posting to this thread if can or restore configuration and advise you of what happened.

As aside I an not quite sure if the second quote I made from your clean up the configuration post was done by me correctly. If not and not too OT to correct me how to do so correctly.

I am not familiar with PBR or mwan3. Did you account for PBR or mwan3 in your configuration clean up? If so can you explain what PBR and mwan3 are and how one accounts for in context of your comment for of my configuration of routers for SeismicR and of JLM002 clients via DownstairsRouter.

As FYI prior to making my posting I had done alot of searching that seem to be divided on if can use same radio for more than one client connection or not. Hence wht i tried using the AC/N radio for SeismicR while JLM002 client running for years on B/G/N radio left as is.