Let's Talk About Palo Alto - Virtual Wire or vWire and Tap Interface

[@DeadFlanders]

Thanks! You explained that in the first 60 seconds of your video better than any Palo Alto document I found in the last 5 minutes of searching! Makes total sense, thanks!

[@RobRikerTechChannel]

Haha thanks!

[@verynice339]

FINALLY SOMEONE YOU CAN HEAR AND UNDERSTAND!

[@jostjeff]

What network diagram apllication are you using?

[@JosephJohnson-sq4bu]

Excellent content Rob

[@dragmuab2]

Very helpful video.

[@muratafsar9753]

By the way thanks for your great works with your very well explained

[@muratafsar9753]

Hey Rob, is that possible to remove grid lines from background for your next contents, I mean horizontal and vertical gray lines. Not sure why but they affect my eyes and brain after looking to screen a bit while. If you won't able to do np, I'll try to just listen without looking to screen. I'm sorry for this request :/

[@shahidsouad]

HI Rob, could you share the eve-ng topology pls for the members? tx

[@goddaynwanmaorhuebor3900]

Thanks

[@MrGmanGB]

Your use of PA and PI is not correct. You are using terms associated with how public I.P Addressing is provided. Which is not good, especially as you got it wrong!

[@RobRikerTechChannel]

Care to elaborate on your comment on how I get it wrong?

[@MrGmanGB]

@@RobRikerTechChannel A provider-independent address space (PI) is a block of IP addresses assigned by a regional Internet registry (RIR) directly to an end-user organization. The user must contract with a local Internet registry (LIR) through an Internet service provider to obtain routing of the address block within the Internet. A provider associated block of IP Address space is exactly that, IPv4 address space that typically can only be announced and routed through the issuing providers network

[@MK1985-z7k]

Thanks