Hi guys,
I setup an openvpn (2.3.11) server on CentOS 7.2 using bridge mode, the CentOS server was hosted in vSphere (ESXi 6.0.0) server with virtual switch promisc settings on, now I can connect to the vpn server correctly with the information like below,
Wed Jul 06 11:27:34 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.1.111/255.255.255.0 on interface {8CAD4D7F-7255-438E-8FD6-84E3680B771C} [DHCP-serv: 192.168.1.0, lease-time: 31536000]
Wed Jul 06 11:27:34 2016 Successful ARP Flush on interface [14] {8CAD4D7F-7255-438E-8FD6-84E3680B771C}
Wed Jul 06 11:27:39 2016 TEST ROUTES: 0/0 succeeded len=0 ret=1 a=0 u/d=up
Wed Jul 06 11:27:39 2016 Initialization Sequence Completed
Wed Jul 06 11:27:39 2016 MANAGEMENT: >STATE:1467775659,CONNECTED,SUCCESS,192.168.1.111,114.160.2yy.xxx
the bridge information on the server is like below,
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno16780032: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq mast er br0 state UP qlen 1000
link/ether 00:0c:29:3a:e4:42 brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:0c:29:3a:e4:42 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.152/24 brd 192.168.1.255 scope global br0
valid_lft forever preferred_lft forever
inet6 2001:a450:274:2400:20c:29ff:fe3a:e442/64 scope global mngtmpaddr dynam ic
valid_lft 14214sec preferred_lft 12414sec
inet6 fe80::20c:29ff:fe3a:e442/64 scope link
valid_lft forever preferred_lft forever
4: tap0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast mas ter br0 state UP qlen 100
link/ether 4e:26:cb:d3:95:dc brd ff:ff:ff:ff:ff:ff
inet6 fe80::4c26:cbff:fed3:95dc/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
br0 8000.000c293ae442 no eno16780032
tap0
and the firewall settings is listed here,
block
interfaces:
sources:
services:
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
dmz
interfaces:
sources:
services: ssh
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
drop
interfaces:
sources:
services:
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
external
interfaces:
sources:
services: ssh
ports:
masquerade: yes
forward-ports:
icmp-blocks:
rich rules:
home
interfaces:
sources:
services: dhcpv6-client ipp-client mdns samba-client ssh
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
internal
interfaces:
sources:
services: dhcpv6-client ipp-client mdns samba-client ssh
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
public (default, active)
interfaces: br0 eno16780032
sources:
services: dhcpv6-client openvpn ssh
ports: 1194/udp
masquerade: yes
forward-ports:
icmp-blocks:
rich rules:
trusted
interfaces:
sources:
services:
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
work
interfaces:
sources:
services: dhcpv6-client ipp-client ssh
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
after successful connection, the strange ping issue happens in the last few days, sometimes I can ping to the gateway server or other subnet nodes, sometimes I cannot, like below, I am sure there is no changes to the configurations and network topology,
来自 192.168.1.111 的回复: 无法访问目标主机。(can not reach the host)
请求超时。(timeout)
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
来自 192.168.1.1 的回复: 字节=32 时间=328ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=329ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=325ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=321ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=322ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=325ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=326ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=322ms TTL=64
来自 192.168.1.1 的回复: 字节=32 时间=325ms TTL=64
请求超时。
请求超时。
请求超时。
请求超时。
来自 192.168.1.111 的回复: 无法访问目标主机。
请求超时。
请求超时。
来自 192.168.1.111 的回复: 无法访问目标主机。
请求超时。
请求超时。
请求超时。
请求超时。
请求超时。
Somebody knows what happening?
