Im not sure why i am getting an ip route conflict when I connect my router to the openvpn [code]Mar 11 21:20:10 openvpn[6933]: TUN/TAP device tun15 opened Mar 11 21:20:10 openvpn[6933]: TUN/TAP TX queue length set to 100 Mar 11 21:20:10 openvpn[6933]: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Mar 11 21:20:10 openvpn[6933]: /sbin/ifconfig tun15 10.8.0.2 netmask 255.255.255.0 mtu 1500 broadcast 10.8.0.255 Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 10.8.0.0 255.255.255.0 Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 192.168.1.0 255.255.255.0 Mar 11 21:20:10 openvpn[6933]: Initialization Sequence Completed[/code] my server conf: [code]port 1194 proto udp dev tun sndbuf 0 rcvbuf 0 ca ca.crt cert server.crt key server.key dh dh.pem tls-auth ta.key 0 topology subnet server 10.8.0.0 255.255.255.0 ifconfig-pool-persist ipp.txt #push "redirect-gateway def1 bypass-dhcp" push "route 10.8.0.0 255.255.255.0" push "route 192.168.1.0 255.255.255.0" route 192.168.1.0 255.255.255.0 client-to-client push "dhcp-option DNS 8.8.8.8" push "dhcp-option DNS 8.8.4.4" keepalive 10 120 cipher AES-256-CBC comp-lzo user nobody group nogroup persist-key persist-tun status openvpn-status.log verb 3 crl-verify crl.pem client-config-dir /etc/openvpn/ccd[/code]

[quote="Final9mare"]Mar 11 21:20:10 openvpn[6933]: /sbin/ifconfig tun15 10.8.0.2 netmask 255.255.255.0 mtu 1500 broadcast 10.8.0.255 Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 10.8.0.0 255.255.255.0[/quote]It looks like you are running more than one instance of openvpn .. [quote="Final9mare"]Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 192.168.1.0 255.255.255.0[/quote]Your server does not need to be configured with the route for its LAN .. it's already done. Also, [list]NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or [b]192.168.1.x[/b]. Be aware that this might create [b]routing conflicts[/b] if you connect to the VPN server from public locations such as internet cafes that use the same subnet.[/list] :arrow: [u]Never[/u] use 192.168.0.0/24 or 192.168.1.0/24 (or other common subnets) for your OpenVPN Server LAN :!: [list]You are advised to change your server LAN to a more unique [url=http://en.wikipedia.org/wiki/Private_network]RFC1918[/url] compliant subnet. For example: 192.168.143.0/24[/list] Out of curiosity, what version of openvpn is that ?

