This time have kept the ping no to verify the data connection is on during the entire test. Attached is the wireshark log for reference. testipv6_8.pcap (57.5 KB)
In the case if the WP76 itself is not able to listen is there any point moving forward to test with PC? Are you suspecting the cm tool not setting up the routes correctly?
PC is showing the same problem, ideally I would have expected the module to behave correctly.
Any pointers what is happening here? The local connection seems to be working so I do not see any issue with the listener and client applications or NC.
I Doubt testing on HL series will result into any conclusion. HL is plain modem working on AT Commands and the TCP Stack inside HL would be handling the incoming client connections.
In case if HL is connected to the PC ( in this case the IP stack used for handling connection is the PC ) it will have the same result as we are seeing in WP and PC.
Is there any other way to know how we can debug this further to resolve the issue?
Android Phone with USB tethering to the PC as listener and the WP76 module as Client.
2 listener were setup one in phone on port 4055 and another in PC on 4058. The WP76 IPv6
client could connect to the listener on 4055 in the phone but not on 4058 in the PC.
It looks like some settings is missing on the PC due to which the client is not able to connect to the listener.
HI I checked out this suggestion on netcat and I am using the openbsd version from the yocto meta layer.
I removed the busybox version and directly used the netcat-openbsd version giving me more option for both IPv4 and IPv6.
btw can you let me know how to set the IPv6 network interface in this rmnet_data0 as the default interface? I believed Cm tool would do it and not bother about what IP was assigned to the rmnet_data0?
A few tests with Android phone Wifi Tethering and USB tethering to PC, it is found that every time the connection is refused when the listener is on the windows PC. Firewall disabled in windows.
On the phone the client connects smoothly to the listener.
Will test further with the linux PC today evening.
I am not sure if nc is doing the binding correctly, from the test till now it seems the client connection never reaches the listener port. tcpdump does produce logs for interface rmnet_data0 but not for port.
Yes Ping to the Public IPV6 address is working correctly. As seen in the above messages the connections do happen in the phones
only when setting up with nc over PC or modules directly the connection is failing. Therefore there is no doubt on the SIM card and the Public Static IPv6 Addressess.
only thing I suspect is the NC and the application code may have some issues. looking into some pointers as below: