🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.socket
Article #5449

Re: Through FireWall

#5449
From: minoy
Date: Sun, 12 Sep 2004 12:01
40 lines
2598 bytes
Hans Galema <dontusethis@dontusethis.nl> wrote:
>minoy wrote:
>>  I actually want to know this :
>>       A client(C) in LAN behind the Firewall/route(F) want to
>>  connect to a Server(S) in WAN.Suppose that we use the UDP.
>>       Now,Client connects to Server directly use S's IP,and
>>  Send a Message To Server,
>> The Server receive the Client's Message,then Send the response Message to Client,Now,
>> I confused,The Server must connect to Client 
>
>No. Why are you thingking so ? The client just connected to the server
>using the port where the server is listening on. The communication
>then goes over a different port indeed. That port is proposed by the
>client. The IP is the IP as seen by the server.

Sorry,You mistook my meaning.
I want to know that :
    Seeing in the Server side,What's the Client's IP and 
Ports? I know that The IP must be FireWall/Rount'IP,But Which
Port?
    I also confused that a Peer(A) behind the FineWall/Route
 connect to anoher Peer(B) behind the FireWall/Rout,Which IP
the A use to connect to B.
    This is like the MSN,When I am using  the MSN in a LAN talking with my friend also in anther LAN,I find that I and myfiend's IP in MSN arn't 
the LAN IP,and the PORT change when I relogin.
     So I Want to kown: How MSN works?

>
> > use Firewall's IP,But use Which Port?
>
>You have no influence on the proposed port(number). As far as I know:
>when a client can connect with the server than the recommunication
>will be ok too. Do you have other experiences?
>
>> If they connect next time,does the Port change?
>
>The communication port can be different each time yes.
>
>Hans.
Technical Details
Message-ID: <41443a7c$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail
References: <41414382$1@newsgroups.borland.com> <4141485f$1@newsgroups.borland.com> <41418641$1@newsgroups.borland.com> <4142b1b4$1@newsgroups.borland.com> <41442a47$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,82d1fc96f1dc2486
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: "minoy" <spam@spam.com>
Sender: "minoy" <spam@spam.com>
Reply-To: "minoy" <spam@spam.com>
Subject: Re: Through FireWall
Newsgroups: borland.public.cppbuilder.internet.socket
X-User-Info: 61.144.146.192     
References: <41414382$1@newsgroups.borland.com> <4141485f$1@newsgroups.borland.com> <41418641$1@newsgroups.borland.com> <4142b1b4$1@newsgroups.borland.com> <41442a47$1@newsgroups.borland.com>
NNTP-Posting-Host: 207.105.83.66
Message-ID: <41443a7c$1@newsgroups.borland.com>
Date: 12 Sep 2004 05:01:00 -0700
X-Trace: newsgroups.borland.com 1094990460 207.105.83.66 (12 Sep 2004 05:01:00 -0700)
Lines: 41
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail