mgolden

I’ve added a “QNETHERNET_ENABLE_PING_REPLY” configuration macro and renamed the other one to “QNETHERNET_ENABLE_PING_SEND”. I changed these locally, but they’ll be up on GitHub soon so you can try them. Thanks for the idea.

Great, thanks. I wonder which way should be the default - from my point of view both should be on, but maybe I am wrong about that.

(Of course, those places wouldn't probably be putting Teensy 4.1 devices on their networks :) )

I do not personally have a need for it. However, I have worked at places that don't want their networks scanned to determine what is on them. In such circumstances, I would expect them to want to be able to turn off responses. In fact, I think...

I can look into that.

Is it possible for someone to add a separate flag to the stack to disable responding? I suspect that not having that ability would make the use of this code a hard no in some situations.

Somehow I thought it had... I just had another thought. I did notice that even when it wasn't willing to _send_ a ping, it was willing to _respond_ to a ping. (That was one of the reasons I didn't think there was a problem with my soldering!) I...

I am not really sure what just happened. I made all the changes that you suggested, but it still wasn't working. I was able to do a DNS lookup, and the print statement was reporting that QNETHERNET_ENABLE_PING was 1. Then I created a new project...

Oh, I should also say that I have version 0.33.1

Thanks for getting back to me. I should have posted the code with the original question! Below I have attached simpleping.ino and ... libraries/QNEthernet/src/qnethernet_opts.h Note that the printf of QNETHERNET_ENABLE_PING I added right before...

I finally got my act together and soldered my ethernet kit for Teensy 4.1. Now I am running into problems. (I am pretty new at soldering and so there's some chance that the problem is hardware.) When I run the SimplePing program, the ping always...