Outgoing route livebox via vpn
mdm18100
-
brupala Posted messages 111946 Registration date Status Membre Last intervention -
brupala Posted messages 111946 Registration date Status Membre Last intervention -
Hello everyone.
I have a Livebox PRO and I have installed its nomadic VPN, which I use on remote workstations with the Shrew application. The Livebox has the IP address 192.168.1.1. The VPN is working correctly.
The VPN is configured with a local network at 192.168.1.0 and a remote network at 192.168.2.0.
I would like to access the PC equipped with the Shrew client, which has the address 192.168.1.148, from the local network (on the Livebox side). Currently, the ping does not succeed.
I think I need to set up a route on the Livebox, but how do I do that?
For your information, when I trace the route to a local IP address (for example 192.168.1.254) from the remote PC (192.168.1.148), I notice that I go through the address of the VLAN 192.168.2.1.
Thank you for your help.
;)
I have a Livebox PRO and I have installed its nomadic VPN, which I use on remote workstations with the Shrew application. The Livebox has the IP address 192.168.1.1. The VPN is working correctly.
The VPN is configured with a local network at 192.168.1.0 and a remote network at 192.168.2.0.
I would like to access the PC equipped with the Shrew client, which has the address 192.168.1.148, from the local network (on the Livebox side). Currently, the ping does not succeed.
I think I need to set up a route on the Livebox, but how do I do that?
For your information, when I trace the route to a local IP address (for example 192.168.1.254) from the remote PC (192.168.1.148), I notice that I go through the address of the VLAN 192.168.2.1.
Thank you for your help.
;)
2 réponses
Hi,
I don't know this dear Shrew, I found this,
but in principle, a VPN should have a separate subnet from the LAN networks to allow routing,
also,
you talk about a remote network, in fact, do you want to create a tunnel, not just connect a single client?
Clearly, we are dealing with IPsec, that doesn't help.
--
and... There you go!
I don't know this dear Shrew, I found this,
but in principle, a VPN should have a separate subnet from the LAN networks to allow routing,
also,
you talk about a remote network, in fact, do you want to create a tunnel, not just connect a single client?
Clearly, we are dealing with IPsec, that doesn't help.
--
and... There you go!
Hello and thank you for your response,
yes indeed, on the Livebox side (VPN server) I have a server that needs to communicate with a PC that is located outside and equipped with a VPN client (using the Shrew application, which is compatible with the Livebox VPN).
You said that it doesn't help; does that mean it's not possible?
Thank you in advance.
yes indeed, on the Livebox side (VPN server) I have a server that needs to communicate with a PC that is located outside and equipped with a VPN client (using the Shrew application, which is compatible with the Livebox VPN).
You said that it doesn't help; does that mean it's not possible?
Thank you in advance.
It's just more complex with IPsec VPNs, they don't like NAT.
I don't know the VPN configuration of the LB Pro either,
what parameters are you using?
I don't think you need to add a route for a "road warrior" VPN, since it's directly connected to the box.
What exactly is the problem?
For your information, when I trace the route of a local IP address (for example, 192.168.1.254) from the remote PC (192.168.1.148), I notice that I'm going through the VLAN address 192.168.2.1.
What is the IP address of the PC in the VPN (ipconfig/all)?
Is it 1.148?
And the box address?
1.1?
So it's the same IP network,
the traceroute should be direct, unless the PC's address is not what you say.
Carefully summarize your numbering plan and check the masks in the VPN connection and in the box.
I don't know the VPN configuration of the LB Pro either,
what parameters are you using?
I don't think you need to add a route for a "road warrior" VPN, since it's directly connected to the box.
What exactly is the problem?
For your information, when I trace the route of a local IP address (for example, 192.168.1.254) from the remote PC (192.168.1.148), I notice that I'm going through the VLAN address 192.168.2.1.
What is the IP address of the PC in the VPN (ipconfig/all)?
Is it 1.148?
And the box address?
1.1?
So it's the same IP network,
the traceroute should be direct, unless the PC's address is not what you say.
Carefully summarize your numbering plan and check the masks in the VPN connection and in the box.