|
From: Miguel C. <mig...@gm...> - 2013-05-10 09:54:41
|
The firewall or some manual route is there certainly (do a route print on cmd line and check), but OpenVPN is also trying to define that route... which is why you get the error... OpenVPN does that if you push that route in server config or push the default gateway and this turns out to be the same subnet... or if you client configs (ccd or the client it self) also define that route! But according to the configs you posted (except ccd - I think you didn't post those) nothing seems to be defining such route, at least that's what the log you posted was showing! On Fri, May 10, 2013 at 10:39 AM, <fo...@si...> wrote: > This is the client.ovpn > client > ns-cert-type server > dev tun > proto udp > remote 84.xxx.xxx.xx 1194 > resolv-retry infinite > nobind > persist-key > persist-tun > ca ca.crt > cert xxxxx.crt > key xxxxx.key > comp-lzo > verb 1 > fragment 1300 > mssfix > > Any chance a firewall might cause this type of routing duplicate IP error? > > > >> [sorry forgot the "reply all" >> >> Hum.. If its not the server config pushing the route and its not in >> the ccd, you're left with the client config.... >> > > > |