AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Bill.Fisher@lsi.com>,<Rendell.Fong@lsi.com>,<Brian.Stark@lsi.com>,<Maxim.Kozlovsky@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	4B072717.20900@lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 20 Nov 2009 16:58:25 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Fisher, Bill" <Bill.Fisher@lsi.com>
Cc: "Fong, Rendell" <Rendell.Fong@lsi.com>, "Stark, Brian"
 <Brian.Stark@lsi.com>, "Kozlovsky, Maxim" <Maxim.Kozlovsky@lsi.com>
Subject: Re: The 192.167.x.y TCP/IP Linux networking legacy hack
Message-ID: <20091120165825.6c26baba@ripper.onstor.net>
In-Reply-To: <4B072717.20900@lsi.com>
References: <4B072717.20900@lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 20 Nov 2009 16:32:39 -0700 William Fisher <bill.fisher@lsi.com>
wrote:

> Folks:
> 
> In the testing of the neteee code and the socket operations
> associated with the protocol, over the mgmtbus, I was looking
> at the NETEEE ifdef's in the Linux tcp/ip
> protocol stack code. There are at least three instances
> that need to be addressed with the new virtual server
> implementation going forward.
> 
> They include:
> 
> 1) The infamous bp0, aka the IP relay device.
>     The current scheme has been ported literally
>     to the txrx and ssc linux driver instances
>     but with the ability to forward standard
>     IP packets over the mgmtbus, we could move
>     to one of the stock IP forwarding encapsulations
>     such as IP over IP, etc.
> 
>     Currently APPID 30 is reserved for this
>     IP forwarding case, but it would be nice
>     to remove some of this legacy going forward.

I'm all for removing things.  Especially since the mgmtbus, as part of
the core product, is history, this can go away.  The daemons will be
running on the 8-way kernel so there shouldn't be any need for this, or
at the least, the loopback device or dbus or something can be used.

> 2) The hard coded "192.167" subnet checks in the
>     Linux routing and datagram code for the TCP/IP
>     stack, route.c, datagram.c, etc.
>     It should be possible to do some sort of
>     special address translation for this reserved
>     subnet using standard tools without having to
>     hack the stock tcp/ip stack. This obviously
>     needs some investigation.

That's history and can be removed as it is no longer used in the virtual
server implementation.  Thank the gods.

> 3) The special IP checksum hack that was added
>     for some special case. I don't know the
>     history of this one.

I'm not sure I do either, is this in the kernel or in the eee code?
