MSP-EXP432E401Y: MSP-EXP432E401Y and CC3120BOOST

Hi,

the MSP432 support team is currently out on 4th of July, but will respond back to you as soon as possible.
Sorry for any inconvenience this may cause.

Best regards,
Andre

Hello Neeraj,

A gateway provides translation services between asymmetric networks, so address transparency is not a must. In this particular example data received on individual interfaces is echo-ed to all interfaces. The MSP432E4 and CC3120 in this case act as a server for this action.

If a specific router function is required then the code needs to be restructured.

Hello Amit,

My post does anticipate that restructuring of the code is required.

But I can't figure out which of the available APIs will be of use.

If I can get some hint about those APIs or some example, please share with me.

From my point of view when TI claims that MSP-EXP432E401Y can be used as a router/intelligent gateway, then what are the APIs that will help me do this?

I also wanted to know if the Raw sockets could be of some help?  

Whether using Raw sockets will be inefficient, and therefore some other API/method needs to be considered to have the router functionality?

--

Regards,

Neeraj Sallh

I will ask for further clarification, but the document you reference makes a distinction between gateways and routers and continues to distinguish intelligent gateways as including resources and intelligence for local applications.

Traditional versus intelligent
gateways
There are several ways to implement an industrial
gateway, depending on the application. Two
common approaches are a traditional gateway and
an intelligent gateway. Both provide consolidated
connectivity by aggregating data from multiple end
points. In general, a traditional gateway organizes
and packetizes data for transport over the internet.
It is also responsible for distributing data back
to end points in applications where two-way
communications are advantageous or required.
Note that a gateway is different from a router. A
router manages similar traffic and connects devices
that share a common interface. For example,
devices that connect to a home router all use IP.
In contrast, because a gateway functions as a
bridge, it must be able to route different types of
traffic, aggregate data from varying communication
interfaces and convert these streams to a common
protocol for access across the WAN. Some devices
might use IP natively, such as Wi-Fi or Thread, while
others might use non-IP-based protocols such
as Bluetooth® or various Sub-1 GHz protocols.
Nodes that are sensors may need to leverage
high-precision analog-to-digital conversion (ADC)
to convert the raw analog voltage to a digital value
before transport.
An intelligent gateway extends the functionality
of a traditional gateway by providing processing

The router functionality is not available.

Chris

Hello Chris,

Thanks for showing interest.

My basic requirement is to be able to use two SIMPLELINK-ETHERNET-WIFI bundles (MSP-EXP432E401Y + CC3120), such that there are two IP networks connected to the two

Ethernet interfaces (of the MSP board).

The WiFi interface will be used to provide the connectivity between the two "SIMPLELINK-ETHERNET-WIFI" bundles.  As a result I will be able to connect to IP networks over the Wireless interface.

Now for IP applications on the two sides should be able to communicate (exchange data frames) with their counterparts on the other side.

There may or may not be NAT implemented (making one side a private network behind the firewall and lets say the other side is the WAN side).

For example, an IP Camera on one side and a VLC player on the other, both should be able to communicate as necessary for the camera video to play on the VLC player.

The two may or may not be having the same IP subnet.

Then there may be more deployments which might say demand that the two IP subnets are different.

Now reading the documents (sway0009.pdf and spru524k.pdf), I think all this should be possible.

But the problem is that I haven't actually implemented a router or a gateway.

The example project "ethernet_wifi_tcp_echo_MSP_EXP432E401Y_tirtos_ccs" is only doing echo of packet received on Ethernet side over to WiFi and vice versa.

This example does not show how to implement a gateway and figuring out the sequence of API calls from "spru524k.pdf" to achieve the gateway functionality was 

not straightforward for me.

So finally what I have been asking is:

1. Which function calls to use from this document "spru524k.pdf" to achieve gateway functionality?
2. I understand that the Cfg* and Nt* calls will be required but
   1. I am not sure of the sequence, 
   2. I am not sure about how to get the WiFi and Ethernet interfaces mapped onto the IP Addresses and then using those addresses in the routes.
3. Also why do the responses to my queries say "the router functionality is not available", whereas "sway0009.pdf " says that 

In Figure 2b, nodes connect directly to the internet
using a WAN connection such as Wi-Fi or Ethernet.
The gateway serves primarily as a router; in fact, it can
actually be a router where the nodes have their own
IoT agent and autonomously manage themselves.

        4. I was even exploring the possibility of using Raw sockets (over Ethernet and Wifi) in order to get a transparent path between the two ends.  This way

            the two sides could just view the connectivity provided between the Ethernet interfaces of the two "SIMPLELINK-ETHERNET-WIFI" bundles simply

            as a channel that passes their Layer 2 Ethernet packets as is (i.e. is a layer 2 connectivity).  

            However, the receive calls over these Raw sockets were failing (EACCES).

            I can explore this in depth too, but need your opinion if my plan of using Raw Sockets will work for the purpose of providing the connectivity (say that of 

            Camera on one side and Video player on the other).

--

Regards,

Neeraj Sallh