cluster:102
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cluster:102 [2011/06/29 15:59] – hmeij | cluster:102 [2020/08/24 11:19] (current) – hmeij07 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| **[[cluster: | **[[cluster: | ||
| - | This is my second NAT story, for the first one look at [[cluster:51|The Story Of NAT, part 1]] | + | Note #1 |
| + | |||
| + | CentOS 8.1 with the standard firewalld.\\ | ||
| + | If this is of interest to you this was how I managed to get it work: | ||
| + | < | ||
| + | EXTIFACE=MASTER_NODE_EXT_INTERFACE_DEVICE (e.g. eno1) | ||
| + | INTIFACE=MASTER_NODE_INTERNAL_INTERFACE_DEVICE (e.g. eno2) | ||
| + | INTIPADDR=MASTER_IP_OF_INTERNAL_IFAC | ||
| + | PREFIX=PREFIX_OF_INTERNAL_NETWORK | ||
| + | firewall-cmd --change-interface=${EXTIFACE} --zone=public | ||
| + | firewall-cmd --change-interface=${INTIFACE} --zone=trusted --permanent | ||
| + | firewall-cmd --permanent --direct --passthrough ipv4 -t nat -I POSTROUTING -o ${EXTIFACE} -j MASQUERADE -s ${INTIPADDR}/ | ||
| + | firewall-cmd --set-default-zone=trusted | ||
| + | firewall-cmd --reload | ||
| + | </ | ||
| + | |||
| + | And make sure the default route is set on all compute nodes. | ||
| + | |||
| + | Note #2 | ||
| + | |||
| + | configured Shorewall on a cluster | ||
| + | |||
| + | Edit the file / | ||
| + | < | ||
| + | MASQUERADE 192.168.0.0/ | ||
| + | </ | ||
| + | where 192.168.0 is the address range of your node interfaces - clearly you need to change this to fit | ||
| + | en01 is the external interface on the head node | ||
| + | |||
| + | My / | ||
| + | < | ||
| + | nat | ||
| + | nat | ||
| + | </ | ||
| + | so substitute ib0 for your internal ethernet interface | ||
| + | |||
| + | |||
| + | |||
| ==== NAT Story, part 2 ==== | ==== NAT Story, part 2 ==== | ||
| + | |||
| + | This is my second NAT story, for the first one look at [[cluster: | ||
| + | |||
| + | |||
| Writing this up so I will remember what I did, and why. Basic problem is this: How do you make a filesystem in a public VLAN available on a private network? | Writing this up so I will remember what I did, and why. Basic problem is this: How do you make a filesystem in a public VLAN available on a private network? | ||
cluster/102.1309363157.txt.gz · Last modified: by hmeij
