IPSec support for NDK

Mark Depp

Hello All

I am using NDK 2.0 with DM648. I want to know whether the NDK 2.0 supports IPSec or not. I just want to route an IPSec packet from the EVMDM648 using NDK 2.0.

Regards

Mark

over 14 years ago

0 Steven Connell over 14 years ago

TI__Mastermind 45025 points

Hi Mark,

Unfortunately, I don't think the NDK supports IPSec. I inspected the code just to be sure and I see that the following defines in socket.h:

//
// Protocols
//
#define IPPROTO_IP      0               // IP Placeholder
#define IPPROTO_ICMP    1               // ICMP
#define IPPROTO_IGMP    2               // IGMP
#define IPPROTO_TCP     6               // TCP
#define IPPROTO_UDP     17              // UDP
#define IPPROTO_IPV6    41              // IPV6
#define IPPROTO_ICMPV6 58              // ICMPV6 Header.

I also see the switch statement which handles IP packets received (IPRxPacket() in ipin.c) does not handle IPSec (protocol number 0x50):

            // Dispatch the IP packet
            switch( pIpHdr->Protocol )
            {
            case IPPROTO_TCP:
                TcpInput( pPkt );
                break;
            case IPPROTO_UDP:
                UdpInput( pPkt );
                break;
            case IPPROTO_ICMP:
                ICMPInput( pPkt );
                break;
            case IPPROTO_IGMP:
                IGMPInput( pPkt );
                break;
            default:
                ips.Delivered--;
                ips.Noproto++;
                RawInput( pPkt );
                break;
            }

Steve

0 Mark Depp over 14 years ago in reply to Steven Connell

Intellectual 765 points

Steve

I have successfully enabled IPSec support in DM648EVM with NDK.Please help me with the following,

I am using NDK 2 with EVMDM648 HelloWorld Application in switch mode (ALEBypass). http://processors.wiki.ti.com/index.php/Network_Developers_Kit_FAQ states that due to EMAC limitation DM648 can only support Jumbo Packets upto 2047 bytes. However Marvell Alaska 88E1111 PHY which is used in DM648 gives full Jumbo Packet support. I just want to activate the Jumbo Frames on my board even if it only gives me 2047 bytes compatiblity as described on the NDK FAQ page refered above because I will still have more bytes than 1514 in standard packets.

Regards

Mark

0 David Friedland over 14 years ago in reply to Mark Depp

TI__Mastermind 18320 points

Please refer to the link below for more details -

http://processors.wiki.ti.com/index.php/Network_Developers_Kit_FAQ#Q:_Does_NDK_support_Jumbo_Packets.3F

http://processors.wiki.ti.com/index.php/Network_Developers_Kit_FAQ#Q:_C6455_EVM_has_a_Gigabit_EMAC._Does_the_hardware_support_Jumbo_Packets.3F

0 Mark Depp over 14 years ago in reply to David Friedland

Intellectual 765 points

Steve

I am waiting for your response.

0 David Friedland over 14 years ago in reply to Mark Depp

TI__Mastermind 18320 points

Sorry Mark -- Steve is actually out until Monday. Did the links I pointed you to help?

0 Mark Depp over 14 years ago in reply to David Friedland

Intellectual 765 points

David

No they only tell that only Mezanine board of C6455 has the Jumbo frame capability. However according to those pages DM648 can support Jumbo upto 2047 bytes. I require that feature how can i enable it using the HelloWorld Applicaition in switch mode? I hope you or Steve will help me out.

0 Steven Connell over 14 years ago in reply to Mark Depp

TI__Mastermind 45025 points

Hi Mark,

Sorry, I was on vacation and so I didn't see your forum posts.

The NDK's jumbo packet support and stack code is surrounded by #if statements like the following:

#ifdef _INCLUDE_JUMBOFRAME_SUPPORT

/* <some jumbo packet code or call...> */

#endif

Unfortunately, the standard NDK libraries that are shipped in the product were not built with _INCLUDE_JUMBOFRAME_SUPPORT defined.

So, you would need to rebuild the NDK libraries and specify this define as an option to the compiler (i.e. "-D_INCLUDE_JUMBOFRAME_SUPPORT")

Please see this wiki for steps on how to rebuild the NDK libraries.

http://processors.wiki.ti.com/index.php/Rebuilding_the_NDK_Core

Steve

0 Mark Depp over 14 years ago in reply to Steven Connell

Intellectual 765 points

Steve

The page you referred about rebuilding the ndk core describes the process for CCSv4. Can i have one for CCSv3.3.

Also please tell me that are these the only 2(giving the compiler option & rebuilding the core) required steps and after that the jumbo packet will be routed?

Regards

Mark

0 Steven Connell over 14 years ago in reply to Mark Depp

