Dead simple, replace USB wireless adapter on Seismic SBC with SeismicR router connected via LAN port of SeismicR to Seismic SBC where all the same existing functionality of DownstairsRouter and UpstairsRouter that had existed that allowed ssh access and Internet access to Seismic SBC is preserved. The additional requirement is ssh and LuCi access via DownstairsRouter wireless connection to SeismicR that was never needed as there was no SeismicR router ever used. I would expect there would be no changes to UpstairsRouter required to effect as purpose of UpstairsRouter is to provide Internet access to DownstairsRouter (has worked for years doing so with no changes needed).
Ok... so I'll reiterate that the best approach is as follows:
- SeismicR runs as STA mode connecting to an AP on the Downstairs Router.
- The STA mode connection will be associated with a network called wwan
- wwan will be added to the wan firewall zone.
This will provide internet access to the SeismicR Router and the devices behind it.
Now, what we can do to satisfy some of the other requirements:
- Set a static route on Downstairs Router for
10.10.20.0/24 via 10.10.10.x
(where x is the address of the SeismicR router on the Downstairs Router's lan. - Disable masquerading on the SeismicR's wan firewall zone
- Change the
input
rule toACCEPT
on the SeismicR's wan firewall zone - Add forwarding from wan > lan in the SeismicR's firewall.
These new steps will allow you to reach the SeismicR router for administration while you are connected to the Downstairs router's lan. They will also allow you to reach all of the devices behind the SeismicR router.
Do I set STA on SeismicR to be static IP or via DHCP? When did the STA approach (before trying the AP approach) it used DHCP. I tried to access the SeismicR configuration via LuCi using the DHCP address the DownstairsRouter assigned to SeismicR DHCP STA and was sent to the DownstairsRouter LuCI configuration. Which one of the steps you noted in the post will allow the SeismicR to be accessible via ssh and LuCI?
Either way is fine. If you use DHCP, you want to set a DHCP reservation for the SeismicR on Downstairs Router so that the IP never changes.
this one:
I did reset to GL.iNet GL-A1300, SeismicR.
I am again (tried before and never posted) challenges with trying to define static IP for WWAN. I think I am configuring static WWAN correctly, but seem to keep messing up LAN part of configuration.
If I set LAN to 10.10.10.100 and then set up STA for SeismicR to DownstairsRouter then WWAN defaults to DHCP. LAN part works by DHCP.
When I change WWAN to 10.10.10.100 and LAN to DHCP for 10.10.10.100 then no longer can connect to via LAN to PC.
What am I missing to configure SeismicR STA WWAN with static IP to connect to DownstairsRouter?
The upstream and downstream networks must not overlap.
The lan subnet of the Downstairs Router is 10.10.10.0/24. So the address you will use for the swan interface must be in this subnet. It must also not conflict with any other devices on that network and it must be outside the DHCP pool. Your DHCP pool is 10.10.10.100-10.10.10.134.
So you could set the wwan interface of SeismicR with the following (assuming no other devices are currently using this address):
IP: 10.10.10.99
Subnet Mask: 255.255.255.0
Gateway: 10.10.10.250
DNS: 10.10.10.250
Then, your lan address on the SeismicR can be 10.10.20.1
(with subnet mask 255.255.255.0
).
On the Downstairs router, you will be setting a static route 10.10.20.0/24 via 10.10.10.99
.
I have not been able to try. I have been trying far more times than can imagine for hours to reset GL-A1300 as result of my error:
Use failsafe... the only connections should be power to the router and an Ethernet cable to your computer. No other connections, and make sure that WiFi is disabled on your computer. Set your computer to a static IP in the 192.168.1.0/24 network (not .1) and use ssh to reset your router to defaults.
https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset
This was the link I was using as reference to enter failsafe on GL.iNet A1300 for hours prior to my post:
with no success. I was able to reach point of fresh install of OpenWRT 23.05.5 for GL.iNet GL-A1300 at 03:45+0500/08:45+0000 in morning that had secondary challenges due to OpenWRT 23.05.5 for GL.iNet GL-A1300 having bad habit of going to snap shot version and not staying on the 23.05,5 version I selected that added 40 minutes to point of fresh OpenWRT 23.05.5 installed.
I believe I have accomplished the following:
Have been accomplished, but I set WWAN interface to 10.10.10.80 and LAN address to 10.10.20.10. I can see 10.10.10.80 on DowstairsRouter summary page for SeismicR and can access SeismicR LuCi via 10.10.20.10 with SeismicR connected via LAN to PC.
I believe I accomplished:
I believe I accomplished:
by unchecking masquerading.
I changed IPv6 DHCP to have same lifetime as IPv4 DHCP and changed DHCP number of leases from 150 to 50.
I will have some questions, but need to switch cables to work the questions after obtain specifics to be able to ask questions.
A question I have:
Is this done via the "General Settings" or "Port Forwards" tab?
I changed hostname to "SeismicRHost", replaced default OpenWRT NTP pool names for NTP servers with NTP server names for Canada (not pool names), and enabled NTP Server.
Static IPv4 Routes
"General Settings" Tab
"Interface" defaults to "LAN"
"Route type" defaults to "unicast"
"Target" defaults to red line box for required input and light grey "0.0.0.0/0"
"Gateway" light grey "192.168.0.1"
"Advanced Settings" Tab
"Metric" light grey "0"
"MTU" light grey "1500"
"Table" light grey "unspecified"
"Source" light grey "unspecified"
"On-link" check box unchecked
Is the 10.10.20.0/24 the Target?
Where do I place the 10.10.10.80 address?
Do I change any of the other values?
Yes.
In the gateway field.
This will be a standard static route with interface lan
and route type unicast
. Don't forget that this static route gets added to Downstairs Router.
Done and I was aware was for DownstairsRouter.
Now have wireless access via LuCi on SeismicR 10.10.20.10 (no LAN ports connected to SeismicR) from PC on LAN of DownstairsRouter. ssh wireless access (no LAN ports connected to SeismicR) to SeismicR 10.10.20.10 also works from CLI terminal on same PC on DownstairsNetwork 10.10.10.250. Both did not work wireless (no LAN ports connected) prior to adding static route, which I expected would not.
Wireless (no LAN ports connected to SeismicR) ssh to SeismicR 10.10.20.10 via PC on DownstairsRouter 10.10.10.250 ping www.google.com works in ssh session to SeismicR, i.e. Internet access on SeismicR via DownstairsRouter 10.10.10.250 provided by UpstairsRouter 10.10.12.10 STA on DownstairsRouter.
I think this is last part of the steps you detailed needed to be done I have not completed. Just curious what this will accomplish and how do I test that once done is done correctly?
This will allow you to reach the devices behind the seismicr router.
This answer to question will likely lead to last configuration item question of items you indicted I needed to do.
Oh. Sorry i missed that one.
It is found in the zone settings. Click on the edit button next to the wan firewall zone (of seismicr). Then add the lan zone to the “allow forwarding to” field.
The "Forward" column for the WAN zone of " Firewall - Zone Settings" says "reject". Do I need to change this to "accept"?