X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80484.0F3D236B@onstor-exch02.onstor.net>; Mon, 1 Oct 2007 15:37:41 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C80484.0F3D236B"
Content-class: urn:content-classes:message
Subject: getsocketname()
Date: Mon, 1 Oct 2007 15:37:41 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E030E3862@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: getsocketname()
Thread-Index: AcgEg5JzXxphrGTSQGi+mlLeCdw3Pw==
From: "Mike Lee" <mike.lee@onstor.com>
To: "dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C80484.0F3D236B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Team:

I'm investigating a RMC misbehavior in the bobcat-linux code, and I've =
narrowed it down to the network function getsockname(), which is called =
by rmc_internal_socket().

I believe we're calling it to retrieve the kernel assigned port number =
and using it as the EEE app id. =20

My question is, do we have our own implementation of getsocketname() for =
linux?

The reason is that the two versions (BSD verus Linux) are behaving =
differently, and causing incorrect RMC routing on my filer.

Thanks.

-Mike



------_=_NextPart_001_01C80484.0F3D236B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>getsocketname()</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Team:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I'm investigating a RMC misbehavior in =
the bobcat-linux code, and I've narrowed it down to the network function =
getsockname(), which is called by rmc_internal_socket().</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I believe we're calling it to retrieve =
the kernel assigned port number and using it as the EEE app id.&nbsp; =
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">My question is, do we have our own =
implementation of getsocketname() for linux?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The reason is that the two versions =
(BSD verus Linux) are behaving differently, and causing incorrect RMC =
routing on my filer.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-Mike</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C80484.0F3D236B--
