Ok, now all works ok. Thank you.

How can I warn developers?

Hi,

i can confirm that. The auto update function inside my latest pfSense Build isnt working. He just hangs up with the php process while he tries to catch the file. Then i need to kill via console the php processes and restart the webserver.

If i try to download the update via console, the same problem occurs. I just tried

fetch http://snapshots.pfsense.org/FreeBSD7/RELENG_1/_updaters/latest.tgz ```and the download stops shortly after the first percent. At the beginning normal download speed but then just hanging up. Too be sure that the problem is the server, i mirrored the pfsense dirs to my server. And i tried to update with my internet server. Its works…. I checked the http headers but they look normal. I dunno why he is hanging up...

Any idea?

Fixed thanks.

Fixed, thanks for the report.
Grab next snapshot.

It should be fixed in next snapshot.

You could NAT 1:1, or you could use PFSense as a bridge. See here:

http://pfsense.icehosting.com/tutorials/transparent_firewall/transparent_firewall.pdf

The gist is that in a bridge config, both interfaces will exist on the same subnet, but with different IPs. The PFSense will not provide routes, but may need some static routes if you have layer-3 switching immediately upstream or downstream of it.

I haven't seen that issue myself. Are you running the latest snapshot?

Did you even try to set it up?
Did you searched this section i already told once a quick/basci setup for per ip bandwidth.

…and one more note. While configuring gateway, the "Monitor IP" has its description that says;

"Enter a alternative address here to be used to monitor the link. This is used for the quality RRD graphs as well as the load balancer entries. Use this if the gateway does not respond to icmp requests. "

Is this really true? My RRD Quality graph shows nothing at all with or without this monitor ip configured.

cheers,

Did you specify only the part you wanted to restore when you backed up the config? You can't backup the entire config and restore only the firewall rules, for example. You need to backup the firewall rules, then restore them.

This was not clear to me, but it does explain the errors I was getting. I guess I have to save individual parts of the configuration, and then restore them. From the GUI its not clear at all that you cannot selectively restore part of an entire configuration.

I thought I explained this in my original post, but the new CA manager presently requires you to create a CA, create a cert, then enable https using the cert. If you are restoring a 1.2 config with https webgui, you will need to create the cert to use https. In my case, I was able to connect via http to configure.

I'm trying to restore an "earler" 1.3 config (from around the beginning of Sept. I believe). It seems that with the new CA manager, its not possible to restore an entire configuration anymore.

I guess I'll have to start from scratch, and then load those bits of the configuration that are important to me  to get back the "previous" state…Perhaps when I get some time.... :-}

Thanks for your help, I hope It will  be implemented for the next release

It's been mentioned before that the CP is maintained by the m0n0wall devs and periodically sync'd. I believe this is still the case, and you will not see this feature unless it is implemented in m0n0wall. (Or you do it yourself, or put up a big enough bounty to entice someone to work on it)

Hey!

That did the trick :-)

I had to change the "HDD Timing":
Before (which worked fine with 1.2-Version) it was set to "Ultra ATA-33".
Now it only works when set to "Standard" or "Fast PIO".

Is the reason for this a change in the FreeBSD-Version from 1.2 to 1.2.1 or 1.3?

Thanks and best regards,

Chris

P.S.: I still don't understand why the live-cd created a "non bootable" CF-Card. Writing
the image with physdiscwrite worked perfectly though…

Maybe an internal cert could be automatically created on first bootup, used for the web config…then you could change it if you wanted, but if not, it would be in the list...

I don't see a CRL specifically, but you can go to the "Connection Specific Overrides" tab, put in the certificate's X509 Common Name, and tell the server it's disabled.

I would love to see CRL support–or even checking/caching the CRL against what's listed in the Netscape Extensions section of the cert, but I'm not sure if it's in the plans--and I'm certainly not elite enough to code it.

Hope that helps.

-A