Why? That makes problems a lot harder to diagnose and you can never be sure what is a cause and what is an effect.Logs are written asynchronously
Yes, I'm seeing that too. Most irritating.Also the last (and most important one) line of the log is very hard to read - it almost always stay "between" lines, auto scroll doesn't always work.
add action=masquerade chain=srcnat dst-address=192.168.0.2 dst-port=22,80,161,443 protocol=tcp src-address-list=OnlyFromHere
So why exactly did you reply to this particular 20 day old thread to add that gem of uselessness?sorry no idea
Did he say he was on a dynamic address?restart your router to get new IP
That doesn't convey any useful information. Where are you getting the firmware upgrade package from? Direct download, or upload to device from some previous download?but no luck at all.
You haven't said where you're testing FROM, and WHAT test you are performing.But no success. No Access to the modem...
No.Is it possible for a Device to be member of multiple Network maps?
Don't do that either. It causes all sorts of weird crashy type problems.I don't want to have one device added twice and then just to assign each to different map.
It's kinda irrelevant when you can't get a TCP connection, doncha think?Go to users under sytem and check the permission of the full group. Admin should be a member of the full group
No, no, no. The WLAN will automatically turn on as soon as someone connects to it. It's so obvious.All it does is make your life more difficult by having to keep turning it back on
You may wish to delete some (or all) of the junk that gets stored in the %appdata%\mikrotik\winbox folder.Whenever I login to winbox and click on Quickset the software shutsdown.
I need to access quickset to enable me configure my router for internet access.
Yes it did.fell from a height of 10 meters to the ground and never broke
It's broken.What is the problem
Buy a new one.and what is the solution ?????
/interface bridge set fast-forward=yes [find]
/system script run "myScriptName"
Why did you bother asking if you knew what the answer was better than anyone else then?set 0 and set 2 have been working fine since 3.x days. As long as the interface # listed on PRINT doesn't change I'm able to use it without issue on 6.43.13 in a script or under terminal mode
It stops it working though, which is almost the same thing.yes, it is. the shutdown command on RouterBOARD devices doesn't turn off the device.
No, it should not.Automatic upgrade should be the default
Only if you're using the Micro$oft definition of 'best', which really means worst.and is quickly becoming best practice.
See also viewtopic.php?f=15&t=130551Discovering CHR via Winbox is very hit and miss. My CHR sometimes comes up if I refresh neighbours about 4 times and leave it for 5 mins. I wouldn't pin "all" of the blame on Winbox/WINE combo at this point.
It's unclear if it's deliberate or not.IP->Cloud has disappeared from menu in WebFig and WinBox.
Apparently not. It's still the same on 6.43rc56Is this change maybe reverted in a later version?
add action=accept chain=input comment=\ "defconf: accept established,related,untracked" connection-state=\ established,related,new,untracked
If hackers can login and change the config. then all anybody else needs to do is login and update the software. Job done. Simple.I'm not really sure what Mikrotik can do about the kit out there that still isn't patched. These routers probably haven't been logged into at all for years.
Who cares?For me it looks correctly. It may be that you have increased your system fonts.
This whole business is completely and utterly STUPID. STOP doing it. Then all the 'not nice' things go away as well.even setting a powervalue that is already selected, triggers a disconnect/reconnect. This is not nice....
What on earth for?I want to reduce Wi-Fi transmitter power on schedule/at night because the router is located in a bed room.
Configuration of what? My Windows machine? How? What? Where?Looks to me like host configuration problem.
add bridge=br_vlan tagged=sfp1,br_vlan,vlan10 untagged=ether4 vlan-ids=20
/ip firewall filter add action=reject chain=output dst-address=169.254.169.254 protocol=tcp reject-with=tcp-reset
Yes, or the equivalent on an Access List entry.do you mean the "default forward" on the wlan1 configuration?
Don't know then.It is actually enable.
Agreed. I put a static IP address on ether1 and deleted the dhcp-client, then rebooted, and no dhcp-client came back afterwards.It looks like latest rc changed something, at least my testing CHR doesn't add dhcp client to random interfaces anymore.
I think you mean 8291It seems the system scans for winbox port 8192 to quickly identify MikroTik devices (since this is a unique port)...