[Fortigate] Hub-and-spoke ADVPN using IPsec VPN wizard/Dynamically add spokes using autoconfig key

Поделиться
HTML-код
  • Опубликовано: 4 окт 2024
  • How to configure Hub-and-spoke ADVPN using IPsec VPN wizard
    Auto-discovery Hub and spoke VPN with BGP as routing protocol
    Add multiple spokes using the autoconfiguration key
    Reference Topology: techtalksecuri...
    ================================
    Please donate to support the channel:
    UPI: techtalksecurity@axl
    PayPal: sumitnick4@gmail.com
    ================================

Комментарии • 13

  • @LostWorldOfComputerAndSoftware
    @LostWorldOfComputerAndSoftware 9 месяцев назад +1

    Nice! This really helped me understand ADVPN. I love how you showed every step and that you didn't edit away mistakes, that way we also learned how to troubleshoot. Thanks man!

  • @kelumidu4116
    @kelumidu4116 Год назад +4

    Thank you sir please do another one ad vpn with sd wan as well

  • @shahbazsandhu1031
    @shahbazsandhu1031 Год назад

    Very nice and informative.
    Also, What do I need to check if I'm unable to ping the HUB from the spokes in my scenario but spokes can able to ping each other. Also, my setup is slightly different as I'm using 2 WAN connections- Primary and Failover.

  • @riyazshaikh6373
    @riyazshaikh6373 Год назад

    Nice! Thanks for the video. I believe you are using private Ip address 192.168 as you are within the premises. This will be same if we use the public Ip address. Please comment.

  • @mehwishwaqas2021
    @mehwishwaqas2021 8 месяцев назад

    in my similar tapology in EVE NG home setup...spokes to spokes communication is not dynamically pinging while the spokes can talk to the hub bidirectionally.. I am figuring out why spokes are not pinging ?

    • @sumitnick4
      @sumitnick4  8 месяцев назад

      take a debug to check what is causing the ping to fail

  • @brutalali32
    @brutalali32 Год назад

    Very informative , in real time does it requires public ip to be on both hub and spoke site or only hub site is enough

    • @sumitnick4
      @sumitnick4  Год назад

      public IP on hub and NAT-T enabled will also work

  • @bonip5278
    @bonip5278 Год назад

    If I want to deny the traffic between spokes by default, how to do that?

    • @bonip5278
      @bonip5278 Год назад

      The spoke only can communicate with the HUB

    • @sumitnick4
      @sumitnick4  Год назад

      You can tune the policy to allow or deny the source or destination