Problem with "TCP Source" module in the client mode

Hi all!

I am trying to build following simple scheme:

Signal source --> TCP Sink (server mode) <---- TCP Source (client mode)
–> GUI Scope Sink

It’s strange but this simple scheme isn’t working.

sockstat shows me:

USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN
ADDRESS
igor python2.7 56206 11 tcp4 10.21.32.6:21950 10.21.32.6:12000

Looks like communication between tcp sink and tcp source blocks has been
established, but tcpdump doesn’t show any packets

I decided to check first part of my scheme (Signal source + TCP Sink),
and connected using netcat utility to the tcp sink port. All looks OK,
the values come as expected.

Can anybody explain, why this simple scheme doesn’t work?

Best regards,
Igor

On 03.03.2014 17:57, Igor V. wrote:

Hi all!

I am trying to build following simple scheme:

Signal source --> TCP Sink (server mode) <---- TCP Source (client mode)
–> GUI Scope Sink

It’s strange but this simple scheme isn’t working.

Are you running both sub-flowgraphs in the same GRC canvas? I just tried
this in 2 canvases and it works. It should work from one, but I’m not
sure GRC is setting things up right.

In any case, try 2 canvases.

M


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

On 03/21/2014 05:52 PM, Tommy T. II wrote:

Dear Martin,

Sorry for the delayed response. My code is all written in C++; I am not
using the GRC. These canvasses; are they separate top blocks?

Yes, and different processes.

M

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs