NDK_EALREADY error is not being translated in slnetif layer

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Network Development Kit
    • NDK-492
    • NDK_3_70_00
    • NDK_3_75_00

      If you attempt to set TCP_SACKPERMITTED with setsockopt() on a socket that already has SACK enabled, NDK_setsockopt() will set fderror to NDK_EALREADY. 

       

      However if you call setsockopt() from NS it will go through NDK's slnetifndk layer. Here the NDK_EALREADY error is not properly translated and sent to NS. 

       

      To fix this getBSDSlNetErr() in slnetifndk.c needs to add the following code 

               case NDK_EALREADY:
                  ret = SLNETERR_BSD_EALREADY_ENABLED;
                  break;

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-2144 - NDK_EALREADY error is not being tra...
                SYNCHRONIZED
                • Last Sync Date: