Hello,
i just get an SXTR&EP06-A US model
latest model
1st thing i notice is that the default IP was not 192.168.88.1 as always
it changed to 192.168.188.1
then the default password was not BLANK…
i had a super hard time resetting the box several times and could not access it
the when i was loosing all hope, and starting to file my RMA to the supplier
i just read the back of the UNIT Label and FOUND that it had a PWD from the factory !!!
Argggg!!!
go figure
anyway, that is not my issue
i changed the default IP from the unit to a 10.10.x.x
and set my DHCP pool range on the same subnet
but when mi clients get the DNS from the DHCP ,the pull up the OLD ip… uh ??
yes they pull 192.168.188.1
and the cant access the internet unless i manualy change the DNS address on the client PC’s
i tried to go
IP>DNS>dns address and change to 1.1.1.1 and 8.8.8.8
apply and same thing, rebooted and same thing
the clients get dhcp address and gateway form the mikrotik current ip;s that i set
but the DNS is pointing to the original 192.168.188.1
i am pulling my Hairs off
help please
Rolo.
As our Holy Llama here uses to say:
if you have a config then post it…
/export file=anynameyouwish ( minus router serial # and any public WANIP information ).
I think the default IP for “link” type equipment was changed from that of routers so you can
put them in the same network without immediately running into a conflict.
then the default password was not BLANK…
It will be illegal to sell equipment delivered with a standard password from next year
in the EU (which is where MikroTik are based). They are likely reworking their products
right now to be in time for that change.
anyway, that is not my issue
i changed the default IP from the unit to a 10.10.x.x
and set my DHCP pool range on the same subnet
but when mi clients get the DNS from the DHCP ,the pull up the OLD ip… uh ??
yes they pull 192.168.188.1
and the cant access the internet unless i manualy change the DNS address on the client PC’s
i tried to go
IP>DNS>dns address and change to 1.1.1.1 and 8.8.8.8
apply and same thing, rebooted and same thing
the clients get dhcp address and gateway form the mikrotik current ip;s that i set
but the DNS is pointing to the original 192.168.188.1
That is just a bug in the firmware that has been there for ages and has been resolved
in the latest beta.
You can change the assigned DNS in the “IP->DHCP->Networks” menu.
Thanks Buddy.
btw,
how do you block the ping from WAN
right now i can the Public IP of the box
i dont want to be a target of those guys doing IP scans
and attacking whoever responds to the ping
also i want to access the box with WINBOX from my remote location
Most of us do not block ping because its an essential tool for debugging issues and because its useful for some functionality.
Most of us have no issues with this setup.
In other words dont feel as if it something you have to do, I certainly dont recommend it.
To access the winbox remotely use wireguard, its relatively easy to setup and you can connect to it from
a. other MT devices
b. your ipad/iphone
c. your pc
Additionally, ICMP (ping is only one of functions based on ICMP protocol) is essential in “path MTU discovery” (which is per-connection). If PMTUD is blocked and actual PMTU is lower than what end device has configured as MTU, then some services don’t work (e.g. HTTPS).
If you use QuickSet’s VPN checkbox, that enables a L2TP VPN. The user name is “vpn” as shown, but you need to use the password as BOTH the vpn user’s password & the L2TP “shared secret”/pre-shared key, so TWO places you’ll need to set the password on a typical L2TP client.
But this won’t work via an typical LTE interface, since you’ll need a public IP address.
