Richard Hsu
December 11th 03, 01:37 PM
I am a NAT device developer.
Unfortunately , our NAT device falls into the class
of symmetric NAT in MSN 6.0 .
It means , we can not use peer-to-peer audio conversation.
It is quite strange to me , our NAT mechanism is a PAT ,
a very normal one. We translate all pakets from internal
address to a unique external address, and change the outbound
souce port to demulplex the NAT entry.
Why is our device classified into symmetric one ?? What rule is
applied to classify NAT device ??
I read the STUN RFC 3489 and captured the packet flow between MS MSN
server
and MSN 6.0 client ,couldn't find any clue to fix the problem.
I think , it could be a NAT classification problem and try to fix it.
If possible, could anyone give me some hints , how the MSN 6.0 to
classify the NAT device ,it obeys RFC 3489 or use microsoft's rule ???
Our NAT should be Port Restricted NAT in my opinion.
many thanks in advance
reagrads
Richard
Unfortunately , our NAT device falls into the class
of symmetric NAT in MSN 6.0 .
It means , we can not use peer-to-peer audio conversation.
It is quite strange to me , our NAT mechanism is a PAT ,
a very normal one. We translate all pakets from internal
address to a unique external address, and change the outbound
souce port to demulplex the NAT entry.
Why is our device classified into symmetric one ?? What rule is
applied to classify NAT device ??
I read the STUN RFC 3489 and captured the packet flow between MS MSN
server
and MSN 6.0 client ,couldn't find any clue to fix the problem.
I think , it could be a NAT classification problem and try to fix it.
If possible, could anyone give me some hints , how the MSN 6.0 to
classify the NAT device ,it obeys RFC 3489 or use microsoft's rule ???
Our NAT should be Port Restricted NAT in my opinion.
many thanks in advance
reagrads
Richard