Hi Again,

I think you should firts remove nics on your vm then add again them. After that do steps.

Regards,
SGTR

Hi,

I have configured pfsense 2.0.1 for email notification and could get the test email message but no events are received by emails. can anyone help me in this regard.
Venkat

On 2.0 and newer versions, the better drivers include details on errors in sysctl output. For instance if you have those errors on em0, run:  sysctl -a |grep em0

and you'll see specifics on what they are.

Are xxx and zzz both public subnets?

Steve

Put the system in a welded "catwalk cage" along side a ZoneMinder monitor with a simple usb cam capable of sms/emailing notifications. Epoxy ports in place and metal shield cables.  Weld/Glue/Lock the case shut. Wire in a high capacity cmos battery. Back the entire thing up with a 4000VA ups with attach notif usb inside the cage.

Or, just hire someone with a larger pay grade and hand them a remington 870 and box of ammo. Cheap and effective.

Thanks for the info. I figured as much regarding the interface running as root etc. Just bothered me to see the perms. Suppose I could always just clean them up myself manually/crond.

Captive portal has no concept of what AP a user is connecting to. As long as the device has the same MAC and IP address, its CP session is still there.

1-Yes you can, you just need to start ppoe server on lan interface, dhcp server can be enable when you install pfsense is askyng you dhcp enable for lan interface ?…and is asking for range, or you can enable it from web gui in SERVICES you have also ppoe server and dhcp.

2-You need to make new rule in firewall, after starting ppoe server wich will appear in rules ex WAN LAN AND PPOE server , click on ppoe server and you should select as gateway ->wan interface for internet acess(for ppoe clients).

For me it worked !

Just to chime in here. I agree that double NAT is best avoided but it only gives trouble in rare circumstances. I have run double NAT for months with no problems at all.
This is not a double NAT problem.

You don't seem to have fully explored the packet capture that showed that pfSense was not NATing traffic. Simply switching from auto to manual should not stop NAT working. You would have to deliberately remove the NAT rules.
Switch it back to auto, I would reboot the box at this point, then rerun your packet captures to demonstrate that NAT is working.

Also unexplained is the fact that you somehow ended up without a default route?  :-\

Going right back to the beginning; is it a specific set of configuration changes that cause pfSense to stop forwarding traffic or simply making too many changes of any sort?

Steve

Thank you for your response stephenw10.  I really appreciate it.  I'll make sure to change one of the interface types to none.

Yes. Go to SYSTEM -> UserManager and set the privileges for a user and/or a group of users.

Yes, you've got the general idea of double NAT.  The primary purpose of NAT is to translate/map public IP(s) to private IP ranges (10.0.0.0/8 172.16.0.0/12, 192.168.0.0/16) to facilitate Internet access.  For this reason, it should only be done once, probably at the provider edge (WAN).  In reality you could do it as many times as you want, but future troubleshooting could be difficult and certain applications might not function properly.

Tested with "Disable Gateway Monitoring" ON, and it brights the link UP again w/o problem.

So that would only apply to something critical, like wireless link.

Other than that, I can only think on RRD Graphs to report for quality link.

I actually didn't need to change anything with Squid, it must default to being active on the VPN interface. What I did have to change was putting the ACTUAL gateway IP as the proxy address instead of the PPTP pretend gateway as the proxy address (the gateway is actually x.x.x.254, the gateway IP in PPTP is set to x.x.x.253; x.x.x.253 gets me to the web UI, but the proxy doesn't work unless I use x.x.x.254).

Oh, your right - im running under VMware and remember first choosing em0 as the Wan link before i switched to ppp in the widget. I check that … Hey, default was at em0 (which is now lan) and not on ppp - thank you
works like a charme now !

Alright thanks for taking a look at those crash reports i was sending. I tried replacing the RAM and HDD but i still get notification light on the server. Even tried removing ram and HDD completely. Thanks again anyways.