Date: Mon, 20 May 2013 16:54:28 -0400 From: Andre Goree <andre@drenet.net> To: freebsd-questions@freebsd.org Subject: Re: route problem Message-ID: <4a61bfe6346c98bdc46bf45798d55d6e@drenet.net> In-Reply-To: <519A8546.4090109@fuckaround.org> References: <519A8074.7070107@fuckaround.org> <d912f05d46dc64a4da29b9bc622b96d8@drenet.net> <519A8546.4090109@fuckaround.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-05-20 4:19 pm, Pol Hallen wrote: > Try: > route add 192.168.1.0/24 192.168.2.250 > > does not run :-( > > Pol Interesting. I had a similar issue I got around with a similar route addition, though I was going from a LAN PC through my server that was running openvpn out to a remotely connected client. What was the error that the route command failed with? I could have the syntax wrong (may need a "-net" in there), but I'm sure I used almost the exact same thing to solve my issue -- in my case, I ran 'route add 10.0.1.0/24 10.0.0.98', where '10.0.1.0/24' is the openvpn client network and '10.0.0.98' is the LAN interface of the openvpn server. If you don't mind could you post the output of ifconfig from both boxes? -- Andre Goree -=-=-=-=-=- Email - andre@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4a61bfe6346c98bdc46bf45798d55d6e>