Skip to content

Future Work

Joe Antony edited this page Dec 1, 2017 · 27 revisions

Proposed Changes To Make The Code Scalable

Modifications in DHCP Server Configuration

  • The current server configuration provides IP addresses to incoming clients from a single address pool.
  • This pool consists of IP addresses from only the server's subnet.
  • The InstallDhcpServer() function adds all the attributes of the server including its own IP address and launches the start application.
  • This should be split into 2 separate functions :
    • ApplicationContainer InstallDhcpServer(Ptr<NetDevice> netDevice, Ipv4Address serverAddr, Ipv4Mask Mask)

      This function will allocate the server IP address to the Ptr argument passed, install a default traffic control configuration, creates a DHCP server app and returns that pointer.

    • void AddAddressPool(ApplicationContainer dhcpServerApp, Ipv4Address minAddr, Ipv4Address maxAddr, Ipv4Address gateway)

      It will add the IP addresses in the given range i.e. within minAddr and maxAddr, as a pair along with given gateway to m_availableAddresses (a map consisting of gateway and IP addresses allocatable a subnet).

Modification in DHCP Relay Agent Configuration

  • Our current implementation supports only two subnets - one having the DHCP server and the other for incoming clients.

  • We have written two functions to initialize client and server side :

    • Ipv4InterfaceContainer InstallFixedAddress (Ptr<NetDevice> netDevice, Ipv4Address addr, Ipv4Mask mask)
    • ApplicationContainer InstallDhcpRelay (Ptr<NetDevice> netDevice, Ipv4Address relayAddr, Ipv4Mask subMask, Ipv4Address dhcps)
  • Hi

Clone this wiki locally