@onhel:

It should also be noted if you are using gitsync in your updater settings to change branch name from master to RELENG_2_0

Unless you are using that to track IPv6, in which case you really do want master. :-)

I wasn't aware anyone was tracking 2.0 on top of 2.0 with gitsync, not much of a point to that. Might hurt more than it helps in some cases, but that's debatable.

The system crashed again with a kernel page fault at the same PC. Despite having set debug.ddb.textdump.pending=1 it didn't reboot automatically so Ityped in the commands in kdb.enter.panic one per line and then on reboot savecore reported it was writing textdump.tar.

This system has a VIA C3 CPU and is running

dmesg

Copyright © 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-RELEASE-p2 #1: Mon Apr 18 23:21:20 EDT 2011
    sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: VIA Samuel 2 (797.74-MHz 686-class CPU)
  Origin = "CentaurHauls"  Id = 0x673  Family = 6  Model = 7  Stepping = 3
  Features=0x803035 <fpu,de,tsc,msr,mtrr,pge,mmx>real memory  = 268435456 (256 MB)</fpu,de,tsc,msr,mtrr,pge,mmx>

I'll switch to a debug kernel as suggested.

Since you can traceroute correctly from the shell it's not the routing table or the default gateway… this is more likely an issue with your firewall rules, including the floating rules used by the traffic shaper. Be sure no rule specifies a gateway directly and uses the 'default' gateway which uses the routing table. Beyond that it might be your NAT setup (especially manual outbound NAT).

@arriflex:

Much of what is mentioned here is not necessary as the OpenVPN:Wizard gets much of it accomplished.

Yeah this was written before that wizard existed.

@fastcon68:

I used the blog steps and it worked.  But it was not quite what I was trying to do.  In version 1.2.3, I could bridge ports to a existing port.  Version 2 is quite different it takes a little more planning before you just jump in.

The other version made it just a little bit easier to set up and be able to add and subtract ports.
RC

You can still bridge ports together by just adding them to the bridge, you don't have to assign the bridge interface. It's just better in the long run to do it that way.

The main problem with failing to assign the bridge interface is that if the interface holding the IP goes down, the whole bridge goes down. When you have the bridge assigned and the IP on the bridge interface, any interface can go down without problems.

You should now be able to build gateway groups easy with dynamic interfaces.

The status gateways page, and status gateways groups page should list your dynamic interfaces.
A gateways widget is also available.

Feedback is sought here.