OpenVPN routing

[Ryan Coleman]

Also:
[root at nbserver1 /usr/home/ryanc]# ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:14:22:15:dc:65
        inet 192.168.46.2 netmask 0xffffff00 broadcast 192.168.46.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether 00:bd:7e:86:1d:00
        inet 192.168.47.1 netmask 0xffffff00 broadcast 192.168.47.255
        Opened by PID 10341
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 46:e1:75:c6:a3:a7
        inet 192.168.47.254 netmask 0xffffff00 broadcast 192.168.47.255
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 5 priority 128 path cost 2000000
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000


On Apr 25, 2011, at 9:36 PM, Ryan Coleman wrote:

> I've got an OpenVPN connection working to my remote server, but I want to route the traffic to the local LAN.
> 
> I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2) from the remote machine.
> 
> Server.conf:
> local 192.168.46.2
> port 1194
> proto udp
> dev tap
> ca keys/cacert.pem
> cert keys/server.crt
> key keys/server.key # This file should be kept secret
> dh keys/dh1024.pem
> # Don't put this in the keys directory unless user nobody can read it
> crl-verify keys/crl.pem
> #Make sure this is your tunnel address pool
> server 192.168.47.0 255.255.255.0
> ifconfig-pool-persist ipp.txt
> #This is the route to push to the client, add more if necessary
> #push "route 192.168.46.254 255.255.255.0"
> push "route 192.168.47.0 255.255.255.0"
> push "dhcp-option DNS 192.168.45.10"
> keepalive 10 120
> cipher BF-CBC #Blowfish encryption
> comp-lzo
> #fragment
> user nobody
> group nobody
> persist-key
> persist-tun
> status openvpn-status.log
> verb 6
> mute 5
> 
> 
> client.conf: 
> #Begin client.conf
> client
> dev tap
> proto udp
> remote sub.domain.ltd 1194
> nobind
> user nobody
> group nobody
> persist-key
> persist-tun
> #crl-verify
> #remote-cert-tls server
> ca keys/cacert.pem
> cert keys/ryanc.crt
> key keys/ryanc.key
> cipher BF-CBC
> comp-lzo
> verb 3
> mute 20
> 
> Any ideas?  As I said, I can talk to the remote server, but not the local LAN.
> 
> To throw a new curveball in the mix, I'd like to talk to 192.168.45.0/24 - which we have another VPN connecting the two networks (not running on a VPN I can do much with).
> 
> 
> Thanks,
> Ryan_______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"