Also - What did you see missing on the features list? I just looked at it, and it mentioned 2.0 and I saw a few 2.0-specific items in the list, but I didn't go over it extensively.

@tech6: how try a smaller Kb size and see if that helps. you mind if i ask u how many users are u trying to limit i don't use captive portal at all to limit same with traffic shaper i use the limiter and that works well for i limit ever users on my network if need be as well some services and servers, u should try the limiter and see if that works out better for you. Thank for your reply, peak time around 900 concurrent and the average it's about 400. It seems hard to understand about traffic shapper in pfsense. Would you mind to advise, what step i should to, i would like to 1.limit bandwidth every pcs in my LAN to 10Mbps to some destination (x.x.x.x) 2.limit bandwidth every pcs in my LAN to 128kbps to all destination beside (x.x.x.x) Appreciated if you can advise

would not expect the mac os to operate any different for web browsing. I have leopards and lions behind my pfs with no issues. check the dns settings on them vs. the windows dns settings but I would guess they all use the same DHCP server and gateways?

I completely reconfigured everything and jumbled up the interfaces. I moved opt 1 to wan I moved wan to opt 1 and I reconfigured opt3 as opt3. I reconfigured the gateway load balance and rules. Now opt3, which is a different internet connection, is not alowing full ftp passthrough with ftp helper. The wan and opt1 interfaces work fine. I now think this is a bug with the ftp helper, but don't know what other information I should collect to report it.

@jimp: Sounds like this: http://redmine.pfsense.org/issues/1572 It's been fixed in 2.0.1 (pending release) and 2.1. https://github.com/bsdperimeter/pfsense/commit/0389f03498994dbdaf47543a325b58d14b1cdbab Thanks for the heads up on this fix. I applied this fix manually and now I am able to spoof without it going into a loop. Thanks!!

yes, both has sync options.

@waiyan.pickme: Hello everyone …. I used pfSense as gateway and connected 18 clients over switch .... no package installed ... pfSense 2.0 (release) (i386) ... Unfortunately since start using of pfSense, the client computer's network become unplugged randomly .... I don't know why ... is that because of pfSense .. ? Is there any options to solve that ... ? When client became unplugged, it can't reconnect by unplug the cable and replug it .... It has to shutdown and also need to close UPS ... (no power to client computer) and then it back again .... I don't know how to solve and that's the main major problem for me ...... P.S --- I already changed switch but it's still happen like that ....... **ံHello everyone, sorry that it's take too long to respond …. , I've got an answer and now everything working fine with pfSense except the pfSense pre-version (before released) was crashed once ... The problem for network cable unplugged was because of Symantec Endpoint Protection Small Business Edition 11.0 .... I don't know the details but after reinstalling all computer with MS Essential and now everything fine ... but we found out the problem before that .... Thanks for everyone who gave me the opinions .... I appreciate that ..... !!**   ;)

@jimp: mdima - yes I got it, haven't had a chance to look it over in detail. I'm not familiar with that port/package so I'm not sure what options can really be used in it, probably best to keep that in a separate thread on here. ok, sorry for the OT!

Use virtual IP to assign a second public IP address to the WAN. I don't know much about VIPs so I can't help you with the details. Turn on advanced outbound NAT and you'll see a bunch of auto-generated NAT rules. For those sourced from the vlan, change the NAT address to the VIP.

Yeah I try not to judge only on release time, especially given how long pfSense has historically gone between releases :-) You might try adding a bounty to see if there is any interest in someone putting together a package there.

And to make it even easier, you can use gitsync to pull the code in without grabbing files from github by hand. http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots

For those who were interested: Changing the <ports>setting inside the XML to the proper interface was the solution (as i assumed before).</ports>

What happened? What did you try? I'd be surprised if FitPC had implemented some other watchdog, why would they when there is already one built into the chipset? Steve

You have to configure the external DNS IPs from Open DNS on every computer. You can do it using DHCP configuration on those clients.

No, never heard of either, I will look into them, thanks for the tip!

@torontob: Hi everyone, While back, I setup traffic shaping on a router to allow dedicated Bandwidth to Phones. After a month of being in service, the pfsense router started slugging. The Data subnet would not allow any data to go through because there was a huge Queue for traffic shaping. This happened over time and not all a sudden which makes me believe there was something wrong with my config and the environment. So, I had to restart and get rid of the traffic shapper. Now, I need to put Traffic Shaping in again but I don't want to face the same problem. If anyone has experience with this please guide me. Thanks I am facing the same issue. Any help in this regard would be appreciated, thanks! :)

Hi guys. Thanks for the replies. After stepping away for a while and coming back I made a discovery. I ran packet traces on both the trust and untrust side. On the untrust I immediately noticed something. The 172.30.2.10 address was being seen on the outside. I jumped back into my NAT settings and noticed I "fat-fingered" an ip address. I can't tell you how many times I checked these settings, but apparently I glossed over it repeatedly. Sorry about that. Thanks again for the replies!

Hmm, OK. Because you are not using pfSense for DNS things get confusing. I assume you can access the server from outside your network? And you are using URLs to do so? You may have to restart the pfSense box before the NAT reflection starts to operate or reset the state table in Diagnostics: States: Reset States. Steve