>
> The Cisco PIX firewall does it like this:
>
> clientA: 10.0.0.1===>(PIX)123.4.5.6:5677====>Server
> clientB: 10.0.0.2===>(PIX)123.4.5.6:5678====>Server
Gotcha, the NAT is responcible for port allocation...
> This
> scheme cannot be used with streaming protocols, according to Cisco; I've
> never tried.
Hmm... I'll have to see if I can get the NAT/PAT on my LAN to ship streaming
audio... that's a good question. As UDPs cary Port numbers, just as TCPs, I
don't know why not... though I am certain someone will edumacate me...
Thanks for your time...
>
> Chris
> =======================================
> Chris Slater-Walker BA(Hons) CCNA CCDA MCSE
> Cisco, Windows NT, Linux, Samba, DNS
- Chris
> > > TinyHoffman wrote:
> > > How does the NAT distinguish between sessions with clients who
> > > whish to talk to the same port on the same IP ?
> > >
> > > My Theory: The NAT or the Foreign IP server will issue a unique port
> number
> > > for each session, and the NAT will then reverse-translate the unique
> > > ports to the port that the client expects...
> >
> > I don't know -- suspect it is one of those details that the devil is in
> > ;-)
> >
> > It does seem to work properly -- I've browsed the same sites from
> > adjacent machines, and never seemed to have a problem that I could
> > attribute to the data coming to the (my) wrong client machine.
> >
> > Maybe somebody else can answer your question.
> >
> > regards,
> > Randy Kramer
> >
> >
>
>
>
>
