PfSense running as DHCP server only
-
You can use one NIC with a fake VLAN, or use two NICs and leave one unplugged when it's in production.
Problem might be you'll likely need a default gateway, you can only enter that on the WAN interface, but you can't serve DHCP on the WAN.
-
@cmb:
You can use one NIC with a fake VLAN, or use two NICs and leave one unplugged when it's in production.
Problem might be you'll likely need a default gateway, you can only enter that on the WAN interface, but you can't serve DHCP on the WAN.
Good points. I have it installed with 2 cards in the machine. I set the LAN IP and left the WAN blank. The default gateway is only a slight problem, since I don't need this machine to traverse any routers. If someone wants to get to the mgmt interface, they have to be on that network, which to me is a plus.
Thanks for the input, I just wanted to make sure that the machine didn't rely on an internet connection to continue to function. Like I said, I have one running, and things look OK, but I don't want to find any gotchas 3 months down the road.
-
Why not just install webmin (http://www.webmin.com/) on the existing box?
Basically, just download it, untar it into /usr/local/ or somesuch, then run setup.sh from the webmin directory…
I love pfSense, but for a straight DHCP server, Webmin has more flexibility. -
I've used the webmin before, and I think it's a great product. Unfortunately, what I am trying to do is make these 4 boxes that I have consistent with each other, so that I only have to train people on one interface. Since I have 2 pfSense boxes already, this is the way for me to go. I think it's great that these boxes are this flexible.
Fortunately I don't need an elaborate DHCP server, just the basics + reservations and lease viewing.
What I did for this particular box is install pfSense onto it with 2 NICs installed. Once the install was done, I configured the LAN interface with the LAN IP, and in the WAN, I put 0.0.0.0 as the IP, and for the gateway, I put the IP of the LAN gateway. This changes the routing table so that the machine can get to the internet for NTP, etc… I'm actually kinda psyched that it works this way! The LAN interface just sits there with nothing plugged into it.
-
What I did for this particular box is install pfSense onto it with 2 NICs installed. Once the install was done, I configured the LAN interface with the LAN IP, and in the WAN, I put 0.0.0.0 as the IP, and for the gateway, I put the IP of the LAN gateway. This changes the routing table so that the machine can get to the internet for NTP, etc… I'm actually kinda psyched that it works this way! The LAN interface just sits there with nothing plugged into it.
Hah, that's cool! Nice hack. ;D I assume you mean leave the WAN interface unplugged, not LAN?
This is blog post worthy. ;D http://blog.pfsense.org/?p=157
We were recently talking about adding input validation to the WAN so you can't do what you just did. Typically when the defined gateway isn't within the WAN IP subnet, things won't work. Breaking this ability would be an unintended consequence. Though by the time a production version has that code, it should also be able to add default gateways on the static routes page if you don't want to use a WAN at all.
-
scratches head thats pretty neat and can allow for our "server mode" only that I have planned in the future at some point in time.
-
What I did for this particular box is install pfSense onto it with 2 NICs installed. Once the install was done, I configured the LAN interface with the LAN IP, and in the WAN, I put 0.0.0.0 as the IP, and for the gateway, I put the IP of the LAN gateway. This changes the routing table so that the machine can get to the internet for NTP, etc… I'm actually kinda psyched that it works this way! The LAN interface just sits there with nothing plugged into it.
I think you might even be able to replace the LAN interface with a VLAN-Interface sitting on the WAN-interface –> You only need one NIC.
-
Server only mode would be an awesome feature!
I will be experimenting with this over the holiday break. One question (Mods feel free to delete this if you think I highjacking the thread), do the two interfaces have to be WAN and LAN or can they be LAN and OPT1, say a wireless lan?
-
You always need at least 2 interfaces: LAN and WAN.
Any additional interfaces are OPTx. -
cool thanks for clearing that up!
-
I created a VLAN and assigned it to the WAN with PFSense RC4. So far so good. During the reboot it brings the LAN up and then hangs on the WAN.
On another system with 2 ethernet I have setup
1st Ethernet Port -> LAN
2nd Ethernet Port -> WAN
Wireless -> Opt1
In this configuration with wireless as an accesspoint you can bridge the Opt1 with either the LAN or WAN.I have an ALIX.3C2 board in an outdoor enclosure with 1 ethernet and 1 wireless. Attempting to do the same thing.
Ethernet Port -> LAN
VLAN -> WAN
Wireless -> Opt1Attempts to bridge the wireless on the WAN directly to the LAN do not seem to work and that is why I have tried this approach.
I think this might be another use for not requiring the WAN. It would really be nice to have a WAN override as a hidden option so that it will not be required. A hidden option would protect beginners from ending up with only one interface unintentionally.
I just thought of another potential approach similar to the one mentioned at the beginning of this thread…
Buy a mini-pci ethernet card so the system recognizes another ethernet nic and set that as the WAN. Seems like a messy way to do it but would may work if I can find a minipci ethernet card compatible with FreeBSD. -
Any thoughts on setting up a DHCP relay agent on your Checkpoint firewall? You could then create a new DHCP scope and leveraging your existing DHCP infrastructure. I like to see networks managed centrally - depending on how they are setup this is not possible sometimes (branch offices, etc…). I don't think you can create/use different scopes with the PFSense box, I'm not sure what it uses behind the scenes I'm just starting to play with it to see how I can use it.
