From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Dan Shelton <dan.f.shelton@gmail.com>,
Sascha Hauer <sha@pengutronix.de>
Subject: barebox + picotcp-1.7.0
Date: Sun, 3 Mar 2024 21:58:03 +0300 [thread overview]
Message-ID: <20240303215803.f8693ec93f03fd048acd3a30@gmail.com> (raw)
Hi all!
In the message [1] Sascha proposed to have the barebox network stack
and picotcp in parallel.
This approach is used in the branch 20240303.picotcp-1.7.0 from
https://github.com/frantony/barebox/ repo [2]:
* all incoming packets go through the barebox network stack and only if
they are not processed by it, they are forwarded to the picotcp network
stack (all incoming ARP packets always go to the picotcp network stack).
* risc-v virtual qemu machine with user networking (slirp network stack)
is used for demonstration; one needs only qemu risc-v emulator
for demonstration;
* these barebox commands are introduced for picotcp stack capabilities
demonstration:
* dhclient --- setup picotcp network interface using the DHCP protocol;
* ifconfig --- print/setup picotcp network interface information;
* route --- print picotcp routing table;
* picoping --- send ICMP ECHO_REQUEST to network hosts, receive replies;
* picohost --- perform DNS lookup (google DNS server is used);
* app_wget --- download file using the HTTP protocol.
* tcpdump code is incorporated into barebox for network stack debugging.
tcpdump supports parsing most of the protocols supported by barebox
(DHCP, ARP, ICMP, DNS, TFTP and TCP).
Please comment!
[1] http://lists.infradead.org/pipermail/barebox/2024-February/045937.html
[2] https://github.com/frantony/barebox/tree/20240303.picotcp-1.7.0
--
Best regards,
Antony Pavlov
next reply other threads:[~2024-03-03 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 18:58 Antony Pavlov [this message]
2024-03-04 14:47 ` Sascha Hauer
2024-03-10 20:19 ` Antony Pavlov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240303215803.f8693ec93f03fd048acd3a30@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=dan.f.shelton@gmail.com \
--cc=sha@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox