Such possibilities include:
- Add Default firewall rules
Block BOGON networks from WAN, incoming and outgoing
Add default FASTTRACK rules
Add IPSEC rules
Add VPN rules
This is exactly why I hate the IT community. Simplifying something isn’t going to cost you your job.You can't simplify this. Each situation is different. For example some people may be behind ISP's NAT and use RFC1918 address... blocking bogons might break this...
In addition, these "premade" rules may be incompatible with existing setting etc... If you have a single change against defconf, it may break so many things...
Too many problems, not much simplification.
Finally, if you know you want bogon rules (i.e. you know the term) then you can create the rule in less than 1 minute anyway. If you want VPN rules, you know exactly what kind of VPN you use and again - you can add it in few minutes. Users, who would benefit from such Wizard will not understand those terms and in the end will not have any benefit.
It would be helpful when there was a feature (in quickset or otherwise) to reset the firewall to defaults (including the required interface lists) without changing other router config.That is why we have quickset where you can disableenable default firewall ruleset or default NAT rules.
I did not know this and I would not reset everything.The default firewall has been improved a lot, but many users still run the old firewall because it is only updated when you reset EVERYTHING to defaults.
That's why I hate the non-IT community. Instead of complaining about what you don't know how to use and asking to dumb down things, you should start by RTFM. It doesn't cost your job. It isn't even your job to begin with.This is exactly why I hate the IT community. Simplifying something isn’t going to cost you your job.
Well of course there is the possibility of having an extra layer on top of the current settings where you would manage the firewall from Quick Set only and you would have selections like "open this service to internet" or "forward this port to that IP (from internet)" and the system would maintain the rules required for that by itself.Some of those things are just too simple (e.g. VPN/IPSec needs one to three simple rules). And you add them once. You save nothing with the wizard. It could make sense for something more complex, but then you have the problem how to put things together. You still need to understand what you're doing, put the rules in right place, etc. It's difficult to do automatically, unless you support it only for one specific basic config. Which IMHO leads again to improved Quick Set.
That's why Interface Lists were introduced: no more "ether1" in firewall rules!You have to be careful because the WAN might not be connected to the first port.
Indeed, that is one of the reasons the new default firewall is so much better.That's why Interface Lists were introduced: no more "ether1" in firewall rules!You have to be careful because the WAN might not be connected to the first port.
Sorry - what's a standard configuration?
If you are not using a “standard configuration“ then you likely don’t want to use a firewall rule or wizard.
I consider a "standard configuration" to be the consumer NAT router with one internet interface (be it ethernet, VLAN, PPPoE or what you can think of) and a local LAN bridge that has the remainder of the ethernet ports and possible wifi interfaces as ports.Sorry - what's a standard configuration?
If you are not using a “standard configuration“ then you likely don’t want to use a firewall rule or wizard.
I'm serious... what you consider to be standard will not be what someone else does.
This is certainly true but why not do an identical procedure on ROS via WinBox or WebFig?For our home users we do customized webfig skins that limit the options shown to them to hide things that they don't care about and might confuse them.
The most user friendly way IMO of managing a home MikroTik is with the iOS or Android app. It might make more sense to have such wizards in there for home routers for the average user with the default config (ex. port forward wizard).
Because it is a waste of developer resources.This is certainly true but why not do an identical procedure on ROS via WinBox or WebFig?
I fixed it for youWizards and guides and quick setups are for home users.
Cisco is doing that under their Linksys brand.MikroTik should focus on fixing bugs and introducing new features. Not cater to noobs that cannot be bothered to read the manual.
Seriously, the amount of posts asking for stuff like that is annoying.
Do you see cisco making it easier to use an ASA? No, there you have to bust your rear, to learn how to use it.
So, stop asking for MikroTik to waste their time on useless stuff, and read the manual.
Oh yes ? so why Mikrotik produces and releases new products suitable for "home and office" use? I love Mikortik products but currently it doesn't make sense to have a QuikSetup page with simplified options just for home users and then to open a door on a firewall do I have to go and read manuals and command line? So why was QuikSetup developed at the time? I don't understand answers like "not convenient"; Wouldn't opening Mikrotik to home users and selling more devices be good for a money-making company?Because it is a waste of developer resources.This is certainly true but why not do an identical procedure on ROS via WinBox or WebFig?
MikroTik should focus on fixing bugs and introducing new features. Not cater to noobs that cannot be bothered to read the manual.
Seriously, the amount of posts asking for stuff like that is annoying.
Do you see cisco making it easier to use an ASA? No, there you have to bust your rear, to learn how to use it.
So, stop asking for MikroTik to waste their time on useless stuff, and read the manual.
Current UI and CLI are perfectly fine. Wizards and guides and quick setups are for losers.
I am not worried about my job. I am worried about general security and about wasting mikrotik's developers time on a feature, which will not have many uses.This is exactly why I hate the IT community. Simplifying something isn’t going to cost you your job.
If you don't modify defconf, then yes, it might work. Once you implement a single change, it may break it. You can't deny the possibility.Simplifying a firewall rule wizard such as adding bogon and certain types of VPN won’t mess anything up for standard configurations as long as you actually follow best practice and put your WAN’s and LAN’s in the address lists.
Excellent. And you have a script why? to simplify your job, because you know EXACTLY what you want to do and why you are doing it. Adding a wizzard will not achieve this for anyone else except you, because average user will not even understand what it does and why its there. On the other hand, experienced user can sort it out with script exactly as you.Personally I have a script written that applies all the firewalls I need for certain situations, including Multi-WAN and Multi-LAN and everything. The scripts utilize the address lists to ensure everything works. I am not the typical user, but I do work with ISPs that utilize Mikrotik products at the customer location, including basic residential.
Noted. Does not change my opinion.Note, I’m saying for standard configurations. One WAN, one LAN, standard.
No. No no no no no. NOOO! Please. If you want to promote this approach, please go, buy an Apple and do not return. Let me remind you why you are here - because mikrotik offers flexibility. Once you start simplifying, you will draw developer resources from other (more useful) tasks and sooner or later, the flexibility will die for sake of simplicity.Get your head out of the sand and realize that simplifying a product or its configuration makes the product more marketable to more people. The more markable routerOS products are, the more cool products Mikrotik will keep making.
Is it only me or there's something wrong with double quotes?..
/user set 0 password="!={Ba3N!"40TуX+GvKBz?jTLIUcx/,"
Good pickup, pattern recognition! Looks like its been fixed.Is it only me or there's something wrong with double quotes?..
Code: Select all/user set 0 password="!={Ba3N!"40TуX+GvKBz?jTLIUcx/,"
The double quotes is OK but when quotes are used in the actual password as shown in your illustration that quote must be preceded with the escape character as follows:Is it only me or there's something wrong with double quotes?..Code: Select all/user set 0 password="!={Ba3N!"40TуX+GvKBz?jTLIUcx/,"
/user set 0 password="!={Ba3N!\"40TуX+GvKBz?jTLIUcx/,"
@anav ..... If one uses their TiK router as a webproxy THAT will mean a significant amount of Read-Write cycles will be made on the NAND memory .... not a good thing cause that may reduce the lifespan of the Router. Best to delegate webproxy to another machine like a capable UTM .... plus most websites are https today and TiK cannot unpack that encrypted stream so that would be a waste of time. A good UTM like UNTANGLE can unpack https streams and payloads for effective layer 7 workWhat do you think about the webproxy stuff near the end: "Blocking Unwanted Websites", to block http traffic - outdated and not useful??
I fail to understand how this is easier for anyone, I'm sorry. Those bunch of options will still be address, port, protocol, action. Same options currently used in the Firewall Filter menu.Click the firewall "wizard" and you get a bunch of options for basically creating and customizing a script for rules
I think what many users mean by "adding a firewall rule" is more like "adding a port forward in a NAT router".I fail to understand how this is easier for anyone, I'm sorry. Those bunch of options will still be address, port, protocol, action. Same options currently used in the Firewall Filter menu.
The argument against this, is that it will produce anecdotal time and money savings.The argument against this is similar to the argument that the gui isn't needed at all because there's a command line.
Anecdotal? How can you pretend to know the benefits, or lack thereof, without fine details regarding the way that it would work?The argument against this, is that it will produce anecdotal time and money savings.The argument against this is similar to the argument that the gui isn't needed at all because there's a command line.
That is because RouterOS has no picture of internal systems. Other routers have integration between their DHCP and DNS servers (so they can put hostnames into the local DNS zone), and often they allow selection of a target for a portforwarding from that info. RouterOS has part of that (it allows you to "fix" the IP address of an internal system that has obtained a dynamic address from DHCP), but there is no way to refer to that address e.g. in a rule. You need to enter it again, and be careful when you change it.So far I don't see it for something like port forwarding, because it's already simple enough, just one rule and nothing to fill in automatically.
I do not pretend. I know that it won't be more beneficial, faster, more money saving (or whatever) than pasting a single command on CLI for example.Anecdotal? How can you pretend to know the benefits, or lack thereof, without fine details regarding the way that it would work?
It's a good thing you aren't in sales.Sorry, but I use ROS professionally, I don't particularly care about non-proficient users trying to dumb down a power-user's network OS.
There are many options out there for those users.
You can tell that to Cisco. With ALL their wizards for noobs. Right? ;)It's a good thing you aren't in sales.
Cisco doesn't make devices like the hAP lite or hAP ac² which are not business class devices, or if they do I'm not familiar with them.You can tell that to Cisco. With ALL their wizards for noobs. Right? ;)
Ah, yes. Dumbing down the system, but with salespeak!Wow. I never said anything about dumbing down the system. Only adding some capabilities that generate more market share which increases profits and produces that outcome you desire.
Which in turn those new groups of customers which were attracted by Quick Set and never bothered to learn how to use ROS properly, ask for more dumbing down. Vicious circle...Quick Set is good example, you may find it useless and waste of developer's time (can't be too much), but is doesn't get in your way, you can simply ignore it. But it helps MikroTik to sell their stuff to new groups of customers.
As MT sells devices like Audience, Chateau, hap ac2 these devices ARE for the average user and you must have QuickSet to enable themThe MT is not for the casual user... or the average home user. They need a TPLINK, DLINK or NETGEAR stuff...
With MT you can do everything.
But that is what Quick Set basically does!If I were Mikrotik I would make an online Wizard to create more advanced (but still standard) configs for their SOHO device product range.
- You select the HW device you have.
- Select the number of separate VLANs and their IP and DHCP servers. Number of Wifi AP (SSID, security, hide SSID) and which VLAN they go on, number of ETH ports and on which VLAN they go, security and IP setup (NAT, basic firewall) etc. and couple of other infos.
- You press the button and you get a config file you download and run after reset in your device...!