Hi!
because I make some script to schedule restart service, create captive portal file, and something. But I do not want to edit or copy every time I install the Pfsense, I want to make an iso to add some changes to.
Pls, help me.

Thanks for the feedback.  This is just a test box using what I had on hand.  I prefer intel nics but I would be hard-pressed to fault the realteks in this case.  I think they should be removed from the HCL.  Simply enabling promiscuous mode shouldn't cause a meltdown like this.  I looks like a freebsd driver issue though and not a pfsense specific issue as far as I can tell.  I just feel bad for anyone using an onboard 8169 in a small form factor setup.

Paul

@dutler:

yes, i would say that is rather ugly :D
are you doing anything else with the debian host?

nop :)

Hallo!

OK, I tried to disable all, but no change. Might the instaler be incombatible to the motherboar chipset?

ais

If you are trying to use the autodetect function you first need to unplug all cables from the nics and then plug each cable back in one at the time when prompted.

If you configure your clients to use pfSense as DNS, you can configure the DNS forwarder accordingly.
I assume you have a domain for your network.

On the DNS forwarder-config page is the part:

Below you can override an entire domain by specifying an authoritative dns server to be queried for that domain.

So you could set your internal DNS for your own domain.

Thanks for the help. I think I have a good idea what I need to do now.

Never mind I downloaded untangle and got it working. I do think PFSense is excellent but will use it in some equipment from one of the recommended vendors.

At the command prompt, sysctl net.inet.ip.ttl=128 (for example) will work. I am not sure if this setting is exposed anywhere in the web interface.

It won't persist across booting - putting the default value in /boot/loader.conf (in which case it would be net.inet.ip.ttl=128) is one way around that.

Note - unless this setting happens to be somewhere in the web interface (in which case don't touch the sysctl), this is unsupported. Change things at your own risk.

Thank you for the resoponse :).  I was trying pxe because i was having issues with using CF (whole other off topic issue I won't go into).  The only reason i was curions about NFS was because i had no other way to test NFS, aside from loopback on the server itself.

Agreed about the FreeBSD boot process.  It looks like this fails when init starts correct?  I think that normal versions of FreeBSD will grab rc.conf at this point, but it looks like pfSesnse (via m0n0wall) has done away with the typical method.  Someother time for me too, I think.

Thank you!

Lots of info on snort in the packages forum.http://forum.pfsense.org/index.php/board,15.0.html

Yeah I tried that too.  What i ended up doing was putting the hard drive in my work (dell vostro) pc, installed from there then moved the hard drive back to the original computer.

Thanks for the help.

I've managed to fix the errors and all is working well now!

I plan on setting up a test with some different traffic patterns to see if the watchdog errors come back again.

I would try to install it with a normal PC that have two IDE port and then boot the CF into your Atom board. This might work, although I didn't test this myself. pfSense install all the drivers even if you don't have the hardware, the purpose of this is probably to allow you to add hardware to your router without having to reinstall. I prefer to sacrefice some MB to have all drivers onboard than having to reinstall pfSense everytime I have to add a NIC that use a different drive than the ones I had at the initial installation.

I just read on those Atom board, you should have SATA ports, get a cheap SATA CDROM and problem solved, but make sure the BIOS can detect SATA CDROM, most new BIOS can, but just be sure before ordering a new hardware.

MageMinds

My first attempt last December had similar issues…  I moved my NIC's around and it worked after that.

Hopefully pfSense 1.2.1 won't be too far away.

Only the developers can speak for sure, but I believe the image I posted the link to is regarded as production grade - albeit to be used only if your hardware requires a later OS than FreeBSD 6.2-RELEASE. It's pfSense 1.2-RELEASE built on top of FreeBSD 6.3-RELEASE rather than 6.2-RELEASE.

It's working well in production here, as I said - current uptime is 28.5 days.