@_freebsd:

I had format my harddisk by DM.
When install 1.0b4. I get "ad0:WARNING WRITE_DMA UDMA ICRC error (retrying request) LBA=xxxxxxxxx"
???

??!!GOOGLE!!?? 2 mins of looking.

http://www.freebsdforums.org/forums/showthread.php?t=26392

It probably has something to do with your ata speed and whether you are using a 40 or 80 ping cable…. unless this is CF.

These are inofficial builds though they should work. Give it a try. The person who builds these images is from Hacom, a company that offers Firewallhardware ( http://shopping.hacom.net/catalog/ ) and that was one of the first who donated hardware to develop pfSense on. Hacom is one of our recommended Vendors ( http://pfsense.com/index.php?id=40 ).

Update for those that might be trying to impliment the same thing i am doing.

Essentialy i am trying to put 2 pfsesne boxes between my core routers and my edge switches with backup links going around the firewal for redundancy.
I've upgraded my config from beta 2 ta 3.

Thank god ftp is fixed that was a huge issue thankx guys.

I've upgraded my in and out nics from 100mb to fiber 1gig cards, and changed the config accordingly.

After a few hours of troubleshooting loop issues and up down interfaces i finnaly was able to get 4 vlans trunked together across my fiber link passing 4-5 megs with about 15-20 physical machines.

Of course like sullrich said, the mac entries are still being broadcasted across all vlans with no fix in sight (might actually look at freebsd code to see if i can make a quick fix) but now i also have the spanning tree packets beign blocked as well.

If i shut filtered bridge off all 4 vlans go into stp disabled status for recieving ther other 4 vlan's stp packets.if i enable the filtered bridge all works but not stp packets pass at all.Apparently the bridge does not know after recieving these packets where to send them on the other side.

This wouldn't be that much of a problem being the bridge on the firewall itself has stp enabled, but being i want to place this inline with my core and edge switches i can not run a secondary (non firewalled) connection to my switches without creating 2 links on the same vlan in stp forward status (IE loop). Its either one link or the other.

So it boils down to this.

You can have 2 pfsense boxes on one switch, you can even have them on multible switches with the redundancy u want. But if you run a trunk of more than 2 vlans (1 natvie and 1 non native) across the firewall stp and mac entries will be screwed to high heaven causing extensive cpu load from learning mac entries over and over again(depending on how many machines u have, i got a few hundred) and possible stp loops even when enabled.

From what i am seeing on google and freebsd boards, this is a limitation of the kernel and not pfsense so no complaints here, but thought i'd give you guys a heads up.

Any suggestions would be apreciated. Anyone curious and want more details about my setup feel free to ask.

No problems here with ADSL2+ 16mbit/s down,1 mbit/s up  :)

Go to diagnostics>edit file. Then open "/conf/config.xml". Edit it, copy, paste or whatever you like and save. If the box has booted up with the configuration on the stick it already is mounted for use.

Ok, thanks.

I'll try a temporary configuration with an unused routable C class to test all this before using it for real. Maybe when I'll be ready for that, the 1.0 final will be out  ;D

You might be able to use linux to dd an image direct to the embedded flash although good luck upgrading it afterward - heh.  Hopefully the unit(s) load the OS into a ramdisk after booting, if not, I can't see how you're going to dd over the on disk OS w/out panic'ing it, resulting in an immediate paperweight.

If possible, I'd do the following.

Boot into linux
configure the flash to read-only (better yet, see if you can put the OS in a ram disk and change the / mountpoint to it - good luck)
SSH into the machine
use ssh to ssh to another unix box passing dd if=pfsense.img of=/dev/whatevertheflashdriveis command to the remote ssh daemon
Pray that nothing writes to disk other than the dd, sync; sync; pull powercord - do NOT let the OS hit that disk
power on and pray some more

If it works, pay me $1000 for the consulting and report back.  If it doesn't work…do the same ;-P

--Bill

@hoba:

Please try to disable serial console at system>advanced, save and turn it on again, save. Then reboot. Does this fix the issue?

I tried this on a IP330, it get's to the same point as the other poster said.  I tried what you suggested.  Still getting the same thing.

Thanks for your quick responce i wasn't sure if it was a known bug or not. I have gone back to beta2 for the moment will upgrade when the new snapshot comes out.

okok, seems to have a problem with the modem..

Btw, pfsens rocks ! thanks to it team for this work :)

regards,
ronan.

yeah, I think that's what you want. you can dump your monitor now  ;D

Thank You!

I think we are now crossing threads.  Please do not do this.

Then make a seperate subnet for the wlan. captive portal can't be enabled at a bridged interface.

At which point does it refuse to start or crash or whatever? What is the last output you get before it stops?

This used to be a problem with older versions but is no longer an issue with beta2.  Atleast not with usb memory sticks.  I wouldnt trust a floppy as far as I can throw it.

Keep in mind that only thr wrap has 3 LEDs. Other devices like the soekris only have an "error" LED to toogle and this then might confuse a user. Also the Wrap LED is solid green before freebsd actually starts booting. This might also confuse as you can't tell is it hung before trying to boot or is it up and running.

But if it can be done like in the following example without breaking something for other platforms that don't have the second LED I would like to have it too:
1st LED is always on (at least for the wrap, indicates Power, you can toogle it but it might confuse due to the above described reasons)
2nd LED is off before BSD starts booting up and switches to blinking state when BSD takes over. It will finally switch to on when it's up (same time when the readybeeps are played)