Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 27 subscribers
  • Views 1956 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

FQDN Host group rule causing high 100% CPU XG Hom

Rick Dunn

I was attempting to allow only specific devices to bypass https scanning by using the FQDN host group method for Netflix.com as the destination. My CPU on the box shortly following adding the new rule hit 100% and stayed. I know we only have one Roku streaming so this was the  single IP hitting the rule. Subsequently 

Not sure the limits of the XG Home or if I need a better CPU to process this type of rule... I have a Pentium 4 3 GHz with 4 GB RAM 2 - 1 GB NICs..

FQDN Hosts group

  • *.netflix.com
  • *.nflxext.com
  • *.nflximg.net
  • *.nflxso.net
  • *.nflxvideo.net

 

Thanks



This thread was automatically locked due to age.
Parents
  • 0

    Could be related to an "old" issue in most of network products. 

    Check the atop of the XG while using this to be sure about it. 

    Saw this on UTM as well, some services uses AWS Loadbalancer and switches the IP every 3 second (which will cause a huge load on the System). 

Reply
  • 0

    Could be related to an "old" issue in most of network products. 

    Check the atop of the XG while using this to be sure about it. 

    Saw this on UTM as well, some services uses AWS Loadbalancer and switches the IP every 3 second (which will cause a huge load on the System). 

Children