Re: [strongSwan] Why doesn't table 220 change forwarded packets source IP address?

2016-11-06 Thread Richard Chan
My scenario is VMs behind the roadwarrior(carol) reaching gateway(moon)'s subnets (alice). 1. carol to moon subnets - this works correctly as a point2site network. 2. carol - has a KVM libvirt 192.168.122.0/24 network totally unknown to moon. I want these VMs to reach the subnets behind moon

Re: [strongSwan] Why doesn't table 220 change forwarded packets source IP address?

2016-11-06 Thread Andreas Steffen
Hi Richard, the table 220 source IP routing rule applies to packets originating from the VPN gateway itself, only . If you want roadwarriors from a subnet behind the GW to assume this address then you have to NAT them to the GW's address. Since the table 220 rule usually maps the GW's source

[strongSwan] Why doesn't table 220 change forwarded packets source IP address?

2016-11-05 Thread Richard Chan
Hi, in the roadwarrior configuration, from a conceptual point of view, why doesn't table 220 change the source IP address of forwarded packets (say the roadwarrior has a subnet behind it)? # ip ro sho table 220 10.0.0.0/8 via 192.168.1.1 dev eth0 proto static src 10.2.0.3 # ip rule show 0: