DHCPd with multiple ipv4 subnets outside of local interface network. (300US$)

deathnite

Im in the same boat. Im sharing my internet connection to a family down the road over a wireless bridge. They cant afford to get internet into their house, and the kids need it for school. This is a routed network over a wireless bridge so I cant extend the interface over to their house to hand out IP's.

I need to turn off my old server to save power (its getting kinda expensive to run just for DHCP).

I'd love to know if this is getting committed in 2.2 as well

I'd also like to donate but not sure I can afford the larger dollar amounts already provided.

Thanks

MnM

Same here - just running a home setup but cant afford the large sums other ppl can donate :( I can squeeze $25 and help the cause but not sure if is acceptable.

marcelloc

Any donation is acceptable for this bounty.

I'll try to push it to 2.2 again soon.

deathnite

Awesome.

Ive sent the bounty to marcellocoutinho@gmail.com

Cheers

Cam

MnM

I have also sent the bounty to marcellocoutinho@gmail.com

Please PM me the instructions and where to get the files from.

MnM

deathnite: did u get the instructions and files? I am still waiting :(

marcelloc

I`ll send it right now

Sorry for the long delay.

And thanks for your donation. :)

MnM

:) Thank you marcelloc!

deathnite

Thanks Mate,

This is a ripper. All my vlans across and working fine. (onto url filtering next)

One bug I did pickup
on the page https://192.168.0.1/status_dhcp_leases.php, when I want to "add a static mapping for this MAC address" for any IP address in the 192.168.1.0/24 range for example.

I click on the button "add a static mapping for this MAC address" it redirects to the page https://192.168.0.1/services_dhcp.php and throws the error "The DHCP Server can only be enabled on interfaces configured with static IP addresses. Only interfaces configured with a static IP will be shown."

This only happens for the addition pools which do not belong to the same interface.

this rocks otherwise.. cheers..Cam

MnM

I am still trying to get this to work as I need it…not much luck :(

Below, I will describe my setup, how it works now and perhaps anyone has an idea to make my setup work with this DHCPd addon?

Pfsesnse 2.1.4

Two physical internal NICs - LAN = 192.168.0.0 and Guests 172.20.0.0
Both LAN and Guests plugged into the same switch.

LAN
Enable DHCP server on LAN interfaceto
Deny unknown clients
All other normal settings plus
Enable Static ARP Entries
Then I have a few DCHP Static Mappings for the interface

Guests
Enable DHCP server on GUEST interface
All other normal settings plus

Now, as the setup above by itself didnt give me what I needed, I modified dhcpd.conf manually with the required settings and then modified /etc/inc/services.inc to write the pfsense dhcpd config to dhcpd.conf.auto (so it doesnt overwrite my config when it reboots) as per below:

/* write dhcpd.conf */
if (!@file_put_contents("{$g['dhcpd_chroot_path']}/etc/dhcpd.conf.auto", $dhcpdconf)) {
printf(gettext("Error: cannot open dhcpd.conf in services_dhcpdv4_configure().%s"), "\n");
unset($dhcpdconf);
return 1;

My dhcpd.conf looks like:

max-lease-time 43200;
default-lease-time 86400;
ddns-update-style interim;

log-facility local4;

DPI Network

shared-network DPI {
# Guests
subnet 172.20.0.0 netmask 255.255.255.0 {
authoritative;
allow unknown-clients;
# don't let clients update A records for ddns;
ignore client-updates;
range 172.20.0.10 172.20.0.30;
max-lease-time 86400;
default-lease-time 43200;
option subnet-mask 255.255.255.0;
option broadcast-address 172.20.0.255;
option domain-name "guest.domain.tld";
option domain-name-servers 172.20.0.254;
option routers 172.20.0.254;
option ntp-servers 172.20.0.254;
allow unknown-clients;
}
# DPI
subnet 192.168.0.0 netmask 255.255.255.0 {
authoritative;
deny unknown-clients;

range 192.168.0.1 192.168.0.9;
max-lease-time 864000;
default-lease-time 432000;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name "dpi.com";
option domain-name-servers 192.168.0.254;
option routers 192.168.0.254;
option ntp-servers 192.168.0.254;
host NAS {
hardware ethernet 00:02:b3:0c:28:54;
fixed-address 192.168.0.5;
}
deny unknown-clients;

range 192.168.0.10 192.168.0.15;
max-lease-time 86400;
default-lease-time 43200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name "dpi.com";
option domain-name-servers 192.168.0.254;
option routers 192.168.0.254;
option ntp-servers 192.168.0.254;
host ps3 {
hardware ethernet a8:e3:ee:7b:ec:b0;
fixed-address 192.168.0.10;
}
deny unknown-clients;

range 192.168.0.20 192.168.0.25;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name "dpi.com";
option domain-name-servers 192.168.0.254;
option routers 192.168.0.254;
option ntp-servers 192.168.0.254;
host oppo93 {
hardware ethernet 00:22:de:89:5c:76;
fixed-address 192.168.0.20;
}
host dunemax {
hardware ethernet 00:16:e8:69:81:e3;
fixed-address 192.168.0.21;
}
host wdhub1 {
hardware ethernet 00:90:a9:a9:13:55;
fixed-address 192.168.0.22;
}
host wdhub2 {
hardware ethernet 00:90:a9:a8:68:b5;
fixed-address 192.168.0.23;
}
host jvc {
hardware ethernet 00:80:88:11:D7:D6;
fixed-address 192.168.0.24;
}
host yamaha {
hardware ethernet 00:a0:de:4c:a6:89;
fixed-address 192.168.0.25;
}
host lg {
hardware ethernet 3c93:11:95:8b;
fixed-address 192.168.0.26;
}
deny unknown-clients;

The above works exactly as I wanted:

A known (defined) device will get an IP form the 192.168.0.0 range.
If an unknown device tries to get and IP address, since its MAC is not defined anywhere it will receive an IP from the 172.20.0.0 network.

This way any guests coming to visit can get a wireless or a wired connection form any Access Point or network point in the house (that's why I am not using VLANs) on the different network than my main network.
Because I have enabled static ARP entries on the LAN interface, guests will not be able to use the LAN interface even if manually entering a 192.168.0.0 (LAN) network address - they will only be able to use the GUESTS NIC and network only.

Now the issue is this - every-time there is an update, I have to manually reconfigure /etc/inc/services.inc then copy my config back to dhcpd.conf
When I get new devices in the house I have manually add them to the dhcpd.conf
Since i am re-directing the output to dchpd.cong.auto the DHCPD logs are not a real representation of what is happening

So I though that with the new code from marcelloc I can get it to work like I have it now and have the added bonus of a GUI to change stuff. But I could not get it to work at all like above :(

pehaps I was wrong the new code form marcelloc doesn't support my configuration? (when i implemented it, it removed ll my custom config as it overwrites the file that I was modifying so basically it was like a normal config).

If anyone has any ideas what to try in the new config form marcelloc to achieve my existing config I am all ears :)

Thanks

marcelloc

@MnM:

Two physical internal NICs - LAN = 192.168.0.0 and Guests 172.20.0.0
Both LAN and Guests plugged into the same switch.

It's not a best practice. The best way is to have a segment for guest and another for lan.

@MnM:

Guests
Enable DHCP server on LAN interface
All other normal settings plus

Guest network on Lan interface?

There are many access points with ap isolation feature and multiple ssids. You can create a guest wifi with if enabled with only one network mask on your network.

The code implements multiple subnets for dhcp but these networks dhcp request on normal situations, came from dhcp relays but not on the same network segment.

MnM

@marcelloc:

Guest network on Lan interface?

Sorry type meant Guest interface.

Thanks for replying. I have a guest wifi on my access point (isolated) - however if I don't run the above configuration I can offer the same for people that come visiting and they plug in their devices into an RJ45 wall socket.

With the setup as it is above I can look after wifi and RJ45 wall socket guests (most of them are actually RJ45 wall sockets as they are teenagers visiting my teenage sons and play games - hence why not so much wifi). The RJ45 wall sockets I have normally have switches in them so my sosn pc, ps3, sound, tv etc are also plugged in to the same network - thats why no vlans cant vlan all the other devices plugging to the same RJ45 wall socket).

Ohh well looks like I will have to stick with manually editing files for now. I was really hoping to have a GUI and make things easier. Not to worry.

Thanks.

haddock

I am interested in testing this.

Would a paypal transfer of 30$ be enough?

marcelloc

@haddock:

I am interested in testing this.

Would a paypal transfer of 30$ be enough?

sure.

Thanks for your interest on donating on this bounty.

haddock

Just a question before donating.

Does static dhcp works also for the additional subnets?
So I can manually configure ip / mac for clients in all subnets?

marcelloc

@haddock:

Does static dhcp works also for the additional subnets?
So I can manually configure ip / mac for clients in all subnets?

Yes.

Multiple dhcp ranges on the same network segment is not a best practice.

haddock

Donation of 30$ has been made.

Will test it out on 2.1.5. once I get the code :)

haddock

It is working well with 2.1.5.

shade

Well, as the top donator (since another person did not pay) I am not quite happy.

The patch breaks if I update my pfSense to newer versions than 2.1.0 (mabee it if because I am on an early sep 2013 patch version).
What happend to inclusion in "main" pfSense, the patch is still not present in 2.1.5 or 2.2.x series ? That was a requirement.
Marcelloc: I reported a bug in the patch back in Feb, and not even a answer from you, therefore is in public: The "Enable network booting" options next-server and filename are not working for sub-pools, only the "head" interface have these setting written to config.

haddock

Testing this further, I have found an implemented feature that is not working correctly and had me spooked for a while until I figured it out.

From testing it affects DNS server / Domain name / Domain search list, including hosts with static dhcp leases, but could be more settings affected. I think it's the global definitions in dhcpd.conf that is the culprit.

option domain-name-servers
option domain-name
option domain-search

It's pretty confusing to explain the issues but here goes, I think it will be easier if I make an example.

Let's say that the pfsense hostname under System –> General setup is:

hostname: pfsense
domain: mycorp.office

This will then generate a global definition on the top row in /var/dhcpd/etc/dhcpd.conf as:

option domain-name "mycorp.office";

So far so good.

Now let's say we want to user different domain-name / search domain / dns for our other subnets.

We start with configuring the subnet that is locally connected to pfsense (default subnet for the LAN interface), not adding any additional pool yet.

Services --> DHCP Server --> LAN

We leave this at default settings.

That would look something like this in dhcpd.conf

subnet 192.168.1.0 netmask 255.255.255.0 {
pool {
range 192.168.1.50 192.168.1.250;
}

option routers 192.168.1.1;
option domain-name-servers 192.168.1.1;

Ok, no problem with this.

Then we define another subnet 192.168.2.0/24

In this subnet we will not be using pfsense as DNS resolver, so we change some settings, dns server, domain name, domain search list.

Then the following config gets generated in dhcpd.conf, as you can see option domain-name-servers get defined twice, I dont know if that is really an issue, but at least its not best practice ;)

subnet 192.168.2.0 netmask 255.255.255.0 {
pool {
option domain-name-servers 10.45.0.10,10.45.0.11;
option routers 192.168.2.1;
option domain-name "mycorp.south";
option domain-search "mycorp.south";
option domain-name-servers 10.45.0.10,10.45.0.11;
option netbios-name-servers 10.45.0.10,10.45.0.11;
option netbios-node-type 8;
range 192.168.50 192.168.2.250;
}

Now, let's say we want to add a client with static dhcp from 192.168.2.0 subnet, and we dont add anything extra to that static config.

host s_lan_0 {
hardware ethernet 11:22:33:44:55;
fixed-address 192.168.2.5;
option host-name "testing";

Now problems arise, this client will now get all the "global config" defined from the 192.168.1.0 subnet, it will not get dns, gateway etc. defined in the 2.0 subnet.

Also, which is what I think is the major issue here, is that the dhcpd.conf static host stanza is entered under the 192.168.1.0 subnet. Like this:

subnet 192.168.1.0 netmask 255.255.255.0 {
pool {
range 192.168.1.50 192.168.1.250;
}

option routers 192.168.1.1;
option domain-name-servers 192.168.1.1;
}
host s_lan_0 {
hardware ethernet 11:22:33:44:55;
fixed-address 192.168.2.5;
option host-name "testing";

I think proper config would be to place static clients after the subnet statement's. so 192.168.2.0 static hosts will have to be defined after the:
subnet 192.168.2.0 netmask 255.255.255.0 {
pool { …
}

I'm sure this will sound confusing, it was even somewhat confusing writing it down, but I hope you get the picture of the problem.

Let me know if you want something explained further.

Seeing shade's post above I think my issue is the same as his:

"- Marcelloc: I reported a bug in the patch back in Feb, and not even a answer from you, therefore is in public: The "Enable network booting" options next-server and filename are not working for sub-pools, only the "head" interface have these setting written to config."