1. LVS NAT模型搭建

1.1 NAT模型网络规划

规划要点:

  • 在生产环境中,客户端与企业互联网出口设备不会时同一网段地址,此处我们规划为同一网段地址,但是没有在客户端上配置网关,因此我们需要在企业出口设备上把LVS的VIP地址192.168.50.100做地址映射或端口映射,映射到企业出口防火墙的外网地址192.168.20.31。
  • LVS设备在LAN网络中设置了两个IP,其中192.168.50.31为实际地址DIP,192.168.50.100为虚IP,为后面的高可用规划地址。
  • 后端nginx服务器RS设备与LVS在同一网段,需要把网关指向LVS的DIP或VIP上,考虑到后期使用两台LVS做高可用,建议把网关配置为LVS的VIP地址。
  • 所有的客户端都是与后端的RS主机进行TCP三次握手,而不是LVS设备。

1.2 NAT模型访问流程

NAT模型流程图如下:

NAT的访问流程如下:

  • 1、当用户请求到达 Director Server ,此时请求的数据报文会先到内核空间的 PREROUTING 链。 此时报文的源IP为CIP , 目标IP为VIP;
  • 2、 PREROUTING 检查发现数据包的目标 IP 是本机,将数据包送至 INPUT 链;
  • 3、 IPVS 比对数据包请求的服务是否为集群服务,若是,通过调度算法挑选一台后端 RS 服务器,并修改数据包的 目标IP为RS的IP ,然后将数据包发至POSTROUTING 链。 此时报文的 源IP为CIP , 目标IP为RIP ;
  • 4、 POSTROUTING 链通过选路,将数据包通过 Director Server 的 DIP 发送给 RS ;
  • 5、 RS 发现目标为自己的 IP ,则交给应用程序处理,然后构建响应报文发回给Director Server 。 此时报文的 源IP为RIP , 目标IP为CIP ;
  • 6、 Director Server 在响应客户端前,会将源 IP 地址修改为 VIP 地址,然后响应给客户端。此时报文的 源IP为VIP , 目标IP为CIP;

1.3 NAT模型配置步骤

