Looks like there is an error on that code then, it works if I run it slightly modified on the command line but not from php, seems to be various bits escaping that \n that trip it up, it needs to be \n to sed, but it's getting escaped to \n when executed.

There are references to the gateway in the rules, and likely the states, but I had thought when PPPoE disconnected it killed all states to the old gateway.

@jimp:

Best way is to use remote syslog to push them off to another system where they can be kept indefinitely.

There isn't a really good way to not clear them and also ensure that the log files are properly formatted at bootup (or there may be but nobody has had time to dig into that)

So it's not a trivial matter to just pick up where it left off?  Dang.

So it seems that on the gui part, all is setup correctly?
But If I connect to the pfsense box, it seems that OPT1( vlan 100 on em1) is still configured as the LAN interface.
I can't use the 'assigned interface' option because it asks me to reconfigure all the vlan and interfaces.

*** Welcome to pfSense 2.0-RELEASE-pfSense (i386) on 2idf00 ***   WAN (wan)                -> pppoe0    -> 1.1.1.1 (PPPoE)   OPT1 (lan)                -> em1_vlan100 -> NONE   WIFI (opt1)              -> ath0_wlan1 -> NONE   VLAN200 (opt2)            -> em1_vlan200 -> 192.168.2.1   VPN1 (opt3)              -> ovpns2    -> 10.0.1.1   DSL (opt4)                -> em0        -> 192.168.3.2   DMZ (opt5)                -> em1_vlan5  -> 192.168.5.1   LAN (opt6)                -> bridge0    -> 192.168.1.1 0) Logout (SSH only)                  8) Shell 1) Assign Interfaces                  9) pfTop 2) Set interface(s) IP address      10) Filter Logs 3) Reset webConfigurator password    11) Restart webConfigurator 4) Reset to factory defaults        12) pfSense Developer Shell 5) Reboot system                    13) Upgrade from console 6) Halt system                      14) Disable Secure Shell (sshd) 7) Ping host

On the synology servers a normal linux is installed.
Install syslog on it and configure the pfSense to send all logs to your syslog-server (Status –> Systemlogs --> Settings).

Since the DS111 is an ARM based system you might have to compile the syslog server yourself.

Thanks jimp for your update  :)

Ok, no problem, i just change the Timezone to America/Asuncion  now my FW has moved to Paraguay : :D

Thanks Jimp for your time

yeah I saw your post about having updated your builds in ipv6 section – and when I get home prob update mine to that build.  Prob no issues and could kick it off remote, but since I vpn into my home network from work and kind of need to get work stuff done with stupid firewall rules they have here I can wait til local to update ;)

Just looking forward to the freebsd 9 builds and actual section for 2.1 I guess..

Currently everything I am doing is working great on my build, but I like to run bleeding edge and help find issues when I can, etc.

The static entries have to be changed under the DHCP Server page. Old normal leases in the database can't be deleted if the mac address is still online as it thinks they're still active.

You may be better off stopping the DHCP service, then rm /var/dhcpd/var/db/dhcpd.leases*, then start it again and just let it redo the whole db.

looks like the link didn't copy/paste right, it shouldn't have http :// in front of it for an FTP link. But it can be accessed via HTTP, just needs a slightly different URL.

Plus FreeBSD moved the packages off to its ftp archive…

So try:

pkg_add -r http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/Latest/pound.tbz

Possible, sure, but not easy. There isn't any code that would make that happen, but the necessary bits are on the box… there is an e-mail library, and the ability to add cron jobs.

I wouldn't recommend sending your config via e-mail in plain text though, especially if it contains anything sensitive.

There are many backup scenarios in the book and also on the doc wiki.

Free RAM is wasted RAM. If the system is just using it for caching and whatnot, that's better than letting it sit empty.

Run top -SH for a bit and see what the memory breakdown looks like there.

That is an artificial limit in the GUI, largely since high numbers haven't been thoroughly tested/vetted.

You can either edit the value in the config.xml directly to be larger and then reboot, or edit the page so it draws many more numbers to choose from. (or change it to a text entry field).

When you have it set to TCP it just tries to connect to the port, it doesn't check that a response is proper, only that a connection can be established.

That may be one of the modems that requires an "eject" command to happen before it triggers into modem mode. Google around for references to cdcontrol or eject with 3g on pfsense and you should hit on some other people who have worked around that.

The interface counters are obtained via pf now, did you perhaps disable pf for some reason?

@DesertPanther:

Should I use the 32 or 64 bit of pfSense? I want to make use of all the hardware that I have.

To use more than about 3.GB to 3.5GB of RAM you should use the 64 bit version of pfSense.

@DesertPanther:

Also is the current version of pfSense based on FreeBSD 8.2?

No, FreeBSD 8.1.

This sounds like it might be applicable to your situation:

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

Did you ever confirm/resolve this?

I'm having the same problem and my <20KB/day of syslog entries under 1.2.3 has blown out to ~150KB/day with these entries.

Thanks