Creating a New Redirection Rule

by default in case of a pull stream in zixi broadcaster uses the dns to resolve the ip of its destination however, if you are pulling the stream from one cluster to another and both clusters are hosted within the same cloud region, you may want to avoid going through an external dns server another scenario is that for security reasons the traffic cannot flow outside the network by creating a redirection rule, you can specify specific routing rules for pull requests from clusters or cidr ip ranges rules can be applied to the client end point cluster, or ip cidr range, from where the pull request is initiated rules are evaluated in order from lowest order to highest you can specify the order of a rule in the rule configuration the first matching rule will apply if there is no match, the default rule prefer public ip with dtls will be used it is possible to use this as feature as an allow list by creating a 0 0 0 0/0 block rule and give it the highest order in this case, any connection not matched by a rule with a lower order will finally be matched by the blocking rule private/nic cidr do not support dtls and will redirect to a non dtls port to create a new redirection rule go to broadcasters and select a cluster click the redirection rules tab redirection rules click add rule add rule button the create redirection rule dialog is displayed in the description field, write a description for the rule in the from field, select one of the following cluster select this option to apply this rule on a pull request from a cluster cidr select this option to apply this rule on a pull request from a cidr ip range cidr rules apply to any zixi pull request, including those from zecs, irds etc if you have selected the cluster option, in the cluster field, select the cluster from which the pull request is sent if you have selected the cidr option, in the cidr field specify the cidr ip range in the to field, select one of the following redirection options redirect to public ip pull requests that match this rule will be resolved by redirecting it through a public ip this is the default behavior redirect to private ip pull requests that match this rule will be resolved by redirecting it through a private ip redirect to nic pull requests that match this rule will be resolved by redirecting it to a specific nic block pull requests that match this rule will be blocked if you have selected the redirect to nic option, in the nic cidr field, specify the cidr ip range of the nic in the latency override field, specify the latency when the redirection rule applies latency is determined by the following order redirection rule latency > source autopull/pull target latency > default 1000ms in the order field, specify the order value for this rule rules are evaluated from lowest to highest order, the first rule that matches will be applied click save