I updated and everything works ok!!

Thanks for the answer

But aren't you supposed to see "XMLRPC sync" messages in the log file? At least attempts to sync? I see nothing on either firewall.

-Sean

thx

I have the almost the same problem, get the same error as you.
But i can not even see the wireless when it is configured as an access point..
Hummm.. 
Is this a shit Card???

Found it at work and noone was using it and i am starting to see why i think..  :P

Thank you so much for this guide I have my CrysalFontz 633 LCD finally working as it was running on a caua0 serial interface.

Everything is working, but I am getting a little tired of manually logging into shell and running the LDCd and lcdproc commands to get the proper output vs the default lcdproc output.

Is their a way to automate this on reboot?

@thegreathoe:

my problem with doing that is that i have no control over what these guests might be doing…  i cant penalize their vpn traffic or anything that they might be legitimately going to that shouldn't impact the network.

Most of the stuff uses known ports. Web on 80, secure web on 443… fairly complete list at http://www.iana.org/assignments/port-numbers

l2tp is on 1701, pptp is on 1723, isakmp is on 500 and so on (for vpn traffic examples).

So it should be quite possible to do a "give these things normal priority and downgrade everything else into the basement" type approach. Work intensive for you to first make a list of stuff you want to permit untouched and then implement the rules and it still won't be bulletproof if the torrenters run their clients on a known port, but might be better than nothing.

thank you very much !

There is an issue with the current snapshot, next snapshot should be better. Use a snapshot from the 7th or before and it should be fine.

It wouldn't say PPPoE necessarily. The name of the program that does it is mpd.

It might be related to a ticket I opened earlier. I'm trying to fix up some binaries on the builder, so the next new snapshot after this post should be ok if it all goes well.

It would help if I read the other threads… sorry! I see this is a known bug.

Pretty well, I suppose.  I bought a second unit, configured failover, and watched.  The original unit continued to fail and got into a state where it was unresponsive even from the console, so I shipped it off for repair.

@luckman212:

cmb: what was the procedure you used to get 2.0 onto the hamakua? mind sharing that?  thanks  :)

Same as 1.2.3.

http://doc.pfsense.org/index.php/Full_install_on_Netgate_Hamakua
http://doc.pfsense.org/index.php?title=Embedded_install_on_Netgate_Hamakua

Do you think it can help if i install these drivers ?
http://forums.freebsd.org/showthread.php?s=c529df415ef86bb8e289617ac92f5695&t=7562

If yes, can you tell me which one i have to install on pfsense 2.0 ?

Thank you

https://github.com/pfsense/pfsense/commits/master

https://github.com/pfsense/pfsense-packages/commits/master

The running on the LAN interface and setting up NAT rules seems to work like a charm…  at least after I remembered to remove multihome from my adv config.

You may also need to switch to manual outbound NAT and add a rule to NAT for the IP alias network. Last I remember, we don't add automatic outbound NAT rules for IP alias subnets. (yet?)

works :) was my fault .. i type a "wrong" key !! thx

Best Regards