You are right !
I'have found in my 1.2.3 release the flag in bridge LAN thath no generate problem.
May be that in version 2.0 is little difference.
However, i take away the bridge and all go OK

Thanks a lot !

Thanks for reporting.
I found the issue http://redmine.pfsense.org/issues/1519 and will soon commit it.

I do not think that will be done for 2.0.
There is code to switch to another xmlreader/xmlwriter but might be somewhat behind in catching up.
It brings speed and even UTF-8

No ETA. We have to release 2.0 before we can even think about ALPHAs of 2.1, let alone BETAs.

I have to hurry up. But no success..

If I look with dmesg, i can see the "link state changed to UP" and DOWN.
But no communication is possible. I have exactly the same pfsense version and config.
Only the factory defaults are working with communication. The "assign interfaces" at the console shows all right.
But here the Link up and down is not detected.

Tomorrow i will leave my company and then the spare pfsense has to work.

Any idea?
Nothing worked. I replaced the NICs too.

download via webgui is somewhat slower than downloading directly. So compared to my line (100MBit) it is extraordinary slow ;-).

So having that download faster, do it manually and then install via console, but i think, the time to upgrade will be nearly the same at the end…

And when pfSense is final, you don't have to upgrade any more.... Enjoy that "wasted" time! ;-)

What kind of config error? The GUI shouldn't allow creating a config that would prevent OpenVPN from starting (unless it was a custom/advanced option that did it…)

@egarnel:

Is the sticky for outbound wan load balancing as well?  The description sounds more like it is for hosted websites behind a pfsense box

As far as I know it is ONLY for outbound.

@danswartz:

Ah, okay.  Re-reading the thread, I'm thinking it is something basic (nothing openvpn related anyway).  How does the elmeg know how to reach the sip server?  A name?  How is the name resolved?

My dear friends,

Finally i found the problem.It was connected to the elmeg PBX.
For some reason it messed up badly the network confs and it didnt allowed to correct them.I had to call the distributor to reset the confs and now everything is working perfectly!!!
Thank you very much for your help and for your work!

there's a ticket open on that

Thanks :-)

Yes there will be another book, we've made a little progress on it lately but it will be a while before it's out.

I have the same problem, but I was using TinyDNS.  Reconfiguring the name servers worked for 10 minutes.  I am now using dnsmasq because the dns server does not resolve.  The problem arise after upgrade to snapshot May 2.

Hi jimp,

I just played with IPsec and after this error I just reverted all I did because of this error.
Perhaps I did some wrong entries. I thought its just a simple syntax problem with a missing "{" or something else.

Please do not spend to much time on this if my racoon.conf will not help you. I will post again I this error occures again and the will offer more details.

# This file is automatically generated. Do not edit path pre_shared_key "/var/etc/psk.txt"; # This file is automatically generated. Do not edit path pre_shared_key "/var/etc/psk.txt"; path certificate  "/var/etc"; listen {         adminsock "/var/db/racoon/racoon.sock" "root" "wheel" 0660;         isakmp 192.168.1.143 [500];         isakmp_natt 192.168.1.143 [4500]; } remote 84.169.95.132 {         ph1id 1;         exchange_mode aggressive;         my_identifier address 192.168.1.143;         peers_identifier fqdn "TESTVPN";         ike_frag on;         generate_policy = off;         initial_contact = on;         nat_traversal = on;         dpd_delay = 10;         dpd_maxfail = 5;         support_proxy on;         proposal_check claim;         proposal         {                 authentication_method pre_shared_key;                 encryption_algorithm aes 256;                 hash_algorithm sha1;                 dh_group 2;                 lifetime time 28800 secs;         } } sainfo  subnet 172.16.0.0/16 any {         remoteid 1;         encryption_algorithm aes 256;         authentication_algorithm hmac_sha1;         lifetime time 3600 secs;         compression_algorithm deflate; }

@sscardefield:

Cool, thanks for the link. Those are all higher-end boxes. I wish they had a benchmark there for a lower end appliance. It's just not reasonable for a SoHo to run a full blown PC for the firewall.

You don't have to run a full blown PC for the firewall. I'm using one of the original dual core Intel Atom 330 (2 cores, 4 threads) which was part of the DG945GCLF2 motherboard, 2GB of DDR2 and a 320GB disk all in a mini itx case. I spent $80 on the CPU/mobo, $20 on the RAM and I already had the drive laying around.

I wiped my settings out when I couldn't get ntop to work a couple of months ago… I have a habit of deleting all settings for a package in the config.xml if I don't plan on using it(well other then snort, waiting on update, too many settings to re-create,lol)

I am too seeing this in my logs when my box starts up. Seems to be the users that are created within the user manager.  I have users in there just for OpenVPN access and they are disabled so they dont have access to the web or console.

That would require rewriting large portions of the restore code and isn't likely to happen any time soon.

It's always just supported restoring one section from an isolated file containing just that one section, not picking bits out of a whole config.

Well, if it happens again I'll be going down there to do a swap with replacement hardware I've purchased.  If so, I'll post an update.

Thanks.