Single NIC install
-
This post is deleted! -
Assigning only WAN has been fine for 6-7 years now, all 2.x versions. Prior to that, LAN and WAN were a requirement (though some people ran single interface back then too just assigning a dummy VLAN as the unused LAN).
-
This post is deleted! -
This post is deleted! -
No. (Why does it matter, though?)
-
This post is deleted! -
If you are going to use this as a DNS server appliance on LAN - wouldn't this be behind a firewall already? Can really just turn off the packet filter altogether.
-
This post is deleted! -
WAN. And you shouldn't end up locked out of the firewall. When you only assign WAN, then access is allowed on WAN until you create another interface. Though, as said, just can disable the packet filter altogether. The wizard is not really useful for this type of setup, just skip it.
-
This post is deleted! -
-
This post is deleted! -
Well, seems like you are doing something basic very wrong. With pf off, there's really nothing to block packets.
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
you seem to misunderstand something.
why do you want to hand out a different gateway IP address via DHCP?
-
why do you want to hand out a different gateway IP address via DHCP?
Probably because pfSense isn't the gateway … (yeah, go figure why ... ;))
-
This post is deleted! -
I just changed the setup of the DHCP IPv4 server (running from the default 192.168.1.1 on LAN)
"Gateway" was empty, I filled in "192.168.1.254" and restarted the DHCP IPv4 server on pfSense.I ripped out the RJ45 from my computer, and put it back in (my PC requested a new IP among others).
Guess what, the IP handed out was the same, DNS was still 192.168.1.1 but the Gateway was … 192.168.1.254 ;D
Yes .. my setup isn't broken - pfSense worked ... again.
