-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error settings socket options for ICMP during Ping #189
Comments
Hi there: for our information, can you indicate which WiFi module this is with? |
Oh, sorry :) |
Oh! Not so much a The AT command manual uses phrases like "If the first |
omg, I'm so sorry, it's very late night already and I needed to go to sleep instead of posting. |
Ah, now I see, 106 == |
It seems that The full command: |
You are right, yes, exactly four. I use default settings for the ping command but it doesn't matter, the result is the same. If it is a connectivity issue why is it always happening the same? only 1 result. The main question is why is it even possible to get errors about the sockets if the ICMP doesn't use them? |
Well, error code 106 is, as written in the AT manual, EDIT: having just looked at the code, (b) is what the module is doing, for instance:
I suspect the only way we will find that out is to set you up for logging the internal behaviour of the module but that will be quite involved, so before we do that, some questions:
|
Let's do that
|
I can't find this |
No, sorry, that is the module code, I was simply posting it to confirm that the module is opening a raw ICMP socket to perform the ping; a socket is being used. |
Please make contact with me at rob.meades@u-blox.com and we can go through the instructions for setting up logging that way rather than trying to do it here. |
I will do my test with the HW tomorrow as I need to go to the office and do the physical reconnection as you described in your email. But in the meantime, by the way, I have to mention that if I turn off uSockGetHostByName just right before my ping command, I don't even get any positive response from the ping, only |
Understood: obviously none of this makes any sense, we need to see what the module is seeing. |
Assuming you're using the |
Sure, after the connection I execute ping function, here it is
|
Thanks: the only thing I'd say is that you are removing the URC handler here:
...pretty much immediately after getting the |
Attachment available until 29. Feb 2024
No, but now I put a delay of 30 seconds before those handlers' removers and the result is better! But anyway, ping gives strange results like this:
+UUPING: 1,64,"www.google.com","172.217.20.196",105,124
+UUPING: 2,64,"www.google.com","172.217.20.196",105,-1
+UUPING: 3,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 4,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 5,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 6,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 7,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 8,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 9,64,"www.google.com","172.217.20.196",0,-1
+UUPING: 10,64,"www.google.com","172.217.20.196",0,-1
TTL and RTT are 0 and -1
and I'm sending you this trace as well.
|
Thanks: that looks much better, I have downloaded those traces and deleted the links from your post. Could the |
I set a 30s delay before the deletion of handlers (uAtClientRemoveUrcHandler) and now there is no more UUPINGER #106, so yes, the "socket" problem was because of the immediate deletion of those handlers. But why do I see these results of 10 pings, I don't understand. |
Understood.
We will need to wait for the relevant expert to look at the log, I will update this issue when I know more. |
The problem is solved by adding more time to wait for ping results |
Understood: I've not heard anything back from the person who was looking into this internally; I will prod them and update this issue when they get back to me. |
Hello,
The question is very simple, how can I get the ping error number 106,
Error settings socket options for ICMP
doing Ping if the Ping itself doesn't need any socket?Ping command, which uses the Internet Control Message Protocol (ICMP), does not directly involve the creation of a socket in the same way that other network communication methods might. ICMP operates at a lower level than TCP or UDP and is used for network diagnostics rather than establishing a connection.
But it's not so simple. I'm receiving one positive answer:
+UUPING: 1,32,"www.google.com","172.217.20.196",109,160
and then right after that
+UUPINGER: 106
The text was updated successfully, but these errors were encountered: