public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: sebastien dugue <sebastien.dugue-6ktuUTfB/bM@public.gmane.org>
To: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dhcp-users-/1rEenAg/5e+51mZqJFLXQ@public.gmane.org,
	OFED mailing list
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org
Subject: Re: [ewg] DHCP over InfiniBand Update
Date: Mon, 6 Sep 2010 15:03:23 +0200	[thread overview]
Message-ID: <20100906150323.1e1b44c2@frecb007965> (raw)
In-Reply-To: <AANLkTinc9dER+PkBO9Yv=oeGd8NcjFtvSRa7+tXkpb+B-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

  Hi Hal,

On Tue, 31 Aug 2010 16:09:19 -0400
Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Hi,
> 
> There appear to be two basic approaches to supporting DHCP (over
> InfiniBand) in Linux. There's LPF support (4.1.1 based) and older
> (3.0.4 based) socket support.
> 
> The 4.1.1 LPF patches are:
> http://lists.openfabrics.org/pipermail/ewg/2010-May/015265.html
> http://lists.openfabrics.org/pipermail/ewg/2010-May/015266.html
> http://lists.openfabrics.org/pipermail/ewg/2010-May/015264.html
> The last being Matthieu Hautreux's <matthieu.hautreux at cea.fr>
> improved XID generation (same as
> https://lists.isc.org/mailman/htdig/dhcp-hackers/2009-January/001773.html).
> 
> AFAIT an LPF based approach will only work on older kernels (due to
> elimination of CONFIG_FILTER support). Is this accurate ?

  Where have you seen that the LPF approach does not work on recent kernels?
AFAICR, the CONFIG_FILTER disappeared a long time ago. Unless I'm missing
something, you only need the CONFIG_PACKET option.

  Sébastien.


> 
> OFED has two patches for 3.0.4 for a socket approach in
> http://www.openfabrics.org/git/?p=~tziporet/docs.git;a=tree;f=dhcp;h=aec68a2905559c8ed91f1157fa11d78cccb266cd;hb=ofed_1_5
> dhcp-3.0.4.patch
> 0001-Make-DHCP-server-print-HW-info.patch
> 
> I've been upporting those to a 4.x based DHCP and have a fundamental
> question which occurs even with the 3.0.4 socket based version. On the
> client machine, the DHCPOFFER in response to the DHCPDISCOVER is
> received (seen with tcpdump) but never seems to make it to the
> dhclient application. I can't see any kernel stack error counters
> incremented so I'm mystified as to what could be going wrong. I've
> also tried this on a number of different kernels. Any idea on why this
> might be or how to figure out where that packet is going ? I do see
> the dhcp client port with netstat -a --udp -n
> udp        0      0 0.0.0.0:68                  0.0.0.0:*
> udp        0      0 0.0.0.0:68                  0.0.0.0:*
> Any idea on what I'm missing ?
> 
> Also, is any of this work making it's way into a released DHCP ?
> What's the process for this ? Is there some branch in a source
> repository where this work is available ?
> 
> Thanks in advance for any pointers on all this.
> 
> -- Hal
> _______________________________________________
> ewg mailing list
> ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-09-06 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 20:09 DHCP over InfiniBand Update Hal Rosenstock
     [not found] ` <AANLkTinc9dER+PkBO9Yv=oeGd8NcjFtvSRa7+tXkpb+B-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-06 13:03   ` sebastien dugue [this message]
2010-09-06 13:15     ` [ewg] " Hal Rosenstock
2010-09-06 13:26       ` sebastien dugue

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100906150323.1e1b44c2@frecb007965 \
    --to=sebastien.dugue-6ktuutfb/bm@public.gmane.org \
    --cc=dhcp-users-/1rEenAg/5e+51mZqJFLXQ@public.gmane.org \
    --cc=ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox