"Miraka" <ak_47@abv.bg> wrote in message
news:44eb6fc1$1@newsgroups.borland.com...
> I understand that but it should be possible to for the
> server just to reply through the open socket
That is exactly what the code you showed earlier is actually doing - sending
a reply back to the PeerIP/PeerPort where the incoming data actually came
from. Whether or not that PeerIP/PeerPort cooresponds to an actual client,
or to a router sitting in front of the client, does not make any difference
at all to the server when sending back the reply. If a router is involved,
then as far as the server is concerned, the router *is* the client. What
the router does on its end to make sure the reply data reaches the real
client is outside the server's knowledge or control. Just send the data to
the PeerIP/PeerPort normally, and let the router handle the rest on its end.
> without port forwarding
The only way to send data to a client through a router without using port
forwarding is if the router has been put into DMZ mode, where all inbound
data is immediately forwarded to the client machine without any other
routing rules applied. Otherwise, you must use port forwarding. That is
the only way routers can know which client machine to forward inbound data
to on a per-packet basis.
> because the sysadmin should be a friend of yours to forward a port to your
inner address
Sorry, but port forwarding and DMZ are the only two options in order to get
the data through a router.
Gambit
