I want to enable the wireless interface in 2011 as an access point.
I’ve configured the radio in “ap bridge” mode, WPA2 security profile, and can log it from a smartphone.
I’ve added IP/Address 192.168.14.254/24 interface wlan1
I’ve added a DHCP server according to a template used on ethernet with a network 192.168.14.0/24 and IP/Pool of 192.168.14.128/26.
There is a dynamic route added under IP/Routes for the new directly connected network, just like for others that work. Adding another static route manually doesn’t make a difference. It remains blue and inactive.
When I log in from the smartphone I get an IP address. I can’t check if I get a network, gateway and DNS on the smartphone. Nothing works on it. I can access the router’s WebUI 192.168.14.254:xxxxx. But I can’t access another webserver over ethernet. I can ping the smartphone from the router, but I can’t ping it from a computer.
It seems that there is a Route missing, but it is there. Dynamically added. I have some routes that disallow access to 192.168.0.0/16 (distance 9). If I disable those I get a timeout. If I have them enabled, I get destination net unreachable. Ethernet routes can bypass those taking priority as distance 0 or 1. As far as I can see, the dynamic route is exactly the same. But it doesn’t work either way.
I’m puzzled by the “ap bridge”. I’ve configured it as a separate interface and don’t want a bridge.
OK. You have a wireless interface with DHCP server. No further connections so far.
There is a dynamic route added under IP/Routes for the new directly connected network, just like for others that work. Adding another static route manually doesn’t make a difference. It remains blue and inactive.
The wifi interface is inactive as long as there is no wireless client connected. With the interface inactive, the corresponding route is not usable
When I log in from the smartphone I get an IP address. I can’t check if I get a network, gateway and DNS on the smartphone. Nothing works on it. I can access the router’s WebUI 192.168.14.254:xxxxx. But I can’t access another webserver over ethernet. I can ping the smartphone from the router, but I can’t ping it from a computer.
.
The wireless network is still standalone. IP addresses will be reachable within that network. The router/AP does not know where to go for the other IP addresses.
You need to add a default route, probably out of the ethernet interface to another router in your home network.
Default route, is a route to 0.0.0.0/0 = all IP addresses.
That other default gateway router, must have a defined route to this router/AP for network 192.168.14.0/24
.
It seems that there is a Route missing, but it is there. Dynamically added.
Dynamically added by the DHCP client on the ethernet interface? Did you accept the default gateway and DNS from the DHCP lease?
I have some routes that disallow access to 192.168.0.0/16 (distance 9). If I disable those I get a timeout. If I have them enabled, I get destination not unreachable.
What destination is unreachable? Those in the 192.168.0.0/16 range? You just disallowed those.
Ethernet routes can bypass those taking priority as distance 0 or 1. As far as I can see, the dynamic route is exactly the same. But it doesn’t work either way.
.
Distance 0 is for local connected subnets. (subnets with a local interface and IP address in that subnet)
The next highest priority is distance=1. WIthin the same distance, more specific destinations like (192.168.14.0/24) over (192.168.0.0/16) take priority over the more general destinations. (0.0.0.0/0) the most general destination.
.
I’m puzzled by the “ap bridge”. I’ve configured it as a separate interface and don’t want a bridge.
.
AP bridge is a wifi setting that will activate the wifi special 4-address mode (works like a real bridge connection) in the wifi connection, but only if the client device is a Mikrotik specifying “station bridge”, and the bridge mode is not disabled in the WLAN AP interface setting.
For the new wifiwave2 drivers, the AP is always AP bridge if AP is used, and will use the 4-address mode if the wifiwave2 station uses wifiwave2’s “station bridge”
Legacy WLAN set as “AP bridge” reacts on legacy WLAN “station bridge”. WLAN driver and wifiwave2 driver wireless bridge mode are not compatible.
A bridge item in an AP is normally used to bridge (L2 connect, 1 subnet) multiple interfaces, like ethernet, wireless and VPN interfaces, that are slaves to the bridge, when connected via bridge ports.
Those router settings in AP and in the home router, and the DHCP server on the AP with an extra subnet, are all not needed if interfaces are bridged in the AP. (ethernet and wifi’s as ports on the AP’s bridge) Then client devices will talk directly to the home router … the simplest access point
I figured out the problem. It was in IP/Route. The router had been set up to use a Per-Connection Classifier for balancing between 2 wan, and I had forgotten how it works. Regrettably, I neglected to mention it because I thought that I had to explicitly activate it. I added two manual routes to 192.168.14.0 and wlan1 that duplicate the one automatically added but with a routing mark. Now it works.
Regrettably, I neglected to mention it because I thought that I had to explicitly activate it. I added two manual routes to 192.168.14.0 and wlan1 that duplicate the one automatically added but with a routing mark. Now it works.