My link comes up automatically at boot or reboot. I added extra log messages to make sure everything was happening in the right order. pfSense executes additional functions after executing the "connect ppp" function. If pppd isn't finished creating the link before the additional functions execute, traffic will not route properly. What country are you in? GNHB

That was fixed the same day it was broken, upgrade.

I am having problems with ftp the program i have to use has passive ftp mode but that doesn't seem to help either

I found another problem about vlans (at least). When switching an interface from a static ip with DHCP server enable to DHCP (client), the DHCP server seem to stay enable. And this interface get an IP from pfsense DHCP server himself… This is not really a problem but it's still not normal.

@_igor_: Are there plans to change this to the "old" behaviour? The possibility to disable accounts needs to be added. http://redmine.pfsense.org/issues/show/65 You should be able to set today's date as the expiration on admin after adding a new user. You can't specify a date in the past to immediately disable.

Found something again today, that sounds like a bug. LoadBalancer                      OPT1        Tier 2                     CABLE      Tier 1 OPT1 goes down, traffic still wants to route of OPT1. 36 bytes from 192.168.1.254: Destination Host Unreachable Any reason why the routes didn't change when it noticed opt1 go down to begin with? And based on the notes of the tiering in the gateway section, everything should route over cable 1 until it goes down, at which point it will route over opt1. Is multi-wan still in early stages on 2.0? An update to this as well: cable (default)  WAN , however in my routing tables: default 192.168.1.254 UGS 0 72 1500 xl1. The default selection of gateways doesn't seem to be working.

@dnarz: Using 2.0-ALPHA-ALPHA built on Fri Aug 21. Very simple setup (single WAN, single LAN) and only a few firewall rules.  My LAN rules look like this: First rule: (block) | protocol: any | source: 192.168.0.2 | port: any | destination: wan net | port: any | gateway: any | no schedule Second rule: (default allow LAN to any rule). So the block rule should stop 192.168.0.2 from getting out. But it doesn't work. 192.168.0.2 still has internet access! As it should. You blocked it from getting to the WAN's IP subnet (i.e. a small chunk of your ISP). The Internet would be any. @dnarz: I tried playing around and the only way I got it to block access to the WAN was to switch destination: wan net to destination: any.  This successfully stops 192.168.0.2 from getting to the internet, but is broader than what I want (I still want it to access other clients on the LAN). The firewall has nothing to do with traffic between LAN hosts.

I spoke to my wife about the line "The sum of children bandwidth exceeds that of the parent." which I don't think I got quite right.  Her suggestion is "The sum of the children's bandwidth exceeds that of the parent."  Other than that it looks good.  I don't think I can break much as long as I stick with comments and quoted strings. I can just add that change to a future patch, I'll probably look through it all again and see if I can clean up anything else.  Thanks for merging it. It looks to me like someone already went through the shaper wizards, or they were done well in the first place, because I cannot find much to fix there. Josh

In 2.0, you have to select your second WAN for one of the DNS servers. In 1.2.x, you have to add a manual static route to push it out the second WAN.

@stompro: @Jerubei: I'm trying to learn traffic shaping in pfsense, so I was hoping that you (or someone else) could confirm my assumptions above. I'll also try using Layer 7 (although I can't find any detailed info on its setup in pfsense either). Jerubei, Take a look at this recent post by ermal where he goes into detail on how to use the layer 7 feature. http://forum.pfsense.org/index.php/topic,17347.0.html I'm working on the traffic shaping guide on the wiki also, that might help you with some of the setup. http://doc.pfsense.org/index.php/Traffic_Shaping_Guide Josh Thank you, this is a very useful reply!

it turns out that you need a lan network card for it to work right…

if you can hard power the box off, and gain access to the console. run the command 'df' this can happen if your running squid, the system runs out of inodes. Again the 1st thing you need to do is find if you really are running out of diskspace or just inodes. -loki

This was fixed in FreeBSD 8 which should be pfSense primary os for 2.0. For 2.0 based on 7.2 you have to merge the patch yourself since it is not in the builds. http://svn.freebsd.org/viewvc/base/head/sys/dev/e1000/if_em.c?r1=195851&r2=195857 This is the fix that went in the tree of freebsd fro 8.0.

You do not have anymore interfaces to add when that happens :).

I tried on vmware and encountered the same problem. anyone can help ? Got it. Incompatible with IE7. Try other browers.

Ermal,   I found the answer from a post of yours in the bounty thread for the new shaper, so please ignore my question. 8- If you have 3 different networks separated from each other and you want to combine to a single centralized management with pfSense and the new shaper, they can be handled/shaped separated or even provide failover for them. Kinda, basic support for different domains. Josh

You have the nat rules there from what you posted so i will not comment any further.