getting client ip in sock-client on server

[Ankit Aneja]

The code of classes given below is for server to which clients connect
i want to get ip address of client which has connected
pls help how can i get
//listen class
public class listen
{
TcpListener server=null;
Thread tcpthread=null;
client[] cl=new client[3];

public listen()
{
//
// TODO: Add constructor logic here
//
}
public void startlisten()
{
Int32 port = 3310;
IPAddress localAddr = IPAddress.Parse ("192.168.0.6") ;

// TcpListener server = new TcpListener(por t);
server = new TcpListener(loc alAddr, port);

// Start listening for client requests.
server.Start();
// Enter the listening loop.
for(int i=0;i<3;i++)
{
cl[i]=new client();
cl[i].status=true;
}

Boolean flag;
while(true)
{
try
{
flag=false;
// Perform a blocking call to accept requests.
// You could also user server.AcceptSo cket() here.
for(int i=0;i<3;i++)
{
if(cl[i].status==true)
{
cl[i]= new client(server.A cceptTcpClient( ));
tcpthread=new Thread(new ThreadStart(cl[i].getClient));
tcpthread.Start ();
flag=true;
break;
}
}
if(flag!=true)
{
//MessageBox.Show ("All Clients Busy");

}


}
catch(Exception se)
{

}
}

}
public void stoplisten()
{
server.Stop();
}
}


//client class
public class client
{
TcpClient tcpClient;
public Boolean status;
// Buffer for reading data
Byte[] bytes = new Byte[256];
String data = null;
IPAddress localAddr = IPAddress.Parse ("192.168.0.6") ;

public client()
{ //
// TODO: Add constructor logic here
//
//status=true;
}
public client(TcpClien t Client)
{
tcpClient =Client;
//
// TODO: Add constructor logic here
//
status=false;
}
public void getClient()
{
try
{
data = null;
// Get a stream object for reading and writing
NetworkStream stream = tcpClient.GetSt ream();
int i;
// Loop to receive all the data sent by the client.
while((i = stream.Read(byt es, 0, bytes.Length))! =0)
{
// Translate data bytes to a ASCII string.
data = System.Text.Enc oding.ASCII.Get String(bytes, 0, i);
// Process the data sent by the client.
string replyMsg = data;
clamdCommand x=new clamdCommand();
replyMsg=x.Comm and(replyMsg);
int
lowerport=int.P arse(Configurat ionSettings.App Settings.Get("l owerport"));
int
upperport=int.P arse(Configurat ionSettings.App Settings.Get("u pperport"));
for(int y=lowerport;y<u pperport;y++)
{
if(replyMsg==y. ToString())
{
replyMsg=replyM sg+"\r\n\0";
byte[] msg = System.Text.Enc oding.ASCII.Get Bytes(replyMsg) ;
// Send back a response.
stream.Write(ms g, 0, msg.Length);
TcpListener listener=new TcpListener(loc alAddr,y);
listener.Start( );
// Buffer for reading data
Byte[] bs = new Byte[256];
String ds = null;
// Enter the listening loop.
while(true)
{ // Perform a blocking call to accept requests.
// You could also user server.AcceptSo cket() here.
TcpClient bufferclient = listener.Accept TcpClient();
ds = null;
// Get a stream object for reading and writing
NetworkStream strm = bufferclient.Ge tStream();
int l;
// Loop to receive all the data sent by the client.
while((l = strm.Read(bs, 0, bs.Length))!=0)
{ ds = System.Text.Enc oding.ASCII.Get String(bs, 0, l);
// Process the data sent by the client.
clamresults obj=new clamresults();
ds=obj.loadData base("STREAM",d s);

replyMsg=ds;
bufferclient.Cl ose();
break;
}
listener.Stop() ;
x.freeport(y-lowerport);
break;
} break;
}

}
replyMsg=replyM sg+"\r\n\0";
byte[] msgs = System.Text.Enc oding.ASCII.Get Bytes(replyMsg) ;
// Send back a response.
stream.Write(ms gs, 0, msgs.Length);

}
}
catch(Exception se)
{
MessageBox.Show (se.ToString()) ;

}
// Shutdown and end connection
finally
{
tcpClient.Close ();
status=true;
}
}

}

[Goran Sliskovic]

""TerryFei" " <v-******@online.m icrosoft.com> wrote in message
news:9G******** ******@TK2MSFTN GXA02.phx.gbl.. .

Hi Ankit,

In this current situation, I suggest you could try to invoke getpeername /
getsockname using PInvoke mechanism. On a connected socket, getpeername
will give you the remote address and getsockname will give you the local
address for the connection. We could use Socket.Handle Property to get the
socket handle and pass it into these API as parameters.

I hope the above inforamtion is helpful for you.If you have any questions
or concerns, please let me know. Thanks again and have a nice day!

....

The problem is that TcpClient does not expose underlying socket. Socket
TcpClient.Clien t is protected property (holds underlying socket). I suspect
OP could get this using reflection (I heard this is possible using
reflection, but haven't tried it myself and it is bad practice to do this of
course). Socket has RemoteEndPoint property, so it should not be needed to
PInvoke. Haven't tested it, though. Or maybe I missed the original problem?

Regards,
Goran

[Ankit Aneja]

can u give me some sample code
how i can get remote ip without changing much of my present code
"Goran Sliskovic" <gs******@yahoo .com> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. .

""TerryFei" " <v-******@online.m icrosoft.com> wrote in message
news:9G******** ******@TK2MSFTN GXA02.phx.gbl.. .

