You'll need to create your own PHP and such.

this would be great for all services like web interface, snmpd, ssh.
i would allow choosing which interfaces this service can listen on. should be able to be more than one or all.

Check DNS.

umm by the PPTP log, the action is allways empty, but everything else seems to work fine.

There is no sendmail.
There is no GCC

This is a firewall.  There are developers editions but they are designed for development.

full installs

Bah, I did what you told me to and it still didnt work. So I thought I would try something. I disabled the logging option, saved and applied the changes, and then went back into the rule and enabled logging and it works now. Go figure. Maybe it didn't save properly at first for some reason. Thank for your help though Scott.

@aldo:

there are lots of setting in the wireless cards. what card are you using.
i have practical experiance with atheros in pfsense and everything was better than
when using mono and older card

try ifconfig and see that the stats are on the wireless card check to make sure the config is the one you put into the gui.

additionally try to setup wireless ssid etc from command line only and  see how it looks

Thank you very much. I use card with intersil prism 2.5 chipset. Directly Z-com 626. I try command line.

Absolutely.  Use Intel or 3com nics for the best experience… Atleast thats what I have found.  YMMV.

sorted thanks.
was proberly my fault rebooted first then installed package
all fine and working on reboot.
now i can work on it.

wee

It was updated a few days ago.

Server address: 192.168.254.254
Remote address range: 192.168.254.0

i dont know what version you are using but i think you have a problem with your subnet mask 'pppoe units'
in your pppoe configureation

192.168.254.0 will be iether 24 25 26 27 28 29 30 as a subnet
you are better to make a 'pppoe units of say 192.168.254.128/25 and a gateway of 192.168.254.1
the pppoe gateway must lye outside of the 'pppoe units subnet'

post the snip of your pppoe xml. your problem looks like it is here and i am sure your logs will reinforce this

Good news: Scott found the error and will fix it in the next snapshot AFTER 2-8-06

We use clog, thats the way its supposed to be.