@stephenw10: At least that's how it's supposed to work. What's 'not working' for you Eduardo? Steve When I login with permissions below: WebCfg - Dashboard (all): so login works, otherwise user can't login WebCfg - Services: Captive portal: Allowed IPs page: Its dupplicated, so I think one must be "Pass-through MAC"'s tab WebCfg - Services: Captive portal: Edit Allowed IPs page WebCfg - Services: Captive portal page: so captive portal options appears on services' menu On Services menu appears only 'Captive Portal', as it should. But when I click on 'Captive Portal' nothing happens. It's missing permission to 'services_captiveportal_zones.php'. If I access 'https://10.1.1.1/services_captiveportal_ip.php?zone=sala_pesquisa', test user can edit IP Address. How can I add a custom permission 'WebCfg - Services: Captive portal Zones (Dashboard/readonly)'? 'WebCfg - Services: Captive portal: Allowed IPs page' and 'WebCfg - Services: Captive portal: Edit Allowed IPs page' are dupplicated here. And I don't have 'WebCfg - Services: Captive portal: Edit Pass-through MAC', nor 'WebCfg - Services: Captive portal: Pass-through MAC' permission on 'Privileges'.

Those look like firewall rules not port forward rules. (or NAT rules) Edit: Just to expand on that. You want to add port forward rules and use the 'Filter rule association' option to add the firewall rule automatically (which is the default behaviour). You may also want to use manual outbound NAT rules if you want traffic returning from your servers to use the IP Alias addresses as their source address. Steve

Awesome! Like your tag says "Hero member" I must agree. . .

pfSense will not work with the TL-WN722N either. The FreeBSD uath(4) driver only supports AR5XXX devices. 4GB CF cards are <$10. Not a very big inverstment.  ;) Steve

It's working now. Port forward and default gateway needed to be resaved to point to the new pfSense gateway. Thanks for the suggestions  :)

Ok, thank you for the responses as I will make those changes shortly as I am waiting for my ISP to bring me my new modem as I found my current modem is DEAD! Thanks again

Thank you

It does sound like firewall rules on LAN. Do a packet capture on the LAN interface of the FW and see if the ping is arriving there - hopefully it is. For testing, make the firewall rule allow any to any on LAN.

Therein lies my confusion. Thank you for your patience.  ;) Dennis

Yeah, it does appear to have it enabled. Still worth checking. It would help for an mSATA but USB might actually be hurt by them.

Changed that

I would go with the Intel NIC personally though I believe there are many people using the HP branded versions here. That particular HP NIC is a Broadcom chipset which is also well supported by FreeBSD (and hence pfSense) but Intel is still the preferred choice. The Intel Pro/1000 PT should give you no problems. https://forum.pfsense.org/index.php/topic,68781.0.html There are some differences between the server and desktop oriented NIC chipsets, the PT has ECC buffers for example, but unless you are pushing the absolute maximum traffic through it I doubt you'll notice. The usually have more hardware offloading capability. A PCI-e 2.0 bus can handle 500MB/s per lane in both directions. That's ~4Gbps. Even in a single lane slot the bus will not be the bottle neck in your system. http://en.wikipedia.org/wiki/PCI_Express#PCI_Express_2.0 Cat 7 you say. Nice. Here at home I have cat 5e and have not seen any data-rate restriction. I didn't really pay much attention to laying the cable either. If you need more than 1Gbps you start getting into trouble if you bend the cables too sharply or run too close to interference etc as I understand it. Steve

The blocked rfc1918 rule will not prevent access to the WAN from the LAN. It should not have caused this problem. Anyway glad you're good.  :) Steve

Sorry for the reply on the old thread, but this is a top hit on Google. I ran an upgrade from 1.2.3 to 2.1 and it worked fine as far as i can see, for my simple config. I have an internet connection at least and can reach the web console. This was on an ALIX board that and been up for almost a year, and i forgot to reboot before running the upgrade, heh. It did take around 10 mins, so be patient and dont pull the plug if you forgot to hook up the serial/vga console like me.

All traffic is blocked on OPT1 when you first assign and enable it. You need to add firewall rule/s to allow traffic. Post what you have so far - IP-subnets of LAN, OPT1 and WAN, rules on the interfaces… - if you need more help.

I moved pfSense to an intel based box, and everything in pfSense worked fine. I still have a problem with my Apple Airport Extremes, but tonight I'll do a factory reset.  I hope to use one extreme as an access point.

Hello to all of you, I finally made it by reloading a 1.2.3 version, for info: 1: i used a Dell optiplex but i needed to put 2 "old" network-cards, the 1.2.3 cannot recognize the on-board one. 2: i had no problem with the LAN interface IP and the DHCP rule having a different range of IP  addresses , still I dont why it's that way; i didn't set up that config, just took over (i dont think thats the right way to do it but its working). I would like to thank everyone here: both reading and answering or helping others with issues. Anyone in Denmark, beers are waiting! s.

If you only configure a single interface, it will appear as WAN, then pfSense will allow access to the webgui via that interface by default. This is it's 'appliance mode'. As soon as you add a further interface, LAN, it will go back to acting as a firewall by default  and prevent any access via the WAN. You should be able to connect via the LAN interface at that point though. To prevent that happening add your own firewall rule to the WAN interface before you add the LAN interface. The rule should allow access to the webgui ports (80, 443) from devices in the WAN subnet. Steve