Bytes received zero for allowed udp ports

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

Bytes received zero for allowed udp ports

L2 Linker

Hi,

 

In traffic allowed logs, I am seeing numbers in byte sent however byte received is zero and connections are getting aged-out for UDP voice traffic.

Can anyone know about such traffic whether it is dropping or since this  is UDP connection hence byte received is zero

 

This traffic is allowing  via security policy configured for outside to inside NAT, NATED IP is of cisco meraki  server.

 

 

Thanks

Dhananjay Bhakte

2 accepted solutions

Accepted Solutions
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

L7 Applicator

Hi @DhananjayBhakte 

These are just sessions that are allowed but don't have any reply. Allowed UDP sessions always have the session end reason aged out as this protocol is stateless. There isn't a packet like FIN or RST packet in TCP, so the firewall applies a timeout after a udp packet and if there is no answer or another UDP packet for the same session, this session will be removed from the session table after this timeout is reached and the session is then displayed as aged-out in the logs.

View solution in original post

Thank You Vsys_remo for reply,

 

Yes I agree with you, later I saw applications are discovering in same traffic logs, those applications was SIP  other voice related applications and these applications always runs on UDP protocol  since it is connection less protocol I was getting bytes received zero and aged-out.

 

Thanks

Dhananjay Bhakte

View solution in original post

2 REPLIES 2
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

L7 Applicator

Hi @DhananjayBhakte 

These are just sessions that are allowed but don't have any reply. Allowed UDP sessions always have the session end reason aged out as this protocol is stateless. There isn't a packet like FIN or RST packet in TCP, so the firewall applies a timeout after a udp packet and if there is no answer or another UDP packet for the same session, this session will be removed from the session table after this timeout is reached and the session is then displayed as aged-out in the logs.

Thank You Vsys_remo for reply,

 

Yes I agree with you, later I saw applications are discovering in same traffic logs, those applications was SIP  other voice related applications and these applications always runs on UDP protocol  since it is connection less protocol I was getting bytes received zero and aged-out.

 

Thanks

Dhananjay Bhakte

  • 2 accepted solutions
  • 7549 Views
  • 2 replies
  • 0 Likes
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!