lukeglazebrook
Occasional Visitor
I knocked up the following firewall-start script and it works sort of ... (think this is the equivalent of IP aliasing in my old Draytek) the intention is to get one of my internal servers externally facing on the interweb thingy
#!/bin/sh
touch /tmp/firewall-start
sleep 10
iptables -t nat -A POSTROUTING -s 192.168.0.145 -j SNAT --to-source 95.172.233.122
iptables -t nat -A PREROUTING -d 95.172.233.122 -j DNAT --to-destination 192.168.0.145
The trouble is as soon as it hit my vCenter server a certificate seems to redirect me to the internally named address
https://MyServer.MyDomain.com/websso/SAML2/SSOSSL?RelyingPartyEntityI=ld-aHR0...... blah blah
Consequently I get a dead page Presumably the "MyServer" part is chucking a spanner in the works?
Are there any fancy scripted work arounds? If I rebuilt the server but gave its NIC the internal IP above (95.172.233.122) would that have a chance of working? The certificate would regenerate, but it may still put a server name prefix at the start.
Any idea's or workarounds anyone has would be greatly appreciated...
#!/bin/sh
touch /tmp/firewall-start
sleep 10
iptables -t nat -A POSTROUTING -s 192.168.0.145 -j SNAT --to-source 95.172.233.122
iptables -t nat -A PREROUTING -d 95.172.233.122 -j DNAT --to-destination 192.168.0.145
The trouble is as soon as it hit my vCenter server a certificate seems to redirect me to the internally named address
https://MyServer.MyDomain.com/websso/SAML2/SSOSSL?RelyingPartyEntityI=ld-aHR0...... blah blah
Consequently I get a dead page Presumably the "MyServer" part is chucking a spanner in the works?
Are there any fancy scripted work arounds? If I rebuilt the server but gave its NIC the internal IP above (95.172.233.122) would that have a chance of working? The certificate would regenerate, but it may still put a server name prefix at the start.
Any idea's or workarounds anyone has would be greatly appreciated...