No real formal list. It will play a tune at startup/shutdown. It will beep on login (but that can be shut off in advanced options). It will beep a few times during the firmware upgrade process as the process starts and then when the reboot is about to happen.

Sounds like he wants some on-site help there. We can certainly help with the software configuration side of things via commercial support, but not the hardware and wiring on-site in that location. For that we do have a list of local/regional support providers on the web site: http://www.pfsense.org/index.php?option=com_content&task=view&id=70&Itemid=82 Someone else on the forum may be able to do that (or know someone who can) in that area.

It isn't normal for it to reboot, but there is not enough information to go on. There should be a panic message on the console or when it comes back up it should detect a crash report and offer to view or upload it. If there is no panic on the console or crash detected, then it's probably the hardware resetting itself for some reason or another, which would be a hardware issue and not a bug.

You can use limiters to do per-IP limits (it's covered in the doc wiki), or if you have a radius server you can use that for authenticating your users and set per-user bandwidth restrictions that way.

It does. Just select "Additional BOOTP/DHCP Options" in the DHCP server setup. Steve

@Metu69salemi: Can you explain why to have "bridged" interface with two dhcp servers? Second that. At the moment your wireless client are experiencing double NAT which can cause problems. A much better settup would be to use the Netgear device as an access point only and allow pfSense to handle dhcp. More importantly, your OPT1 interface is in the same subnet as the other bridged interfaces. You need to have this in a different subnet. (Assuming you have /24 masks on each interface). Steve

@alehawk: Will this software work with 3 LAN adapters? Yes, it will work with many more than 3 NICs. @alehawk: I mean, I want one to connect my ADSL modem, and two wired adapters plus one wireless. Will it work? Yes, provided you use supported adapters.  Most (but not all) NICs that have been around for a while are supported. The range of supported WiFi adapters is rather smaller. @alehawk: The adapters configuration can be found after installing the soft via http? Generally you need to configure one NIC as LAN and then the others can be configured by web GUI. Installation and configuraion documents can be found at http://doc.pfsense.org

That rule say that, if you have several clients they're able to discuss each other. If you want to allow traffic somewhere else, you should add another destination. one possibility: create alias, which has all networks you want to access create a rule which has newly created alias as destination

Thank You, I was worried something was wrong. Thanks again.

Perfect thanks for the link helps a lot.

Thanks! it's work the name's :ad1 ad1: 152627MB <wdc wd1600aajs-07psa0="" 05.06h05="">at ata0-slave UDMA100 SATA Now I just have a problem to format and mount it.  :) @wallabybob: @zsunol: I added a second hard disk SATA of 160Go. (Bios OK) But I do not see him(it) in Shell SSH. How are you expecting to see it? For it to show in df output you will need to have formatted it and mounted it. To see in the OS thinks the drive is connected you could use either # ls /dev/ad* or # dmesg | grep ad If you want help interpreting the output from these commands post the output as a reply.</wdc>

On 2.0 RC3 I can enable the serial console, and it works (I get a menu on both) and I can also password protect it and it protects both. Not sure what is going on there but at the very least make sure you're using the most current 2.0 snapshots. ssh is protected by the password on ssh - it's not a "console" in the way that vga/serial are.

Yes, otherwise you're going to have no end of problems.

That'll be handled by the WET54G and covered in it's manual ;)

Sounds like what used to happen on older snapshots if you had no functional DNS on the router itself. Upgrade to the most recent 2.0 snapshot and it will probably behave better.

On the official strikeback forum topic I explain that you need to go into the settings and change the user to root. Upcoming updates will do this automatically.

That probably depends on what/how you are testing. PPPoE will add a bit of overhead, both in terms of CPU usage on the router and in terms of adding data to every packet. Though it shouldn't cut it by half I wouldn't think.

In VirtualBox, the virtual environment with which I have some familiarity, it is necessary to establish interconnections between physical interfaces and virtual interfaces. I suggest you draw a network diagram including both virtual and physical machines and interfaces. Use the diagram to help you work out how traffic will get from a particular source to a particular destination. In some cases the link will be a piece of wire, in other cases it will be a link you have specified in your virtual environment. When I last tried pfSense on VirtualBox (some months ago) I found it didn't work well with the default virtual NIC (an emulation of an AMD NIC). I forget the details; it might have been nothing showed up on a packet trace when there should have been ping transmits. I switched to an emulated Intel NIC and all was well.