Currently we use just basic static IP routing; no VLAN, no tunneling protocols, no OSPF etc., also no DHCP yet. The current network is as follows:
WAN ↔ Router(192.168.127.254/17) ↔ LAN-L3-Switch(192.168.88.1/17)
The L3 switch is a CRS326 with RouterOS and operates in Bridge Mode, and its interfaces are bound to a single bridge; ie. the device’s defaults).
I need to integrate the AP inside the LAN address space.
The AP is by default in Router mode. It has WAN (Internet) settings (IP, netmask, gateway)
as well LAN settings (IP, netmask). And disabling NAT is possible.
I attached the AP to the switch and tried these static settings on the hAP:
WAN (Internet):
IP: 192.168.126.254/24
Gateway: 192.168.127.254
Firewall Router: disabled for testing
LAN:
IP: 192.168.125.254/24
NAT: disabled
>
But this somehow didn't work as I couldn't ping neither of the two above IPs of the AP from a PC attached to the switch.
Can someone tell me how to integrate that AP in this scenario under the subnet 192.168.125.0/24 within the 192.168.0.0/17 ?
Can I completely omit the WAN port of the AP and just use one of its LAN ports as the uplink port to the switch (--> router)?
If yes, will wireless then still be possible on the AP? IMHO should be possible, isn't it?
**Update:**
Changed the above WAN IP to 192.168.127.251/24. Now it's possible to reach this WAN side of the AP from other PCs, including the http GUI interface, but pinging 192.168.125.x is still not possible, ie. the LAN side of the AP. Do I need to set up some extra routes to this LAN subnet under the AP?
Probably best to reset it to defaults and select AP Wisp or AP home (not sure of the options).
Then go into winbox and make the necessary changes to fit into your network.
Hello, I told you not to participate in MY discussions! You are in my IGNORE LIST!
Your useless postings are never of any help, as everybody can see and judge.
Hello Moderator, can you please tell this anav guy to respect my wish that this guy not to participate in threads that I started, as he never ever makes any useful contribution but starts to flame, insult and hijack the thread, plus disturbing the thread with such totally far-fetched and useless postings like above.
Integrating it into an existing LAN by attaching it to an L3-switch somehow (ie. unexpectedly ) did not work,
even after assigning the subnet address to the interface on the L3 switch where the AP was attached.
So, finally I set up a new LAN 192.168.129.0/24 and put it there by attaching that AP to the router and setting some static routes on the router.
That way it now works fine as “Home AP Dual”. Due to the said static routes, it’s reachable also from the other LAN, and vice-versa
I think that’s ok, I can live with that solution. Case closed.
An important tip for new users of this device: UPDATE FIRMWARE AND OS!
You have to update RouterOS to the latest stable version AND also the firmware to the latest stable version.
Without these steps, you cannot use the Dual Band feature under “Home AP Dual” in QuickSet
as it always switches back to “WISP AP”, but this one does not have the 5GHz band.
RouterOS update: via System/Packages/CheckForUpdates
Firmware update: via System/RouterBoard/Upgrade and then do a manual REBOOT via System/Reboot
The reboot takes about 3 minutes. You can ping the device to see whether it’s online again.
Then you could set up your wireless profile in caps-man config. Once that’s set… All you need to do on the APs is set the to caps-mode. You can do this in cli with one line. Or you can do it by press and hold on the WAP at Power Up.
) did not work,