Taking a packet capture on a Palo Alto firewall

Поділитися
Вставка
  • Опубліковано 16 гру 2024

КОМЕНТАРІ • 35

  • @rileylabski
    @rileylabski 3 роки тому +1

    Thank you, this is exactly what I was looking for. I needed a quick and dirty on how PanOS regards 'transmit' and 'receive' in the overall TCP or UDP flow, and you delivered! Nice work!

  • @MichaelAPhillips
    @MichaelAPhillips 7 років тому +1

    I appreciate the step by step directions, thanks so much.

  • @CiscoVoiceTech
    @CiscoVoiceTech 8 років тому +1

    This cleared up so much confusion for me. Thanks for the great video!

  • @vijaykannan6861
    @vijaykannan6861 2 роки тому

    Excellently delivered. 🤝

  • @Qubifree
    @Qubifree 10 років тому +3

    Nice video, It is very very helpful. Thanks for sharing .keep up the good work

  • @michaelgill6717
    @michaelgill6717 7 років тому +1

    Excellent guide, keep up the good work!

  • @joshuaprem3788
    @joshuaprem3788 7 років тому +1

    fantastic video.. Very helpful.. Please post more videos

  • @sureshsinha8124
    @sureshsinha8124 5 років тому +1

    Excellent video. Thank you

  • @Yeman011
    @Yeman011 8 років тому +1

    Nicely done. Thank you for sharing!

  • @azadsingh-w5d
    @azadsingh-w5d Рік тому

    Very nice video. Can you please make a video on troubleshooting on dropped packets?

  • @snasheet
    @snasheet 6 років тому +1

    Very well explained, God bless you.

  • @rajendradhangar1655
    @rajendradhangar1655 Рік тому

    Very nicely explain..
    Thank you so much...

  • @macolop
    @macolop 9 років тому +2

    Great video. Life is more clear from now on:)

  • @paloaltobytes5029
    @paloaltobytes5029  9 років тому +1

    Thanks Alex,Maciej and Abhishek :)
    Will try to add more videos

  • @PDM985
    @PDM985 2 роки тому

    Thank you..good explanation 👍

  • @vivekrajput9245
    @vivekrajput9245 3 роки тому

    Thank you so much for sharing with us..

  • @amitchauhan-fs4pm
    @amitchauhan-fs4pm 9 років тому +1

    Great Presentation.. really made it simple ! pls post new videos related to tshoot. Thnx

  • @danishkhan476
    @danishkhan476 2 роки тому

    This is so poetic

  • @AbhishekSingh-so2fd
    @AbhishekSingh-so2fd 9 років тому +1

    Waiting for more videos :)

  • @whlewis9164
    @whlewis9164 6 років тому +1

    super helpful, ty!

  • @amarjeetkumar8735
    @amarjeetkumar8735 2 роки тому

    What is use of firewall packet?

  • @pankajbane8929
    @pankajbane8929 5 років тому

    Hello
    I want to know if there is inbound traffic having device action allow and in reason coloum as "aged out" then should we monitor such traffic or not.
    Is there any threat related such traffic.

    • @tejasmapuskar3023
      @tejasmapuskar3023 5 років тому +1

      It depends on what kind of traffic is getting Aged out. You will see Aged out response for UDP traffic as there is no handshake.

  • @Yugandhar635
    @Yugandhar635 5 років тому

    If we have a Dynamic NAT configured where multiple private IPs map to one Public IP then will your filter capture work as expected ?.

    • @tejasmapuskar3023
      @tejasmapuskar3023 5 років тому

      in that case you need to include the destination port in the filter.

    • @Yugandhar635
      @Yugandhar635 5 років тому

      @@tejasmapuskar3023 Thank you Tejas

  • @jkshar2005
    @jkshar2005 6 років тому +1

    When are more videos coming :)

  • @gurulee73
    @gurulee73 7 років тому +2

    Thank you for sharing. Your IP's don't match between diagram and config.

  • @Gauravkumar-xx3yy
    @Gauravkumar-xx3yy 5 років тому

    where is packet capture for natted ip.i want to know nat is really happening here or not ?

    • @afara2000
      @afara2000 4 роки тому

      I was wondering about NAT IP too because he mentions about packet source NATed at 03:19 which is not true! It looks like he never configured any NAT because packet capture detail in Wireshark at 08:05 shows the egress packet B has same source IP as source and ingress packet C has same destination IP as trust PC and there is no 192.150.1.2 in the logs. People who don't have enough experience should NOT rely on anybody making inaccurate videos.

  • @aradhanaandjudesmelody1777
    @aradhanaandjudesmelody1777 3 роки тому

    thank you

  • @alinaqvi385
    @alinaqvi385 3 роки тому

    Good.

  • @NickSmith-hv9zi
    @NickSmith-hv9zi 4 роки тому

    great video but you really should make sure the docs is matching with your video. 192.150.1.1 to 192.150.1.2 will never traverse the firewall and this will confuse many. but otherwise good explanation.

    • @afara2000
      @afara2000 4 роки тому

      He never configured a NAT IP 192.150.1.2 despite claiming B packet with source NAT at 03:16. Otherwise it would have been in the log details.

  • @AamZingadiVlogs
    @AamZingadiVlogs 3 роки тому

    Thankyou, Really helpful. Can you please provide your email ID where I can ask you for more related videos where I stuck in. That would be really helpful.