Actually by default pfSense installs with an "allow all" rule on the LAN interface. This will allow traffic to any other interface on the box.  When you add a second LAN you will need to copy the default LAN rule to the new interface unless you want to specifically limit traffic.

If you wish to limit traffic between interfaces you would place the "limiting" rule(s) above any "allow all" rule.

LANrules.jpg
LANrules.jpg_thumb

Look at DHCP Static Mappings in Server > DHCP Server

Thank you BlueKobold, but i was hoping to make it work without buying any new devices. But if I buy a Cisco Spaxxx what information do I need from my ISP to configure the Spa.

I pretty sure it will run under special set up conditions and something does the trick for you,  but how more often you will
be using such work around then how more often or at one day nothing really will going ahead or still along the road based
on many "special" things. And how more often you will stay or match the most common or well known way, how better it
will be running with all other things besides or on top of this.

I am afraid my ISP wont give much information.

You will be able to speak to him and tell him also your wishes and needs and then he must tell you something
about his doings and work. I would give it a shot to see if it will be more easy to go with or another solution must
be jumping in here.

@Areomayo:

The above did not solve my problem alone rather a combination.

What fixed it for me was uploading a compiled version of realtek driver 1.92 if_re.ko to /boot/kernel/ and in /boot/loeader.conf.local add the following line: if_re_load="YES" then reboot and wupti.

I also however tick the 3 Disable hardware offloadings in System - Advanced - Networking

Heres some links that helped me solve my issue including the compiled if_re.ko, i hope it helps others having same problem.
https://bugs.freenas.org/issues/1850
https://www.ateamsystems.com/tech-blog/freebsd-pfsense-link-state-re0-watchdog-timeout-errors/

How did you upload that compiled file to the /boot/kernel? I'm ready to do this and can't figure it out (I'm new to this – obviously).

Thanks!

2.4.0 to 2.4.1
But originally it was 2.3 and up to 2.4.0 no problems. I just have openvpn client to connect to PIA VPN

@oscar.atkins:

Hi all,

As the title says, how do I know/find out whether my clients are using PFSense box (their gateway) as the NTP server?

I have configured NTP on the PFSense box but I need to somehow find out if my clients are using it.

For example, I have an Ubuntu client box, in which I see two options for date and time; Manual and From Internet. Since it has internet access, I assume it is getting date and time from the internet. I don't want that, I want them to use my PFSense as the time server and I don't know how to check.

Could anyone please help?

Thanks

Run sudo ntpq -p on the ubuntu server.

It may be using the ubuntu ntp servers.

https://help.ubuntu.com/lts/serverguide/NTP.html

true not like they are expensive I own quite a few of them, just to play with here and there..  I picked up one just a few weeks ago for 88cents for first year.. Haven't done anything with it as yet.. But yes I agree domains can be cheap.. But never as cheap as free like local.lan ;)  And very descriptive to me, etc. etc.  Don't have to worry about anyone using it or grabbing a name I like and forcing me to use a different tld, etc..

But I doubt this OP has multiple pfsense boxes he is trying to manage ;)

if pfsense able to sleep/suspend (S3 level) when there is no network activity, for a period of time ?

And what is when pfSense is the only routing and DHCP device inside of the entire LAN? Who is routing then?
And what is with IDS/IPS on a DMZ or LAN or WAN Port? A network will never really sleep!

i am aware that wake-up would have to be manually done

Why would a firewall have to sleep? It is my WAN / DMZ / LAN device that should be even online and reachable.

So I decided to test some other setups. I've decided to add a quad NIC to the server and allocate a physical NIC to each "VLAN" then just change the PVID for each port according to the VLAN ID required for the virtual NIC in pfSense.

I'm keen to hear from someone that has had VLAN tagged passed through HyperV vNICs however. My HyperV trunk matched a whole lot of documentation I've read, but still go go; I've probably missed something.

If there a better way of doing this?

Not that I can think of.  If you want to resolve your local clients to some bogus domain then you will have to add an entry for every client.  How many boxes are you talking about here?  What is it that you're really doing or trying to test?  You mentioned a web server.  Are you trying to test multi-domain hosting or something, or reverse proxying?

What do you mean?  What are you looking at?

Your question would be better off in the Hardware forum since it's pretty much all about custom builds.

There are many options.  It really depends what what you need to do, and how much you have to spend.  Have you checked out the Netgate store for official pfSense hardware?  The SG-3100 seems to be quite popular rigth now.  Whatever you get, make sure it has an x64 CPU with AES-NI support or you will be orphaned at pfSense 2.4.

What vpn methodology are you using?  OpenVPN, L2TP, or IPsec? The configuration will vary depending on which of these you use.

@JKnott:

I'd expect you'd have trouble finding a computer that could keep up with 100 Gb.  High bandwidth network gear generally uses a lot of custom hardware to handle the processing.

PCI Express lanes are the real problem requiring X16, we have found a motherboard/cpu combo that has no problem pushing 100gbps.  SuperMicro X10SRi-F Motherboard with a Intel Xeon E5-1630v3 is capable of doing so.  So don't be afraid to try different things, this is the current configuration for our 100G test nodes.  We currently have Mellanox, Broadcomm, and QLogic NICs in the field.  Though the Mellanox has proven to be the more stable card at the moment (bleeding edge can be interesting at times).

@ivor:

Current pfSense architecture will be the biggest limitation in achieving such speeds. We have demoed next gen "3.0" which is capable of doing 40Gbps IPsec, so far. We intend to demonstrate 100Gbps IPsec in the following months.

Here's the talk on it by our Jim Thompson https://twitter.com/NetgateUSA/status/923994053015982080

Thank you, I'll give that a look.  We are jumping from 10g to 100g and skipping 40g (probably)

Are you certain it's that mouse and not a virtual connection from the virtual console (does that have a DRAC?)