To use GRE over IPsec, you need to put IPsec into transport mode – not tunnel mode. It should be possible in the 2.0 GUI (though I haven't tried it yet)

Hi guys,

I am using this system http://www.pcengines.ch/alix2d3.htm

The internal IP is configured on Bridge, LAN and WLAN do not have any IP address…

Here are some config shots... http://db.tt/aV8urfS

I can confirm this error. I have the following setup:

Site 1----------------------- Site 2 |                            | DNS at 192.168.11.123        Site2:Static route to 192.168.11.123 via LAN interface (Goes through IPSec)

I get the same error "A valid gateway must be specified".
Running an older version of pfSense on other hardware does not have this issue.

Non-working version:
2.0-BETA4  (i386)
built on Mon Sep 27 05:13:14 EDT 2010
FreeBSD 8.1-RELEASE-p1

Working (old) version:
2.0-BETA4  (i386)
built on Sun Sep 5 18:43:23 EDT 2010
FreeBSD 8.1-RELEASE

i upgraded from sept 10 snapshot to sept 24 snapshot.
and i can confirm tha it works well:
captive portal is fine
active and passive ftp is fine

the only problem i had, was that i had to recreate my static routes
they were showing up in "System: Static Routes"
but they were not active. just opened one, and clicked "save config"
and they worked again

its been running stable for last 2 days

If it means anything, I have working version of status gateway group. It is cosmetic thing because some major problems still exists.
end of page - http://redmine.pfsense.org/issues/876

fact is that i'm updating nearly every day, but it was a new install of squidguard.
Only packages i installed before were squid and lightsquid. Its not so important, but good to know.

I will test that and give you an answer.

You never need ssh to do that if you know where the logs are, you can use Diagnostics > Command, or Diagnostics > Edit File (and the latter can even browse through the filesystem with a GUI)

I wouldn't do the log clearing with a cron job most of the time, only manually, but I suppose that might be a personal preference.

Thanks for the clarification!!! ;)

It will be nice for futures newbies (like I am) with the same question if you could add this to the description text.

Many more than that are likely to work but just haven't had updated confirmation from those testing them.

Some others have reported similar errors with other packages after doing a factory reset. It may be due to other packages installed on the filesystem already (not pfSense packages, but the FreeBSD type packages). So perhaps looking at what is there with pkg_info and deleting unused packages might help.

There's always a risk that some portion of your configuration could become broken after updating.  One case is that when there are changes to the config.xml layout, sometimes the upgrade code isn't quite correct initially.  You could end up using a snapshot with incomplete configuration upgrade code and your configuration won't just automatically be fixed when updating to a snapshot where the configuration upgrade code is fixed.

Should be on newer snapshots.
Thanks.

Pfsense 2.0 Beta 4 built on Fri Sep 24 14:30:24 EDT 2010 - stable

PM me with your email address if you want to test changes in advance of them being committed to the repository.
Thanks,
GB

@jimp:

FYI- I documented the procedure for 2.0 a week or so ago:

http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall#Configure_a_new_Interface

Hey Jim!

That was exactly the info I needed! Thanks, now it works as expected!

10x for the quick reply.
that was it..

Okay. With this snap it is working. No problems no more…