mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Daniele Lacamera <daniele.lacamera@tass.be>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Colin Leitner <colin.leitner@googlemail.com>,
	PicoTCP <picotcp@tass.be>, barebox <barebox@lists.infradead.org>
Subject: Re: Adding IPv4 multicast support
Date: Sun, 13 Jul 2014 16:28:58 +0200	[thread overview]
Message-ID: <CAOngqVV-PcbsowH9iOHXpxXNvJEb_k7KyWakQVVGT9FMm4iFLw@mail.gmail.com> (raw)
In-Reply-To: <20140713145526.2cf6407fc9a17a4e8db89a50@gmail.com>

On Sun, Jul 13, 2014 at 12:55 PM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> On Sun, 13 Jul 2014 12:11:17 +0200
> Colin Leitner <colin.leitner@googlemail.com> wrote:
>
>> Hello everyone,
>>
>> I'm working on adding multicast support to barebox (for device discovery) and wanted to know if there's interest in having that included in upstream.
>
> There is an initiative on integrating picotcp into barebox.
>
> picotcp is a free TCP/IP stack implementation, see
>   https://github.com/tass-belgium/picotcp
>
> AFAIK latest picotcp-enbled barebox anounced here:
>   http://lists.infradead.org/pipermail/barebox/2014-June/019723.html
>
> Can be network device discovery realized using picotcp entities?
>
> To Daniele: how things stand with picotcp tftp support?
>
>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>
>
> --
> --
> Best regards,
>   Antony Pavlov

TFTP is integrated in masterbranch, documented and tested.
PicoTCP app can act as TFTP server as well as client. Supports put/get
operations. Tested against tftp(d)-hpa.

What would you need for "network discovery"? Currently picotcp
supports the following protocols:
- IPv6 neighbor discovery
- IPv4 SLAAC (like avahi-style autoconf)
- mDNS (at the moment over v4 only)
- OLSR (automatic detection of neighbors and best route calculation to
N-hops nodes)


Regards,

-- 
Daniele

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2014-07-13 14:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 10:11 Colin Leitner
2014-07-13 10:55 ` Antony Pavlov
2014-07-13 10:52   ` Colin Leitner
2014-07-13 13:15     ` Colin Leitner
2014-07-13 14:28   ` Daniele Lacamera [this message]
2014-07-15  7:01     ` picotcp tftp support [was Adding IPv4 multicast support] Antony Pavlov
2014-07-15  9:31       ` Daniele Lacamera
2014-07-15 10:27         ` Antony Pavlov
2014-07-15 10:57           ` Daniele Lacamera
2014-07-15 12:57             ` Antony Pavlov
2014-07-15 15:55               ` Daniele Lacamera
2014-07-15 19:02                 ` Antony Pavlov
2014-07-16  6:30             ` Sascha Hauer
2014-07-16  6:48               ` Daniele Lacamera
2014-09-04 17:14                 ` Antony Pavlov
2014-09-05  7:37                   ` Daniele Lacamera
2014-09-26  9:27                   ` PicoTCP
2014-09-28 14:22                     ` Antony Pavlov
2014-09-29  9:45                       ` Daniele Lacamera
2014-09-29 10:10                         ` Michele Di Pede
2014-09-29 10:19                         ` Antony Pavlov
2014-07-15 18:17     ` Adding IPv4 multicast support Colin Leitner

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=CAOngqVV-PcbsowH9iOHXpxXNvJEb_k7KyWakQVVGT9FMm4iFLw@mail.gmail.com \
    --to=daniele.lacamera@tass.be \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=colin.leitner@googlemail.com \
    --cc=picotcp@tass.be \
    /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