Status –> "Carp (failover)" ?

SMTP I assume then (Simple Mail Transfer Protocol)?

If you can identify them by IP then just create a firewall rule blocking access to 25/TCP for those IPs.

It does show up, a least in 1.2 stable as enc0.

you can create a php page to enable/disable this function and upload it on captive portal login page web server. I do this to multiple function/add on for captive portal. then u can simply call the function from web page. Just make sure the php page called captiveportal-????? so web server can serve it.

In fact, in a full install, it is possible to install the net-snmp daemon and let it bind on an other port as the snmp default one (udp-161), it works without any trouble…

Did you try a snmpget or snmpwalk with the OID ?

Something like :
snmpwalk -v2c -c public 192.168.0.2 .1.3.6.1.4.1.26573

My network-professor just recently gave me the following link for quite a few network monitoring tools:
http://www.slac.stanford.edu/xorg/nmtf/nmtf-tools.html

I also am trying to monitor via SNMP remotely from the wan side however this particular box has the lan bridged to the wan to pass through a .248 live subnet.  I keep getting msgs that the pfsense box is not responding to the requests.  I have confirmed that SNMP is active.

I should add that "enable filtering bridge" is currently disabled.

Anyone know what a rule should look like here?

http://cvstrac.pfsense.com/tktview?tn=257

well, ive not changed back to "up" yet, but snmp-get against it from this side appears to be working.  i would assume in another 4 minutes, he should be "recovering".

thanks hoba :)

You should check the file locations mentioned in the article as not all of the mibs are ouputted on the same page.

Hi guys,
Having solved the WoL issue temporarily - yes temporarily because now I can't have a list of hosts to wake up :( - I have been trying to understand what is happening with the SNMP service.
And suddenly, while watching my logs I saw this:

Dec 7 13:08:29 php: : DynDns: Running updatedns() Dec 7 13:08:29 php: : DynDns: updatedns() starting Dec 7 13:08:29 php: : DynDns: _detectChange() starting. Dec 7 13:08:29 php: : DynDns: Current WAN IP: x.x.x.x Dec 7 13:08:31 kernel: sis1: Applying short cable fix (reg=e8) Dec 7 13:08:33 php: : DynDns: Cached IP: 0.0.0.0 Dec 7 13:08:33 php: : DynDns: cacheIP != wan_ip. Updating. Dec 7 13:08:33 php: : DynDns: DynDns _update() starting. Dec 7 13:08:37 kernel: sis1: Applying short cable fix (reg=e8) Dec 7 13:08:38 kernel: sis1: Applying short cable fix (reg=e8) Dec 7 13:08:40 php: : DynDns: DynDns _checkStatus() starting. Dec 7 13:08:40 php: : DynDns: Current Service: dyndns Dec 7 13:08:40 php: : phpDynDNS: PAYLOAD: abuse

I thought, oh man, I really need the dynamic dns service up.
Although it doesn't show as being "down" in the status > services window I checked my DynDNS account and they say it's blocked :(.
I can assure you it was working perfectly before I tried pfSense instead of m0n0.
So, 1st it was the SNMP, then it was the WoL, then the networking performance is very poor and now a dynamic dns problem.
What else will happen to me?…
Cheers