From: Christopher Fowler <cfowler@outpostsentinel.com>
To: Kevin K <k_krieser@sbcglobal.net>
Cc: James Carlson <carlsonj@workingcode.com>,
linux-ppp@vger.kernel.org,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sending raw packets via PPP
Date: Tue, 07 Aug 2007 00:32:29 +0000 [thread overview]
Message-ID: <1186446749.29150.40.camel@shuttle.linxdev.com> (raw)
In-Reply-To: <E210D1E9-9265-48EE-91BB-E6027547F01E@sbcglobal.net>
On Mon, 2007-08-06 at 19:24 -0500, Kevin K wrote:
> The DHCP source code therefore wants
> to send raw packets (SOCKET_PACKET) (down to the ethernet addressing
> info).
I can imagine that would be the case. The box requesting the DHCP
address has no IP address. Therefore TCP/IP can not be used at that
point to communicate between the two. I've not had to look at the DHCP
code to see how this works.
WARNING: multiple messages have this Message-ID (diff)
From: Christopher Fowler <cfowler@outpostsentinel.com>
To: Kevin K <k_krieser@sbcglobal.net>
Cc: James Carlson <carlsonj@workingcode.com>,
linux-ppp@vger.kernel.org,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sending raw packets via PPP
Date: Mon, 06 Aug 2007 20:32:29 -0400 [thread overview]
Message-ID: <1186446749.29150.40.camel@shuttle.linxdev.com> (raw)
In-Reply-To: <E210D1E9-9265-48EE-91BB-E6027547F01E@sbcglobal.net>
On Mon, 2007-08-06 at 19:24 -0500, Kevin K wrote:
> The DHCP source code therefore wants
> to send raw packets (SOCKET_PACKET) (down to the ethernet addressing
> info).
I can imagine that would be the case. The box requesting the DHCP
address has no IP address. Therefore TCP/IP can not be used at that
point to communicate between the two. I've not had to look at the DHCP
code to see how this works.
next prev parent reply other threads:[~2007-08-07 0:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 22:45 sending raw packets via PPP Kevin K
2007-08-06 22:45 ` Kevin K
2007-08-06 23:30 ` James Carlson
2007-08-06 23:30 ` James Carlson
2007-08-07 0:24 ` Kevin K
2007-08-07 0:24 ` Kevin K
2007-08-07 0:32 ` Christopher Fowler [this message]
2007-08-07 0:32 ` Christopher Fowler
2007-08-07 10:33 ` James Carlson
2007-08-07 10:33 ` James Carlson
2007-08-07 8:46 ` Matt Keenan
2007-08-07 8:46 ` Matt Keenan
2007-08-07 10:30 ` James Carlson
2007-08-07 10:30 ` James Carlson
2007-08-07 16:53 ` Kevin K
2007-08-07 16:53 ` Kevin K
2007-08-19 23:46 ` Kevin K
2007-08-19 23:46 ` Kevin K
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=1186446749.29150.40.camel@shuttle.linxdev.com \
--to=cfowler@outpostsentinel.com \
--cc=carlsonj@workingcode.com \
--cc=k_krieser@sbcglobal.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.