Pfsense + VM + OVH IP Failover GW = Set static route with shell, where is conf?

ggsab

Hi, fresh new to Pfsense, I enjoy the webGUI powerfull interface, I use it as a VM in a Esxi OS hosted on OVH, works great only when I set a route and the weird OVH gateway threw the shell:

route add -net x.x.x.254/32 -iface em0

route add default x.x.x.254

Where x.x.x is the subnet of my Esxi host and last for all OVH customers by 254
The issue is that when pfsense is rebooted these root are wiped away
Fixing it by the webGUI won't work and even by creating a /etc/rc.conf with these route command.
So I am looking for the very basic information, does anyone here knows where the route conf file is on a pfsense OS?

Seems not to be /etc/rc.conf like on classic FreeBSD OS

And here some links that may help other OVH users :
http://forum.ovh.co.uk/showthread.php?6507-ESXi-pfSense-and-failover-IP
http://help.ovh.ie/BridgeClient (FreeBSD section)

Thanks

MindfulCoyote

@ggsab:

So I am looking for the very basic information, does anyone here knows where the route conf file is on a pfsense OS?

Are you looking for System: Routing: Routes?

ggsab

Thanks for your reply, in fact adding this weird OVH Gateway threw System:Routing:Routes as you suggest won't work even if record is accepted.
I was looking a way to drop shell line like in /etc/rc.conf. on freebsd to be read at pfsense boot.

Seems I found a way, which is telling again everything's on pfsense should be done via the web interface..

**So after I set my route by SSH as I explained in my previous post:

I logged to my pfsense webGUI
I download the shell package module (menu: system:packages)
Once installed, I set my 2 commands (menu: services:shellcmd) by choosing shellcmd and not earlyshell.**

I already reboot 2 and my routes are kept up in the tables so far…

I'm sure there is another way to do so, or maybe I'm wrong somewhere but I think for now I lost too much time for what's peanuts to save on other systems..
This said Pfsense and I, are speaking the same language! :-D

Thanks btw to people involved there.
And thanks for any coming tricks to deal with weird gateway users like OVH

MindfulCoyote

Excellent. Sorry I wasn't of any assistance. I wonder what the difference was between adding the route in the GUI and the shell.

boiss007

Just so the answer is somewhere, u can put a nice little script in /usr/local/etc/rc.d like

#!/bin/sh
###route.sh : create route on initialisation
/sbin/route add -net xxx.xxx.xxx.254/32 -iface emx
/sbin/route add default xxx.xxx.xxx.254

Didnt invent it, this solution was out there already… on OVH soyoustart forums