[quote="Final9mare"] I did not know the server routed the LAN automatically[/quote]It does not .. please read this: [url=http://openvpn.net/index.php/open-source/documentation/howto.html#scope]HOWTO: Expanding the scope of the VPN to include additional machines[/url] Note, the server LAN is handled by the server network stack .. This message:[quote="Final9mare"]Mar 11 21:20:10 openvpn[6933]: [b][i]Ignore conflicted routing rule[/i][/b]: 10.8.0.0 255.255.255.0[/quote]does [b]not[/b] appear in the openvpn 2.3.11 source code, so I am guessing it is something to do with your router. It also, very likely, means you are running two openvpns with [i]that[/i] same subnet.

Okay I understand, I am not routing any LAN on the server side so i don't need the first part of that HOWTO. However I am trying to include the subnet on the client side. I created the ccd file and did the[code] iroute 192.168.1.0 255.255.255.0[/code] and then I add to the server conf [code]route 192.168.1.0 255.255.255.0[/code] and then I also add [code]client-to-client push "route 192.168.1.0 255.255.255.0"[/code] What am I doing wrong? that is not letting my other client which is a phone access the LAN?

[b]Stop[/b] using 192.168.1.0/24 [i]everywhere[/i] :geek:

I think you need to [i]learn[/i] about [i]routing[/i] and so : tincanteksup gmail If anybody else wants to [i]step in[/i] here .. please do.

Ip route conflict

Final9mare

Im not sure why i am getting an ip route conflict when I connect my router to the openvpn

Mar 11 21:20:10 openvpn[6933]: TUN/TAP device tun15 opened
Mar 11 21:20:10 openvpn[6933]: TUN/TAP TX queue length set to 100
Mar 11 21:20:10 openvpn[6933]: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Mar 11 21:20:10 openvpn[6933]: /sbin/ifconfig tun15 10.8.0.2 netmask 255.255.255.0 mtu 1500 broadcast 10.8.0.255
Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 10.8.0.0 255.255.255.0
Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 192.168.1.0 255.255.255.0
Mar 11 21:20:10 openvpn[6933]: Initialization Sequence Completed

my server conf:

port 1194
proto udp
dev tun
sndbuf 0
rcvbuf 0
ca ca.crt
cert server.crt
key server.key
dh dh.pem
tls-auth ta.key 0
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
#push "redirect-gateway def1 bypass-dhcp"
push "route 10.8.0.0 255.255.255.0"
push "route 192.168.1.0 255.255.255.0"
route 192.168.1.0 255.255.255.0
client-to-client
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
keepalive 10 120
cipher AES-256-CBC
comp-lzo
user nobody
group nogroup
persist-key
persist-tun
status openvpn-status.log
verb 3
crl-verify crl.pem
client-config-dir /etc/openvpn/ccd

TinCanTech

Final9mare wroteMar 11 21:20:10 openvpn[6933]: /sbin/ifconfig tun15 10.8.0.2 netmask 255.255.255.0 mtu 1500 broadcast 10.8.0.255
Mar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 10.8.0.0 255.255.255.0

It looks like you are running more than one instance of openvpn ..

Final9mare wroteMar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 192.168.1.0 255.255.255.0

Your server does not need to be configured with the route for its LAN .. it's already done.

Also,

NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.

:arrow: Never use 192.168.0.0/24 or 192.168.1.0/24 (or other common subnets) for your OpenVPN Server LAN :!:

You are advised to change your server LAN to a more unique RFC1918 compliant subnet.
For example: 192.168.143.0/24

Out of curiosity, what version of openvpn is that ?

Final9mare

I understand that using the common subnet is a problem but I am just testing it before I deploy it. I did not know the server routed the LAN automatically. I am still not able to access the LAN from my phone though. The documentation I was reading said I needed to do this. I am at a loss.

The Version is this

 OpenVPN 2.3.11 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 22 2016
library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 2.08
Originally developed by James Yonan
Copyright (C) 2002-2010 OpenVPN Technologies, Inc. <sales@openvpn.net>

TinCanTech

Final9mare wrote I did not know the server routed the LAN automatically

It does not .. please read this:
HOWTO: Expanding the scope of the VPN to include additional machines

Note, the server LAN is handled by the server network stack ..

This message:

Final9mare wroteMar 11 21:20:10 openvpn[6933]: Ignore conflicted routing rule: 10.8.0.0 255.255.255.0

does not appear in the openvpn 2.3.11 source code, so I am guessing it is something to do with your router.

It also, very likely, means you are running two openvpns with that same subnet.

Final9mare

Are you suggesting im running two openvpns on my VPS side?

Final9mare

Okay I understand, I am not routing any LAN on the server side so i don't need the first part of that HOWTO. However I am trying to include the subnet on the client side. I created the ccd file and did the

 iroute 192.168.1.0 255.255.255.0

and then I add to the server conf

route 192.168.1.0 255.255.255.0

and then I also add

client-to-client
push "route 192.168.1.0 255.255.255.0"

What am I doing wrong? that is not letting my other client which is a phone access the LAN?

TinCanTech

Stop using 192.168.1.0/24 everywhere :geek:

Final9mare

I am just following the https://openvpn.net/index.php/open-source/documentation/howto.html#scope instructions for client 🙁

TinCanTech

I think you need to learn about routing and so : tincanteksup <at> gmail

If anybody else wants to step in here .. please do.