Hi Ankit,

In this current situation, I suggest you could try to invoke getpeername
/
getsockname using PInvoke mechanism. On a connected socket, getpeername
will give you the remote address and getsockname will give you the local
address for the connection. We could use Socket.Handle Property to get
the
socket handle and pass it into these API as parameters.

I hope the above inforamtion is helpful for you.If you have any questions
or concerns, please let me know. Thanks again and have a nice day!

...

The problem is that TcpClient does not expose underlying socket. Socket
TcpClient.Clien t is protected property (holds underlying socket). I
suspect
OP could get this using reflection (I heard this is possible using
reflection, but haven't tried it myself and it is bad practice to do this
of
course). Socket has RemoteEndPoint property, so it should not be needed to
PInvoke. Haven't tested it, though. Or maybe I missed the original
problem?

Regards,
Goran

[Goran Sliskovic]

"Ankit Aneja" <ef*****@newsgr oups.nospam> wrote in message
news:eb******** ******@TK2MSFTN GP14.phx.gbl...

can u give me some sample code
how i can get remote ip without changing much of my present code

....

Hi,

Here it is:
<CUT>
using System;
using System.Reflecti on;
using System.Reflecti on.Emit;

using System.Net;
using System.Net.Sock ets;

namespace ConsoleApplicat ion1 {
public class Test {
public static void Main() {
TcpListener tcpListener = new TcpListener(IPA ddress.Any, 10000);
tcpListener.Sta rt();
TcpClient client = tcpListener.Acc eptTcpClient();
Type tcpClientType = typeof(TcpClien t);
//get value of protected TCPClient property Client that holds
socket...
Socket clientSocket =
(Socket)tcpClie ntType.InvokeMe mber("Client", BindingFlags.Ge tProperty |
BindingFlags.No nPublic | BindingFlags.In stance , null, client, null);
//socket RemoteEndpoint is address of connected tcpClinet...
IPEndPoint endPoint = (IPEndPoint) clientSocket.Re moteEndPoint;
string remotAddr = endPoint.Addres s.ToString();
}
}
}
</CUT>

Please note that such thing is considered bad practice and potentialy
dangerous. No guarantees.

Regards,
Goran

[TerryFei]

Hi Goran,

Socket has RemoteEndPoint property, so it should not be needed to
PInvoke. Haven't tested it Thanks for your reply! Yes, Socket has RemoteEndPoint property and we could
access relevant address with it in theory. However customer has tried it
and failed. So I suggest use PInvoke to achieve this goal.

Best Regards,

Terry Fei[MSFT]
Microsoft Community Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

--------------------

From: "Goran Sliskovic" <gs******@yahoo .com>
References: <uq************ **@TK2MSFTNGP14 .phx.gbl> <dq**********@s unce.iskon.hr> <Oz************ **@TK2MSFTNGP15 .phx.gbl>
<e0************ **@TK2MSFTNGP10 .phx.gbl>
<Ox************ **@TK2MSFTNGP09 .phx.gbl>
<9G************ **@TK2MSFTNGXA0 2.phx.gbl>Subject: Re: getting client ip in sock-client on server
Date: Fri, 20 Jan 2006 14:03:53 +0100
Lines: 27
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <#q************ *@tk2msftngp13. phx.gbl>
Newsgroups: microsoft.publi c.dotnet.langua ges.csharp
NNTP-Posting-Host: 194-152-209-27.adsl.net.t-com.hr 194.152.209.27
Path: TK2MSFTNGXA02.p hx.gbl!TK2MSFTN GP08.phx.gbl!tk 2msftngp13.phx. gbl
Xref: TK2MSFTNGXA02.p hx.gbl microsoft.publi c.dotnet.langua ges.csharp:3799 94
X-Tomcat-NG: microsoft.publi c.dotnet.langua ges.csharp
""TerryFei" " <v-******@online.m icrosoft.com> wrote in message
news:9G******* *******@TK2MSFT NGXA02.phx.gbl. ..

Hi Ankit,

In this current situation, I suggest you could try to invoke getpeername

/ getsockname using PInvoke mechanism. On a connected socket, getpeername
will give you the remote address and getsockname will give you the local
address for the connection. We could use Socket.Handle Property to get the socket handle and pass it into these API as parameters.

I hope the above inforamtion is helpful for you.If you have any questions
or concerns, please let me know. Thanks again and have a nice day!

...

The problem is that TcpClient does not expose underlying socket. Socket
TcpClient.Clie nt is protected property (holds underlying socket). I suspect
OP could get this using reflection (I heard this is possible using
reflection, but haven't tried it myself and it is bad practice to do this

ofcourse). Socket has RemoteEndPoint property, so it should not be needed to
PInvoke. Haven't tested it, though. Or maybe I missed the original problem?

Regards,
Goran

[Goran Sliskovic]

""TerryFei" " <v-******@online.m icrosoft.com> wrote in message
news:3n******** ********@TK2MSF TNGXA02.phx.gbl ...

Hi Goran,

Socket has RemoteEndPoint property, so it should not be needed to
PInvoke. Haven't tested it

Thanks for your reply! Yes, Socket has RemoteEndPoint property and we

could access relevant address with it in theory. However customer has tried it
and failed. So I suggest use PInvoke to achieve this goal.

....

Hi,

I posted example with tcpclient/remoteendpoint that works (no my lan),
framework 1.1. Though I can guess there may be problems in non-trivial
network setups (NAT for example).

Regards,
Goran