Christian Mauderer commented on a discussion on package/libbsd/developer/network_drivers.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/50#note_113864 > + Windows). Otherwise Wireshark can't detect checksum errors. Start > Wireshark > + on that interface on the PC. > +#. Start LibBSD `media01` test on the target. > +#. Configure a fixed IP address on the target using `ifconfig` on the RTEMS > + shell. > +#. Ping the IP of your PC from the target and the target from the PC. > +#. Check on the Wireshark if your PC receives packets from the target. If > yes: > + Check if the PC responds to them. > + - If it responds, the target can send correctly formatted packets. > + - If your PC doesn't respond, check the packet content and checksums for > + errors like endianess, missing bytes, wrong bytes (can be a cache > issue), > + wrong checksum (only works if checksum offloading has been disabled). > +#. Check interface statistics. Some drivers offer statistics via `sysctl`. > Some > + basic informations can also be printed using `netstat` independent of the > + driver. > +#. `media01` should also provide a `tcpdump` that you can use to dump > received I more or less noted down what I usually use. media01 has quite a lot of stuff so in my experience it's a good starting point for testing most functionality. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/50#note_113864 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
