Category: Mikrotik

MikroTik routers running RouterOS provide powerful firewall features to control network traffic. You’re securing your LAN, limiting external access, or managing bandwidth usage. It is essential to know how to allow traffic. It is also important to learn how to drop or reject traffic based on IP address, port, and protocol.

Steps: Controlling Traffic MikroTik Firewall

This step-by-step guide will walk you through the basic rules to control traffic on your MikroTik device. These are the most commonly used rules for effective traffic control, and you’ll understand how to control MikroTik firewall efficiently.

✅ Step 1: Winbox Access MikroTik

• You can use Winbox, WebFig, or the terminal (CLI) to add rules to your MikroTik firewall control flow.
• All the steps below can be entered directly into the terminal or configured through the GUI.

✅ Step 2: Allow Traffic from Specific IP

Example: Allow traffic from 192.168.1.100 to any service. This step is crucial to utilize control over the MikroTik firewall effectively.

/ip firewall filter add chain=input src-address=192.168.1.100 action=accept comment="Allow IP 192.168.1.100"

✅ Step 3: Allow Traffic Specific Port

Example: Allow TCP traffic on port 80 (HTTP). Adding such rules helps in controlling the MikroTik firewall.

/ip firewall filter add chain=input protocol=tcp dst-port=80 action=accept comment="Allow HTTP traffic"

For UDP: Control effort in setting up your MikroTik firewall includes configuring rules like these.

/ip firewall filter add chain=input protocol=udp dst-port=53 action=accept comment="Allow DNS traffic"

🚫 Step 4: Drop Traffic from Specific IP

Example: Drop traffic from 203.0.113.45. It’s a key part of controlling MikroTik firewall settings.

/ip firewall filter add chain=input src-address=203.0.113.45 action=drop comment="Drop traffic from malicious IP"

🚫 Step 5: Drop Traffic to a Specific Port

Example: Drop all traffic trying to access port 23 (Telnet). That is a precise method to control traffic on MikroTik firewall.

/ip firewall filter add chain=input protocol=tcp dst-port=23 action=drop comment="Drop Telnet"

❌ Step 6: Reject Traffic with Feedback

Example: Reject access to port 21 (FTP) with an ICMP message. Efficient implementation is key to controlling MikroTik firewall operation.

/ip firewall filter add chain=input protocol=tcp dst-port=21 action=reject reject-with=icmp-port-unreachable comment="Reject FTP access"

Reject vs Drop:

• Reject sends a response back (e.g., port unreachable), useful for debugging or soft-blocking.
• Drop silently discards the packet, good for stealth blocking.

⚠️ Step 7: Place Rules in Correct Order

• MikroTik processes firewall rules top to bottom. Gaining control over the MikroTik firewall relies on understanding this processing sequence.
• Place “accept” rules before “drop” or “reject” for the same traffic type.
• Use /ip firewall filter print to see rule order and priorities.

🧹 Step 8: Clean Up Unused or Test Rules

This step can (Optional)

/ip firewall filter remove [find comment="Test Rule"]

With MikroTik’s firewall filter rules, you have granular control over your network traffic. You need to understand how to work with IP addresses. It’s essential to know how to work with ports and protocols. This knowledge is fundamental.

Always test your rules in a controlled environment. Regularly review your firewall policies to keep your network secure and efficient. Moreover, controlling the MikroTik firewall effectively ensures continued network security and efficiency.

MikroTik’s RouterOS is a powerful operating system for network routers, renowned for its robust feature set and granular control. Two of its most critical components for managing network security and traffic are the Firewall and the Proxy server. While both are used to control data flow, they operate at different network layers. They also serve distinct primary purposes.

The firewall acts as a gatekeeper and traffic cop, enforcing security policies based on IP addresses, ports, and protocols. In contrast, the proxy server acts as an intermediary. It also functions as a caching agent, primarily for web (HTTP/HTTPS) traffic. It offers control over content and potentially improves performance. Understanding their individual functions is key to building a secure and efficient network.

The Function of Firewall in MikroTik

The firewall is your network’s primary line of defense. It operates at the network layer of the OSI model. It also operates at the transport layer. It inspects packets and makes decisions based on rules (filters).

Its core functions include:

1. Packet Filtering: This is the fundamental job of a firewall. It examines the header of each packet entering or leaving the network. Based on predefined rules, it accepts, drops, or rejects the packet.
   • Criteria: Rules are built using criteria like source/destination IP address, port number (e.g., port 80 for HTTP, port 22 for SSH), and protocol (e.g., TCP, UDP, ICMP).
   • Example: A rule can block all incoming SSH connection attempts from the internet. It would drop all packets with dst-port=22 coming from the WAN interface.
2. Network Address Translation (NAT): MikroTik’s firewall handles NAT, which is essential for most networks.
   • Src-NAT (Masquerade): This allows multiple devices on your local network (with private IPs like 192.168.88.xxx) to share the router’s single public IP address to access the internet. It “masquerades” all local traffic as coming from the router itself.
   • Dst-NAT (Port Forwarding): This feature lets you redirect a specific external port. It uses the router’s public IP to route to a port on a specific internal server. For example, forwarding external port 80 to a local web server’s IP on port 80.
3. Stateful Inspection: This is a crucial advanced feature. A stateful firewall doesn’t just look at individual packets. It tracks the state of active connections. This includes identifying which internal device started a request to a website. It dynamically allows returning traffic for that established connection. This makes rule management more secure. It is simpler than a simplistic “stateless” firewall.
4. Traffic Flow and Classification (Mangle): The firewall’s “mangle” feature marks packets for special processing. This is not for security but for advanced traffic management, such as:
   • Quality of Service (QoS): Marking certain types of traffic (e.g., VoIP, gaming) for priority treatment.
   • Policy-Based Routing: Forcing specific traffic (e.g., from a particular IP) to use a specific gateway or route.

The Function of Proxy in MikroTik

The proxy in MikroTik is primarily a web proxy (caching proxy). It operates at the application layer (Layer 7) for HTTP and HTTPS traffic. It acts as an intermediary for requests from clients seeking resources from servers.

Its core functions include:

1. Caching: This is the primary reason to use the proxy. It stores (caches) frequently accessed web pages, images, and files locally on the router’s storage.
   • Benefit: When a second user requests the same content, the proxy serves it from the local cache. It doesn’t fetch from the internet again. This reduces bandwidth usage and speeds up web browsing for users.
2. Content Filtering and Access Control: Because it understands HTTP, the proxy can make filtering decisions based on website content.
   • URL Filtering: You can create blacklists (block specific websites) or whitelists (only allow specific websites).
   • Domain Filtering: Block access to entire domains.
   • Keyword Filtering: Block pages that contain specific words in their URL.
3. Bandwidth Management: You can apply speed limits for HTTP traffic through the proxy. This allows for basic per-user or global HTTP bandwidth control.
4. Authentication: The proxy can require users to authenticate. They may need to log in with a username and password. Only then are they allowed to browse the web. This is useful for public hotspots or corporate networks to identify users.

Important Note on HTTPS: Modern web traffic is largely encrypted (HTTPS). A basic web proxy cannot see or cache the content of HTTPS connections. It can do so only if it acts as a man-in-the-middle. This requires installing a custom certificate on every client device. This is complex to set up. It has security and privacy implications. Many administrators use the proxy primarily for HTTP. They use the firewall for general access control.

Conclusion

In summary, the Firewall and Proxy in MikroTik serve complementary but distinct roles in network management. The Firewall is your indispensable, high-performance security guard, controlling all traffic based on IPs, ports, and connection states. It is essential for every MikroTik setup to protect the network from external threats and manage NAT.

The Proxy, on the other hand, is a specialized application-layer tool focused on web traffic. Its main value lies in caching to save bandwidth and accelerate browsing, and in performing content-based filtering. For most small office or home setups, a well-configured firewall is sufficient. The proxy becomes more relevant in environments with many users. In these environments, web caching provides a tangible benefit. Detailed HTTP-specific logging and filtering are also required. Ultimately, using them in tandem provides a comprehensive solution for both robust security and efficient web traffic management.