Re: How port forwarding programs really work?
- From: Igor Volkin <igor.volkin@xxxxxxxxx>
- Date: Sun, 17 May 2009 04:51:11 -0700 (PDT)
tnx for your response.
that's an idea that could work if we would have some control over the
clients, but we don't. i.e. clients are not really aware that we're in
the middle and they work like they would work if they're connecting
directly to the server. as the server uses just one UDP port for the
communication, all clients are sending their packets to this same
port.
it is possible that maybe the MAC address (written in the ethernet
header which comes before the IP header) could be used to distinguish
between clients...? but if so, I'm not aware that you can read or
manipulate the ethernet header using the raw sockets and that means
this idea is out as well :(...
.
- Follow-Ups:
- Re: How port forwarding programs really work?
- From: Chris Taylor
- Re: How port forwarding programs really work?
- References:
- How port forwarding programs really work?
- From: Igor Volkin
- Re: How port forwarding programs really work?
- From: Chris Taylor
- How port forwarding programs really work?
- Prev by Date: Re: How port forwarding programs really work?
- Next by Date: Re: How port forwarding programs really work?
- Previous by thread: Re: How port forwarding programs really work?
- Next by thread: Re: How port forwarding programs really work?
- Index(es):
Relevant Pages
|