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.

No.

This is a firewall, not a SAMBA platform.

I say leave it out.  I'm a bit of a "llama" as you put it.  But I have managed to learn from not knowing pretty much anything to knowing how to setup a network with pfsense doing my routing, with port forwarding/NAT etc, and I know what almost all the options do etc.

Just by reading everything and asking the odd question,  infact I chose pfense because it looked like the easiest one ( I think I was a little wrong on that call though :) ).

I remember one of my questions being, "why is my red/WAN nic running in halfduplex mode, is it supposed to be?".  I guarentee if that option were avialable I would have definatly tried it before asking any questions or reading up on what it did, until I broke something.

But in saying that,  all it needs is a little warning beside it such as.  "Leave this to auto unless you really know what you are doing, as it may lead to a duplex mismatch which will degrade performance".

I rather meant that it could be used for status purposes, for example…

WAN droppep,
any errors,
New IP,
...

Ooh forgot to mention. 83.227.180.253 is my wan (static) ip adress.

Could you add some kind of ascii art to describe your setup? would be helpful. I don't understand it yet.

I have no idea.  I haven't worked on it in a bit.

Use the force^Wcode, luke.

http://pfsense.com/cgi-bin/cvsweb.cgi/pfSense/etc/rc?rev=1.225

It's back in the latest snapshots.

I's not really ignored, it's just not happening to anybody else (at least I haven't heared about it). I'm not sure if this is somehow pure-ftpd related (that it borked something or whatever). I would suggest reinstalling the latest testsnapshot from scratch and test again without having pure-ftpd installed. We are focusing at coredevelopement atm and pure-ftpd might just be broken and mess up something. This is a package not many people use and as Scott pointed out (and the description says as well), it's not meant to be installed at a machine running as firewall anyway.

Done. Together with the themerework I added:

RSS-Feed Header information RSS-Link (top right of page) Link back to pfSense.org fixed some more black textcolors

(btw, smf should rework their themesystem. You not really can call that themeing)

One way to tell if this is happening is that you will loose you're ethernet sync light every second or so.  Its pretty noticable if there is a problem.

That SIS chipset bug has caused way more damage than good.  Really sucks when there are bugs in hardware chips.

None as of now, I haven't spent any time on this, but i know Progie and a few others are working on EVDO (means that ppp will be an option). Once that is done it should be a simple matter to add plip and kernel drivers to get modems and other serial communication to work.