Just to preface, I’m what I would consider an enthusiast but far from an IT pro.
This routerOS is quite a bit more complicated than what I am used to so please bare with me.
I just set up a new RBwAPG-60ad wireless wire kit and it seems to be working as it should.
But the default configuration has it set up with a 192.168.88.xx ip range while my network is using 192.168.1.xx which means (at least to my knowledge) the devices themselves will not get internet connection and to connect to them I have to manually set my computer to the same ip range.
My question is, can I safely change the ip range of the devices to fit into my LAN’s IP range without messing up the factory config? Or is it supposed to be this way to work properly?
RouterOS can be quite daunting at first, that’s a fact.
Learning curve is quite steep, we’ve all been there (and still learning).
As for your problem:
Default your device will act as router with its own subnet.
Devices connecting to it should have internet access but you can not see them from your normal network since the router will be in between.
In fact you will get a double NAT situation which for several reasons is to be avoided (though personally I rarely saw issues because of it so I still find it strange some people claim it’s to be avoided like the plague).
I assume your wAP is connected via wire to your 192.168.1.xx subnet ?
Connect wireless to your device using Winbox (preferably using MAC address since you will otherwise loose access during following steps)
Raw steps to be taken:
move ether1 from WAN to LAN interface list
remove DHCP server
add ether1 to bridge
change DHCP client from ether1 to bridge
remove 192.168.88.1 address from device
(cleanup: remove all firewall rules if your router does all that already)
Your wAP will now be in bridge mode and all devices connecting to it, will be served by your main router.
If I’m not much mistaken, RBwAPG-60ad wireless wire kit comes preconfigured so that it serves as a transparent bridge between both wired ends (as if they were switches, connected with a high-delay cable). So IP addresses used in both wired ends doesn’t matter, traffic between devices on both ends should pass via the wireless wire kit just fine.
What is missing is management of those two wireless wire devices which can’t be done directly from computers using LAN IP addresses (unless when using winbox with it’s MAC connectivity feature). To fix this, it’s pretty safe to change IP addresses of both wireless wire kit devices to match those used in LAN. Don’t forget to change IP address of the gateway and IP address of DNS server … which will make possible for the two devices to reach Mikrotik upgrade servers (and hence upgrade ROS).
But to be entirely sure that my analysis is correct, we’d have to see config (preferably of both devices) … you can create export by opening terminal window, then execute command /export hide-sensitive file=anynameyouwish (the hide-sensitive part is necessary when running ROS version 6.x; it became default with v7). After that, fetch file to your management PC, open it with your favourite text editor, redact remaining sensitive data such as serial numbers, any passwords, etc. … and copy-paste them here inside [__code] [/code] tag pair.
Yes. But try not to use QuickSet GUI option, it tends to mess with any custom configuration which might be done after QuickSet template was applied. So go via normal Webfig UI layout and change IP address. Don’t forget to include the subnet mask part (e.g. 192.168.1.X**/24**), without specifying it’s taken to be /32 (and hence IP connectivity doesn’t work as it might be expected).
Explicitly avoid changing settings in wireless portion of config (until you get more familiar with ROS), if you mess something up there you may loose the “wireless wire” part of the setup. Also try not to mess with bridge settings (and port membership), that’s another aspect of ROS which comes hard to cope with by many ROS users.
Pretty simple config … so just go ahead and change IP addresses on both devices. As I already warned, don0t torget to set subnet mask in address property … just like it is now (the “/24” part). And if you’re going to use GUI (ether winbox or webui), don’t use quickset, use “normal” UI (IP → address) part.
ROS verdion is currently up-to-date, so no need to set default gateway in IP route … If you happen to run a NTP server in your LAN, you may want to use it : if not for other things just to have sensible timestsmp in log entries.
How do I backup these settings in case things go south? Are the configurations I downloaded the backups? If not, how do I backup and how do I restore?
When setting the gateway (my router’s ip is indeed 192.168.1.1) I assume I need to set this the same for both devices right? @jaclaz seeing my gateway is the same as you said, instead of doing the steps in the guide you posted, I can just run the command you posted in terminal using winbox?
Does it matter in what order I make the changes? Maybe the Master device first then slave. Should I change IP first then set gateway?
Yes, each device needs to know where to find internet . And yes, either method, GUI or CLI will do, whatever you feel more confident with.
3.The order doesn’t actually make a difference, since anyway you will be connected with Winbox via MAC, though logically It makes sense to first add the addresses, check that they work, that there are no conflicts, that each device Is reachable via IP, and only later add the route/gateway.
