@darkcrucible: It might also be the outbound NAT. Do you use automatic outbound nat or manual? If it's manual then you'll need to add a rule for the other network to go through NAT. If it's automatic then you might need to switch to manual. Not too sure since I've never really used automatic. Aha! Thank you so much for that suggestions! I just enabled manual outbound NAT on the remote server (the one I would like to route all of my youtube traffic through, and added a rule to pass all traffic from 192.168.1.0/24). Thank you!

Solved my own issue with a little accidental help from marvosa In the client file on ubuntu, near bottom placed: route 10.0.0.0 255.255.255.0  (substituted my LAN Subnet) I haven't ever seen a good fix for this anywhere, but this is so simple.  Why didn't I do earlier (pfsense needs a facepalm icon) :-[ keywords added for web searches: ubuntu linux mint pfsense openvpn can't access LAN TUN client

Assuming you've setup the HQ as the server and the Satellite as the client, you need to add a route(s) to the HQ config to define the client subnet(s) ie: route 10.0.0.0 255.255.255.0 route 10.0.1.0 255.255.255.0       ….. etc.  Need to be added to the server config. The 'push "route....' lines on the server side send the appropriate routes for the client to understand the server's subnets. You don't need any 'push "route...' lines on the client side. If you post a screenshot of your server and client configs, you may get more specific help on your setup

I thought this was going to be more difficult.  Turned out I had my SIP client settings field populated with the wrong authorization number, that would do it.  It also required the SIP client "force address" setting match the PfSense LanGW IP given the OpenVpn tunnel via Wan. Happy days…

https://forum.openwrt.org/viewtopic.php?id=33678 Its not pfsense but it is seeming to sort of be what you want to know.

If you are going to run a SIP server, remember to forward port 5060 OK?  I read some places it helps.

Reinstalling the package worked. I have no idea why it didn't grab the package during the upgrade. anyway thanks guys! life savers. :)

I provide the IP of my DNS forwarder (The LAN IP in my case) because I force all traffic through the client.

Ok my fault. I was talking about 800kb/s throughput when running openvpn on the dd-wrt router. I tought this was clear due to the advice in the previous post. Thats why i want to use the ubuntu-server.

i installed certificates, but there are some config lines , namely nobind auth-retry nointeract tls-client ns-cert-type server keepalive 10 30 tls-cipher TLSv1:!ADH:!SSLv2:!NULL:!EXPORT:!DES:!LOW:!MEDIUM:@STRENGTH persist-key persist-tun tun-mtu 1500 mssfix passtos verb 3 which i paste in "Advanced" section in https://192.168.1.1/vpn_openvpn_client.php?act=new but it still dont work, any ideas? why i cannot just upload .conf to config directly?

Sounds like you have it all worked out then.  :D

Thank you phil.davis, that's exactly what I did. Everything is working now.

@kejianshi: Yeah - Does Win7 sell an upgrade pack to upgrade from Win8 up to Win7?  I'm pretty sure lots would buy it. ;) Actually it's included with Pro and Enterprise. Just not the media, but many resellers already sell laptops preupgraded to W7 with W8 license.  ;D :D

Yes, a graphical representation of your network (also unmask all the private subnets), e.g. here's a simple one for my home network: Internet -> PFsense (192.168.50.1/24) -> switch -> LAN Once we get your network map maybe we'll have a clearer picture, but just a couple things that look weird: Your config says your WAN IP on PFsense is 192.168.17.107, but then you go on to push DNS on the WAN subnet, which doesn't make sense.  (I'm guessing you want something on the 14.x side, since that's what you are routing thru the tunnel) Post a network map, so we can troubleshoot further.  Also, make sure your firewall rules (openvpn tab) are any/any for now.

@jg3: The LAN host here, is 1:1 NAT'ed behind a public IP (not the firewall's).    That's the only thing I can imagine is problematic, but I'm not sure how to pinpoint / fix it. Fixed!  Thanks for the help johnpoz, your questions set me in the right direction (finally). I disabled a 1:1 NAT rule I had created that applied to the LAN host on the OpenVPN interface and now the LAN machine can reach the VPN clients.  Great. I had implemented this rule to cover a corner case of no-split VPN clients needing NAT reflection, discussed here: http://forum.pfsense.org/index.php/topic,65793.msg359377.html