If you haven't already seen this, it will probably be very helpful to you. http://doc.pfsense.org/index.php/WPAD_Autoconfigure_for_Squid

Everything related to PPPoE is in the System log.

Can you be more specific?  Also, what does this have to do with traffic shaping?

Nope, just tried it no go. The last 2 lines read: appending output to nohup.out Bootup complete.

Are you trying to use the same key file that you use for PuTTY?  If so, then that is your problem.  You need to convert it to the format that OpenSSH uses (the key generator for PuTTY can do this).

According to the OpenSSH documentation, it is also possible to use it with tun interfaces for using it to make a VPN connection.  Of course, other VPN types (like OpenVPN, for example) are probably more suitable for that.

Being able, or not, to ping an interface has no impact on whether or not you can use IPsec or port forwarding works.  Rather than confusing matters for Ntldr, why not ask a separate question about your problems.

Is the interface enabled? I think by default the third interface needs to be specifically enabled by marking a box. what does it show if you go to "status", "interfaces"? if what you are saying, is that you connected a switch directly to the OPT1 interface, and then connected your computer to that switch and put your computer in the same network as the OPT1 interface then yes, you should be able to ping the OPT1 interface. Actually, you may have to allow a firewall rule on the OPT1 interface because there aren't any setup by default on that interface. So make sure you allow ICMP to that interface too.

Yes,thank you,I know that,but I looking for the way to make that.Have I input all of IP`s(the specific range) in the Traffic shaper ?

weird for sure that pinging a host on one interface "fixes" all of them :(  that said, i have seen situations where due to some switch issues, the switch would not forward traffic to a port until it added that mac address to its learning table, which would happen if you pinged an IP, which would cause an ARP to be sent (a broadcast packet).

Exactly. My guess is that someone got ahold of the Nomadix features list and pasted into a requirements spec. Whether this was intentional to sell Nomadix or someone liked the feature list and stole it or there's really a need for some of those features…no way to know without asking. Will require clarification, but like Jim confirmed, if they absolutely have to have that exact feature set, you've gotta buy the Nomadix pretty much. Like I said it's a good device though complex to set up and expensive.

I am a Newbie - I tried older versions before - but had to  go for Smoothwall. Version 2 works EASY! So finally I can use Pf Sense. ;D

Its often hard to tell how much people already know, but when you describe your question as a "dumb N00B" question its possible you may need this level of detail: To exit from the shell (CLI) type Control-D (hold the Ctrl key down while you tap the D key). What you did would possibly be more accurately described as entering shell mode rather than exiting the pfSense configuration menu. On exiting the shell you return to the menu.

If you are looking for a hard interface failure (e.g. the port is unplugged or CPE powered off) look into the link events in /etc/devd.conf (read the FreeBSD man page) As for a "soft" failure, such as a high delay or connectivity loss (no pings returned) you might be able to get that info from /tmp/apinger.status Or just route the system logs to another server (the system log settings page can do this) and have something that watches/parses the log and reports on failures there.

Edit the LAN rule (or rules you want this limit to apply to) and click the "Advanced" button, this will give you options to limit states, connections and the like.