Have a look at http://forum.pfsense.org/index.php/topic,3330.0.html . It should fix your issue.

It's something I'm interested in, as I have an EVDO card for my laptop, but not anything I'll have time to look at for probably a few months. If you would like to shift priorities, start a bounty.

What you're describing is very typical of pegging your connection with cable. When you hit your cap, packets start to queue in your cable modem, and your latency goes through the roof.

hello
I have mentioned in very first post that I have already syslog machine… but it is useless in case of interfaces hanging

;)

Basically the config.xml is stored there only (the same file that can be downloaded at diagnostics>backup/restore). Additionally to that it will write the rrd data to this media on a clean shutdown (when performed from wengui or shellmenu). Everything elso is stored on ramdisk and therefore will be gone (like dhcp leases unless you have added static mappings which will be backed up in the config.xml).

That is what i use to test with.
http://www.nwlab.net/art/netio/netio.html
http://www.koepi.org/smbdownloader.html

When pfsense will support the "from" parameter of the pf rdr rule type it will be possible. For the moment you can try to script it in order to add these rules at runtime.

Problem solved, but don't ask why or how.

I was trying tonight for yet another time. Changed the modem to router and put WAN on DHCP (wanted to know if maybe the interface was broken). This worked.
Then changed back the modem to bridge mode, configured pfSense for PPPoE on Wan and BINGO, it work all of a sudden.

I thought there might be a bug in the configuration of pfSense (the only thing i did different this time was first configuring pfSense for DHCP on WAN, saving, then back to PPPoE). So, i reinstalled pfSense completely (reflashed the CF for my WRAP board). Tried again and it worked first time with PPPoE.

To cut a long story short, i did nothing wrong in pfSense the first times, i did nothing wrong on the modem the first times, but after configuring it for the 999th time, it worked.  ??? ??? ???

Nevertheless, i'm happy ;D

Many thanks to all trying to help.

Already been asked 1000 times.  Search.

Good to hear  :)

@hoba:

there are some hosts at your fxp1 subnet that have the same IP. This could be some teamed nics. If that is not the case you should find the conflict and resolve it.

I doubt if those are teamed NIC's in this case - usually that'll be two NIC's from the same vendor. These are two different vendors:
00:13:8f - Asiarock Incorporation
00:14:c2 - HP

Gintaras: I would look into this and see why you're seeing that IP switching between MAC's.

@Juve:

I started working on that type of addon few month ago, it is not yet "usable" but I hope I will finish it asap and release it to our great pfsense community. It's a windows service with a frontend GUI that stores all information about multiple boxes (securely stores password for automatic logons), makes full backup of every box everyday (with tunable history list), detects whether or not a node of a cluster has fail over (triggers mail alert). I would like to add some other features as well….like managing a whole box through the GUI (I'm looking at the xmlrpc interface instead of building my own HTTP requests and parsing the replies (that's what I do now for box backup for example)...). At the moment I have not enough time to go through it quickly...this may change soon.
;-)

Nothing else roxxx as pfsense do!

Nice! Can't wait to see this  ;D

If you have another device plugged in, your ISP may only allow you to get one lease. If you're changing out an existing device, you may have to power cycle your modem before it'll let a different machine online.

Try firefox.

I would also very much like to use SNORT to block P2P traffic.  SNORT does an excellent job of detecting P2P no mater what port is being used.  I have SNORT running on the WAN interface set to block any one who generates a snort aleart.  However with P2P traffic it is always my own public IP that is detected as "generating" the alert.  Since my own IP is in the whitelist all that is acomplished is that I am alearted to the use of the programs.  I would run SNORT on the LAN side but I have about 25 other smaller firewalls behind PFsense with each of them connecting 5-20 individual clients. So if I blocked any one ip on my LAN interface I will cut off internet to several people. If it were possible to run SNORT on the WAN interface and set it to block BOTH ip addressees associated with a SNORT alert.  I believe that this would solve my problem and effectively stop the P2P. (And help keep my little wisp from getting sued by the RIAA)  ;)

(1) when using an incoming ftp server you would be best to disable the ftp helper on the interface in question.
(2) pure ftpd can use passive ftp where you set a port range 3000-3500 and you forward those ports along with port 21 on to the server.
(3) most ftp servers allow you to work with nat by allowing a field to enter the public ip address in the ftp server startup script to allow for better translation.
(4) first thing to do is get your ftp server working correctly without nat then add the nat specific stuff into ftp server configuration and firewall after the thing is working.

good luck

its nothing fancy.. just some oldass compaq deskpro i picked up for like $50. no raid or anything like that.. i'll check what kind of motherboard/NIC its got.. thanks

If the squid package supports AUTH then require people to authenticate to the proxy.  That'll make it fairly trivial to track who visited where (assuming you enable logging of the authenticated user).

This may break some things that perform web updates, so you may have to spend some time adding ACL rules that'll bypass the auth for certain destinations.