SITUATION
Cudy WR3000S with OpenWrt 24.10 set up as dumb AP with its own wireless network, connected by ethernet cable to Netgear Orbi RBR20 main router with its own wireless network, has excellent uplink capacity and 10% of the downlink capacity that it should have.
I cannot access the AP by IP address either through the web interface or SSH.
(I am moving one step at a time toward merging the networks under the same SSID. I wanted to know that the WR3000S is working well on its own first.)
QUESTIONS
Why is the downlink performance bad?
Why can't I access the AP through the web interface or SSH?
WHAT I HAVE DONE
I followed the directions for configuring a bridged AP.
Set static IP address of the AP to 192.168.0.1. (Not an address in the directions, but this is what I got to work.)
Set custom DNS server to the IP address of the main router, 192.168.1.1.
Set the IPv4 gateway to the IP address of the main router.
Disabled the DHCP interface on the AP.
Disabled the RA service, DHCPv6 service, and NDP proxy on the AP.
Set the country code for both radios.
Enabled the 2.4 Ghz and 5 Ghz radios with security.
Connected the main router to the AP lan-to-lan.
Conducted several searches of the forum.
I cannot post configuration settings because I cannot access the WR3000S either through the web interface or through SSH.
Yes, naturally, I was connected when I configured the AP. Now, I cannot connect.
I have used a client that was physically connected to the AP and two clients that were connected to the AP's wireless network.
AP is 192.168.0.1.
Client was 192.168.1.13 wired just now. Now it is 192.168.1.11 wireless. Can access the AP both ways.
Main router is 192.168.1.1.
Should the AP be 192.168.1.#? I could not get such an address to work. Maybe I was doing something else wrong then. The directions are not clear. I'm supposed to pick an address that is in the same subnet but outside the range of addresses that the main router assigns to devices. The main router's range of addresses is 192.168.1.2 to 192.168.1.254. Am I supposed to avoid that whole range? Or just the part of the range that the router actually uses, which seems to be 192.168.1.2 to 192.168.1.15 or so for the few devices that use the network.
Client has subnet mask of 255.255.255.0.
I did not change the subnet mask of the AP, so I assume that it is also 255.255.255.0.
Do you have a hypothesis about what is happening and why?
Looks like you have access if you are on the main routers network.....
but when you put the AP on a different network - no access. I think that is as expected unless you have the main router setup to 'bridge' the two networks.
Does it work if you put the AP on the its own network (DHCP on) and directly connect the client (no main router) ?
Let's take a look at your config. That can reveal a lot.
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:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
I don't know if you mean access to the internet or access to the AP's settings. I could access the AP's configuration until I connected it to the main router. I can access the internet through the AP when it is connected to the main router and when it is set up as the main router itself.
Isn't the AP the bridge?
Isn't a main router always needed? Are you asking if the AP works as the main router? Yes, it works well as the main router. I don't know what else it could mean to put the AP on its own network without a main router.
If you mean "bug" in a program, well, no. I entered those addresses. Maybe you mean "mistake"?
I used 192.168.0.1 for the AP because I could not get 192.168.1.# to work and I found a post on the forum from someone who said that he solved a similar problem by using 192.168.0.# for the AP. Maybe I was doing something wrong and I would be able to make it work if I tried again.
Are you suggesting that I things would work better if I used 192.168.1.# for the AP? What digit should I use for #?
The configuration of my main router is not complicated. It has one lan port that one client usually uses; it serves wi-fi on two radios; and it has two self-configuring mesh satellites (both of which are unplugged while I am setting up the AP). I don't even know what it would mean to have more than one network in the router.
I re-set the router and followed the directions for the nth time for setting up a bridged AP. This time, I gave the AP the address of 192.168.1.2.
The results are the same. Good uplink, very slow downlink. The web interface is sometimes very slow or unresponsive and I get XHR errors and "the connection has timed out" messages. I don't know what XHR means. When I try SSH to access the AP, I get the message: "ssh: connect to host 192.168.1.2 port 22: Operation timed out".
The computer that I am on is connected to the AP by wire into a lan port. The AP is connected to the main router by wire in lan ports on both sides.
