Topics - Pakken

Hi, I'm currently running a pfsense custom made box with a Supermicro A1SAi-2550F, 60GB SSD and a quad gigabit intel network pci-e card. At the moment I'm happily running 2.3 beta snapshot without any kind of problems. The only thing I can't get to work properly, even though I doubt it's pfsense-related, is dhcp with wireless clients, mostly phones and tablets.

I have 2 wireless AP at the 2 extreme edges of the building, on the same vlan, so that clients are roaming between channel 6-11.Sometimes, mostly when a client gets away and comes back in wireless range later on, they can't get a dhcp lease anymore.On pfsense system logs I can clearly see that the client requests an IP, the pfsense' dhcp server offers an IP but then there's no bloody way the dhcpack process completes.

And this goes on and on forever until I reboot the AP. Once it's rebooted the clients are once again able to get a lease but as soon as they get off the wireless range and jump in again everything breaks again.

Even though I know this is unlikely to be a pfsense issue (cabled clients work like a charm) I just wanted to know if anyone of you ever faced this problem.Thank you in advance

I'm currently working with a multiwan (2 dsl and 1 high-speed wireless wan link with a /29 routed static ip class) pfsense setup.

Given the fact the 2 dsl links external ip's are dynamically assigned by my isp, I need to ensure that some traffic goes straight through the other gateway due to access lists based on external ip set on the remote endpoint.

That said, I'm used to work with Fortinet firewalls and, to achieve this, all you need to do is add a static route with the destination IP and the internal gateway you wish to pass traffic to.All I could see so far is that this won't work with pfsense. Is PBR and perhaps an "apply instantly on hit" flag the only way to achieve this in Pfsense?

Hey there, in pfsense 2.1.5 I've got a pretty simple setup (2 wans, 3 lans and a dmz) with a couple of web servers, and multiple websites, behind a pfsense virtual firewall (ESX) and squid3 set to work in reverse proxy mode. Everything's fine.

Same setup on a 2.2 setup won't work. Neither does with the last squid3 release/package.Everytime I try to bind it to listen on port 80, I get an error message saying I need to lower net.inet.portrange.first from 1024 to 0, which I did at least 20 times with no results, tried restarting squid-restarting the entire vm, no results.In the squid's log all I get is a permission denied when trying to bind on port 80.

Is this a known issue?Thank you for all your hard work, everything but squid is running great on 2.2RC.