netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: jamal <hadi@cyberus.ca>
Cc: Pekka Savola <pekkas@netcore.fi>,
	netdev@oss.sgi.com, shemminger@osdl.org,
	shollenbeck@verisign.com
Subject: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling
Date: Sun, 16 Jan 2005 21:22:54 +0100	[thread overview]
Message-ID: <20050116202254.GD22165@xi.wantstofly.org> (raw)
In-Reply-To: <1105905906.1097.860.camel@jzny.localdomain>

On Sun, Jan 16, 2005 at 03:05:06PM -0500, jamal wrote:

> > Apparently they mis-read the RFC and write the etherip header as 0x0300
> > instead of 0x3000 (they have the version nibble in the wrong place.)  This
> > would likely prevent interoperability.
> 
> Thinking about it a bit - you should be able to break yours to do 0x0300
> to test with them ;->

Etherip is a really simple standard, the header is only 16 bits which
can only assume a single value (0x3000).  Looking at encapsulated packets
with tcpdump makes me 99.99% confident that it's all okay on that level.


--L

      reply	other threads:[~2005-01-16 20:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 22:24 [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling Lennert Buytenhek
2005-01-12 22:42 ` Ben Greear
2005-01-12 22:48   ` Lennert Buytenhek
2005-01-12 23:11     ` Ben Greear
2005-01-12 23:16       ` Lennert Buytenhek
2005-01-12 23:43         ` Thomas Graf
2005-01-13  0:18           ` Lennert Buytenhek
2005-01-13  0:28             ` Thomas Graf
2005-01-13  0:36               ` Lennert Buytenhek
2005-01-13  1:20                 ` Thomas Graf
2005-01-12 23:43         ` Ben Greear
2005-01-13  0:04 ` Stephen Hemminger
2005-01-13  0:29   ` Lennert Buytenhek
2005-01-13  7:49 ` Pekka Savola
2005-01-13  9:23   ` Lennert Buytenhek
2005-01-16 17:37     ` jamal
2005-01-16 18:55       ` tunneling in linux (was: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling) Lennert Buytenhek
2005-01-16 19:51         ` Pekka Savola
2005-01-16 19:57           ` Lennert Buytenhek
2005-01-17  5:45             ` Pekka Savola
2005-01-16 20:02         ` jamal
2005-01-16 20:20           ` Lennert Buytenhek
2005-01-16 20:37             ` Hasso Tepper
2005-01-16 21:21               ` Lennert Buytenhek
2005-01-16 21:32                 ` Hasso Tepper
2005-01-16 21:44                   ` Lennert Buytenhek
2005-01-16 23:09             ` jamal
2005-01-16 19:02       ` [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling Lennert Buytenhek
2005-01-16 20:05         ` jamal
2005-01-16 20:22           ` Lennert Buytenhek [this message]

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=20050116202254.GD22165@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=pekkas@netcore.fi \
    --cc=shemminger@osdl.org \
    --cc=shollenbeck@verisign.com \
    /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;
as well as URLs for NNTP newsgroup(s).