1.3.1 ROUTER设备配置

  • ROUTER设备的IP地址和路由信息如下:

    [root@router ~]# ip add
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:4f:a9:ca brd ff:ff:ff:ff:ff:ff
    inet 192.168.20.50/24 brd 192.168.20.255 scope global noprefixroute eth1
    valid_lft forever preferred_lft forever
    4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:4f:a9:d4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.50/24 brd 192.168.50.255 scope global noprefixroute eth2
    valid_lft forever preferred_lft forever #此场景中无需配置路由
    [root@router ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.20.0 0.0.0.0 255.255.255.0 U 101 0 0 eth1
    192.168.50.0 0.0.0.0 255.255.255.0 U 104 0 0 eth2
  • 打开router设备的ip_forward功能:

    [root@router ~]# echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf
    [root@router ~]# sysctl -p
    net.ipv4.ip_forward = 1
  • 把LVS的虚IP地址的80和443端口映射到路由器外网地址的80和443端口,也可以使用地址映射:

    #端口映射:
    [root@router ~]# iptables -t nat -A PREROUTING -d 192.168.20.50 -p tcp --dport 80 -j DNAT --to 192.168.50.100:80
    [root@router ~]# iptables -t nat -A PREROUTING -d 192.168.20.50 -p tcp --dport 443 -j DNAT --to 192.168.50.100:443 #地址映射:
    [root@router ~]# iptables -t nat -A PREROUTING -d 192.168.20.50 -j DNAT --to 192.168.50.100 #源NAT,让内部主机上网使用
    [root@router ~]# iptables -t nat -A POSTROUTING -s 192.168.50.0/24 -j SNAT --to 192.168.20.50 #查看NAT配置:
    [root@router ~]# iptables -t nat -vnL
    Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination
    0 0 DNAT tcp -- * * 0.0.0.0/0 192.168.20.50 tcp dpt:80 to:192.168.50.100:80
    0 0 DNAT tcp -- * * 0.0.0.0/0 192.168.20.50 tcp dpt:443 to:192.168.50.100:443 Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination
    0 0 SNAT all -- * * 192.168.50.0/24 0.0.0.0/0 to:192.168.20.50

1.3.2 后端nginx服务器配置

  • nginx02主机的网络配置如下:

    [root@nginx02 ~]# ip add
    4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:d9:f9:7d brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.22/24 brd 192.168.50.255 scope global noprefixroute eth2
    valid_lft forever preferred_lft forever #路由配置:网关指向LVS的VIP地址192.168.50.100
    [root@nginx02 ~]# ip route add default via 192.168.50.100 #本实验场景中存在ETH1口地址为192.168.20.0/24网段,因此需要配置指向客户端的主机路由,生产中不需要
    [root@nginx02 ~]# ip route add 192.168.20.17/32 via 192.168.50.100 [root@nginx02 ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 192.168.50.100 0.0.0.0 UG 0 0 0 eth2
    192.168.20.0 0.0.0.0 255.255.255.0 U 101 0 0 eth1
    192.168.20.17 192.168.50.100 255.255.255.255 UGH 0 0 0 eth2
    192.168.50.0 0.0.0.0 255.255.255.0 U 103 0 0 eth2
  • nginx03主机的网络配置如下:

    [root@nginx03 ~]# ip add
    4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:0a:bf:63 brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.23/24 brd 192.168.50.255 scope global noprefixroute eth2
    valid_lft forever preferred_lft forever #路由配置:网关指向LVS的VIP地址192.168.50.100
    [root@nginx03 ~]# ip route add default via 192.168.50.100 #本实验场景中存在ETH1口地址为192.168.20.0/24网段,因此需要配置指向客户端的主机路由,生产中不需要
    [root@nginx03 ~]# ip route add 192.168.20.17/32 via 192.168.50.100 [root@nginx03 ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 192.168.50.100 0.0.0.0 UG 0 0 0 eth2
    192.168.20.0 0.0.0.0 255.255.255.0 U 101 0 0 eth1
    192.168.20.17 192.168.50.100 255.255.255.255 UGH 0 0 0 eth2
    192.168.50.0 0.0.0.0 255.255.255.0 U 103 0 0 eth2
  • nginx配置文件两台WEB服务器保持一致:

    [root@nginx03 ~]# cat /etc/nginx/conf.d/xuzhichao.conf
    server {
    listen 80 default_server;
    listen 443 ssl;
    server_name www.xuzhichao.com;
    access_log /var/log/nginx/access_xuzhichao.log access_json;
    charset utf-8,gbk; #SSL配置
    ssl_certificate_key /apps/nginx/certs/www.xuzhichao.com.key;
    ssl_certificate /apps/nginx/certs/www.xuzhichao.com.crt;
    ssl_session_cache shared:ssl_cache:20m;
    ssl_session_timeout 10m;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    keepalive_timeout 65; #防盗链
    valid_referers none blocked server_names *.b.com b.* ~\.baidu\. ~\.google\.; if ( $invalid_referer ) {
    return 403;
    } client_max_body_size 10m; #浏览器图标
    location = /favicon.ico {
    root /data/nginx/xuzhichao;
    } location / {
    root /data/nginx/xuzhichao;
    index index.html index.php; #http自动跳转https
    if ($scheme = http) {
    rewrite ^/(.*)$ https://www.xuzhichao.com/$1;
    }
    }
    } #重启nginx服务:
    [root@nginx03 ~]# nginx -t
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful
    [root@nginx03 ~]# systemctl reload nginx.service
  • nginx02主机的主页文件如下:

    [root@nginx02 certs]# cat /data/nginx/xuzhichao/index.html
    node1.xuzhichao.com page
  • nginx03主机的主页文件如下:

    [root@nginx03 ~]# cat /data/nginx/xuzhichao/index.html
    node2.xuzhichao.com page
  • 测试访问:

    [root@lvs-01 ~]# curl -Hhost:www.xuzhichao.com  -k https://192.168.50.23
    node2.xuzhichao.com page
    [root@lvs-01 ~]# curl -Hhost:www.xuzhichao.com -k https://192.168.50.22
    node1.xuzhichao.com page

1.3.3 LVS设备配置

  • LVS设备的网络配置如下:

    #1.配置虚地址192.168.50.100
    #临时配置:
    [root@lvs-01 ~]# ifconfig eth2:1 192.168.50.100/24 up #永久配置,使用配置文件:
    [root@lvs-01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2:1
    TYPE=Ethernet
    BOOTPROTO=none
    IPADDR=192.168.50.100
    PREFIX=24
    DEVICE=eth2:1
    NAME=eth2:1
    DEFROUTE=yes
    ONBOOT=yes #重启网卡:
    [root@lvs-01 ~]# ifdown eth2 && ifup eth2
    [root@lvs-01 ~]# ifdown eth2:1 && ifup eth2:1 #2.LVS地址配置:
    [root@lvs-01 ~]# ip add
    4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:21:84:9d brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.31/24 brd 192.168.50.255 scope global noprefixroute eth2
    valid_lft forever preferred_lft forever
    inet 192.168.50.100/24 brd 192.168.50.255 scope global secondary eth2:1
    valid_lft forever preferred_lft forever #3.LVS配置默认路由指向出口路由器192.168.50.50
    [root@lvs-01 ~]# ip route add default via 192.168.50.50 #本实验场景中存在ETH1口地址为192.168.20.0/24网段,因此需要配置指向客户端的主机路由,生产中不需要
    [root@lvs-01 ~]# ip route add 192.168.20.17/32 via 192.168.50.50 [root@lvs-01 ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 192.168.50.50 0.0.0.0 UG 0 0 0 eth2
    192.168.20.0 0.0.0.0 255.255.255.0 U 101 0 0 eth1
    192.168.20.17 192.168.50.50 255.255.255.255 UGH 0 0 0 eth2
    192.168.50.0 0.0.0.0 255.255.255.0 U 102 0 0 eth2
  • 打开lvs设备的ip_forward功能:

    [root@router ~]# echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf
    [root@router ~]# sysctl -p
    net.ipv4.ip_forward = 1
  • 配置IPVS的规则:

    #创建80和443两个集群,并添加后端主机:
    [root@lvs-01 ~]# ipvsadm -A -t 192.168.50.100:80 -s rr
    [root@lvs-01 ~]# ipvsadm -A -t 192.168.50.100:443 -s rr
    [root@lvs-01 ~]# ipvsadm -a -t 192.168.50.100:80 -r 192.168.50.22:80 -m
    [root@lvs-01 ~]# ipvsadm -a -t 192.168.50.100:80 -r 192.168.50.23:80 -m
    [root@lvs-01 ~]# ipvsadm -a -t 192.168.50.100:443 -r 192.168.50.22:443 -m
    [root@lvs-01 ~]# ipvsadm -a -t 192.168.50.100:443 -r 192.168.50.23:443 -m [root@lvs-01 ~]# ipvsadm -Ln
    IP Virtual Server version 1.2.1 (size=4096)
    Prot LocalAddress:Port Scheduler Flags
    -> RemoteAddress:Port Forward Weight ActiveConn InActConn
    TCP 192.168.50.100:80 rr
    -> 192.168.50.22:80 Masq 1 0 0
    -> 192.168.50.23:80 Masq 1 0 0
    TCP 192.168.50.100:443 rr
    -> 192.168.50.22:443 Masq 1 0 0
    -> 192.168.50.23:443 Masq 1 0 0

1.3.4 客户端访问测试

  • 客户端网络配置如下:

    [root@xuzhichao ~]# ip add
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:2f:d0:da brd ff:ff:ff:ff:ff:ff
    inet 192.168.20.17/24 brd 192.168.20.255 scope global noprefixroute eth1
    valid_lft forever preferred_lft forever [root@xuzhichao ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.20.0 0.0.0.0 255.255.255.0 U 101 0 0 eth1
  • 测试访问:

    #1.测试使用http方式访问,重定向到https
    [root@xuzhichao ~]# for i in {1..10} ;do curl -k -L -Hhost:www,xuzhichao.com http://192.168.20.50; done
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page #2.测试直接使用https方式访问
    [root@xuzhichao ~]# for i in {1..10} ;do curl -k -Hhost:www,xuzhichao.com https://192.168.20.50; done
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
    node2.xuzhichao.com page
    node1.xuzhichao.com page
  • 查看LVS的状态信息:

    [root@lvs-01 ~]# ipvsadm -Ln --stats
    IP Virtual Server version 1.2.1 (size=4096)
    Prot LocalAddress:Port Conns InPkts OutPkts InBytes OutBytes
    -> RemoteAddress:Port
    TCP 192.168.50.100:80 21 122 71 7976 9278
    -> 192.168.50.22:80 10 62 39 4056 4902
    -> 192.168.50.23:80 11 60 32 3920 4376
    TCP 192.168.50.100:443 22 198 132 20454 60570
    -> 192.168.50.22:443 11 99 66 10227 30285
    -> 192.168.50.23:443 11 99 66 10227 30285 [root@lvs-01 ~]# ipvsadm -Ln --rate
    IP Virtual Server version 1.2.1 (size=4096)
    Prot LocalAddress:Port CPS InPPS OutPPS InBPS OutBPS
    -> RemoteAddress:Port
    TCP 192.168.50.100:80 0 1 1 89 122
    -> 192.168.50.22:80 0 1 0 44 61
    -> 192.168.50.23:80 0 1 0 44 61
    TCP 192.168.50.100:443 0 2 1 210 614
    -> 192.168.50.22:443 0 1 1 105 307
    -> 192.168.50.23:443 0 1 1 105 307 [root@lvs-01 ~]# ipvsadm -Lnc
    IPVS connection entries
    pro expire state source virtual destination
    TCP 00:31 TIME_WAIT 192.168.20.17:52494 192.168.50.100:80 192.168.50.22:80
    TCP 00:21 TIME_WAIT 192.168.20.17:43218 192.168.50.100:443 192.168.50.23:443
    TCP 00:32 TIME_WAIT 192.168.20.17:52530 192.168.50.100:80 192.168.50.23:80
    TCP 01:21 TIME_WAIT 192.168.20.17:52554 192.168.50.100:80 192.168.50.23:80
    TCP 00:32 TIME_WAIT 192.168.20.17:43260 192.168.50.100:443 192.168.50.23:443
    TCP 00:31 TIME_WAIT 192.168.20.17:43240 192.168.50.100:443 192.168.50.22:443
    TCP 01:22 TIME_WAIT 192.168.20.17:52570 192.168.50.100:80 192.168.50.23:80
    TCP 00:31 TIME_WAIT 192.168.20.17:52506 192.168.50.100:80 192.168.50.23:80
    TCP 01:21 TIME_WAIT 192.168.20.17:43280 192.168.50.100:443 192.168.50.22:443
    TCP 01:21 TIME_WAIT 192.168.20.17:43304 192.168.50.100:443 192.168.50.22:443
    TCP 00:31 TIME_WAIT 192.168.20.17:52502 192.168.50.100:80 192.168.50.22:80
    TCP 00:21 TIME_WAIT 192.168.20.17:43220 192.168.50.100:443 192.168.50.22:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43330 192.168.50.100:443 192.168.50.23:443
    TCP 00:31 TIME_WAIT 192.168.20.17:52510 192.168.50.100:80 192.168.50.22:80
    TCP 00:32 TIME_WAIT 192.168.20.17:43268 192.168.50.100:443 192.168.50.23:443
    TCP 01:21 TIME_WAIT 192.168.20.17:52542 192.168.50.100:80 192.168.50.22:80
    TCP 01:40 TIME_WAIT 192.168.20.17:43328 192.168.50.100:443 192.168.50.22:443
    TCP 00:22 TIME_WAIT 192.168.20.17:43232 192.168.50.100:443 192.168.50.22:443
    TCP 02:00 TIME_WAIT 192.168.20.17:43342 192.168.50.100:443 192.168.50.23:443
    TCP 02:00 TIME_WAIT 192.168.20.17:43338 192.168.50.100:443 192.168.50.23:443
    TCP 00:11 TIME_WAIT 192.168.20.17:43212 192.168.50.100:443 192.168.50.22:443
    TCP 00:32 TIME_WAIT 192.168.20.17:43272 192.168.50.100:443 192.168.50.22:443
    TCP 00:31 TIME_WAIT 192.168.20.17:43248 192.168.50.100:443 192.168.50.22:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43314 192.168.50.100:443 192.168.50.23:443
    TCP 00:07 TIME_WAIT 192.168.20.17:52466 192.168.50.100:80 192.168.50.22:80
    TCP 15:00 ESTABLISHED 192.168.20.17:43344 192.168.50.100:443 192.168.50.22:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43318 192.168.50.100:443 192.168.50.23:443
    TCP 02:00 TIME_WAIT 192.168.20.17:43334 192.168.50.100:443 192.168.50.23:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43320 192.168.50.100:443 192.168.50.22:443
    TCP 01:21 TIME_WAIT 192.168.20.17:43284 192.168.50.100:443 192.168.50.23:443
    TCP 02:00 TIME_WAIT 192.168.20.17:43340 192.168.50.100:443 192.168.50.22:443
    TCP 00:32 TIME_WAIT 192.168.20.17:52518 192.168.50.100:80 192.168.50.22:80
    TCP 01:21 TIME_WAIT 192.168.20.17:43308 192.168.50.100:443 192.168.50.23:443
    TCP 00:31 TIME_WAIT 192.168.20.17:43236 192.168.50.100:443 192.168.50.23:443
    TCP 01:21 TIME_WAIT 192.168.20.17:52566 192.168.50.100:80 192.168.50.22:80
    TCP 00:22 TIME_WAIT 192.168.20.17:43222 192.168.50.100:443 192.168.50.23:443
    TCP 01:21 TIME_WAIT 192.168.20.17:52534 192.168.50.100:80 192.168.50.22:80
    TCP 00:22 TIME_WAIT 192.168.20.17:43230 192.168.50.100:443 192.168.50.23:443
    TCP 00:21 TIME_WAIT 192.168.20.17:43214 192.168.50.100:443 192.168.50.23:443
    TCP 00:32 TIME_WAIT 192.168.20.17:43264 192.168.50.100:443 192.168.50.22:443
    TCP 00:32 TIME_WAIT 192.168.20.17:43256 192.168.50.100:443 192.168.50.22:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43332 192.168.50.100:443 192.168.50.22:443
    TCP 00:31 TIME_WAIT 192.168.20.17:43252 192.168.50.100:443 192.168.50.23:443
    TCP 00:31 TIME_WAIT 192.168.20.17:52498 192.168.50.100:80 192.168.50.23:80
    TCP 00:21 TIME_WAIT 192.168.20.17:43216 192.168.50.100:443 192.168.50.22:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43322 192.168.50.100:443 192.168.50.23:443
    TCP 00:22 TIME_WAIT 192.168.20.17:43226 192.168.50.100:443 192.168.50.23:443
    TCP 01:21 TIME_WAIT 192.168.20.17:43292 192.168.50.100:443 192.168.50.23:443
    TCP 00:22 TIME_WAIT 192.168.20.17:43224 192.168.50.100:443 192.168.50.22:443
    TCP 00:32 TIME_WAIT 192.168.20.17:52522 192.168.50.100:80 192.168.50.23:80
    TCP 01:21 TIME_WAIT 192.168.20.17:52546 192.168.50.100:80 192.168.50.23:80
    TCP 01:21 TIME_WAIT 192.168.20.17:52562 192.168.50.100:80 192.168.50.23:80
    TCP 01:21 TIME_WAIT 192.168.20.17:43300 192.168.50.100:443 192.168.50.23:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43324 192.168.50.100:443 192.168.50.22:443
    TCP 01:21 TIME_WAIT 192.168.20.17:52538 192.168.50.100:80 192.168.50.23:80
    TCP 01:40 TIME_WAIT 192.168.20.17:43326 192.168.50.100:443 192.168.50.23:443
    TCP 01:21 TIME_WAIT 192.168.20.17:52550 192.168.50.100:80 192.168.50.22:80
    TCP 00:31 TIME_WAIT 192.168.20.17:43244 192.168.50.100:443 192.168.50.23:443
    TCP 01:21 TIME_WAIT 192.168.20.17:43288 192.168.50.100:443 192.168.50.22:443
    TCP 02:00 TIME_WAIT 192.168.20.17:43336 192.168.50.100:443 192.168.50.22:443
    TCP 00:32 TIME_WAIT 192.168.20.17:52526 192.168.50.100:80 192.168.50.22:80
    TCP 01:21 TIME_WAIT 192.168.20.17:43276 192.168.50.100:443 192.168.50.23:443
    TCP 00:22 TIME_WAIT 192.168.20.17:43228 192.168.50.100:443 192.168.50.22:443
    TCP 01:21 TIME_WAIT 192.168.20.17:52558 192.168.50.100:80 192.168.50.22:80
    TCP 01:22 TIME_WAIT 192.168.20.17:43312 192.168.50.100:443 192.168.50.22:443
    TCP 01:21 TIME_WAIT 192.168.20.17:43296 192.168.50.100:443 192.168.50.22:443
    TCP 00:07 TIME_WAIT 192.168.20.17:43208 192.168.50.100:443 192.168.50.23:443
    TCP 01:40 TIME_WAIT 192.168.20.17:43316 192.168.50.100:443 192.168.50.22:443
    TCP 00:32 TIME_WAIT 192.168.20.17:52514 192.168.50.100:80 192.168.50.23:80
    TCP 00:11 TIME_WAIT 192.168.20.17:52470 192.168.50.100:80 192.168.50.23:80

LVS负载均衡(2)-- NAT模型搭建实例的更多相关文章

  1. 20.LVS负载均衡群集—NAT模式实例

    LVS负载均衡群集-NAT模式实例 目录 LVS负载均衡群集-NAT模式实例 群集引用概述 群集的含义 问题 解决方法 企业群集分类 群集的三种类型 负载均衡群集(Load Balance Clust ...

  2. LVS负载均衡之NAT模式部署

    1.LVS的NAT模式介绍 参考自官网:http://www.linuxvirtualserver.org/zh/lvs3.html 由于IPv4中IP地址空间的日益紧张和安全方面的原因,很多网络使用 ...

  3. LVS负载均衡集群服务搭建详解(二)

    lvs-nat模型构建 1.lvs-nat模型示意图 本次构建的lvs-nat模型的示意图如下,其中所有的服务器和测试客户端均使用VMware虚拟机模拟,所使用的CentOS 7 VS内核都支持ipv ...

  4. LVS负载均衡集群服务搭建详解(一)

    LVS概述 1.LVS:Linux Virtual Server 四层交换(路由):根据请求报文的目标IP和目标PORT将其转发至后端主机集群中的某台服务器(根据调度算法): 不能够实现应用层的负载均 ...

  5. LVS负载均衡群集(NAT)

    ----构建NAT模式的LVS群集----------client---------------LVS----------------WEB1-----------WEB2------------NF ...

  6. LVS负载均衡NAT模式实现

    LVS负载均衡之NAT模式配置 NAT 模式架构图: 操作步骤 实验环境准备:(centos7平台) 所有服务器上配置 # systemctl stop firewalld //关闭防火墙 # sed ...

  7. CentOS7Linux中服务器LVS负载均衡、高可用集群搭建(NAT、DR);

    目录 集群 声明 集群概念 集群特性 Web服务器并发相应瓶颈 集群的分类 LB实现方法: LVS集群 负载调度器 服务器池 共享存储 LVS负载均衡的三种模式 负载均衡 集群 声明 文档不断更新中. ...

  8. Linux中keepalived+LVS负载均衡的搭建测试

    1.1 LVS简介       LVS(Linux Virtual Server),也就是Linux虚拟服务器, 是一个自由软件项目.使用LVS技术要达到的目标是:通过LVS提供的负载均衡技术和Lin ...

  9. lvs负载均衡的搭建

       lvs负载均衡的搭建 作者:尹正杰 版权声明:原创作品,谢绝转载!否则将追究法律责任.         在部署环境前,我们需要了解一下一些协议 一.什么是arp 地址解析协议,即ARP(Addr ...

  10. LVS负载均衡常用的工作模式有NAT、DR、和TUN三种,其中DR模式性能最为优越,使用最为广泛。

    一.安装LVS LVS的编译安装参考本站文章:http://www.linuxe.cn/post-192.html,对于LVS这种功能性软件,在生产中用yum安装也是没有问题的. 1 yum inst ...

随机推荐

  1. C++ 线程安全的队列

    无界队列 #include<queue> #include<mutex> #include<condition_variable> #include<opti ...

  2. C++简单实现unique_ptr

    唯一指针 管理指针的存储,提供有限的垃圾回收工具,与内置指针相比几乎没有开销(取决于所使用的删除程序). 这些对象具有获取指针所有权的能力:一旦它们获得所有权,它们就会通过在某个时候负责删除指向的对象 ...

  3. 【WCH以太网接口系列芯片】CH9121\9120、CH395\392以太网系列芯片的硬件电路注意事项

    本篇基于沁恒微电子官方的以太网接口芯片的DEMO参考原理图进行分析,对一些注意事项进行标注,如果硬件设计上出现问题可以对照参考. CH912x系列: 1.CH9121:建议设计中可以将31脚RUN脚预 ...

  4. #轻重链剖分,线段树#洛谷 3703 [SDOI2017]树点涂色

    题目传送门 分析 可以发现相同的颜色一定组成一个连通块. 那么操作2就相当于 \(f_x+f_y-2*f_{lca}+1\) 操作3就相当于询问 \(f\) 的最大值. 最关键的就是操作1,考虑往上跳 ...

  5. #直径,线段树#51nod 1766 树上的最远点对

    题目 多组询问,在 \([a,b]\) 和 \([c,d]\) 中分别选一个点 \(x,y\) ,使得 \(dis(x,y)\) 最大 分析 考虑直径的一个性质,两个点集两条直径的四个端点可能成为合并 ...

  6. PriorityQueue和PriorityBlockingQueue

    目录 简介 PriorityQueue PriorityBlockingQueue PriorityQueue和PriorityBlockingQueue 简介 Queue一般来说都是FIFO的,当然 ...

  7. OpenHarmony 技术日直播回顾丨共建新技术,开拓新领域

    4月25日,"共建新技术,开拓新领域"OpenAtom OpenHarmony(以下简称"OpenHarmony")技术日在深圳顺利召开.OpenHarmony ...

  8. XML 简介及用法详解

    XML 是一种用于存储和传输数据的与软件和硬件无关的工具. 什么是XML? XML代表eXtensible Markup Language(可扩展标记语言).XML是一种与HTML非常相似的标记语言. ...

  9. 实战:如何优雅的从 Skywalking 切换到 OpenTelemetry

    背景 最近公司将我们之前使用的链路工具切换为了 OpenTelemetry. 我们的技术栈是: OTLP Client──────────►Collect────────►StartRocks (Ag ...

  10. Velero系列文章(五):基于 Velero 的 Kubernetes 集群备份容灾生产最佳实践

    考量维度 基于CSI 快照 基于Restic 文件复制 应用性能影响 低,CSI 接口调用存储系统快照 取决于数据量,占用额外资源 数据可用性 依赖于存储系统 对象存储和生产环境隔离,独立可用性,支持 ...