Have you ever wanted to intercept DHCP requests and squeeze in a few extra DHCP options, unbeknownst to the sender? Probably not. However, should the need ever come, dhcpoptinj will (hopefully) help you.
There can be many a reason to mangle DHCP requests, although chances are you ought to look for a much better method for solving your problem. Perhaps you do not have access to the DHCP server/clients and need to modify their DHCP options, perhaps the DHCP software is difficult to configure (or does not support what you want to do), perhaps you have a very complex and/or odd setup, or perhaps you just want to experiment sending exotic or malformed options? There is a small chance that dhcoptinj might actually be of some use.
dhcpoptinj waits for packets to arrive in a netfilter queue. It will ensure that a packet is in fact a BOOTP/DHCP packet, and if so proceed to inject options. It will recalculate the IPv4 header checksum, disable the UDP checksum (for a simpler implementation) and then give the packet back to netfilter.
You need an iptables rule in order to intercept packets and send them to dhcpoptinj. Let us say you have two interfaces bridged together, _ eth0 _ and _ eth1 _ . Let us say you want to intercept all BOOTP requests coming from _ eth0 _ and inject the relay agent information option (82/0x52). Let us make up a silly payload: An agent circuit ID sub-option with the value "Fjas".
Add a rule to the iptables mangle table:
sudo iptables -t mangle -A PREROUTING -m physdev --physdev-in eth0 -p udp --dport 67 -j NFQUEUE --queue-num 42 .
Then run dhcpoptinj (let us run it in the foreground with extra debug output):
sudo dhcpoptinj -d -f -q 42 -o'52 01 04 46 6A 61 73' . Note that dhcpoptinj must be run by a user with the CAP_NET_ADMIN capability. You do not need to, and you really should not run dhcpoptinj as root. Instead, you can for instance grant the CAP_NET_ADMIN capability to the binary (using _ setcap _ ) and limit execution rights to only a specific user or group. This is a method used for running wireshark as non-root, so you will find several guides helping you accomplish this.
Now send a DHCP packet to the _ eth0 _ interface and watch it (using a tool like wireshark ) having been modified when it reaches the bridged interface. It should have the injected option at the end of the option list. If you capture the incoming DHCP packet with Wireshark, it will appear unmodified although it will in fact be mangled.
Note the format of the argument to the _ -o _ option: It should be a hexadecimal string starting with the DHCP option code followed by the option payload. The option length (the byte that normally follows the option code) is automatically calculated and must not be specified. The hex string can be delimited by non-hexadecimal characters for readability. All options must have a payload, except for the special pad option (code 0).
Code | Length | Data
52 | (auto) | 01 04 46 6A 61 73 ("Fjas")
Sub-opt. | Length | Data
01 | 4 | 46 6A 61 73 ("Fjas")
Note that dhcpoptinj does not care about what you write in the option payloads, neither does it check whether your option code exists. It does however forbid you to use the option code 255 (the terminating end option). dhcpoptinj inserts this option as the last option automatically.
dhcoptinj is quite a simple program and should be unproblematic to build.
You need cmake and libnetfilter_queue (and a C compiler that supports C99). Hopefully, you are using a Debian-like system, in which case you can run the following to install them:
sudo apt-get install cmake libnetfilter-queue-dev .
git clone git://github.com/misje/dhcpoptinj
cmake -DCMAKE_BUILD_TYPE=Debug .if you want a debug build)
sudo make install
sudo make uninstallfrom your build directory
The build directory with all its contents can be safely removed. If you did not use a build directory, you can get rid of all the cmake rubbish by running
git clean -dfx . Note, however, that this removes everything in the project directory that is not under source control.
This readme should have got you started. There is no man page for dhcpoptinj, but the help (
dhcpoptinj -h ) should cover everything the utility has to offer.
For bugs and suggestions please create an issue.
dhcpoptinj is simple and will hopefully stay that way. Nonetheless, the following are missing features that hopefully will be added some day:
Most likely you do not have CAP_NET_ADMIN capability or there is another process (perhaps another dhcpoptinj instance?) bound to the same netfilter queue number.
I am not experienced in the netfilter library. There may be (although I cannot promise) bugs.
This issue is not fully investigated yet.
This is not considered a leak. However, there should be no memory leak on a normal exit (catching SIGTERM, SIGINT or SIGHUP).
When creating iptables rules to use with dhcpoptinj, the following options can be useful:
Do not drop packets, but let them pass through if dhcpoptinj is not running (or not listening on the correct queue number).
If you have any suggestions please leave an issue, and I will come back to you. You are welcome to contribute and pull requests are much appreciated.
If you find dhcpoptinj useful I would love to hear what you are using it for. Update the wiki page and describe your use.