[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] Remote address conflict (Was: Possible minor bug with IP aliases)


  • Subject: [Openvpn-users] Remote address conflict (Was: Possible minor bug with IP aliases)
  • From: "Erhard Weinell" <weinell0707@xxxxxx>
  • Date: Sun, 25 Nov 2007 15:07:30 +0100

Greetings again,

my last problem got solved by using the 'local' directive in the server config. Sorry for the 'possible bug'.

However, I got another problem regarding routing. Setup: 'Road warrior' connects to the office network 10.1.0.0/24 through the OVPN server on 10.1.0.10, using tap setup. Road warrios get an ip of the range .240 to .254. and should be able to reach all machines inside the office network. Relevant config lines:

local 10.1.0.10
server-bridge 10.1.0.10 255.255.255.0 10.1.0.240 10.1.0.254

Problem: Clients get a proper address assigned, and a route is added to 10.1.0.0/24 on tap0. OVPN on client side outputs a warning:
  --remote address [10.1.0.10] conflicts with --ifconfig subnet
  [10.1.0.240, 255.255.255.0] -- local and remote addresses cannot be
  inside of the --ifconfig subnet.

I understand this issue, BUT I would like to create an additional route on the client, i.e. to 10.1.0.10 using the current default connection. If I do this manually (e.g. route add 10.1.0.10 default gw 192.168.0.1), the vpn connection works fine. Is there a config directive to do this automatically?

Best,
Erhard
______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users