Ohh okI didn't realise that it grabed the details from the traffic shaper. I did notice that the interfaces page show the nic speed.

The embedded image forwards the console output to the serial port. If you are using a monitor your not going to see anything after it starts to load freebsd.

Your bootime is related to hardwarespeed and/or wan setting. If you have DHCP at WAN and it doesn'T get a lease right away it might take a bit longer for example.

pfSense's loadbalancer is roundrobin every new connection to the next gateway in the pool. If it doesn't do this it's not configured properly. See http://wiki.pfsense.com/wikka.php?wakka=OutgoingLoadBalancing .

could do i got confused with scott lat time i tryed to do it though will post the diff
again anyway

If /tmp/config.cache exists, it is read otherwise /cf/conf/config.xml

Update:  It turns out that after I updated my onboard NIC drivers to the most current version this version allows you to set the wake-up type (after enabling WOL in APM for the NIC, which is also a setting through this driver) to several different things, one of which was magic packet. Now all is well. Thanks fly out to squarepusher for putting me on to the idea of multiple events triggering a WOL scenario.

I bet this $280 NIC will WOL and then some more…and for that much it better wake me from bed, too.

http://killernic.com/KillerNic/

Make sure you have the ftp helper enabled at the interface where your client is behind.

Seems like this is your gym room as well, eh?

Anyway we really should setup gallery2 to be used as a pfSense Machine Gallery. There we could also provide pfSense screen shots.

Regards
Daniel S. Haischt

Not in 1.0.  Code exists to allow this to work in -HEAD and will appear for 2.0.

SSH is disabled by default anyway…

pfSense can do natreflection to make your forwarded services available by their public IP for the internal clients. Just enable it at system>advanced (very bottom of the page). Other option is to setup a split dns (resolving the internal IP of your server for the clients). This has to be done at the DNS-Server that your client use. In case it'S the DNS-forwarder of the pfsense visit services>dns-forwarder and add static mappings to make it resolve the internal IP for your servers.

And we had complaints about the latter, hence the reason it is using terminal.

I cannot win either way so I'll just leave it alone.  Sorry.

And we also assume your on 1.0.1.  If you are not, please upgrade.

dia is good, if you are using  *nix.

@rsw686:

If you get a network card with a dongle you could stick it on the bottom and put the wireless card on top. That way you wouldn't have to take it apart.

Or if you do take it apart just rip off the plastic that covers the antenna. That way metal casing can guide the card in correctly.

btw, the metalcase is also used to get rid of heat. Removing it could load to heat issues besides the danger of short circuits.

This is working sometimes, and not others.  It may have been a simple case issue (grep -i).  Is it possible the log file contains characters that could cause grep to prematurely detect an end of file?