The paper aims to automatically assign IP addresses to machines based on their MAC addresses using DHCP. It does this by initially feeding static IP addresses along with the corresponding MAC addresses and reservations into the DHCP server. Filters are then applied. Thereafter, whenever a machine with a known MAC address connects, DHCP will dynamically assign it the IP address associated with its MAC address. This allows machines to always receive the same IP address each time they connect to the network based on their unique MAC identifier.

1. ASSIGNING STATIC IP USING DHCP IN ACCORDANCE
WITH MAC
ASWIN YEGAPPAN M, DINESH RAVI, BALAKRISHNAN N, KAARTHI S, J. RAMPRASATH
Department Of Information Technology
Dr . Mahalingam College of Engineering and Technology, Pollachi - 642003
Abstract
The paper “Assigning Static IP Using DHCP In Accordance With MAC” aims at automatically
assigning IP address into a machine with respect to the MAC address of the machine. DHCP is a
network protocol that enables a server to automatically assign an IP address to a computer from a
defined range of numbers configured for a given network. Integrating DHCP through the kernel
the allocation of IP is carried over. Initially the IP’s are fed statically for the mac addresses along
with which the reservations are added and filters are applied. Once this process is completed the
IP’s with respect to its corresponding machine’s mac address will be allocated dynamically to the
machine whenever it is identified by the DHCP.
V Reference
1. P. Wu et al., “Transition from IPv4 to IPv6: A State-of-the-Art Survey,” IEEE Comm.
Surveys & Tutorials, Dec. 2012, pp. 1407–1424.
2. B. Carpenter et al., Transmission of IPv6 over IPv4 Domains without Explicit Tunnels, IETF
RFC 2529, Mar. 1999; www.ietf. org/rfc/rfc2529.txt.
3. E. Nordmark, Stateless IP/ICMP Translation Algorithm (SIIT), IETF RFC 2765, Feb. 2000.
4. G. Tsirtsis et al., Network Address Translation-Protocol Translation (NAT-PT), IETF RFC
2766, Feb. 2000; www.ietf.org/rfc/rfc2766.txt. 5. B. Carpenter et al, Connection of IPv6
Domains via IPv4 Clouds, IETF RFC 3056, Feb. 2001;.
5. T. Mrugalski et al., “DHCPv6 Options for Configuration of Softwire Address and Port
Mapped Clients,” IETF Internet draft, work in progress, Mar. 2014.
6. M. Boucadair et al., “(DHCPv6) Options for Shared IP Addresses Solutions,” IETF Internet
draft, work in progress, Dec. 2009.
7. Q. Sun and Y. Cui, “DHCPv6 Option for IPv4 Configuration,” IETF Internet draft, work in
progress, Feb. 2013.
8. B. Rajtar et al., “Provisioning IPv4 Configuration over IPv6 Only Networks,” IETF Internet
draft, work in progress, Feb. 2014.

2. 9. Y. Cui et al., “DHCPv4 Behavior over IP-IP Tunnel,” IETF Internet draft, work in progress,
July 2011.
10. O. Troan, “DHCPv4 over A+P Softwires,” IETF Internet draft, work in progress, June 2013.
11. Y. Cui et al., “DHCPv4 over IPv6 Transport,” IETF Internet draft, work in
progress, Oct. 2013.