TNC w/TCP connection - Integration

[rtubio]

Task to handle the integration process with a TNC that can be accessed through a local TCP connection.

To do this, it is highly recommendable to go through the following steps:

1. Implement a new command line argument so that the client can be executed with the following parameters:

python client_amp.py -g -u crespo -p cre.spo -t 2 -c tcp -i 127.0.0.1 -u 5001

2. The UDP connection mode that is already implemented is a very good starting point for this issue. Find out how it is implemented along the code and try just to copy it and modify this new copy in order to implement the TCP connection.

3. There are some automated tests that were created in order to implement the continuous integration process for the application. Maybe it is worth to take a look at them as well and try to implement the new test for the TCP conneciton.

[rohling]

There are diagrams of the implementation of generic-client? t will be helpful in understanding the code ...

[rtubio]

@sgongar : do you have any diagrams about the client?

[rohling]

The TCP connection mode is implmented. But the UDP connection mode that is already implemented not is stable, and TCP connection mode this with the same problem .... during the call function "procressframe" from the object gsi.

Failure: exceptions.TypeError: unbound method _processframe() must be called with ClientProtocol instance as first argument (got GroundStationInterface instance instead)

[rtubio]

@sgongar : can you give a hand on this to @rohling ?

[Jespindoladiaz]

The problem is this: The computer where the client is installed SATNET is different to where the TNC of ISIS, so it is important that the client listen on a variable IP address and a variable port, in this case the computer's IP ISIS: 161.24.19.170:7777

[sgongar]

Actually some parts of the program are "patched" for initial tests and are working in local mode.
I will look if this point is good or not.

[rtubio]

@sgongar : that should not be a problem, we should support both local and remote connections without the necessity of patching.... is there any issue that we are not aware of for this matter?

[rtubio]

@rohling : how are you doing with this issue? Do you need any help?

[rohling]

@rtp-calpoly : already implemented and merged the pull request: bd51211

[rtubio]

@rohling : ok, perfect! Have you tried using it with the real TCP connection with the ISIS software?

[rohling]

@rtp-calpoly: As I wrote above: the UDP connection mode that is already implemented not is stable, and TCP connection mode this with the same problem .... during the call function "procressframe" from the object gsi.
Failure: exceptions.TypeError: unbound method _processframe() must be called with ClientProtocol instance as first argument (got GroundStationInterface instance instead)

I get an error when I create a socket client and forward a frame for the generic-client.(UDP/TCP)

[rtubio]

@sgongar : can you take a look at this?

[rtubio]

@rohling : working on your branch for this TCP implementation, can you try to fix the bug?