I am having a similar issue but with a static IP.  I have a multiwan setup with one static cable and one pppoe DSL.  I have the voip traffic all pushing through the static connection.  There are 2 different voip providers I am using.  One has no issues and the other always loses registration overtime and I have to clear the state manually to fix this.  The state always says multiple:multiple and has 2 entries for in/out paths.  I am trying the state timeout to see if it will help me in this scenario. Funny thing is when I push the traffic from that provider out through the pppoe link everything works well but I have no traffic shaper as that has been configured on the static line and there is no multiwan traffic shaper yet.  I need the shaper because calls tend to get choppy when it gets busy otherwise.

I've never tried to do this. I've not seen any instructions anywhere else for doing it. Its a long while since I've done an install so my recollection of the install options might be incorrect. Here are a few different ways I would tackle the problem. If I had two disks I would the two versions to the separate disks, selecting the FreeBSD boot loader. On startup the boot loader gives the option of booting from either disk, defaulting to the one previously used. If I had only one disk I would install the two versions to two different '"slices", selecting the FreeBSD boot loader. On startup, the FreeBSD boot loader gives the option of booting from either slice, defaulting to the one previously used. If I had limited physical access to the system and I had time on my hands I would try either of the above variants but use GRUB as the boot loader. (I seem to recall some recent reports of problems with GRUB as the boot loader but I don't recall the details. I've never used GRUB to boot FreeBSD. I have used GRUB to boot Linux systems.) GRUB would probably be better suited to unattended operation than the FreeBSD boot loader in that you can specify a default kernel in the GRUB configuration file and the default is unchanged by booting a non-default kernel. Thus you could make (for example) version 1.2.3 the default and version 2.0 as an option. Then if you boot version 2.0 and the system reboots it should boot version 1.2.3. I don't know if there is a way to get the FreeBSD boot loader to forget what was last booted. But this would probably not be an issue if you planned to run version 2.0 only while you are in attendance.

your question gave me the answer. i stopped squid and it went away. but i still don't understand why it's communicating with itself.

There's a search feature.  How about you use it? http://forum.pfsense.org/index.php/topic,7233.0.html

That fixed it!  Thanks for the help!

pfSense 1.2.3 is based on FreeBSD 7.1 so (generally) has newer drivers than pfSense 1.2.2 which is based on FreeBSD 7.0. Earlier versions of pfSense are based on 6 series FreeBSD. The developers say pfSense 1.2.3 should be considered "production ready" - see http://blog.pfsense.org/?p=377.

Nope, there isn't anything like that in pfSense.

After playing around with it a bit more, it seems like only one port was bad.  The three dedicated to VLAN 2 worked fine, the three dedicated to VLAN 3 worked fine, and the second for VLAN 1 worked fine.  The first port for VLAN 1, on the other hand, seems to be broadcasting traffic on all three.  That's what I get for spending three times as much for a single switch that supports VLANs over a pair of cheap ones that don't but would have been physically segregated…

Hi all (specially sullrich), Is there any way to begin working on the translation without using the POOTLE ?. An XML file, ASCII file, CSV file ??? Would be very glad to begin working on it, to translate PFSense to spanish (from Spain) …. ;) Perhaps some other friends from America could use my translation to adapt it to other "flavours" of the spanish language used on America. Regards Jose

Hey pachini, There are many posts describing how to do this function.  Since I'm not sure exactly what you are tring to achieve, I'll give you a general brief run through.  Under the interfaces tab, select the interface you want to bridge to another interface.  So, if you wanted to bridge the servers interface to the lan interface, go to the servers interface and select "bridge with: lan".  That interface will not need an ipaddress and will gray out the appropriate boxes. Once this is complete, you will need to set up rules to allow the interfaces to talk to one another.  You can limit the traffic to only DHCP only or you can completely open up the communication between the interfaces or choose something in between.  If you want the two interfaces to act like a switch, open up the the firewall between the two interfaces.  Go to the firewall tab and select rules.  under the LAN tab, you will see a single rule (unless you modified it).  there will be a plus button that will say "add a rule based on this one" when you hover your mouse over it.  this is the rule that allows your LAN traffic to access the wan or any other interface.  click that plus button.  on the page that comes up, change the source tab from LAN subnet to servers subnet or what ever you see fit.  If you want a more restrictive, give me a reply and ill tell you how to do DHCP only rule. note: pfsense 2.0 handles bridging a bit differently.  There is a bridging tab under assign interface tab to setup the bridge. EDIT:  Here is a good post on how to pass dhcp between bridges.  http://forum.pfsense.org/index.php/topic,13351.0.html Good luck, -V