Score:0

OpenSwan GW not routing VLAN traffic through tunnel

pk flag

I do have a tunnel configured using OpenSwan on a side and libreswan on the other. The issue seems to be on the openswan side, where I do have 2 subnets, one for the main interface, the other is on a VLAN let's say: eth0 192.168.254.0/24 eth0.22 192.168.22.0/24 on the other side I do have eth' 192.168.78.0/24 tunnel on the two sides are configured properly.

conn standard_interface
   also=common_params
   leftsubnet= 192.168.254.0/24
conn vlan_interface
   also=standard_interface
   leftsubnet=192.168.22.0/24

Once ipsec gets started I can ping from a host in the fist network the network on the other side, but from the second network, the one on the vlan, there's no way of pinging the hosts on the network behind the VPN tunnel. I'm quite sure that the problem is VLAN related, as if I invert the declaration of the networks I always get traffic only on the LAN on the normal ethernet card (not VLAN). I tried even disabling the working LAN and leaving the interface in the VLAN itself, without a result. I hope someone can help.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.