Video summary

آموزش میکروتیک 2026 | آموزش MTCNA | میکروتیک روتر | قسمت سوم

Main summary

Key takeaways

Educational

Main ideas / lessons

  • DHCP purpose and roles

    • DHCP (Dynamic Host Configuration Protocol) automatically assigns IP configuration to clients.
    • DHCP is framed as having three entities:
      • DHCP Server: stores and provides IP options to clients.
      • DHCP Client: requests IP configuration (e.g., laptop/TV/phone).
      • DHCP Relay Agent (“relay rail”): helps DHCP communication when the client and server are on different network segments, since DHCP discovery uses broadcast.

  • Why DHCP involves broadcasting (and what routers do to broadcasts)

    • DHCP DISCOVERY is sent as a Layer 2 broadcast.
    • Switches forward broadcasts within the same broadcast domain.
    • Routers typically do not forward broadcasts between networks (Layer 3 boundaries), so DHCP may fail across routed segments.

  • DHCP message exchange (the 4-step sequence)

    • DHCP uses a cycle of four message types between client and server:
      1. Discover (client → broadcast): “Find a DHCP server”
      2. Offer (server → client): “I can provide configuration”
      3. Request (client → server): “I want that offered configuration”
      4. Acknowledgement / ACK (server → client): “Confirmed—configuration is now valid”
    • These steps ultimately deliver:
      • IP address
      • Subnet mask
      • Default gateway
      • DNS servers
      • (and other DHCP options)

  • DHCP relay solutions for cross-router scenarios

    • When a DHCP server is on a different network, the relay agent forwards the client’s request to the server and routes the server’s reply back to the client.
    • The lesson emphasizes topology changes:
      • Use bridging/switching so broadcast reaches the server (Layer 2), or
      • Use DHCP Relay so broadcast-like discovery works across routers (Layer 3).

  • DHCP security concepts

    • Risks include a rogue/malicious DHCP server on the network:
      • A hacker may flood the network with fake DHCP offers/requests (DoS-like behavior).
    • Mitigation techniques mentioned:
      • DHCP Snooping (on Layer 2 devices/switches): allow only legitimate DHCP server ports; block others.
      • “Alert”-like behavior: notify when unexpected DHCP servers appear.
      • Enabling snooping is described specifically with MikroTik switch/bridge capabilities.

  • DHCP on MikroTik: available modes

    • MikroTik is said to support all three DHCP roles:
      • DHCP Server
      • DHCP Client
      • DHCP Relay
    • DHCP configuration is done via MikroTik’s IP menus, using tabs for modes and settings.

  • DHCP server configuration prerequisites and workflow (as explained)

    • Before running a DHCP server, you must:
      • Assign an IP address to the interface serving the DHCP network.
    • Then configure:
      • DHCP server on the selected interface
      • Address pool/range (“DHCP Pool” / “IP range”)
      • Gateway (default route) for clients
      • DNS servers
      • (optionally) reservations and additional DHCP options

  • DHCP lease management: ranges, reservations, and “static” binding

    • DHCP assigns addresses dynamically from a pool; leases expire and clients may receive different IPs later.
    • Reservations / static binding:
      • Lock an IP address to a specific client identity (commonly via MAC address).
      • Commonly used for devices like printers/servers.
    • Also mentioned:
      • Pool exclusions: do not include certain IPs in the pool (e.g., router-reserved addresses).

  • Bridging routers/switching to form a Layer 2 domain

    • Bridging can make routers behave like Layer 2 forwarding devices for broadcasts.
    • Key concept: when interfaces are bridged, DHCP DISCOVERY broadcasts can reach the DHCP server because they remain in the same Layer 2 domain.
    • In MikroTik, this involves:
      • Creating a Bridge interface
      • Adding physical interfaces as bridge ports
      • Ensuring DHCP server/client are placed on bridged interfaces appropriately

  • Troubleshooting concepts

    • If a client has no connectivity:
      • Confirm the client received an IP via DHCP.
      • Confirm default gateway and DNS options are present.
      • If discovery can’t reach the server, consider relay vs bridging vs topology changes.
    • The video also references:
      • Ping gateway/server to validate routing
      • Traceroute to identify where forwarding breaks

  • VPN / tunnels used to carry Layer 2 traffic (conceptual)

    • Layer 2 (broadcast-like) requirements can be transported over long distances using VPN/tunnels that support bridging-like behavior (examples mentioned conceptually).
    • Takeaway: DHCP over routed links typically needs relay, but Layer 2 bridging via specialized tunnels is another conceptual approach.

  • Round-off / wrap-up

    • The session focus includes:
      • DHCP + bridging concepts
      • DHCP security (snooping)
      • Practical lab scenarios in VMware/MikroTik (routers as clients/servers)
    • The next module is teased as continuing additional scenarios.

Methodologies / instruction-like content

A) DHCP operation sequence (protocol flow)

  • Client side
    • Send DHCPDISCOVER as broadcast (Layer 2).
  • Server side
    • Respond with DHCPOFFER.
  • Client side
    • Send DHCPREQUEST for that offered configuration.
  • Server side
    • Send DHCPACK confirming final configuration options (IP, mask, gateway, DNS, etc.).

B) When DHCP fails across routers: choose one of two approaches

  • Approach 1: Keep DHCP in Layer 2 using bridging

    • Bridge interfaces so broadcast traffic can reach the DHCP server.
    • Goal: DHCP DISCOVER broadcasts propagate to the server.

  • Approach 2: Use DHCP relay

    • Keep Layer 3 routing.
    • Configure a relay so DHCP messages forward to the remote DHCP server and replies return to the client.

C) DHCP server configuration logic (MikroTik workflow described)

  • Precondition

    • Assign an IP address to the interface where the DHCP server will run.

  • Configure DHCP server

    • Select DHCP Server mode.
    • Choose the correct interface.
    • Define Address pool (range of assignable client IPs).

  • Set client options

    • Configure gateway (default route) option (typically the first router IP in the LAN).
    • Configure DNS servers option.

  • Reservations / static assignments (optional but emphasized)

    • Create a mapping:
      • MAC address → fixed IP
    • Used especially for printers/servers/devices needing stable addressing.

D) DHCP address pools and reservation rules (as taught)

  • Ensure:
    • The DHCP pool range is valid for the subnet you assigned.
    • The router’s own IP is typically excluded from the pool.
  • Reservation behavior:
    • If a MAC is reserved, when it requests an address it should receive the same IP (until changed or the reservation is removed).
  • Lease duration:
    • Reservations may remain stable regardless of lease expiration (depending on configuration intent described).

E) DHCP security (DHCP Snooping) mitigation steps (conceptual)

  • Enable DHCP snooping on the Layer 2 device/switch (or MikroTik bridge equivalent).
  • Mark trusted ports:
    • The legitimate DHCP server port(s).
  • For untrusted ports:
    • Block unauthorized DHCP server replies.
  • Optionally:
    • Enable alerting when unexpected DHCP servers appear.

Speakers / sources featured

  • Primary speaker: The instructor/host (unnamed in the subtitles; presented as a lecturer in a MikroTik training course, referencing teaching MTCNA/MikroTik topics).
  • Source systems mentioned:
    • MikroTik (router/switch platform; MikroTik UI features such as WinBox/IP menus)
    • VMware (lab virtualization)
    • Microsoft / Linux / Cisco / TP-Link (example device categories that can run DHCP)

Original video