Thanks for a speedy hint  ;D Hmm not sure about whether it is changing, I left the mac adress boxes blank on my lan and lan_port interfaces. Maybe I could generate random macs to put in the spoof boxes and that would stop it?

Installing FreeBSD packages not included in the Package Manager is doable but not recommended. By doing so you introduce security vulnerabilities to your firewall, not a good place to add unnecessary vulnerabilities. Especially when you are adding it for a nice to have feature that you don't need at all. If you must, then search for the forums for how to do it, it can be done.

Hense my apology.

NC360T is Intel  82571EB  based card that is supported by FreeBSD. I currently have one box running  with same chipset and have no problems with cable detection. Does it work on gigabit link? Do you have problem with both ports? Card have LEDs on the both ports, do the LEDs ON/blink when the cable is connected?

I also have a similar problem (Vlan 40 Mnet) .

Are you experiencing across the across the board packet loss (the internet doesn't work at all), or is it particular to your monitor target address? If you are not experiencing across the board packet loss, the easiest guess is that the problem is to particular your monitor address. Try using a different address, such as a google public address such as 8.8.8.8 for monitoring and see if the issue goes away. If it does, you can use traceroute to help you choose an appropriate monitor address.

I'm checking this out more. As we have the export option in the certmanager but it seems that pfsense shows all certificates when you bound the Certificates Page as provilege to the user. It would be nice if you can add the certs to the user and show only these in the certmanager. Anyone some extra information ?

@cluelessvictory: I have ipv6 disabled on pfsense. It doesn't disable anything. Read the checkbox description. The only thing is does is blocking IPv6. If you don''t want the logs spammed, then either allow it, or create a rule to block it without logging.

@malcmail: I presume that still allows the LAN clients to access anything on OPT1? Sure, you always filter what is coming IN on a specific interface. What's coming from your LAN is OUT on Opt1 interface. If you wanted to filter that it would be on the LAN rules tab. @malcmail: If I want to open one item (a printer) to OPT1 users I presume I canset up an allow rule before the deny rule to allow OPT1 net to access 192.168.1.{printer] (clearly with a number instead). Exactly.

Thanks that seems to work description xxx.xxx.xxx.xxx/x description 2 xxx.xxx.xxx.xxx/x xxx.xxx.xxx.xxx/x

Its easy to see quickly your rules if on their own interfaces.  To be honest easier to setup as well for source and destination. Floating rules make sense if you need to do outbound rules.  Or you need some rule that is common that applies to all interfaces sure, floating rules apply before rules on the interface. And with you using aliases and not posting the details of those it makes it very difficult to make heads or tails of your rules.

I managed to get it working today by using a different pxelinux.0 program…. Don't know how I used the wrong one, but I'm glad it's sorted.

Dpinger would not appear in that service list. Couple of things you can do: 1) go to the gateway edit page (System / Routing / Gateways / Edit), scroll to the bottom and press save. See if you get any configuration errors; 2) Go to your gateway log (Status / System / Logs / System / Gateways) and check for error messages from dpinger itself.