Thanks, I'll add that one too.

@cmb: That would be the safest thing to do at this point, but yeah given it's limited to /root/ it's not strictly necessary. You probably need to set noschg before deleting. cd /root/ && chflags -R noschg * Then the rm -rf you were trying. Make sure you only do that when you're in /root/ otherwise you'll be doing the reinstall and restore. Make sure to backup your config before doing that just in case. Haa haa you are great! Instead of * I just specified the few files/folders that I needed to delete and the rm -Rf command worked like a charm! Thanks!

@virgiliomi: @The: UniFi AP's are not 802.3af natively remember. https://www.ubnt.com/accessories/instant-8023af-adapters/ That depends on the AP model used. Their current AC-Pro model does support both 802.3af (PoE) and 802.3at (PoE+). I do see that their two lower models don't, though. That's right, forgot about that one!

sorry for that sir, :( with regards with my firewall setting or even the rules it's all by default, that all lan can pass.

https://forum.pfsense.org/index.php?topic=105315.0

https://forum.pfsense.org/index.php?topic=105315.0

I know it's not fixed in 2.3 beta. I am still getting them but nowhere near the rate you are. For my use, the percentage of discarded packets is so small (around one thousand of a percent) that I didn't bother researching it further. Have you tried the tips on Pfsense NIC tuning? Carlos

Marking this topic as solved. I've already deployed my pfSense to our production environment. I am currently monitoring its stability. I did not encounter any issues with the setup I made, thanks for enlightening me.  ;D

or just mkdir -p /usr/local/share/nmap/; fetch -o /usr/local/share/nmap/nmap-mac-prefixes http://nmap.org/svn/nmap-mac-prefixes Don't have to install the nmap package [image: vendorsforarp.png] [image: vendorsforarp.png_thumb]

Either something off a subnet of the /24 or something off a different subnet. It really doesn't matter - you can do what you want. Without more knowledge of what you're trying to do and what your WAN interface scheme is and what is routed to you it would just be guessing.

Run Virtualbox with 2 VM's, one for pfSense and one for your Lubuntu client.  I just talked about this exact same scenario in this thread.

probably somewhere in the next 10 years or so ;) 3.0 will be a complete rewrite of ALL the backend code. Its not something you should wait for, it'll be a while. 2.3 will probably release within 6 months, chances are there will be some point release after that. (2.3.1 , 2.3.2) while i've not seen any official statement about this, i expect there to be a 2.4 release prior to 3.0

System: Gateways: Edit gateway  => disable gateway monitoring for the openvpn. When it happens, everyone inside the network can work fine, but they just cannot get out on the internet. Can you still login to the pfSense webgui at this point?  ==> check logs when the problem is occuring, it might indicate the cause. Can you ping to a public ip (like 8.8.8.8) ? ==> if you can still ping that ip but have no internet, then you have a DNS issue. in other words, we need more data. you can ofcourse just contact pfSense support that was included with your purchase … but if this ends up being an end-user issue, then you might waste precious minutes in the contract. (I have no clue how the official support works, so i'm not sure how the "billing" works)

As explained in French section too: there is no reason to face problem while configuring Daloradius as back-end Radius server assuming this one behaves as real Radius server  ;) limiting connection time using vouchers is straightforward. Using Radius for authentication, I don't know how to achieve it as this would mean to prevent authentication. Coupling captive portal with http proxy (assuming goal is to control HTTP flow) would be easier, IMHO

Definitely matches up with what I expected to see. Completely lost connectivity to the ISP. Your ISP might be able to tell you whether it's likely the modem or the line at fault.

Or you might try leaving don't pull routes unchecked and forcing the SMTP traffic out your WAN gateway in a rule above the pass any any default. Tried it but unable to send mail out. You have to make sure you are using external name servers on the clients behind the VPN. Added the PIA DNS servers to the client which worked. I'm able to send emails out, ran the dns leak test which showed the PIA host IP and PIA's DNS server IP but I'm not able to login to pfSense using the host domain name no longer. I must now use the gateway IP. Do you leave this VPN up all the time or do you only want it active when it's manually brought up Yes I do

I have played alot with my cables yesterday and the # prompt came back. I think it might have something to do with lcdproc reloading everytime a port goes up/down