如何解决服务器80端口被运营商封掉问题 如何解决无公网ip如何假设web

admin管理员组

文章数量:1531236

2023年12月16日发(作者：)

如何解决服务器80端口被运营商封掉问题

如何解决无公网ip如何假设web服务器

一.拓扑图

二.原理

假设:国内web服务器service2的web端口是990 国外服务器service1开启了80端口.

通过架设虚拟局域网将国内web服务器990端口映射转发到国外服务器80端口上达到访问国内web服务器上的网站且不需要输入端口访问.

利用openvpn将service1和service2组建成一个虚拟局域网.虚拟局域网ip需要固定.所以openvpn必须分配给service1虚拟ip是固定的. 将service2上的web服务器监听分配给它的虚拟ip.同时service1必须开启80端口,并且开启路由转发功能.当客户端访service1的80端口时.service1就通过路由转发功能将请求包通过虚拟虚拟局域网80端口发送给service2的web端口990上.service2获取到请求后将web数据在通过内网ip的990端口路由转发给service1的80端口上.然后提交给客户端.这样用户访问的就是国内服务器上的网站.解决了服务器无公网ip和运营商未开启80端口如何将网站强制通过80端口发布出去.也同时解决了无固定公网ip的问题

Service1和service2的请求速度取决于两者间的网络环境.建议service1和service2使用的是骨干节点网络.且

必须是光纤。

三.操作步骤（service1和service2以linux系统为主。因为稳定，且设置生效不用重启服务器）

1. 在service2上架设web服务。

#

yum install httpd mysql-server mysql php php-mysql –y /安装服务apache和 数据库服务 及php/

# service httpd restart /启动apache服务/

# service mysqld restart /mysql服务/

# chkconfig httpd on /设置apache开机启动/

# chkconfig mysqld on /设置mysql开启启动/

# vim /etc/httpd/conf/ /配置apache/

将监听端口修改成990，并保存退出

# service httpd restart /启动apache服务/

测试：

在浏览器中输入网址加端口号看是否架设成功，出现下面内容就说明架设成功。

2. 在service1上架设openvpn服务器端。

# rpm -ivh /redhat/el6/en/i386/rpmforge/RPMS/

# yum –y install openvpn

/安装服务/

# cp -R /usr/share/doc/openvpn-2.2.2/easy-rsa /etc/openvpn

# cd /etc/openvpn/easy-rsa/2.0

# chmod +x *

/先将easy-rsa脚本copy到/etc/openvpn，并添加可执行权限：/

# cd /etc/openvpn/easy-rsa/2.0

# ln -s

/然后使用easy-rsa的脚本产生证书/

# vim vars

编辑所需的参数再调用之，也可以默认参数

# source vars

注意：下面这个命令在第一次安装时可以运行，以后在添加客户端时千万别运行，这个命令会清除所有已经生成的证书密钥。

# ./clean-all

/清理所有/

# ./build-ca

/生成服务器端ca证书/

Generating a 1024 bit RSA private key

............++++++

..................++++++

writing new private key to ''

-----

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [CN]:

State or Province Name (full name) [SH]:

Locality Name (eg, city) [PD]:

Organization Name (eg, company) [zyfmaster]:

Organizational Unit Name (eg, section) []:zyfmaster

