Without a lot more information, it is impossible to tell what you might be encountering.

To get back in, try some of the suggestions here:

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

@GuzmanDiaz18:

¿But this can have some solution?

Yes but the solution depends on the cause. My previous questions were to help me better understand your configuration and so be better placed to suggest an appropriate solution.

I have been running pfSense 1.2.3 for some time and could not be happier with the product. I recently built a second box with a fresh install of pfSense 1.2.3, in order to play with Freeswitch. Unfortunately, I have run into the same dilemma that sdudley experienced, "When starting the vhosts service it indicates at the top of the window that the service has been started however, viewing the LigHTTPD web server service status shows it to be stopped." I have removed both packages (Freeswitch and vHosts) and reinstalled them, but no change. I have completely populated the vHosts settings tab, but still no joy.

Thanks in advance for any suggestions!

Installed packages:
Freeswitch
vHosts

Mostly, you can do what you want with pfSense.

*) Splitting the bandwidth:  traffic shaper

*) Monitoring content: yes, packages available to do that

*) Who's accessing what tied to Active Directory:  I don't think so.

*) Wifi via MAC address: MAC addresses are trivial to change, so access via MAC address is about as effective a security strategy as posting signs saying "Please don't hack me"

*) Other Wifi stuff: Yeah, you can do Radius authentication to an Active Directory

*) PCAnywhere from out in the Internet - yes, you'll probably want to look at OpenVPN

For more details, RTFM.  (Or spend some time reading the individual tech forums (EG: OpenVPN, Traffic Shaper, etc)

Good luck.

nice one  ;D

|      PPoE pfSense DHCP  Snort        |
–----------------------------------
      LAN        OPT1        OPT2
        |            |            |
        |          VOIP          |
    switch                    switch   
    |    |                    |      |
  PCs WiFi              WWW  DNS

1. pfSense's DHCP server uses clients MACs for assigning IPs (usefull for wake up on lan also)
2. All servers and clients are using OPT2 DNS (bind9's views)
3. Snort uses different rules for each interface.

Just been following the logic to join services with similar security risks on the same interface.
Possibilities are unlimited ... but common sense will give you the right setup.

This sounds like a timeout of the DNS query.
I would configure the DNS on the pfSense fix to 208.67.222.222 and 208.67.220.220 and uncheck the "allow DNS to be overwritten by DHCP on the WAN".
Then set your clients all to use pfSense as DNS server.

Thank Perry for the answer.

If I add a line to the OLSR PHP file, it will chang de config.xml file for something like this.

<olsrd><config><enable>on</enable>
<enablelqe>2</enablelqe>
<iface_array>lan,wan</iface_array>
<enablehttpinfo>on</enablehttpinfo>
<port>8117</port>
<allowedhttpinfohost><allowedhttpinfosubnet><enabledyngw><enableannounce><announcedynamicroute>10.5.200.232/29</announcedynamicroute>
<ping><polling><enabledsecure><securekey><linkqualitymult>192.168.10.7 0.10</linkqualitymult></securekey></enabledsecure></polling></ping></enableannounce></enabledyngw></allowedhttpinfosubnet></allowedhttpinfohost></config></olsrd>

but when PF will creat is oslr.conf file from this file, it will not know what to do with the <linkqualitymult>option and it will probabely result in a error. I would also need to add somewhere that the option <linkqualitymult>mean that it have to write LinkQualMult = "text box" and also cheak if the text box have a valid IP adresse and multiplicator.

Somebody know how I can add this or show me a howto of how script are built from config.xml ?</linkqualitymult></linkqualitymult>

This is, admittedly, an easier approach but its not without its downsides.  Bridge filtering isn't supported by CARP so if you need to do a CARP firewall cluster because you have an HA requirement for your network, then bridging isn't going to work.  Its really about your needs, pick the solution that fits yours best.

pfSense 1.2.3 is based on FreeBSD 7.2 which provides the operating system including device drivers. See http://www.freebsd.org/releases/7.2R/hardware.html for list of supported devices including wireless chipsets. The corresponding information for pfSense 2.0 BETA (based on FreeBSD 8.0) is at http://www.freebsd.org/releases/8.0R/hardware.html

also resetting my router during my pfense installation may have activated this feature from my isp as well

Yes, other settings that particular brand and model might have.

If you keep all incoming ports closed, nothing can get in that way regardless.

If something (virus, etc) gets in, it's because a PC on your LAN downloaded it or let it in, which is a completely different problem.

This minimum length still is true if you have a hub somewhere.
The collision detection cannot work if the cable is too short.
I think the exact value for the length is somewhere in the CSMA/CD standard.
Wiki has a short notice to this too: http://en.wikipedia.org/wiki/Ethernet_physical_layer#Ethernet_minimum_cable_lengths

But with current equipment you will have to look very hard to find a situation where a colission is possible.
As long as you dont use hubs (or rings even) you wont have problems with the minimum cable length.