Hi,
Since Azure has limitation of only 1VPN gateway i created Centos VM inside it and i sucessfully established VPN with Cisco 1800 router. Now i can ping both sides of the tunnel but traffic is not going trough when i want to ping something from Azure LAN to
other side of VPN. I don't have any iptables rules and ipfowarding is enabled. Port 4500 and 500 are forwarded to the Centos VM.
This is my conf:
version 2.0 # conforms to second version of ipsec.conf specification
# basic configuration
config setup
# Debug-logging controls: "none" for (almost) none, "all" for lots.
# klipsdebug=none
# plutodebug="control parsing"
# For Red Hat Enterprise Linux and Fedora, leave protostack=netkey
protostack=netkey
nat_traversal=yes
virtual_private=%v4:10.0.0.0/8,%v4:192.168.0.0/16,%v4:172.16.0.0/12
oe=off
# Enable this if you see "failed to find any available worker"
# nhelpers=0
#You may put your configuration (.conf) file in the "/etc/ipsec.d/" and uncomment this.
#include /etc/ipsec.d/*.conf
conn test
auto=start
type=tunnel
authby=secret
keyexchange=ike
ike=3des-sha1;modp1024
ikelifetime=8h
esp=3des-sha1;modp1024
keylife=1h
pfs=no
###our gateway
left=172.17.1.19
leftnexthop=%defaultroute
leftid=1.1.1.1
leftsubnet=172.17.1.0/25
###remote peer
right=2.2.2.2
rightsubnet=192.168.38.0/24
I can ping Centos LAN interface from other subnet so looks like tunnel is only working one way. I added the route to several machines to use Centos VM to reach my remote geteway but looks like packets are not going trough. I don't see any traffic even reaching
LAN interface of Centos Vm when i try to ping remote subnet. It looks to me that Azure is doing source/destination checking (blocking).
Can anyone confirm this?
Thanks!