Common Name (eg, your name or your server's hostname) [zyfmaster CA]:server

Name []:

Email Address [905407204@]:

# ./build-key-server server

/生成服务器端密钥key, 后面这个server 就是服务器名，可以自定义。/

Generating a 1024 bit RSA private key

.......................................++++++

.......++++++

writing new private key to ''

-----

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [CN]:

State or Province Name (full name) [SH]:

Locality Name (eg, city) [PD]:

Organization Name (eg, company) [zyfmaster]:

Organizational Unit Name (eg, section) []:zyfmaster

Common Name (eg, your name or your server's hostname) [server]:server

Name []:

Email Address [905407204@]:

Please enter the following 'extra' attributes

to be sent with your certificate request

A challenge password []:abcd1234

An optional company name []:zyfmaster

Using configuration from /etc/openvpn/2.0/

Check that the request matches the signature

Signature ok

The Subject's Distinguished Name is as follows

countryName :PRINTABLE:'CN' #可以默认也可以根据实际情况填写

stateOrProvinceName :PRINTABLE:'SH' #可以默认也可以根据实际情况填写

localityName :PRINTABLE:'PD' #可以默认也可以根据实际情况填写

organizationName :PRINTABLE:'zyfmaster' #可以默认也可以根据实际情况填写

organizationalUnitName:PRINTABLE:'zyfmaster' #可以默认也可以根据实际情况填写

commonName :PRINTABLE:'server' #可以默认也可以根据实际情况填写

emailAddress :IA5STRING:'905407204@' #可以默认也可以根据实际情况填写

Certificate is to be certified until Dec 2 04:14:34 2022 GMT (3650 days)

Sign the certificate? [y/n]:y

#这里注意一定要选择y，否则证书生成的是空证书

1 out of 1 certificate requests certified, commit? [y/n]y #这里注意一定要选择y否则证书生成的是空证书

Write out database with 1 new entries

Data Base Updated

/服务器端证书生成成功/

# ./build-key client1

/生成客户端 key后面这个client1就是客户端名，可以自定义/

Generating a 1024 bit RSA private key

............++++++

........................................................++++++

writing new private key to ''

-----

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [CN]:

State or Province Name (full name) [SH]:

Locality Name (eg, city) [PD]:

Organization Name (eg, company) [zyfmaster]:

Organizational Unit Name (eg, section) []:zyfmaster

Common Name (eg, your name or your server's hostname) [client1]:client1 #重要: 每个不同的client 生成的证书, 名字必须不同.

Name []:

Email Address [905407204@]:

Please enter the following 'extra' attributes

to be sent with your certificate request

A challenge password []:abcd1234

An optional company name []:zyfmaster

Using configuration from /etc/openvpn/2.0/

Check that the request matches the signature

Signature ok

The Subject's Distinguished Name is as follows

countryName :PRINTABLE:'CN'

stateOrProvinceName :PRINTABLE:'SH' #可以默认也可以根据实际情况填写

localityName :PRINTABLE:'PD' #可以默认也可以根据实际情况填写

organizationName :PRINTABLE:'zyfmaster' #可以默认也可以根据实际情况填写

organizationalUnitName:PRINTABLE:'zyfmaster' #可以默认也可以根据实际情况填写

commonName :PRINTABLE:'client1' #可以默认也可以根据实际情况填写

emailAddress :IA5STRING:'905407204@' #可以默认也可以根据实际情况填写

Certificate is to be certified until Dec 2 04:15:50 2022 GMT (3650 days)

Sign the certificate? [y/n]:y

/这里注意一定要选择y，否则证书生成的是空证书/

1 out of 1 certificate requests certified, commit? [y/n]y

/这里注意一定要选择y，否则证书生成的是空证书/

Write out database with 1 new entries

Data Base Updated

/客户端证书生成成功/

# ./build-key client2

# ./build-key client3

/以此类推建立其他客户端 key/

# ./build-dh

/生成Diffie Hellman参数 （这里等待一段时间。等待时长和你服务器性能决定）/

# tar zcvf keys/*

/将 keys 下的所有文件打包下载到本地(可以通过winscp,http,ftp等等……)/

# cp -r /usr/share/doc/openvpn-2.2.2/sample-config-files/ /etc/openvpn/

# vim /etc/openvpn/

/创建服务端配置文件，并修改配置文件/

;local d

改成：

local 192.168.2.3

port 1194 （根据自己实际情况修改）

proto udp （根据自己实际情况修改）

dev tun （根据自己实际情况修改）

ca

cert

key # This file should be kept secret

改成

ca /etc/openvpn/easy-rsa/2.0/keys/ （根据自己存放证书位置修改）

cert /etc/openvpn/easy-rsa/2.0/keys/ （根据自己存放证书位置修改）

key /etc/openvpn/easy-rsa/2.0/keys/ # This file should be kept secret

（根据自己存放证书位置修改）

dh

改成

dh /etc/openvpn/easy-rsa/2.0/keys/ （根据自己存放证书位置修改）

server 10.8.0.0 255.255.255.0

;push "route 192.168.10.0 255.255.255.0"

;push "route 192.168.20.0 255.255.255.0"

改成

;push "route 192.168.10.0 255.255.255.0"

push "route 10.8.0.0 255.255.255.0"

;push "route 192.168.20.0 255.255.255.0"

ifconfig-pool-persist

;push "redirect-gateway def1 bypass-dhcp"

改成

push "redirect-gateway def1"

;push "dhcp-option DNS 208.67.222.222"

;push "dhcp-option DNS 208.67.220.220"

改成

push "dhcp-option DNS 114.114.114.114"

push "dhcp-option DNS 114.114.115.115"

keepalive 10 120

comp-lzo

persist-key

persist-tun

status

;log

改成

log

verb 3

# #

# This config should work on Windows #

# or Linux/BSD systems. Remember on #

# Windows to quote pathnames and use #

# double backslashes, e.g.: #

# "C:Program " #

# #

# Comments are preceded with '#' or ';' #

#################################################

# Which local IP address should OpenVPN

# listen on? (optional)

;local d

local 192.168.2.3

# Which TCP/UDP port should OpenVPN listen on?

# If you want to run multiple OpenVPN instances

# on the same machine, use a different port

# number for each one. You will need to

# open up this port on your firewall.

port 1194

# TCP or UDP server?

;proto tcp

proto udp

# "dev tun" will create a routed IP tunnel,

# "dev tap" will create an ethernet tunnel.

# Use "dev tap0" if you are ethernet bridging

# and have precreated a tap0 virtual interface

# and bridged it with your ethernet interface.

# If you want to control access policies

# over the VPN, you must create firewall

# rules for the the TUN/TAP interface.

# On non-Windows systems, you can give

# an explicit unit number, such as tun0.

# On Windows, use "dev-node" for this.

# On most systems, the VPN will not function

# unless you partially or fully disable

# the firewall for the TUN/TAP interface.

;dev tap

dev tun

# Windows needs the TAP-Win32 adapter name

# from the Network Connections panel if you

# have more than one. On XP SP2 or higher,

# you may need to selectively disable the

# Windows firewall for the TAP adapter.

# Non-Windows systems usually don't need this.

;dev-node MyTap

# SSL/TLS root certificate (ca), certificate

# (cert), and private key (key). Each client

# and the server must have their own cert and

# key file. The server and all clients will

# use the same ca file.

#

# See the "easy-rsa" directory for a series

# of scripts for generating RSA certificates

# and private keys. Remember to use

# a unique Common Name for the server

# and each of the client certificates.

#

# Any X509 key management system can be used.

# OpenVPN can also use a PKCS #12 formatted key file

# (see "pkcs12" directive in man page).

ca /etc/openvpn/easy-rsa/2.0/keys/

cert /etc/openvpn/easy-rsa/2.0/keys/

key /etc/openvpn/easy-rsa/2.0/keys/ # This file should be kept secret

# Diffie hellman parameters.

# Generate your own with:

# openssl dhparam -out 1024

# Substitute 2048 for 1024 if you are using

# 2048 bit keys.

dh /etc/openvpn/easy-rsa/2.0/keys/

# Configure server mode and supply a VPN subnet

# for OpenVPN to draw client addresses from.

# The server will take 10.8.0.1 for itself,

# the rest will be made available to clients.

# Each client will be able to reach the server

# on 10.8.0.1. Comment this line out if you are

# ethernet bridging. See the man page for more info.

server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address

# associations in this file. If OpenVPN goes down or

# is restarted, reconnecting clients can be assigned

# the same virtual IP address from the pool that was

# previously assigned.

ifconfig-pool-persist

# Configure server mode for ethernet bridging.

# You must first use your OS's bridging capability

# to bridge the TAP interface with the ethernet

# NIC interface. Then you must manually set the

# IP/netmask on the bridge interface, here we

# assume 10.8.0.4/255.255.255.0. Finally we

# must set aside an IP range in this subnet

# (start=10.8.0.50 end=10.8.0.100) to allocate

# to connecting clients. Leave this line commented

# out unless you are ethernet bridging.

;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging

# using a DHCP-proxy, where clients talk

# to the OpenVPN server-side DHCP server

# to receive their IP address allocation

# and DNS server addresses. You must first use

# your OS's bridging capability to bridge the TAP

# interface with the ethernet NIC interface.

# Note: this mode only works on clients (such as

# Windows), where the client-side TAP adapter is

# bound to a DHCP client.

;server-bridge

# Push routes to the client to allow it

# to reach other private subnets behind

# the server. Remember that these

# private subnets will also need

# to know to route the OpenVPN client

# address pool (10.8.0.0/255.255.255.0)

# back to the OpenVPN server.

;push "route 192.168.10.0 255.255.255.0"

;push "route 192.168.20.0 255.255.255.0"

push "route 10.8.0.0 255.255.255.0"

# To assign specific IP addresses to specific

# clients or if a connecting client has a private

# subnet behind it that should also have VPN access,

# use the subdirectory "ccd" for client-specific

# configuration files (see man page for more info).

# EXAMPLE: Suppose the client

# having the certificate common name "Thelonious"

# also has a small subnet behind his connecting

# machine, such as 192.168.40.128/255.255.255.248.

# First, uncomment out these lines:

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

# Then create a file ccd/Thelonious with this line:

# iroute 192.168.40.128 255.255.255.248

# This will allow Thelonious' private subnet to

# access the VPN. This example will only work

# if you are routing, not bridging, i.e. you are

# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give

# Thelonious a fixed VPN IP address of 10.9.0.1.

# First uncomment out these lines:

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

# Then add this line to ccd/Thelonious:

# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different

# firewall access policies for different groups

# of clients. There are two methods:

# (1) Run multiple OpenVPN daemons, one for each

# group, and firewall the TUN/TAP interface

# for each group/daemon appropriately.

# (2) (Advanced) Create a script to dynamically

# modify the firewall in response to access

# from different clients. See man

# page for more info on learn-address script.

;learn-address ./script

# If enabled, this directive will configure

# all clients to redirect their default

# network gateway through the VPN, causing

# all IP traffic such as web browsing and

# and DNS lookups to go through the VPN

# (The OpenVPN server machine may need to NAT

# or bridge the TUN/TAP interface to the internet

# in order for this to work properly).

;push "redirect-gateway def1 bypass-dhcp"

push "redirect-gateway def1"

# Certain Windows-specific network settings

# can be pushed to clients, such as DNS

# or WINS server addresses. CAVEAT:

# /#dhcpcaveats

# The addresses below refer to the public

# DNS servers provided by .

;push "dhcp-option DNS 208.67.222.222"

;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different

# clients to be able to "see" each other.

# By default, clients will only see the server.

# To force clients to only see the server, you

# will also need to appropriately firewall the

# server's TUN/TAP interface.

;client-to-client

# Uncomment this directive if multiple clients

# might connect with the same certificate/key

# files or common names. This is recommended

# only for testing purposes. For production use,

# each client should have its own certificate/key

# pair.

#

# IF YOU HAVE NOT GENERATED INDIVIDUAL

# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,

# EACH HAVING ITS OWN UNIQUE "COMMON NAME",

# UNCOMMENT THIS LINE OUT.

;duplicate-cn

# The keepalive directive causes ping-like

# messages to be sent back and forth over

# the link so that each side knows when

# the other side has gone down.

# Ping every 10 seconds, assume that remote

# peer is down if no ping received during

# a 120 second time period.

keepalive 10 120

# For extra security beyond that provided

# by SSL/TLS, create an "HMAC firewall"

# to help block DoS attacks and UDP port flooding.

#

# Generate with:

# openvpn --genkey --secret

#

# The server and each client must have

# a copy of this key.

# The second parameter should be '0'

# on the server and '1' on the clients.

;tls-auth 0 # This file is secret

# Select a cryptographic cipher.

# This config item must be copied to

# the client config file as well.

;cipher BF-CBC # Blowfish (default)

;cipher AES-128-CBC # AES

;cipher DES-EDE3-CBC # Triple-DES

# Enable compression on the VPN link.

# If you enable it here, you must also

# enable it in the client config file.

comp-lzo

# The maximum number of concurrently connected

# clients we want to allow.

;max-clients 100

# It's a good idea to reduce the OpenVPN

# daemon's privileges after initialization.

#

# You can uncomment this out on

# non-Windows systems.

;user nobody

;group nobody

# modify the firewall in response to access

# from different clients. See man

# page for more info on learn-address script.

;learn-address ./script

# If enabled, this directive will configure

# all clients to redirect their default

# network gateway through the VPN, causing

# all IP traffic such as web browsing and

# and DNS lookups to go through the VPN

# (The OpenVPN server machine may need to NAT

# or bridge the TUN/TAP interface to the internet

# in order for this to work properly).

;push "redirect-gateway def1 bypass-dhcp"

push "redirect-gateway def1"

# Certain Windows-specific network settings

# can be pushed to clients, such as DNS

# or WINS server addresses. CAVEAT:

# /#dhcpcaveats

# The addresses below refer to the public

# DNS servers provided by .

;push "dhcp-option DNS 208.67.222.222"

;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different

# clients to be able to "see" each other.

# By default, clients will only see the server.

# To force clients to only see the server, you

# will also need to appropriately firewall the

# server's TUN/TAP interface.

;client-to-client

# Uncomment this directive if multiple clients

# might connect with the same certificate/key

# files or common names. This is recommended

# only for testing purposes. For production use,

# each client should have its own certificate/key

# pair.

#

# IF YOU HAVE NOT GENERATED INDIVIDUAL

# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,

# EACH HAVING ITS OWN UNIQUE "COMMON NAME",

# UNCOMMENT THIS LINE OUT.

;duplicate-cn

# The keepalive directive causes ping-like

# messages to be sent back and forth over

# the link so that each side knows when

# the other side has gone down.

# Ping every 10 seconds, assume that remote

# peer is down if no ping received during

# a 120 second time period.

keepalive 10 120

# For extra security beyond that provided

# by SSL/TLS, create an "HMAC firewall"

# to help block DoS attacks and UDP port flooding.

#

# Generate with:

# openvpn --genkey --secret

#

# The server and each client must have

# a copy of this key.

# The second parameter should be '0'

# on the server and '1' on the clients.

;tls-auth 0 # This file is secret

# Select a cryptographic cipher.

# This config item must be copied to

# the client config file as well.

;cipher BF-CBC # Blowfish (default)

;cipher AES-128-CBC # AES

;cipher DES-EDE3-CBC # Triple-DES

# Enable compression on the VPN link.

# If you enable it here, you must also

# enable it in the client config file.

comp-lzo

# The maximum number of concurrently connected

# clients we want to allow.

;max-clients 100

# It's a good idea to reduce the OpenVPN

# daemon's privileges after initialization.

#

# You can uncomment this out on

# non-Windows systems.

;user nobody

;group nobody

# The persist options will try to avoid

# accessing certain resources on restart

# that may no longer be accessible because

# of the privilege downgrade.

persist-key

persist-tun

# Output a short status file showing

# Output a short status file showing

# current connections, truncated

# and rewritten every minute.

status

# By default, log messages will go to the syslog (or

# on Windows, if running as a service, they will go to

# the "Program FilesOpenVPNlog" directory).

# Use log or log-append to override this default.

# "log" will truncate the log file on OpenVPN startup,

# while "log-append" will append to it. Use one

# or the other (but not both).

log

;log-append

# Set the appropriate level of log

# file verbosity.

#

# 0 is silent, except for fatal errors

# 4 is reasonable for general usage

# 5 and 6 can help to debug connection problems

# 9 is extremely verbose

verb 3

# Silence repeating messages. At most 20

# sequential messages of the same message

# category will be output to the log.

;mute 20

# service openvpn restart

/启动服务/

#ifconfig

这样就是成功了。

# sed -i '/_forward/s/0/1/g' /etc/

# sysctl -w _forward=1

/开启路由转发功能/

#

iptables -t nat -A POSTROUTING -s 10.8.0.0/255.255.255.0 -j SNAT --to-source 192.168.0.64

# /etc/init.d/iptables save

# service iptables restart

/设置防火墙规则/

3. 在service2上架设openvpn客户端。

# rpm -ivh

/redhat/el6/en/i386/rpmforge/RPMS/

# yum –y install openvpn

/安装服务/

# cp -R /usr/share/doc/openvpn-2.2.2/easy-rsa /etc/openvpn

# cd /etc/openvpn/easy-rsa/2.0

# chmod +x *

将勾选的证书传输到service2服务器上的/etc/openvpn/目录里

#vim /etc/openvpn/

将下列内容输入进去

##############################################

# Sample client-side OpenVPN 2.0 config file #

# for connecting to multi-client server. #

# #

# This configuration can be used by multiple #

# clients, however each client should have #

# its own cert and key files. #

# #

# On Windows, you might want to rename this #

# file so it has a .ovpn extension #

##############################################

# Specify that we are a client and that we

# will be pulling certain config file directives

# from the server.

client

# Use the same setting as you are using on

# the server.

# On most systems, the VPN will not function

# unless you partially or fully disable

# the firewall for the TUN/TAP interface.

;dev tap

dev tun

# Windows needs the TAP-Win32 adapter name

# from the Network Connections panel

# if you have more than one. On XP SP2,

# you may need to disable the firewall

# for the TAP adapter.

;dev-node MyTap

# Are we connecting to a TCP or

# UDP server? Use the same setting as

# on the server.

proto tcp

；proto udp

# The hostname/IP and port of the server.

# You can have multiple remote entries

# to load balance between the servers.

remote 192.168.2.3 1194

;remote my-server-2 1194

# Choose a random host from the remote

# list for load-balancing. Otherwise

# try hosts in the order specified.

;remote-random

# Keep trying indefinitely to resolve the

# host name of the OpenVPN server. Very useful

# on machines which are not permanently connected

# to the internet such as laptops.

resolv-retry infinite

# Most clients don't need to bind to

# a specific local port number.

nobind

# Downgrade privileges after initialization (non-Windows only)

user nobody

group nobody

# Try to preserve some state across restarts.

persist-key

persist-tun

# If you are connecting through an

# HTTP proxy to reach the actual OpenVPN

# server, put the proxy server/IP and

# port number here. See the man page

# if your proxy server requires

# authentication.

;http-proxy-retry # retry on connection failures

;http-proxy 10.0.0.172 80

# Wireless networks often produce a lot

# of duplicate packets. Set this flag

# to silence duplicate packet warnings.

;mute-replay-warnings

# SSL/TLS parms.

# See the server config file for more

# description. It's best to use

# a separate .crt/.key file pair

# for each client. A single ca

# file can be used for all clients.

ca

cert

key

# Verify server certificate by checking

# that the certicate has the nsCertType

# field set to "server". This is an

# important precaution to protect against

# a potential attack discussed here:

# /#mitm

#

# To use this feature, you will need to generate

# your server certificates with the nsCertType

# field set to "server". The build-key-server

# script in the easy-rsa folder will do this.

ns-cert-type server

# If a tls-auth key is used on the server

# then every client must also have the key.

;tls-auth 1

# Select a cryptographic cipher.

# If the cipher option is used on the server

# then you must also specify it here.

;cipher x

# Enable compression on the VPN link.

# Don't enable this unless it is also

# enabled in the server config file.

comp-lzo

# Set log file verbosity.

verb 3

# Silence repeating messages

mute 20

#openvpn --config /etc/openvpn/

/启动客户端/

#ifconfig

这样就是成功了

4. 在service1上配置防火墙。

#vim /etc/sysconfig/iptables

# Generated by iptables-save v1.4.7 on Sat May 9 22:32:39 2015

*nat

:PREROUTING ACCEPT [238:26220]

:POSTROUTING ACCEPT [6:330]

:OUTPUT ACCEPT [4:234]

-A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE

-A PREROUTING -d 192.168.2.3/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.8.0.6:990

-A POSTROUTING -s 10.8.0.0/24 -d 10.8.0.6/32 -p tcp -m tcp --dport 990 -j SNAT --to-source 192.168.2.3

-A POSTROUTING -s 10.8.0.0/24 -j SNAT --to-source 192.168.2.3

COMMIT

# Completed on Sat May 9 22:32:39 2015

# Generated by iptables-save v1.4.7 on Sat May 9 22:32:39 2015

*filter

:INPUT ACCEPT [6:585]

:FORWARD ACCEPT [6:240]

:OUTPUT ACCEPT [14:1336]

-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT

COMMIT

# Completed on Sat May 9 22:32:39 2015

测试：

192.168.2.3

本文标签： 端口服务器证书生成虚拟