Hi forum members, I need assistant in configuring routerOS to ONLY act as a Hotspot on my private network. Below is a sample scenario.
Ether1 —> connected to WAN using net 192.168.1.0/24 Gateway 192.168.1.254
Ether2 —> LAN need it to give out hotspot connection in the same IP range that is from 192.168.1.1-192.168.1.250 mask /24
Please assist. New to Mikrotik.
I have a setup that has mikrotik behind a cisco 897 VAW router and does not have option to to configure it a router cause Service provider refuses to give out login details, so would like an other available option. If i try to connect to this setup get connection errors I think double NAT issue. Hence my needo of using mikrotik as a hotspot. Please suggest solutions. Thanks in advance.
I am aware that I can not use it addresses from same subnet. But my point is how do i make my rOS act as a hotspot only giving out the same ip addresses as the cisco router is already doing NAT and is a DHCP server. I am trying to avoid double NAT-ing. Unfortunately my ISP refuses to issue login details to the cisco router to disable dhcp and put out mikrotik ros in DMZ since its still under their contract, we have tried fruitlessly to get them effect the changes. So was hoping for any solutions that can be a work around or can work. Thank again.
Ok. But if i do that i am getting all sorts of errors like loop errors ip conflicts and network constantly disconnecting n reconnecting every 1 minute. I would appreciate if any1 can send me a lab scenario of the solution. If i test the same setup at a different where the mikrotik rOS acts as a router it works fine. But when i put it behind other router all sorts of problems occur. Please i need assistance on full solution l. PS. - Reconfiguration on our ISP provided router which is acting also as dhcp server is not an option as the ISP refuses with login credentials.
You can connect cisco-bound ethernet cable to ether2 and disable dhcp server on MT box. Default config has bridging between ether ports (except for ether1) and wlan which works just fine even for DHCP requests of wlan clients. And tape-off ether1 port so you know it’s not useable
Beware of the following: you’ll have to manually set address on a computer to manage MT to some address in subnet of MT (default is 192.168.88.1) when needed.
You could set address on MT to some address in your LAN subnet together with gw address (or start DHCP client on bridge). In any case (but in second even more so) your MT will get easy target for any potential attacker from LAN … if you don’t trust cisco’s LAN, then you’d better revert to double-NAT solution anyway.
