I'm setting up my second AWS server, using the exact same server config (Literally. Minus a couple routing settings specific to certain clients, all settings are the same) and for some reason, the openVPN adapter cannot ping the servers other NIC. If I try to do it on the working server, here is what I get:
C:\Users\xxxx>ping 172.31.30.148 -S 10.10.0.1
Pinging 172.31.30.148 from 10.10.0.1 with 32 bytes of data:
Reply from 172.31.30.148: bytes=32 time<1ms TTL=127
Reply from 172.31.30.148: bytes=32 time<1ms TTL=127
Reply from 172.31.30.148: bytes=32 time<1ms TTL=127
Reply from 172.31.30.148: bytes=32 time<1ms TTL=127
Ping statistics for 172.31.30.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
172.31.30.148 being the servers regular NIC, 10.10.0.1 being the openVPN interface.
On the second server, same command, this happens:
C:\Windows\system32>ping 172.31.13.1 -S 10.10.0.1
Pinging 172.31.13.1 from 10.10.0.1 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 172.31.13.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
And here is my config:
port 1194
proto udp4
sndbuf 0
rcvbuf 0
compress
tun-mtu 1500
#Routing Settings
client-config-dir "C:\\Program Files\\OpenVPN\\config\\ccd"
#AWS route
route 10.10.0.0 255.255.0.0
push "route 10.10.0.0 255.255.0.0"
push "dhcp-option DNS 10.10.0.1"
push "dhcp-option DNS 8.8.8.8"
topology subnet
persist-tun
persist-key
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\server.crt"
key "C:\\Program Files\\OpenVPN\\config\\server.key"
dh "C:\\Program Files\\OpenVPN\\config\\dh2048.pem"
tls-auth ta.key 0 # This file is secret
ifconfig-pool-persist ipp.txt
client-to-client
keepalive 10 120
cipher AES-256-CBC
status openvpn-status.log
verb 5
explicit-exit-notify 1
dev tun
server 10.10.0.0 255.255.255.0
tls-server
And even though I have not added any routes specifically, here are the routes from the working and non working servers:
WORKING:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.31.16.1 172.31.30.148 15
10.10.0.0 255.255.0.0 10.10.0.2 10.10.0.1 25
10.10.0.0 255.255.255.0 On-link 10.10.0.1 281
10.10.0.1 255.255.255.255 On-link 10.10.0.1 281
10.10.0.255 255.255.255.255 On-link 10.10.0.1 281
10.10.10.0 255.255.255.0 10.10.0.2 10.10.0.1 25
10.10.20.0 255.255.255.0 10.10.0.2 10.10.0.1 25
10.10.30.0 255.255.255.0 10.10.0.2 10.10.0.1 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
169.254.169.123 255.255.255.255 172.31.16.1 172.31.30.148 30
169.254.169.249 255.255.255.255 172.31.16.1 172.31.30.148 30
169.254.169.250 255.255.255.255 172.31.16.1 172.31.30.148 30
169.254.169.251 255.255.255.255 172.31.16.1 172.31.30.148 30
169.254.169.253 255.255.255.255 172.31.16.1 172.31.30.148 30
169.254.169.254 255.255.255.255 172.31.16.1 172.31.30.148 30
172.31.16.0 255.255.240.0 On-link 172.31.30.148 271
172.31.30.148 255.255.255.255 On-link 172.31.30.148 271
172.31.31.255 255.255.255.255 On-link 172.31.30.148 271
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.10.0.1 281
224.0.0.0 240.0.0.0 On-link 172.31.30.148 271
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.10.0.1 281
255.255.255.255 255.255.255.255 On-link 172.31.30.148 271
===========================================================================
NON WORKING:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.31.0.1 172.31.10.1 15
10.10.0.0 255.255.0.0 10.10.0.2 10.10.0.1 25
10.10.0.0 255.255.255.0 On-link 10.10.0.1 281
10.10.0.1 255.255.255.255 On-link 10.10.0.1 281
10.10.0.255 255.255.255.255 On-link 10.10.0.1 281
10.10.10.0 255.255.255.0 10.10.0.2 10.10.0.1 25
10.10.20.0 255.255.255.0 10.10.0.2 10.10.0.1 25
10.10.30.0 255.255.255.0 10.10.0.2 10.10.0.1 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
169.254.169.123 255.255.255.255 172.31.0.1 172.31.10.1 30
169.254.169.249 255.255.255.255 172.31.0.1 172.31.10.1 30
169.254.169.250 255.255.255.255 172.31.0.1 172.31.10.1 30
169.254.169.251 255.255.255.255 172.31.0.1 172.31.10.1 30
169.254.169.253 255.255.255.255 172.31.0.1 172.31.10.1 30
169.254.169.254 255.255.255.255 172.31.0.1 172.31.10.1 30
172.31.0.0 255.255.240.0 On-link 172.31.10.1 271
172.31.10.1 255.255.255.255 On-link 172.31.10.1 271
172.31.15.255 255.255.255.255 On-link 172.31.10.1 271
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 172.31.10.1 271
224.0.0.0 240.0.0.0 On-link 10.10.0.1 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 172.31.10.1 271
255.255.255.255 255.255.255.255 On-link 10.10.0.1 281
===========================================================================
Settings in AWS are identical. I would really appreciate some help on this. Not sure what could be causing it. I've added/deleted several routes with no luck.
Also, all windows firewalls disabled for testing purposes. I'm honestly not sure what I am missing. Anyone have any ideas/pointers?
