Quick update. I manage to compile it by adding this line on the top:
#include <arpa/inet.h>
But now I am unable to connect. I get those errors:
(base) ➜ RGMII_AT_Client ./quectel_client
RGMII-AT Client Up => 192.168.225.1:1555
Can Not Connect To => 192.168.225.1:1555
Can Not Connect To => 192.168.225.1:1555
Can Not Connect To => 192.168.225.1:155
I can connect with telnet, but I get no response from at commands.
Can you please send me the details?
Thank you,
Hey im considering on doing the same for my rm500-ae, having at-commands over ethernet. But im installing tailscale firstly. But may i also have that same email?
This “Client” application is not functional at all.
I can get it to compile no problem but it reports that it’s not making a connection, but yet it still seems to send some data to the open socket (1555) however the output is atrocious and unusable. There must be some other tool being used internally by Quectel to test and validate this functionality. I assume the Quectel software validation team (SVT) are using something that provides a better output response then this application???
@svandive Could you show the log or some pictures?
Can you ping the 192.168.225.1?
As I know not all the module suuport the AT over ETH.
As I stated in my comment, I can successfully telnet to port 1555 and I can see the response “RGMII_ATC_READY” so I know the socket is open. I also have a packet capture from running the tool, and can see the session connect, the response “RGMII_ATC_READY” come from the modem, the ATI command being sent, but no response back from the modem.
I was going to upload the packet capture here, but I guess I can’t upload pcap or .gz files.
I don’t know what you are concerned about now. Is it that eth_AT doesn’t work or that it can’t upload files?
If you are using Open firmware, you can use tftp to transfer files.
