Introduction to Azure Firewall

Поделиться
HTML-код
  • Опубликовано: 25 окт 2024

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

  • @NinoEl81
    @NinoEl81 2 месяца назад

    Clear and succinct explanation my man, Thanks

  • @AhmadHassanUetian
    @AhmadHassanUetian 2 месяца назад

    Hi,
    I have an FTP server configured behind an Azure Firewall. In passive mode, it is able to establish the control connection successfully but fails to establish data connection occasionally with the error "Data Peer IP [x.x.x.x] differ from control peer IP [x.x.x.x]: This should not happen, aborting the data connection.". Note that these IPs are private IPs from Private Address Space CIDR of the firewall. What configuration are required to ensure that single internal IP is used for both control and data connections? FTP server does not have a private IP and I have configured DNAT rule in firewall. For testing purpose, I only configured 5 ports in DNAT rule for passive mode.

  • @mohsinkhan973
    @mohsinkhan973 9 месяцев назад

    Nice explanation

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

    What if I don't want to use the Azure Firewall? Can I allow access to an external FQDN (not IP address) using the NSG? Or, am I forced to use the Azure Firewall? The reason I'm asking is because I recently am having an issue reaching orxy cdn from within a VNET subscription during deployment to an azure app service.