Configuring ISP failover using SD WAN

Поделиться
HTML-код
  • Опубликовано: 20 июн 2023
  • Configuring ISP failover using SD-WAN
  • НаукаНаука

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

  • @glenntembo2693
    @glenntembo2693 10 месяцев назад

    Thanks Bro- I always love your labs -straight forward-so clear. Keep educating us my brother

    • @techy-world3716
      @techy-world3716  10 месяцев назад +1

      Thank you so much, that means a lot to me. I will do my best and continue creating more videos.

  • @livestronger1981
    @livestronger1981 Месяц назад

    This is great. The only improvement I see is to setup the actual outgoing Destination in the Firewall policy rather then just selecting "ALL". This is a best practice so that the SDwan service is only dedicated to that one remote network. If you have two or 3 then maybe selecting ALL makes more sense. Right?

    • @techy-world3716
      @techy-world3716  Месяц назад

      I am not too sure I fully understand your point. Here is a pointer, if the traffic is destined for the internet selecting all as the destination is best since you don't want to create different policy for traffic going to teams, zoom, Facebook, outlook etc. But if you the destination is local, then selecting a single remote network is best practices.

  • @vishnuk9523
    @vishnuk9523 Месяц назад

    My eve-ng lab FortiGate vm firewall limit with 3 interface. It says trail vm license support 3 interface. How to use more interface.

  • @livestronger1981
    @livestronger1981 Месяц назад +1

    Oh cool. What program did you use to draw the Topology?

    • @techy-world3716
      @techy-world3716  Месяц назад

      GNS3 is the application used to draw the topology

  • @MiladMantashi
    @MiladMantashi 2 месяца назад +1

    thanks bro

  • @livestronger1981
    @livestronger1981 Месяц назад

    I have a questions. Is there a difference between enabling NAT on the Policy? What does it do?

    • @techy-world3716
      @techy-world3716  Месяц назад

      When NAT is enabled on a policy you are stating that you need the private IP translated to the public and vice versa. This is mostly used when you intend for that policy to go to the internet. If the traffic is going to the LAN or VLANs only there is no need to enabled the NAT option on the policy.