Explanation for why all applications are not available for PBF

Reply
L1 Bithead

Explanation for why all applications are not available for PBF

Hi All,

 

Just wondering if anyone can explain why the application objects have thousands of objects, but when attempting to create a policy based forwarding rule for a specific app (in my example, ms-teams), it does not appear in the drop down options in the Application drop down.

 

Can anyone guide me on the best way to setup PBF for ms-teams? 

 

Thanks All.


Accepted Solutions
Highlighted
L7 Applicator

Re: Explanation for why all applications are not available for PBF

this is how pbf works

 

consider how you redirect packets out to the internet: a syn packet goes out to establish a session: does it need to take a route or go through pbf? all we can see at this point is port 443

if pbf is set for ports, it will send via pbf, if it's set for applications, it can't know at this point,  so the packet is set out through regular route

so the syn/ack comes back and another ack is sent out via the regular route, still no clue what application we're talking and we're already 3 packets in

then comes payload and app-id can go to work. once a rudimentary application is identified, pbf can kick in. for this session however it's already late but app-id leanrs this session and stores it in the app cache so it can apply pbf on the next connection to the same source/destination/port combination

 

this is why it's recommended not to use applications in pbf, and why only some app-ids are available to begin with (because these are more easily identifiable and can use this 'bypass' without too many false positives)

 

hope this makes sense

reaper - PANgurus.com
I drink and I know things

View solution in original post


All Replies
Highlighted
L7 Applicator

Re: Explanation for why all applications are not available for PBF

this is how pbf works

 

consider how you redirect packets out to the internet: a syn packet goes out to establish a session: does it need to take a route or go through pbf? all we can see at this point is port 443

if pbf is set for ports, it will send via pbf, if it's set for applications, it can't know at this point,  so the packet is set out through regular route

so the syn/ack comes back and another ack is sent out via the regular route, still no clue what application we're talking and we're already 3 packets in

then comes payload and app-id can go to work. once a rudimentary application is identified, pbf can kick in. for this session however it's already late but app-id leanrs this session and stores it in the app cache so it can apply pbf on the next connection to the same source/destination/port combination

 

this is why it's recommended not to use applications in pbf, and why only some app-ids are available to begin with (because these are more easily identifiable and can use this 'bypass' without too many false positives)

 

hope this makes sense

reaper - PANgurus.com
I drink and I know things

View solution in original post

Highlighted
L1 Bithead

Re: Explanation for why all applications are not available for PBF

Many thanks for the answer @reaper. Clear and concise which is a very hard trait to have in the world of firewalls. Many people over complicate answers and this was spot on.

 

 

Highlighted
L7 Applicator

Re: Explanation for why all applications are not available for PBF

thanks for the compliment @ccarter ! glad my answer was helpful

reaper - PANgurus.com
I drink and I know things
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!