Thank you very much.  I was able to find a good definition and I understand better now.  ;D

Does anyone have any ideas on this? I have a few customers that want this system setup for them and I do not want to do it without network discovery working correctly.

@jimp: PPPoE always gets a subnet mask of 255.255.255.255 Gateway doesn't really matter for PPP connections the way it does for others. Though I haven't seen it give out 0.0.0.0 before, it should be giving the "server address" value to the clients for their gateway. Does it actually work? I don't recall seeing any other complaints about the PPPoE server. excuse my english, i have the same problem, works ok with captive portal, but with pppoe server no default gateway asigned to the pppoe client (0.0.0.0). DNS Works OK indeed, ping to google.com resolves ok to IP address, but cannot reach or explore. NAT ok, Firewall Rule for PPPoE ok. Tested on 2 Pfsense Servers 2.0.1 Release. Need Help PD: maybe should i try the patch commented before?

I added a note to the wiki: http://doc.pfsense.org/index.php/Interface_Settings

That may be true for gstripe, but we do have gmirror support (even in the installer) Why would you want to stripe two disks on pfSense? That doesn't make a lot of sense, RAID 0 would only reduce your stability over time. It only helps to gain space by adding disks together to get a larger storage area. Not much use on a firewall (unless it's a separate non-boot volume for something like squid). gmirror makes sense as it gives you RAID 1 redundancy with two or more disks.

ok, thank You all for helping me!! really appreciate that ! now I understand it better …. Tom

I'd like a simple method for this as well. The best I have so far is to access DarkStat and then hosts. From there I just refresh to see what's doing the most bandwidth. From there it's tricky though, sometimes I can figure it out just from the device, but if it's my mac, I have to use something like Little Snitch to see what process/port is being naughty. If someone has a simple solution, I'm all ears.

IPv6 has no relation to the DHCP server. All that checkbox does is either add rules blocking all IPv6 or not add them. Neither way has any impact on anything with IPv4. Is the DHCP server running when it stops giving leases? Check Status>Services, and the system logs. The only time I've seen the DHCP server stop handing out leases is when it doesn't have any to hand out. It may be possible there is some missing input validation somewhere that lets you generate an invalid config file that stops dhcpd, which would be in the logs, but that would have to be something atypical you're doing.

bump

there is a FreeRADIUS package on pfsense, but from testing it in the past it is very limited in comparison to a standalone FreeRADIUS server. (I havent tried the package for a while so it may have gotten better)

@marcelloc: Does a df -h answer what you want or you need a kind of fdisk tool? Perfect! Thanks!

depends easiest way  create rules that  based  alias  change the lan net to single or alias create an alias with the ips you wish to have access to the internet or use network and only allow it that way x.x.x.x/24 I usually  create a couple of rules one that allows ports 1-79 (tcp/udp) and one that allows 81- 1000 (tcp/udp)   that way if people have email clients they work behind the system but web surfing is dead . ( you can create a third rule if you want to omit the https port 443 if you want ) in your case probably would add in a rule for the ports for logmein too ( what ever they are)  i believe microsoft updates use a specific port  443 then  create an alias  firewall rule that allows port 80 to certain ips or range that you wish to have access to the internet. that way client email will work and  so should windows updates but web surfing is limited to those who are found with in the alias ip range if you keep the maxium port at 1000 then there are very few if any proxy servers that use anything under this port range. so it be  but surfing via proxy port usually sucks any ways.. oops miss read your first post I thought  you wanted updates on all computer and websurfing  to only a select few. but the rules still apply  just block port 80  and any thing over a 1000 or only allow  port 443 and what every log me in ports are it still works though you might have access to other 443 site then you just allow microsoft  443 ports and what ever else 443 websites you might want. it pretty  hard to surf with out port 80 for most people.  if you still having problems with windows update  because of lack of port 80  simple fix to that is schedule  port 80 in during down times and have your computer do their updates during that time period as a added foot note: if they have hotmail login page booked mark that will still show up. but once  they log in it switches form https to http and the page will fail to load as do all  most web based emails for the most part .. just pointing this out so you do not get perturbed when you first try and then complain it does not work..

You can edit /boot/loader.conf and/or /boot/loader.conf.local from Diagnostics > Edit File or over ssh. It's possible that loader.conf is empty if all defaults are being used there.

oh I have it working now and it works fine. just can not upload pictures because of no GD support basically it is really easy to install CMS and works fine steps how to very easy: install vhost set up vhost is you want to use port 80 you have to give pfsense a different port and disable webgui redirect in the system advance to set up vhost enter in host name  (use something simple ie: info) enter in ip you wish to binded too enter in port  (80 if the above is disabled) save go to service and start Vhost it will not change to green  but it is statred test enter in webpage in url it should work  (http://x.x.x.x/"hostname"   example ( if using port 80) : http://pfsense.local/info  or http://192.168.1.1/info if using port 8001 then http://pfsense.local:8001/info or http://192.168.1.1:8001/info) to get sqlite to work enable ssh in system advance ssh in to pfsense  via putty in windows or console in a linux box ssh root@x.x.x.x  (x.x.x.x being the ip either wan or lan ip) goto shell ( 8 ) touch /etc/php_dynamodules/pdo touch /etc/php_dynamodules/pdo_sqlite /etc/rc.php_ini_setup exit restart webconfiguator (11) restart system (5) after it restarted use filezilla to log in with sftp user name is not admin  but root ( password is what ever your password is) go too  usr/local/vhost/ up load  CMS into your host directory working CMS frog ( will have to disable ( comment out) the security feature in the index.php and do not forget to place the database in a readable directory) XE mediawiki cmsimple ( does not require sqlite) dokuwiki  (does not require sqlite) plus other open browser enter in vhost address into uRL follow instillation procedure finished a working CMS just no GD support until someone say how to get them activated in Vhost

I would not have guessed that, though it makes sense. Good to know. Hopefully this will help anyone else with a similar issue. Steve

There was no problem with the line … did a new installation from 2.0 to 2.01 and everything was ok again ??

In general, yes that will cause significant Internet connectivity problems in almost every circumstance, you need to get rid of the IP conflict.