Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 3221 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DSCP Marking not working in 17.5.3?

OtherUTMGuy

My XG 330 HA pair is at our co-lo and protects multiple locations connected on the LAN port via private WAN links.

There is one WAN link providing internet access to all locations.

We have two IPSec tunnels to two different hosted applications.

I want to ensure that traffic coming in from these two tunnels to the LAN receives DSCP markings so that my private WAN providers core and edge routers will prioritize the traffic.

The following rule is being processed when viewing the logs, but WireShark shows the tagging is not being applied.

I called support and escalated the case, but am still waiting for a reply from their recent packet capture.

 

What config have I missed, or how should I adjust this rule to properly mark the traffic?

 

Thanks.

 



This thread was automatically locked due to age.
Parents Reply Children
  • +1 in reply to FloSupport

    Hi Community,

    To provide a follow up to Daniel's issue, after further investigation it was determined that their ISP was causing issues by blocking DSCP.

     Thank you for your patience and participation during the troubleshooting process. Please don't hesitate to reach out to me in the future for any questions or concerns :)

    Cheers,