CC3200MOD: Getting Connection Refuse (-111) Error in AP mode

Hi Yuval,

Can you clarify the setup?

Is CC3200 in AP mode running a TCP server and in parallel used as a TC client trying to connect to another server (what you mentioned as your PC)?

if so, it this PC connected to the CC3200 which is in AP role?

Regards,

Shlomi

Hi Sholmi,

You understood it perfectly.  

CC3200 is in AP mode running a TCP server and in parallel used as a TCP client trying to connect to another server (my PC).

The PC is connected to the CC3200 which is in AP role.

Yuval

Yuval,

Are you able to connect to the TCP server running on your PC regardless of the TCP server running on your CC3200?

I want to make sure it is not an issue with running both server and client concurrently.

Shlomi

Shlomi Itzhak said:

Are you able to connect to the TCP server running on your PC

No, that is the issue.

Shlomi Itzhak said:

it is not an issue with running both server and client concurrently

It is.

Is there a reason why the server and client cannot run concurrently? 

no reason that I know of but I need to check.

Have you tried running each one separately just to make sure they can run while the other is down?

I did run the one scenario where no client connect to the server on the cc3200, same results.

FYI, Since it is in AP mode:

the CC3200 is on IP 192.168.1.1 and listen on port 5001

the http_client is trying to get to the PC on 192.168.1.2 port 5002

So you cannot even connect to the server running on the PC while in AP role.

Since CC3200 has only a single station connection while in AP role, you need to connect with the same station running the TCP server and be able to connect both ways, the PC to the HTTP server on CC3200 and the CC3200 as TCP client to the server on the PC.

Again, I do not see any issue here. I can try myself and let you know.

Shlomi

Hi,

I agree with Shlomi.

At one of my previous project I used TCP server and TCP client running simultaneously at CC3200 in AP mode without any issue. Only issue which I had was support for two TLS sockets only.

I think there two possible reasons of your issue:

• implementation issue inside your CC3200 code (e.g. mixing socket handles for TCP client and server)
• issue with your TCP server at PC (e.g. blocking by firewall). This can be easily determined by running network sniffer (e.g. Wireshark) at your computer

Jan

Thanks, I'll go back and test each socket separately, verify the firewall settings, and hope for the best. I needed clarification that the CC3200 is not preventing me from doing so. 

Thanks Shlomi

Hi Shlomi,

Can you please share your test code?

I'm still fighting it with no success.

Yuval

Hi Shlomi,

When using TCP client on the device, are you using the leased IP as the destination server (or IP address?)

Hi Yuval,

I am running on CC3120 with an external Windows PC using one of our older internal development platforms so I am not sure how it can be useful for you. The application code is straight forward though. I just opened a TCP socket as server and waiting on ACCEPT to receive connection. In parallel, I opened a CP client socket and connected to the IP address of the server behind the AP.

Shlomi

What do you mean by "in parallel"?

Isn't the "IP address of the server behind the AP" the leased IP?

in parallel means that the AP IP address of CC3120 is 192.168.1.1 and the connected station is 192.168.1.2 (leased IP from the AP).

Then, the station acts as a TCP client connecting to the server running on the AP and stay connected while the AP acts as a TCP client and connects to another TCP server running on the connected station.

So in total I have one AP (CC3120) and one station connected to it and each one opens a TCP connection to the other side. Both connections are active concurrently.

Shlomi