OpenVPN Client : ERROR: FreeBSD route add command failed: external program …..

ericab

Previously running a build from Sunday, the 20th of march (3 days old), today updated to:
2.0-RC1 (i386)
built on Wed Mar 23 09:48:32 EDT 2011

my lan traffic no longer routes through my vpn gateway.
the client successfully establishes a link, but;
the OpenVPN log is loaded up with this error:

openvpn[17289]: ERROR: FreeBSD route add command failed: external program exited with error status: 1

ericab

bump ???

anyone else experiencing this problem ?

eri--

You have your openvpn assigned?

ericab

assigned ?
could you be more specific ?
ive got the client assigned to the WAN

ericab

im going to move back to the march 20th snapshot;
if anyone knows how to fix this please give me a hand here :-\

ericab

ive downgraded to the "pfSense-Full-Update-2.0-RC1-i386-20110320-0050" snap

and everything works once again.

ive gone through the bugtracker activity and cant seem to find the cause, but its somewhere within March 21st, and March 23rd.

-eric

ericab

is this really of no interest to the developers ?

cmb

@ericab:

is this really of no interest to the developers ?

Sure if you can provide more detailed info than it it being within March 21 to 23, nothing even remotely close to being related to that has changed in that period. If there were any widespread issue with OpenVPN and routes we would have seen it long ago and you wouldn't be the only one reporting it.

The only time I've ever seen route errors is when you incorrectly have static routes defined that overlap with routes from OpenVPN.

ericab

alright fair enough.

but i must say, going from the release on the 20th to the 23rd, i had made absolutley no changes to the configuration.
im going to go ahead and update to todays release, the 29th, and report back with more details.

ericab

@cmb:

@ericab:

is this really of no interest to the developers ?

Sure if you can provide more detailed info than it it being within March 21 to 23, nothing even remotely close to being related to that has changed in that period. If there were any widespread issue with OpenVPN and routes we would have seen it long ago and you wouldn't be the only one reporting it.

The only time I've ever seen route errors is when you incorrectly have static routes defined that overlap with routes from OpenVPN.

cmb;

ive moved on to todays snapshot
2.0-RC1 (i386)
built on Tue Mar 29 13:39:02 EDT 2011

and it has happened again.

again, moved back to the
march 20th snapshot
and everything works once again.

might be able to PM you with the openvpn status log so you can see the details privately ?
id rather not post it here publicly.

ericab

CMB

this broke it:

https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/bf87b4d7d1e9c0064e59727afd7601c111f6f3da

eri--

Can you try latest snapshots.
There were fixes in that section which would possibly fix even the reported issue.

ericab

hi ermal;

i forgot to update this post. someone else was experiencing the same issue so we worked it out on another thread with jimp:

http://forum.pfsense.org/index.php/topic,35024.0.html