TI__Mastermind 45025 points

Mark,

I apologize, I misinformed you somewhat because I thought that you were on the latest NDK. I see from your original post that you are on NDK 2.0. This makes things easier actually.

NDK 2.0 comes with the jumbo libraries. You should only need to link them into your application in place of the "normal" ones. The libraries are:

netctrl_jumbo.lib
nettool_jumbo.lib
os_jumbo.lib
os_sem_jumbo.lib

Steve

0 Mark Depp over 14 years ago in reply to Steven Connell

Intellectual 765 points

Hello Steve

I removed the netctrl.lib, nettool.lib, os.lib and os_sem.lib from the project and added the ones you refered. Then compiled the project but still i m unable to route a packet of jumbo category. I passed the packet of around 1900 bytes keeping in view the 2047byte restriction for DM648 EMAC buffer. However I recieved the EMAC_send() packet returned 3000028 error. Please tell me what is missing here. Also note that when i incresed the buffer size in ethdriver.c the emac failed to register upon program execution. I also tried to increase the rxbuffer size in ethdriver.c and RXMAXLEN in cpsw3g_init_cfg.h file but in vain the packet was returned.

Regards

Mark

0 Steven Connell over 14 years ago in reply to Mark Depp

TI__Mastermind 45025 points

Hi Mark,

I'm not sure that you need to change the sizes of the buffers in ethdriver.c; that doesn't sound right to me.

Can you put break points at each of the jumbo APIs to make sure that they are being called (and to make sure that they are linked into your app)?

_jumbo_mmInit()
jumbo_mmAlloc()
jumbo_mmFree()
_jumbo_mmCheck()

Thanks,

Steve

0 Mark Depp over 14 years ago in reply to Steven Connell

Intellectual 765 points

Steve

I cannot find the function definitions or calling to these functions in my whole code. I can only find their declaration as external functions such as _extern _jumbo_mmAlloc().

Please tell me in which file they are present so that i can put the break point and tell you.

Regards

Mark

0 Steven Connell over 14 years ago in reply to Mark Depp

TI__Mastermind 45025 points

Hi Mark,

If you enter the function name into the disassembly window and hit enter, it should take you to the assembly code for that function. You can then add a breakpoint from within the disassembly window. You don't need to have the source files. (note that you can also set a break point in a similar fashion using the break point manager). When you run the program, you should see the PC hit your B.P. within the disassembly window.

Regarding jumbo frame support, I've contacted some engineers who know more about this than I do. Here's what they replied with:

You should be able to build the OSAL, NetCtrl and the stack with _INCLUDE_JUMBO_SUPPORT defined. To quickly test jumbo packets, you can run a ping with a large size packet; and ensure that ping between NDK and the other device is not fragmented. This would essentially test the Jumbo packets data path through the stack.

For the above, there's no need for you to rebuild as you're linking in the *_jumbo versions of the libraries (confirmed by setting the breakpoints at those jumbo functions as mentioned previously)

Steve,

In the old NSP release (NDK 2.1?), you don’t need to modify the Ethernet driver, since ETH_MAX_PAYLOAD is used in the Ethernet driver and it is defined in ndk\inc\stack\inc\etherif.h:

/* Maximum Ethernet Payload Size. */

#ifdef _INCLUDE_JUMBOFRAME_SUPPORT

#define ETH_MAX_PAYLOAD 10236

#else

#define ETH_MAX_PAYLOAD 1514

#endif

0 Lakshmanan Kuppan over 11 years ago in reply to Mark Depp

Intellectual 330 points

Hi Mark/Steve,

I am not clear about enabling IPSec with NDK . Is NDK able to receive IPSEC and transmit IPSEC packets?

Is NDK will do the IPSEC for the IP packets?

Thanks in advance.

Regards,

K. Lakshmanan

0 Steven Connell over 11 years ago in reply to Lakshmanan Kuppan

TI__Mastermind 45025 points

K. Lakshmanan,

The NDK does not support IPSec. Mark must have updated the NDK sources himself to add this feature to the stack. The NDK ships with full source code that is buildable so you can try this yourself, but we won't be able to provide much support with that.

Steve

0 Barry Andrews over 11 years ago in reply to Steven Connell

Genius 3460 points

Hello Steve

Do you know if there is any intention to add IPSEC to NDK or third party stack compatible with TIRTOS which supports IPSEC?

This is something we may require and I am not sure we have capacity to add ourselves.

Thanks

Barry

0 Steven Connell over 11 years ago in reply to Barry Andrews

TI__Mastermind 45025 points

Hi Barry,

We will be adding support for SSL (working with a 3rd party) in an upcoming release of TIRTOS. I don't believe we have IPSEC on our roadmap.

Steve

Processors

Processors forum

IPSec support for NDK