How to make OpenVPN to push for more routes to the client?

I’ve managed to get an OpenVPN (ovpn) tunnel going between Fedora 17 and ROS v5.24, but the ROS is pushing only one route to the client side. I wonder how someone shall get the whole routing table to propagate over that tunnel? Currently I just add those routes by hand after the tunnel is up and running, but surely there is more elegant ways to accomplish that.

Sun May 12 23:32:55 2013 [A-VPN] Peer Connection Initiated with 1.2.3.4:1194
Sun May 12 23:32:58 2013 SENT CONTROL [A-VPN]: 'PUSH_REQUEST' (status=1)
Sun May 12 23:33:03 2013 SENT CONTROL [A-VPN]: 'PUSH_REQUEST' (status=1)
Sun May 12 23:33:09 2013 SENT CONTROL [A-VPN]: 'PUSH_REQUEST' (status=1)
Sun May 12 23:33:09 2013 PUSH: Received control message: 'PUSH_REPLY,route 192.168.255.0 255.255.255.248,ifconfig 192.168.255.4 192.168.255.1'
Sun May 12 23:33:09 2013 OPTIONS IMPORT: --ifconfig/up options modified
Sun May 12 23:33:09 2013 OPTIONS IMPORT: route options modified
Sun May 12 23:33:09 2013 ROUTE default_gateway=192.168.100.1
Sun May 12 23:33:09 2013 TUN/TAP device tun0 opened
Sun May 12 23:33:09 2013 TUN/TAP TX queue length set to 100
Sun May 12 23:33:09 2013 /sbin/ip link set dev tun0 up mtu 1500
Sun May 12 23:33:09 2013 /sbin/ip addr add dev tun0 local 192.168.255.4 peer 192.168.255.1
Sun May 12 23:33:09 2013 /sbin/ip route add 192.168.255.0/29 via 192.168.255.1
Sun May 12 23:33:09 2013 Initialization Sequence Completed

Ideally that route pushing should be routing table based, but I am fine by getting it to push over an arbitrary routes.

Obviously that functionality is not implemented and the ROS OpenVPN support is limited by design. I’ve yet to read any reason why.