WARP Project Forums - Wireless Open-Access Research Platform

You are not logged in.

#1 2017-Apr-01 07:38:46

gmkim
Member
Registered: 2016-Jul-19
Posts: 27

.

.

Last edited by gmkim (2020-Aug-17 20:04:17)

Offline

 

#2 2017-Apr-03 10:42:55

chunter
Administrator
From: Mango Communications
Registered: 2006-Aug-24
Posts: 1212

Re: .

The Local Traffic Generation (LTG) subsytem that runs locally on the node can only generate a couple of simple traffic profiles like CBR. This isn't a real transport layer protocol, but it's analogous to UDP. For something complex like TCP, you'd have to make some really significant additions to the LTG subsystem.

Instead, if it's viable to use a host PC in conjunction with your design you might consider using the built-in Ethernet portal to carry TCP traffic generated by your host PC. Depending on what you need to do, you could inspect and modify the frames from the TCP on the WARP kit before transmission.

The wlan_eth_encap() encapsulation code is a pretty good reference on how to inspect the contents of an Ethernet frame. It looks to see if the underlying packet is an ARP or IP frame and acts accordingly.

Offline

 

Board footer