radius server ip is going to be the ip of your radius authentication server and the shared secret is the secret ket you setup on the radius server to check for when other computers would like to talk to it. How far have you gotten in your setup as of now?

usually they are flag files that are just touched so that other processes which are run periodically (cron, etc) can see some action that needs to be done. Not sure about the one named "touch" that was probably a bug somewhere or perhaps done by hand(?)

Yeah, it's broken on 1.2.3 release. See here: http://forum.pfsense.org/index.php/topic,21381.0.html

"0 24 * * *" is what you give crontab for the date. You probably want something like: date +%Y%m%d%H%M%S in that place.

I checked it, it seems like pretty good. I am gonna install pfsense 1.2.3 upgrade, I checked the upgrade guide.it seems like it is pretty safe doing that. but since I am not very knowledgeable about pfsense, I have little concerns. if you guys kindly share your suggestions before doing this upgrade, I really appreciate. Thank you

@crazybyte: Could you explain why it works only after the service is ran for some time? My guess is that the ntp server needs some time to pass to be confident that the ntp client has stabilised its time offset calculation and that the server doesn't offer the service until that has happened.

I tested an other CF-Card (2GB instead of 4GB), and nanobsd is working like expected: on boot, I can change interactively which slice to boot, mount shows /dev/ufs/pfsense0 and pfsense1 for slice 1 and 2, and I can change the bootup slice in Webgui without errors. Thank you for your comments. Up to last week I knew that pfsense is great. Now I know additionally that this forum is great, too.

On embedded, /var is a memory disk, only about 30MB in size. You must disable squid's caching if you want to run it on embedded – its useful only for access control and authentication in that context. If you really want caching, you'll need to manually connect and configure some kind of volatile storage (e.g. external or secondary HDD) and set squid to go there. There have been other threads in the forum that discuss this, but it is unsupported.

@Perry: Might help http://forum.pfsense.org/index.php/topic,14847.0.html I went through many posts in the forum but I missed this one… it contains exactly what I need. Thanks a million!

If your modem has your name and password in it, then it is doing PPPoE for you, and pfSense should just use DHCP on WAN. If it's a half bridge, you may be better off doing a factory reset on the modem, which should make it act like a bridge, and then setting pfSense up for PPPoE.

This is definitely a challenging problem. I looked at your second ps output and saw irq18: fxp0 is the biggest consumer of CPU time. The startup output shows irq18 is shared by fxp0 and atapci0. This means the disk driver is called every time the fxp requests an interrupt. This is suboptimal. There may be a BIOS setting to set the disk controller into LEGACY mode rather than NATIVE mode. In legacy mode the disk will use irq14 and irq15. The shell command vmstat -i can be used to check interrupt line assignment. See if you can get the disk to use irq14 and irq15 and see if that makes a difference to who is using the most CPU. The next biggest CPU consumer is em0 taskq. The startup output shows irq16 is shared by vgapci0 and em0. Again, this could mean (I don't know if the vgapci driver uses interrupts) the vga driver is called for every em0 interrupt. It could be worth trying to eliminate that sharing by (possibly) moving the Intel GigE NIC to another slot so that em0 get assigned a different irq (not 16 and not 18). It appars the video card is a AGP card so there is probably no scope for moving that to a different slot to eliminate interrupt sharing. Since there are no USB devices listed in the startup I presume the BIOS has been configured to disable USB devices. This is a good idea (if you aren't using USB devices) since it helps reduce interrupt sharing. I don't know if the motherboard includes any PCI Express slots. If it does, it could be worth trying an Intel PCI Express GigE NIC because the OS may be able to initialise it to use MSI (Message Signalled Interrupts) which would give it a dedicated interrupt line. However, the system chipset might be too old to support MSI correctly. I took another look at the information you provided and it appears that though the FreeBSD startup says the disk controller atapci0 uses irq18 the interrupt listing says its using irq14 and irq15. Perhaps the system is confused in which case it could be worth seeing if it has the most current BIOS and updating if there is a more recent BIOS available.

At least for me it does not wrap around at 4 GB on the interfaces page in 2.0.  It also does not have the 4 GB note on that page anymore.  I haven't checked whether the dashboard widget also works correctly.

Hmm, right now I'm being very (understatement) surprised… Book shipped on January 30, arrived just now. I have never seen the British mail work this fast.

@jyavenard: however "Other" only let met define one IP address; no netmask nothing … Just for completeness, I'll point out I found it possible to add multiple "Other" Virtual IP addresses but had to do so one address at a time. Concerning sipproxyd, in case you meant siproxd, siproxd works fine for me on pfSense 1.2.3 RELEASE provided I use suitable VOIP applications. More details at http://forum.pfsense.org/index.php/topic,18204.0.html. The siproxd maintainers might be interested in some more details of the problem you had.