Bug #1889
closed
"route change" doesn't work (after commit:fb85533d)
0%
Description
It seems that fb85533d (or related ones) breaks my pfSense. When I add a static route (even the default route), I have this error :
php: /interfaces.php: The command '/sbin/route change -inet default '172.16.16.1'' returned exit code '1', the output was 'route: writing to routing socket: No such process change net default: gateway 172.16.16.1: not in table'
The correct action should be "add" (it works if I type it in the console).
Thanks
Updated by Thomas NOEL over 12 years ago
Also, revert fb85533d54d4ad2dfcbda5a7b0b8007b5e4eac43 fix the bug.
Updated by Thomas NOEL over 12 years ago
Oups, the correct URL of the problematic commit is :
https://github.com/bsdperimeter/pfsense/commit/fb85533d54d4ad2dfcbda5a7b0b8007b5e4eac43
Updated by Ermal Luçi over 12 years ago
- Status changed from New to Feedback
I am not sure what is your 'pfSense' referring to but you need to upgrade fully your installation to latest 2.0-RELEASE and it works.
Updated by Seth Mos over 12 years ago
To clarify further, the newer route binary we use in pfSense somewhere around RC3 also adds routes when specifying the "change" command. Clearly you gitsynced 2.0 with older binaries.
Updated by Thomas NOEL over 12 years ago
Ermal Luçi wrote:
I am not sure what is your 'pfSense' referring to but you
need to upgrade fully your installation to latest 2.0-RELEASE and it works.
Ok, I see : https://github.com/bsdperimeter/pfsense-tools/commit/769f677050a58e08d041505b5417ddb
I build my own pfSense without always update binaries. My fault.
Sorry for the noise... :(
Updated by Seth Mos over 12 years ago
- Status changed from Feedback to Rejected
Please don't file tickets on pfSense when you are also modifying it.
Updated by