Wrong NAT detection with pjstun_client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 22, 2008 at 3:23 PM, Alain Totouom <alain.totouom at gmx.de> wrote:
> Hi,
>
>
>  Helmut Wolf wrote:
>  > Hi Benny,
>  >
>  > In RFC 3489 the situation is not described if we got no response from the alternate server. I think this is a special network
>  > configuration I have tested :-)
>  >
>
>  IMHO this assertion is not correct.
>  In such a case you might have 3 possible NAT types
>  - a port restricted (Test #1 & #3)
>  - a restricted (Test #1 & #3)
>  - or a symmetric NAT (Test #1)
>
>  depending on one (Test#1) or two (Test #1 & #3) additional tests you'll have to
>  perform after Test#2 has failed. Please check rfc.3489 page 21 for clarity.
>

This may not be possible since test 1B failed with no response.
Perhaps at best what we can do is something like this:

 if (test 1B failed with no response) {
   if (test 3 is successful)
      Type=Restricted;
   else
      Type=unknown (can't distinguish between Port Rest. and Symmetric).
 }

What do you think?

Cheers
 Benny



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux