ricardgb commented on PR #3630:
URL: https://github.com/apache/nuttx-apps/pull/3630#issuecomment-5067682802

   @linguini1 here are on-hardware test logs from a Raspberry Pi Pico 2 W 
(RP2350), NuttX 13.0.0-RC0.
   
   The mDNS responder was built with `CONFIG_NETUTILS_MDNS_STACKSIZE=8192` — 
the value this PR makes the default — and run over a USB CDC-NCM link (board 
`eth0` 192.168.7.1 ⇆ Linux host `usb0` 192.168.7.2).
   
   **Board — responder starts and answers a live query:**
   ```
   nsh> mdnsd_start
   Local IPv4 address: 192.168.7.1
   Opened 1 socket for mDNS service
   Service mDNS: _http._tcp.local.:80
   Hostname: nuttx
   Sending announce
   ...
   Query PTR _http._tcp.local.
     --> answer nuttx._http._tcp.local. (multicast)
   ```
   
   **Board — responder task running at the 8 KiB stack, no overflow (`ps`):**
   ```
     TID   PID  PPID PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK        
  STACK COMMAND
       8     8     0 100 RR       Task      - Waiting  Semaphore 000...0000     
  0008080 --service _http._tcp.local --hostname nuttx --port 80
   ```
   (The responder task shows an ~8 KiB stack; other tasks are ~2 KiB.)
   
   **Host — discovery / resolution / reachability:**
   ```
   $ avahi-browse -rt _http._tcp
   =   usb0 IPv4 nuttx                     Web Site         local
      hostname = [nuttx.local]
      address = [192.168.7.1]
      port = [80]
      txt = ["other=value" "test=1"]
   
   $ avahi-resolve -n nuttx.local
   nuttx.local  192.168.7.1
   
   $ ping nuttx.local          # name resolved via the board's responder
   64 bytes from 192.168.7.1: icmp_seq=3 ttl=64 time=16.9 ms
   3 packets transmitted, 3 received, 0% packet loss
   ```
   
   The responder runs, advertises, and answers queries at the 8 KiB stack 
without overflowing.
   
   *Disclosure: these tests were run and captured with the help of an AI agent 
(Claude Code, Anthropic); results are from real hardware and human-reviewed.*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to