<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.32">
<TITLE>RE: [OLSR-users] DHCP on an OLSR net</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I've been testing a plug-in I've written which forwards DHCP messages using OLSR. Mobile nodes that are already 'configured' start up a DHCP relay server (written in Python/Twisted) listening on port 67. When a DHCP Discover/Request message is heard it gets forwarded to the plug-in via TCP/IP IPC interface and flooded. [there is a random delay before forwarding to limit the number of configured nodes from forwarding the message]. A gateway node is configured to to unicast the DHCP message to the DHCP server which resides on a separate subnet not on the MANET. The DHCP Offer/Ack goes back over OLSR and the configured mobile node responsible for first forwarding the Discover/Request message broadcasts the response back to the configuring node. I've left out many details but that is basically how it works.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: olsr-users-bounces@olsr.org on behalf of Jon Smirl<BR>
Sent: Thu 2/8/2007 8:51 PM<BR>
To: OLSR discussion and development<BR>
Subject: [OLSR-users] DHCP on an OLSR net<BR>
<BR>
Is there any way for DHCP to work on an OLSR mesh? It seems like it<BR>
could propagate out from the DHCP server as each hop came up. A node<BR>
that wasn't part of the mesh yet would just send out broadcast<BR>
requests until it got assigned an address.<BR>
<BR>
--<BR>
Jon Smirl<BR>
jonsmirl@gmail.com<BR>
<BR>
_______________________________________________<BR>
olsr-users mailing list<BR>
olsr-users@olsr.org<BR>
<A HREF="https://www.olsr.org/mailman/listinfo/olsr-users">https://www.olsr.org/mailman/listinfo/olsr-users</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>