Yes, the different alias types are sometimes a little bit confusing. :)

The documentation on bridging is a little sparse. Especially for 2.0.X where bridging changed somewhat. http://doc.pfsense.org/index.php/Interface_Bridges It is my understanding that your second description is the correct way to bridge interfaces in 2.0. However if it's working for you….  ;) If you do reconfigure your interfaces as described it's worth noting that since you can now assign a bridge interface, like any other, you can choose to have firewall filtering either on the bridge interface itself or on the member interfaces. By default filtering is on the member interfaces which is suitable for a transparent firewall for example. However if you wish to bridge interfaces simply as a convenient way of connecting network segments, to connect a wifi AP say, then you can filter on the bridge interface instead. To do this you need to change two values in: System: Advanced: System Tunables: net.link.bridge.pfil_member and net.link.bridge.pfil_bridge. This is as I understand it from my own testing and reading other posts but I'd love to hear from one of the developers on this. Steve

@Nonsense: Could the lack of being able to be pinged cause my central office DSLAM to drop my connection? I have never encountered that but it is conceivable. There are many threads here about pppoe problems unfortunately. I have never had any trouble though. I can't see anything in your log that looks unusual (not that I am any sort of expert!) other than the connection gateway being in a private subnet. Steve

Thanks for your replies Steve, thats great info. I will give it a go soon!

This logging is all to ram only unless you have setup something different so I wouldn't worry about your disk. You can set the rekeying interval to something higher if you wish. There is some trade off in security. I have Key Rotation set to 3600 and Master Key Regeneration set to 7200. Steve

You're probably looking to do it in the wrong place. Unless you have something like Squid setup where the firewall actually initiates traffic, the firewall has no control of that, has to be done on the actual source device.

Yes it should be in 2.1. Not sure what else there would be to "update" this - it was fixed in our repo (as I mentioned before) so it would be fixed in the next release.

@wetfish: Is there a way I can fix this please? Thanks in advance. @sammy2ooo: Same happens here on 2.0.1-RELEASE (i386). Resetting the RRD graphs did not help… Nothing to fix, or to worry about, check this: http://redmine.pfsense.org/issues/1399

@chpalmer: The GUI will sometimes pause if there is no WAN active. You may just need to wait. Your MLPPP is still not configured correctly.   You need to look at my examples and make yours like that. my WAN is active, but I always can't edit any  /interfaces_ppps.php and /interfaces_ppps_edit.php?id=2.  when I click edit its, pfsense server will dead. So How I do like you ?

It depends on the status of the box (full install vs NanoBSD, etc) but in general that works OK. Read the upgrade guide on the wiki. Be sure to check the config as suggested there. I have done remote upgrades on even NanoBSD installs using console upgrade by URL that went from 1.2.3-RC1 up to 2.0.1-RELEASE without issues.

http://doc.pfsense.org/index.php/I_locked_myself_out_of_the_WebGUI,_help!

SOLVED SOLVED SOLVED quick answer: disable ACPI on boot choosing option 2! Later follow http://doc.pfsense.org/index.php/Booting_Options#Disabling_ACPI to make it permanent. long history: I was having another problems with that machine… and it was not production yet... so I started to debug. I was worried about how slow it was! I was worried about error messages about timeout and missing interrupts on NICs. I was worried about PPPoE do not work JUST FOR ME ... and I REALLLY WANNA TO HAVE PPPoE to avoid double NAT! So I started to change settings / replace items! I replate 2 NICs twice I replace all CABLES involved I replace ADSL modem nothing helps. I choose DHCP to WAN and discovered my future pfSense2 firewall was taking 1 minute to get an IP from modem... on a direct connection. So... should be something on machine...not in pfS2, not in other HW (NIC, cable, modem). With that information was easy...  my first tought was to disable ACPI... a long history of problems with it (never one had included this sintoms!) in just one minute I was a HAPPY user! Now I'll SCREAM this in ANY forum I can find SOMEONE with PPPoE problem... it's a simple and quick test!!!

A search of the forums for alc0 found a couple of topics which suggest the alc driver is built in the kernel. See, for example, http://forum.pfsense.org/index.php/topic,30729.0.html which demonstrates the alc driver was built into a 2.0 snapshot kernel. Please provide the output of the pfSense command``` dmesg ; pciconf -l

I have exactly the same problem with the AVAYA phone and pfsense. Was anyone able to fix this?

When I setup WAN2, should I set the load balancer? I have read several

actualyl i seem to be having a more serious issue i can't connect to my webserver on WAN, but others can. For my 2nd modem which is also accessible I can access that one to my webserver, and others can see it. I did not always have this issue, it seems brand new. I don't see where it could have come from. What's strange is that my 2nd modem works just fine.

You can also try negotiate mode instead of ntlm http://wiki.squid-cache.org/ConfigExamples/Authenticate/WindowsActiveDirectory