-
IPsec is not routing
Hello,
I need a little help for the ipsec
Today I have a good network 192.168.10.0 and within it have an interface that closes a virtual 10.100.0.0 with my vpn client that has this same network, untangle I can do to troubleshoot the other network oservidores put my LAN can not get out to her, I left for my internet link instead of leaving the network.
I nat all to all
Sorry for my bad English
thank you
-
It's a little unclear. Could you provide a network diagram?
-
yes
My situation is as follows
I am connected with a vpn ipsec tunnel mode
however do not think my internal network route to reach the server on the other side
my network 192.168.10.0/23
virtual interface created 10.91.164.3/25
LAN created 10.91.164.0/25
Moreover network 10.100.0.0/16
only works untangle
not on my internal network
-
Plz help me
the problem is in teh subnet mask?
-
I don't understand what you mean by "virtual interface created". Is this on a VMware server?
Please post a network diagram.
-
hi no
this is a alias eth0:1 eth0:2 ....
is sux
-
I think I understood his issue.
He is facing the following problem:
The LAN primary IP Address is: 192.168.10.1 / 23 and it has two alias:
Alias 1: 10.91.164.1 / 25
Alias 2: 172.17.32.1 / 24
He has one tunnel set up in IPSEC with remote network 10.100.0.0 / 16 and local network as 192.168.10.0 / 23 and his local gateway is 192.168.10.1.
The IPSEC VPN is working great with just one exception.
All internal desktops in the network 192.168.10.0 / 23 and gateway 192.168.10.1 are not being able to reach the hosts on the remote network (10.100.0.0 / 16).
BUT…
If he set up the internal IPs from network 10.91.164.0 / 25 with gateway 10.91.164.1 (IP Alias), all the internal PCs can reach the remote network (10.100.0.0 / 16).
BUT with that approach…
He is not being able to access the network 192.168.10.0 / 23.
What's wrong? Why Untangle does not route between networks 192.168.10.0 / 23 and 10.91.164.0 / 25 and 10.100.0.0 / 16?