<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/08/2012 04:40 AM, Alex Bligh
wrote:<br>
</div>
<blockquote cite="mid:239F0311F6B974D60B32164D@nimrod.local"
type="cite">
<pre wrap="">
--On 8 September 2012 08:31:30 +0100 Simon Hobson <a class="moz-txt-link-rfc2396E" href="mailto:dhcp1@thehobsons.co.uk"><dhcp1@thehobsons.co.uk></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">It may even be possible to run the relay agent on the gateway if you can
set it up in some sort of partitioned environment with it's own ethernet
interface such that it uses one interface and it's server traffic goes
via the local wire and back in on the main ethernet interface (and
vice-versa for return packets).
</pre>
</blockquote>
<pre wrap="">
If running under Linux you can use a veth device pair to achieve
this:
ip link add FOO type veth peer name BAR
These can participate in bridges so I'm pretty sure they would work.
I'm not sure you need a separate network container though. I would
have thought some policy routing might be enough.
</pre>
</blockquote>
<font face="sans-serif">Hello,<br>
Faced with the same problem I used a stand alone program from
FreeBSD it compiles on Linux also.<br>
<a class="moz-txt-link-freetext" href="http://www.freebsdsoftware.org/net/dhcprelay.html">http://www.freebsdsoftware.org/net/dhcprelay.html</a><br>
<br>
</font><br>
<div class="moz-signature">-- <br>
Stephen Clark<br>
<b>NetWolves</b><br>
Director of Technology<br>
Phone: 813-579-3200<br>
Fax: 813-882-0209<br>
Email: <a class="moz-txt-link-abbreviated" href="mailto:steve.clark@netwolves.com">steve.clark@netwolves.com</a><br>
<a class="moz-txt-link-freetext" href="http://www.netwolves.com">http://www.netwolves.com</a><br>
</div>
</body>
</html>