From Secure Computing Wiki
Revision as of 02:29, 17 August 2008 by Krzee (talk | contribs) (Multiple Lans: route, push route, iroute)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

here is an example from ##OpenVPN on freenode.

The user had the following in his server.conf:

push "route" route route route route route route client-to-client

The push route means that he is telling his server to let ALL clients to know about the fact that they should add an entry in their routing table to route through their vpn. That is because is a LAN behind his VPN server, which the clients should be able to communicate with.

The route entries are telling his server to add a route for each of .1.0 .3.0 .4.0 .5.0 .6.0 7.0 to its kernel's routing table, which should go through the tunnel interface. The server's kernel now has an entry for 6 LANs to all go through the vpn interface, but when that happens how will openvpn know what client to send each network to? The answer is iroute!

Iroute does not bypass or alter the kernel's routing table, it allows openvpn to know it should handle the routing when the kernel points to it but the network is not one that openvpn knows about. The Iroute entry tells the openvpn server which client is responsible for the network. Without the iroute entry you will find the following in your logfiles:

MULTI: bad source address from client [IP ADDRESS], packet dropped

The thing is, we cant just drop the iroute into server.conf because it would then be used for every client, and iroute is only to tell the server at which client it should send traffic destined for a network that the kernel said should go to the openvpn interface. That is why we add the iroute commands to a ccd entry.

You will need client-config-dir ccd/ in your server config file to enable ccd entries. ccd entries are basically included into server.conf, but only for the specified client. You put commands in ccd/client-common-name, and they are only included when the client's common-name matches the name of the file in ccd/.

In this example lets assume the client owning the network 1.0 has a common-name of client1. In ccd/client1 He should have the following:


But our user also wants client-to-client to work, so lets say he also wants the LANs behind those clients to be able to communicate. In ccd/client1 we add some more entries... now it would look like this:

iroute push "route" push "route" push "route" push "route" push "route"

As you can see, each client our user has will have a ccd/ entry including an iroute for the network behind the client, and pushed routes for all networks behind other clients.