Quantcast
Channel: CentOS Bug Tracker - Issues
Viewing all articles
Browse latest Browse all 19115

0007900: SCTP destination port can not be chaged when specifying iptables rule.

$
0
0
We used iptables to translate the port number and ip address.<br /> iptables version we used is 1.4.21 as we check the latest Linux command of iptables and it said it support SCTP protocol and and also destination port can be changed.<br /> <br /> After our trial, the ip address was changed, however, the destination port number was NOT changed.<br /> <br /> Here is our setting sample:<br /> <br /> For example)<br /> Expected<br /> 1. Source B is sending the SCTP INIT to NAPT server(172.20.63.12(36412) -> 172.20.0.12(36412) <br /> 2. NAPT to forward the message to Target A. (172.20.63.12(36412) -> 172.20.86.50(36413) <br /> <br /> The following is the configuration of iptables )<br /> iptables -t nat -A PREROUTING -i enp7s0f0 -d 172.20.0.2 -p sctp --dport 36412 -j DNAT --to-destination 172.20.86.50:36412<br /> iptables -t nat -A PREROUTING -i enp7s0f0 -d 172.20.0.12 -p sctp --dport 36412 -j DNAT --to-destination 172.20.86.50:36413<br /> iptables -t nat -A PREROUTING -i enp7s0f1 -d 172.20.0.2 -p sctp --dport 36412 -j DNAT --to-destination 172.20.86.50:36414<br /> iptables -t nat -A PREROUTING -i enp7s0f1 -d 172.20.0.12 -p sctp --dport 36412 -j DNAT --to-destination 172.20.86.50:36415<br /> <br /> Result<br /> 1. SCTP INIT to NAPT (172.20.63.12(36412) -> 172.20.0.12(36412)<br /> 2. NAPT to forward the message to Target A. (172.20.63.12(36412) -> 172.20.86.50(36412)<br /> <br /> <br /> <br /> Hope this issue will be solved soon.<br /> Takashi

Viewing all articles
Browse latest Browse all 19115

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>