Hello, i got a SXTsq Lite 5 yesterday, running latest stable 6.48.3.
To better understand what i want to do ill tell you my old setup:
Vdsl Router at work 192.168.1.10, tp link access point 192.168.1.250 transmitting to my home
Outdoor tp link client at home 192.168.1.251, connected to a switch where i have an indoor tp link access point 192.168.1.249 wan address 192.168.0.1 lan address…i use that for computers and smartphones to connect wirelessly with dhcp.
I just want to make it work like before, ive used 3-4 brands of wireless aps but im lost with this one!
I did not used any of the templates,i reset settings, so there is no firewall rules active, i have added a bridge to the lan but i still cant ping or access the web interface, i can only connect with the software through the mac.
Im guessing this will not be my only problem, upnp was disabled, i enabled it (will teamviewer work for example or is there something more), what do i need to do to have the same connectivity as before. Sorry if im not specific enough, im not at home rn, thanks
For example, UPnP must be off on ap and client, the only network device than must have UPnP active is the Vdsl Router
reset again without remove the defaults for have a base to work.
my main problem is that i cant ping or access the web interface, i couldnt with the defaults either, i need the web interface to experiment, i never moved to windows 10, i have 7 on an old drive which i dont feel comfortable using
use winbox, do not need an IP,
or paste this on terminal
/ip add add interface=ether1 address=192.168.88.1/24
Please read again: winbox is not an option for me, i néed ip and web interface like any other normal router…and changing the ip back to default wont make it reachable, tried it.
Terminal ≠ WinBox. There are many other ways to get a terminal on a MikroTik RouterOS box:
- SSH
- Telnet
- MAC-Telnet (i.e. telnet via MAC address)
- Console cable (not on SXTsq Lite, but on many MT devices)
- WebFig (the web UI)
Inferring from your insistence that WinBox isn’t an option and that you’ve reset your WAP to factory defaults, I’d suggest trying the MAC-Telnet client. It has a discovery mode that will find the WAP for you, if it’s on the local network segment.
changing the ip back to default wont make it reachable, tried it.
Have you tried temporarily reconfiguring your client to put it on the 192.168.1.0/24 subnet? You can do that statically, or you can just add a temporary alias on the network interface you use to connect to the WAP.
None of those protocols work when im connected to my home ap wirelessly, only winbox, when connected directly to the pc they all work
It’s already on 192.168.1.0/24, its ip is 192.168.1.251, same as the previous client
There’s a 10/100 port on that AP. Use it to get the AP configured, then you can use it wirelessly.
It’s already on 192.168.1.0/24, its ip is 192.168.1.251, same as the previous client
Sorry, I meant 192.168.88.0/24, the default IP subnet for MikroTik equipment. After a factory reset, the AP should be at 192.168.88.1.
FIrst: RouterBOARD is not a “normal router”.
Second: You know than you can set a static ip on your ethernet interface ( like 192.168.88.2 subnet 255.255.255.0 no gat/dns/etc. required)
with that you can open the IP http://192.168.88.1 for configure the device,
after in some way you paste this on terminal:
/ip add add interface=ether1 address=192.168.88.1/24
OR
Paste this on one terminal window,
you lost all your configuration, but the device restart with default settings (dhcp on ether1) and with that settings you can use again webfig.
/system reset-configuration skip-backup=yes no-defaults=no keep-users=no caps-mode=no
none of you seems to understand what i need, i don’t know how else to say it..
you suggesting things i’ve already tried, i can already configure it with winbox, how do i make it be http/ping/ reachable on 192.168.1.251 based on my current setup* god, why is this so hard to grasp?
You wrote it:
my main problem is that i cant ping or access the web interface
We do. You aren’t understanding our answers.
You use the wired 192.168.88.1 link only long enough to replace this default configuration, including the IP.
The documentation is a treasure trove of configuration ideas. At your level, if you think a thing cannot be done, it is almost certainly a limitation in your knowledge, not in RouterOS itself.
MikroTik devices have other default IP address than your old router. You can’t magically make it work the same, you must connect and set up this IP that you wish to use. Either with SSH or Winbox, like others suggested.
You have two options:
- Adapt your setup (change addresses on the other devices) and not touch the MikroTik device
- Use Winbox to connect to the MikroTik device and then adapt the MikroTik device to your old setup
in 25 years online, this is T H E W O R S T support forum i’ve ever seen.
you kept repeating the same things and none of that was even close to solving my problem. i made it clear from the first post that i KNEW how to access the configuration UI, reading the same answer from a mod is just sad.
solution: connect as pseudobridge station and open a dynamic bridge port (just adding a bridge not enough) for lan/wlan
i’m getting tfo of here and i’m never buying mikrotik again
If I, @tangent and @normis has not understand what you want is because you can’t explain yourself at all.
Non fare il Pollo,
this is user forum, who say than this is support forum?
Is written everywhere, for support contact support@mikrotik.com
If you buy one MikroTik device (or another brand device) with that price, you never have lifetime support for free…
Buy 1.000€ device with lifetime support and dedicated helpdesk…
It goes with the name, Pollo, run away when the paella pan gets hot. 
I would like to see a labelled network diagram with sufficient detail to explain the scenario.
Perhaps there is something we are missing because we cannot ‘see’ it.