However the issue I'm trying to resolve is that I do not have a way to wirelessly access the DumbAP/relay bridge router when the main router goes down.
Is there a simple way to set that up? I've tried to create a new interface with a new wifi network on the dumb ap but must have some of the configs wrong.
I'd recommend a wired configuration to do this... depending on the specific hardware you are using, the radios on the relay device may be down as a function of the the upstream wifi network not being available. A wired connection will still work, provided that you give it a static IP address (you could even create a unique management subnet for this device).
if your openwrt device is dualband i think you can do that using a fixed ip adrress on your pc. dhcp is disabled on lan to make relay work.
so if your openwrt device is 192.168.2.1, use static address 192.168.2.2 on your pc.
that should work.
If you're running AP and STA on the same radio, the AP will shut down when the STA loses contact with its AP. This is because the radio resources are directed to scanning channels trying to re-establish contact. The travelmate package can be used to work around this. It will disable the STA and allow the local AP to function until the upstream AP is detected again.
Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
Will the travelmate package allow me to be on the same subnet as the primary AP? If I use this package do I just not configure the relayd method that I used before or do they work together?
An issue with the travelmate package that conflicts with my current setup is that it does not allow me to make "Master" stations on the radio that I'm using for the uplink.
So if you plug into the ethernet port and try to access via 192.168.1.1, does it work? Keep in mind, your computer may still have an IP address on the 192.168.2.0/24 network, so you may have to set a static IP address on your computer (for example, 192.168.1.5 with subnet 255.255.255.0)
Yes it works as you describe if the wireless connection between the two routers is maintained, but if I disconnect the wireless connection then I lose all ability to access and have to go through a TFTP recovery process.
Yes I have been trying to answer that question. I have tried exactly what you describe and what happens is it works fine until the wireless is disconnected.
For instance if I turn off the wifi on my computer, set the ethernet port on my computer to static 192.168.1.5 and subnet 255.255.255.0 then I can access OpenWrt from the computer until I disconnect the wireless link between the two routers.
config device
option name 'br-mgmt'
option type 'bridge'
list ports 'lan4'
config interface 'management'
option br-mgmt'
option proto 'static'
option ipaddr '192.168.5.1'
option netmask '255.255.255.0'
create a new firewall zone for this network
config zone
option name 'management'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
list network 'management'
Then plug your computer into lan4 and set the ethernet to a static IP in that network (192.168.5.5 as an example).
Keep in mind that it should be physical port lan4, but there is always a possibility that the logical ports and physical ports may be labeled differently -- so if it doesn't work, try the other ports.
Okay, I removed lan4 from br-lan using vi to open /etc/config/network and editing that file. In the process of trying the rest.
After trying this:
try removing lan4 from br-lan.
Then create a new bridge and interface
config device
option name 'br-mgmt'
option type 'bridge'
list ports 'lan4'
config interface 'management'
option br-mgmt'
option proto 'static'
option ipaddr '192.168.5.1'
option netmask '255.255.255.0'
create a new firewall zone for this network
config zone
option name 'management'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
list network 'management'
Then plug your computer into lan4 and set the ethernet to a static IP in that network (192.168.5.5 as an example).
Keep in mind that it should be physical port lan4, but there is always a possibility that the logical ports and physical ports may be labeled differently -- so if it doesn't work, try the other ports.
I could no longer access the device (tried all lan ports and manually set Ethernet port) and had to go through the TFTP recovery, OpenWrt factory install, upgrade, and restore.
