Re: [LEDE-DEV] [OpenWrt-Devel] Test results of OpenWrt 15.05.1 according to BSI test concept for home routers

[Eric Schultz]

On 04/08/2017 11:38 AM, Hauke Mehrtens wrote:

> The German Bundesamt für Sicherheit in der Informationstechnik (short:
> BSI, English: Federal Office for Information Security) published a
> "Testkonzept für Breitband-Router (DSL-, Kabel-, SOHO-, CE-, CPE-Router,
> IADs)" (English: Test concept for broadband routers). This test concept
> is only available in German and most chapters are published in the
> public by the BSI, chapter 4 and 5 are only available after signing a
> NDA (Traffic Light Protocol) with the BSI:
> https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Cyber-Sicherheit/Themen/Testkonzept-Breitbandrouter.pdf?__blob=publicationFile=5
>
> Some unnamed organization tested OpenWrt 15.05.1 on a TP-Link  TL-WR841N
> V10.0 according to this test concept. Because I commented on the first
> public draft of the test concept and said that I am active in the
> OpenWrt project, the organization contacted me to check if their test
> results are correct and provided me with the full test report under NDA.
>
>
> OpenWrt 15.05.1 failed this test and LEDE will probably also fail this
> test, because we failed on section 4.5.1 "Firewall-Bypass", which is a
> criterion for exclusion (Ausschlusskriterium), see details below.
>
> The test concept focus on "normal" routers and only tests the web GUI
> and also looks mostly on features normal home routers have. We are
> missing some functionality like individual default password, for the web
> GUI and the Wifi, the logging is not very good and so on. The tests
> regarding DNS are interesting and more advanced, if someone wants to
> look into that it would be very nice.
>
> The main problem is in section 4.5.1 "Firewall-Bypass".
> OpenWrt and LEDE implement RFC4890 section 4.3.1:
> ---
> 4.3.1.  Traffic That Must Not Be Dropped
>
>Error messages that are essential to the establishment and
>maintenance of communications:
>
>o  Destination Unreachable (Type 1) - All codes
>o  Packet Too Big (Type 2)
>o  Time Exceeded (Type 3) - Code 0 only
>o  Parameter Problem (Type 4) - Codes 1 and 2 only
>
>Appendix A.4 suggests some more specific checks that could be
>performed on Parameter Problem messages if a firewall has the
>necessary packet inspection capabilities.
>
>Connectivity checking messages:
>
>o  Echo Request (Type 128)
>o  Echo Response (Type 129)
> ---
>
> The BSI used RFC6092 (Recommended Simple Security Capabilities in
> Customer Premises Equipment (CPE) for Providing Residential IPv6
> Internet Service) with this section as the base for the test:
> ---
> 3.2.1.  Internet Control and Management
>
>Recommendations for filtering ICMPv6 messages in firewall devices are
>described separately in [RFC4890] and apply to residential gateways,
>with the additional recommendation that incoming "Destination
>Unreachable" and "Packet Too Big" error messages that don't match any
>filtering state should be dropped.
>
>REC-10: IPv6 gateways SHOULD NOT forward ICMPv6 "Destination
>Unreachable" and "Packet Too Big" messages containing IP headers that
>do not match generic upper-layer transport state records.
> ---
>
>
> Attached are the results of this test of OpenWrt 15.05.1. The
> information on how the tests from chapter 4 and 5 are done is redacted
> from the document, if you want to work on these problems and would like
> to get more details about the problems from chapter 4 and 5, please
> contact me. I can also help you with translating the problem from German
> to English. ;-)
>
> The "sensitive" informations are under the Traffic Light Protocol
> classification "TLP AMBER", see these German information about the NDA:
> https://mip.bsi.bund.de/Anlage_1_TLP-Merkblatt.pdf
>
>
> I commented on the tests itself, because they are missing many important
> stuff to test, most of the security problem of IoT devices and home
> routers one hears about in the media are not covered here at all.
>
>
> History:
> 20.10.2015: I read this article https://heise.de/-2851354 and wrote some
> comments to the BSI based on the first public draft. In this mail I
> mentioned that I am activate in the OpenWrt project.
> 23.10.2015: The BSI answered me and offered me the full draft when I
> would sign an NDA, I did so and got the full document, but did not
> comment on it again.
> 23.2.2016: I got the full final draft from the BSI
> 22.11.2016: I was told by the unnamed organization that they tested a
> TP-Link device running OpenWrt 15.05.1 and if I could comment on their
> results. I got the results under the NDA and commented in them.
> 31.3.2017: I asked if I can publish at lest some parts of the results
> again and got the OK that I am allowed to publish the 

Re: [LEDE-DEV] Github's new TOS

[Eric Schultz]

On 03/02/2017 12:02 PM, Daniel Golle wrote:
> Hi!
>
> For your consideration: Please have a look at
> https://joeyh.name/blog/entry/removing_everything_from_github/
>
> This is not very surprising -- if power gets too concentrated it's
> only a matter of time to see it being abused. Hopefully we can pull
> stuff out there without implicitely acknowledging the new terms by
> doing that.
> I wonder how big player (torvald/linux.git and such) are going to
> react to this.
>
>
> Cheers
>
>
> Daniel

As another datapoint, I asked Richard Fontana, current Redhat lawyer and
co-drafter of the GPL3, and he referred to analysis in the article as
"basically wrong"[1]. So it seems unclear whether this has a negative
effect or not.

Eric Schultz

[1]: https://twitter.com/richardfontana/status/837370085392199681




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] automated signed firmware upgrades / hide a secret in image

[Eric Schultz]

Bastian,

prpl member IntrinsicID has physically unclonable function technology
which allows a key to be generated at bootup based upon the physical
characteristics of the device. It's the same key generated everytime but
it isn't actually stored in flash. Their technology requires a paid
license but we might be able to convince them to release an open-source
version with more limited capabilities. I can put you in touch with
folks both at IntrinsicID and prpl to discuss this further if you'd like.

Eric

On 02/22/2017 03:05 AM, Bastian Bittorf wrote:
> dear devs,
>
> I'm polishing up our work-in-progress regarding automated
> firmware-upgrades in our community network and I have a concept problem:
>
> our images/the sha256-sum's are signed:
> http://intercity-vpn.de/networks/liszt28/firmware/models/Buffalo%20WZR-HP-AG300H/testing/Standard,DSLR,fotobox,kalua/info.json
>
> The downloader checks against a list of signatures, where
> e.g. 3 signatures must match the sha256 sum.
>
> There are "automated" signatures (e.g. from builbot) and manual ones,
> from humans. For protecting ourselfes from bad admins, there
> should be a "secret thing" which is baked into the firmware and
> only seeable during runtime: this way we can prevent, that a lazy
> admin "signs" a sha256 sum, without really has flashed the image
> and can make sure that it really runs.
>
> Now the question: a secret can be e.g.
> # ls -la /etc | md5sum
>
> This is naive, and a dumb admin can e.g. unsquashfs the
> image for getting the data. are there better methods? any ideas?
>
> bye, bastian
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [bufferbloat-fcc-discuss] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

[Eric Schultz]

All,

Since it's relevant to this discussion, I wanted to let folks know that
I've recently joined the Software Controlled Radio sub-group of the
FCC's Technical Advisory Council in my role as prpl Community Manager. A
press release about my participation is at
https://prpl.works/2016/11/21/prpl-foundation-collaborating-with-fcc-working-group/.
 The
sub-group consists of members of industry and academia with FCC staff
observing. We've been tasked with providing background on and, if
possible, recommendations to the FCC on how to balance reducing
interference with protecting innovation and the flexible addition of
features. I'm coming into the the sub-group late in the process (the
report is supposed to be done this year) but in the first few weeks, I
think I've been able to add some important viewpoints from the open
source community.


While the final report will be public, I've been asked by the chair of
the committee to keep the draft report confidential. If anyone here is
willing to help and will keep the draft confidential, I'd welcome your
assistance.

Thanks,

Eric

On 11/17/2016 11:06 PM, Paul Gardner-Stephen wrote:
> Hello,
>
> I think the fundamental problem is that the FCC wants to:
>
> 1. Make sure no one can run non-vendor-supplied firmware (presumably
> to try to stop harmful interference);
>
> and
>
> 2. Not ban the open-source movement from innovating on wireless using
> commercial wireless routers.
>
> We can all see that using that formulation they are trying to ban and
> allow the same thing at the same time.
>
> This is not unique to the US at the moment. The EU directive
> 2014/53/EU is trying to do the same thing.
>
> I am currently working with a team here at TU-Darmstadt to put a
> submission in to the German government to make sure that their
> implementation of the EU directive doesn't ban open-source firmware
> (actually, our reading of the current draft is that it would also
> accidentally ban a lot of other things due to a couple of small
> oversights). This is also causing me to extend my German vocabulary
> with words like "Zweckbestimmungsänderung,"
> "telekommunikationsendeinrichtungen," , and
> "harmonisierungsrechtsvorschriften."
>
> This is part of a larger project to understand (and hopefully improve)
> the legal situation for wireless ad-hoc emergency and humanitarian
> telecommunications networks.  While this use-case may be rather
> specific, it touches on most of the issues that affect the open-source
> wireless community in general.
>
> In this project, we intend to understand the current regulatory
> situation in the USA, Germany/EU, Australia and a handful of other
> countries, to see how they compare, and try to propose a rational
> framework that would be acceptable to national regulators, while not
> undermining the value of the various activities of the open-source
> wireless communities around the world.  Anyone who would like to help
> with this effort, feel free to poke me.
>
> Paul.
>
> On Fri, Nov 18, 2016 at 2:26 AM, Wayne Workman
> > wrote:
>
> I don't understand how this group's efforts weren't successful
> after what TP-Link had to do.
>
> Was it TP-LINK'S choice to support open source in an effort to
> save face and get brownie points or was it mandated by court?
>
> The FCC's stance, to me at least, is even more vague now.
>
> On Nov 17, 2016 10:03 AM, "Dave Taht"  > wrote:
>
> The linked document below is the same document we attacked, I
> thought
> successfully, last year,
>
> 
> http://www.computerworld.com/article/2993112/security/vint-cerf-and-260-experts-give-fcc-a-plan-to-secure-wi-fi-routers.html
> 
> 
>
> with the ultimate response from the fcc being
>
> 
> https://www.fcc.gov/news-events/blog/2015/11/12/clearing-air-wi-fi-software-updates
> 
> 
>
> Merely being asked to describe how the regdb works is all I
> see as the
> current FCC requirement. More than one manufacturer has got
> through
> this process since. Also, the context of that whole original
> debate
> was a dispute with tp-link, which only came out after the
> legal dust
> had settled.
>
> 
> http://arstechnica.com/information-technology/2016/08/fcc-forces-tp-link-to-support-open-source-firmware-on-routers/
> 
> 
>
> On Wed, Nov 16, 2016 at 2:15 PM, Simon Wunderlich
>  

[LEDE-DEV] Update on prpl Funding for OpenWrt/LEDE Projects

[Eric Schultz]

I wanted to let everyone know that prpl will be accepting proposals for
OpenWrt/LEDE project funding on a rolling basis. We want to fund your
projects to improve or add features to OpenWrt/LEDE. If you want your
project funded or you're interested in learning more, please
visit https://prpl.works/2016/09/26/openwrt-funding-round-two/ or
contact myself. Also, if you're having trouble with your proposal,
please let me know, I'm happy to help.

Thanks,

Eric

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] OpenWrt Summit Live Streaming

[Eric Schultz]

For those of you who are attending OpenWrt Summit, I'm looking forward
to seeing you!

For those who aren't able to make it, I wanted to let you know that
OpenWrt Summit will be live streamed on Youtube. We have links for
almost all the sessions at OpenWrtSummit.org and the last few will be
added before tomorrow. We also have an IRC channel to participate. You
can get all the information at OpenWrtSummit.org.

Eric

NOTE: if you're in Germany, you may need a VPN to watch it live due to
local law. We have a suggestion from an attendee for a free VPN provider
on OpenWrtSummit.org.



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt] [OpenWrt-Users] OpenWrt Summit Nearing Capacity; please register soon!

[Eric Schultz]

Ben,

Yes, there will be live streaming of the event! We'll have the links to
the streams posted on http://openwrtsummit.org
<http://openwrtsummit.org/> prior to the event. The streams will also be
saved on Youtube for those who can't watch them live.

Thanks,

Eric

On 09/29/2016 07:43 AM, Benjamin Henrion wrote:
> On Wed, Sep 21, 2016 at 8:53 PM, Eric Schultz
> <eschu...@prplfoundation.org> wrote:
>> I'm excited to let folks know that the response to OpenWrt Summit has
>> been very strong; we currently have over 170 registrations. If you've
>> already registered, thank you so much! If you're interested in attending
>> but haven't registered yet, please do so as soon as possible. Depending
>> on demand this week, we may be forced to close registrations very soon.
>>
>> To register or find out more about OpenWrt Summit, please visit
>> http://openwrtsummit.org
> Is there any streaming foreseen?
>
> Best,
>
> --
> Benjamin Henrion 
> FFII Brussels - +32-484-566109 - +32-2-3500762
> "In July 2005, after several failed attempts to legalise software
> patents in Europe, the patent establishment changed its strategy.
> Instead of explicitly seeking to sanction the patentability of
> software, they are now seeking to create a central European patent
> court, which would establish and enforce patentability rules in their
> favor, without any possibility of correction by competing courts or
> democratically elected legislators."
> ___
> OpenWrt mailing list
> open...@lists.prplfoundation.org
> http://lists.prplfoundation.org/cgi-bin/mailman/listinfo/openwrt


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Second round of OpenWrt/LEDE project funding

[Eric Schultz]

I wanted to let folks know that prpl Foundation will be funding another
round of OpenWrt/LEDE projects. Following up on our first round of
projects (https://prpl.works/2016/09/26/openwrt-funding-round-two/), we
want to continue funding the stellar work of community members. A funded
project can relate to core OpenWrt/LEDE, a package, testing or
documentation. While we encourage folks to submit a project based upon
our suggested projects list, we’ll consider any project related to
OpenWrt or LEDE. To find out more, see the suggested projects and to
apply for funding, please visit
https://prpl.works/2016/09/26/openwrt-funding-round-two/ or shoot me
over an email.


Thanks,


Eric



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] OpenWrt Summit Nearing Capacity; please register soon!

[Eric Schultz]

I'm excited to let folks know that the response to OpenWrt Summit has
been very strong; we currently have over 170 registrations. If you've
already registered, thank you so much! If you're interested in attending
but haven't registered yet, please do so as soon as possible. Depending
on demand this week, we may be forced to close registrations very soon.

To register or find out more about OpenWrt Summit, please visit
http://openwrtsummit.org

Thanks,

Eric Schultz, Chair, on behalf of the OpenWrt Summit Committee:

Abhijit Mahajani
Beda Kosata
Eric Schultz
Federico Capoano
Hans Dedecker
Hauke Mehrtens
Imre Kaloz
Kathy Giori
Luka Perkov
Paul Blay
--
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org <http://www.prplfoundation.org/>
eschu...@prplfoundation.org <mailto:eschu...@prplfoundation.org>
cell: 920-539-0404 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] FCC regulatory compliance

[Eric Schultz]

Ryan,

I'm pleased to hear about  interest in addressing the effects of the FCC
rules on free and open source software. I'd be happy to facilitate and
organize a subgroup to address this topic both with interested
OpenWrt/LEDE members as well as other interested parties in the open
source and related technology communities. During my activism on this
topic both at prpl and on my own, I've built a number of contacts and
relationships that would valuable to bring to this discussion. We do
have a running topic on the prplwrt Weekly meeting about the regulatory
issue (connection info at http://wiki.prplfoundation.org/wiki/Prplwrt)
so we'd be happy to have you join there and discuss this topic as well
and what ideas you have and how we can move this forward.

Thanks,
Eric

On 09/20/2016 04:27 PM, Ryan Nowakowski wrote:
> As you know, the FCC is enforcing rules around securing regulatory and DFS
> behavior and that is affecting how manufacturers respond to end-user
> re-flashing. We're aware of some suggestions that have been proposed[1], but
> some of those inherently would block re-flashing. We'd like to open discussion
> on what could be done on the chip/wi-fi firmware side that would maximize the
> opportunity to re-flash a router with the latest OpenWRT/LEDE while still
> ensuring compliance with the rules. This would most likely be for new products
> rather than the installed base.
>
> [1] 
> http://wiki.prplfoundation.org/wiki/Complying_with_FCC_rules_on_Wifi#List_of_possible_methods_of_complying
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] OpenWrt Summit Session Announcements

[Eric Schultz]

All,

I wanted to let everyone know that the sessions for OpenWrt Summit have
been announced and are listed at http://openwrtsummit.org. We have a
really broad range of sessions this year that address both the technical
and industry sides of the OpenWrt/LEDE communities. I think I can speak
for the rest of the summit committee-members when I say that we're very
excited by our list of sessions. This will be great chance to meet in
person with others who are using or involved with OpenWrt or LEDE.

I encourage everyone to check out the session list and consider joining
us in Berlin on October 13. It's free to attend, we only ask that you
register ahead of time at http://openwrtsummit.org. I look forward to
seeing everyone there!

Eric Schultz, Chair, on behalf of the OpenWrt Summit Committee:

Abhijit Mahajani
Beda Kosata
Eric Schultz
Federico Capoano
Hans Dedecker
Hauke Mehrtens
Imre Kaloz
Kathy Giori
Luka Perkov
Paul Blay
Zoltan Herpai
-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschu...@prplfoundation.org
cell: 920-539-0404

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] OpenWrt Summit Proposal Deadline - August 19

[Eric Schultz]

The deadline for session proposals at OpenWrt Summit is coming up on
*August 19*. If you’ve already submitted your proposals, thank you! If
not, there’s still time to submit your proposal for a session on any
topic related to OpenWrt, LEDE or the broader ecosystem by going
to http://openwrtsummit.org <http://openwrtsummit.org/>.

If you’re not sure of a topic to propose, the committee has a few
suggested topics that we think would be particularly interesting; if you
have experience in or have done work related to the following topics,
please submit a proposal:

* OpenWrt/LEDE and Docker – running in Docker containers and/or running
Docker on OpenWrt/LEDE
* How to submit patches? When the OpenWrt/LEDE split happened, the
number of patches was at an all time low. Some people don't feel
comfortable submitting because they don't understand the process or feel
their patch won't be well received.
* Wifi subsystem in OpenWrt/LEDE – How does it work? How is it
configured? How is it different from base Linux?
* Recent features and changes in OpenWrt/LEDE such as jails, usign,
build system changes in LEDE and others.
* Future features of OpenWrt/LEDE – What features are you adding? What
features are you considering adding?

If you idea isn’t on this list, don’t worry; we still welcome your
proposal and session! Also, if you’d like help completing your proposal
please email myself at eschu...@prplfoundation.org
<mailto:eschu...@prplfoundation.org> and I’ll help you out. You can also
ask any of the OpenWrt Summit Committee members for help as well. As a
reminder, financial assistance is be available for speakers who require it.

I look forward to the session proposals! If you have any questions,
don't hesitate to ask myself or anyone else on the committee.

Thanks,

Eric Schultz, Chair, on behalf of the OpenWrt Summit Committee:

Abhijit Mahajani
Beda Kosata
Eric Schultz
Federico Capoano
Hans Dedecker
Hauke Mehrtens
Imre Kaloz
Kathy Giori
Luka Perkov
Paul Blay
Zoltan Herpai

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] TR-069 and OpenWrt Meeting Videos

[Eric Schultz]

I've posted the recordings of the TR-069 and OpenWrt Meetings from June
10 and June 17. Check them out via the links below if you're interested
in the discussion.

* June 10 - https://youtu.be/U2SiveQwKm8
* June 17 - https://youtu.be/Hvqi1EFs_U0

We'll be having another meeting this week on June 24 at 7AM PT as well;
everyone interested is welcome to join. Be on the lookout for the
connection info in the next few days.

Thanks everyone,

Eric

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt] Poll on date for TR-069 & OpenWrt Face to face

[Eric Schultz]

Pasquale,

Sure, no problem. I've added the week after to the poll. If you've
already participated, please update with your dates for the week after.
Reminder the poll is at: http://doodle.com/poll/f4zc8nseeb5s8s69

Thanks,

Eric

On 06/11/2016 12:35 PM, Pasquale Bombino wrote:
> Hi All,
>
> Can we also add the week after (first of July) as per our discussion during 
> last week call ?
>
> Cheers,
> Pasquale
>
>
> -Original Message-
> From: openwrt-boun...@lists.prplfoundation.org 
> [mailto:openwrt-boun...@lists.prplfoundation.org] On Behalf Of Eric Schultz
> Sent: sabato 11 giugno 2016 19:18
> To: open...@lists.prplfoundation.org; lede-dev@lists.infradead.org; 
> openwrt-de...@lists.openwrt.org
> Subject: [OpenWrt] Poll on date for TR-069 & OpenWrt Face to face
>
> All,
>
> As requested, I've created a Doodle poll to help decide on the best dates for 
> the TR-069 & OpenWrt Face to face. Please visit
> http://doodle.com/poll/f4zc8nseeb5s8s69 as soon as possible and select the 
> days that work for you. Given the short time-constraints, it's likely best 
> that we settle on a date by the end of the day on Monday, June 13.
>
> Thanks everyone!
>
> Eric
> ___
> OpenWrt mailing list
> open...@lists.prplfoundation.org
> http://lists.prplfoundation.org/cgi-bin/mailman/listinfo/openwrt
> connecting lives
> connecting worlds


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Meeting on TR-069 Work - Friday, June 10 - 7 AM PT

[Eric Schultz]

All,

Just noticed that the Fuze url was sent inappropriately in my mail
client. The correct URL is http://fuze.me/32924366

Thanks,

Eric

On 06/03/2016 04:41 PM, Eric Schultz wrote:
> I'm excited to see so many people interested in TR-069 support! As a
> follow up to the previous TR-069 email, I've set up a meeting on TR-069
> support for OpenWrt. The meeting is on Friday, June 10 at 7 AM PT.
>
> I expect the meeting will discuss:
>
> * The proposals for creating/integrating TR-069 support into OpenWrt
> from Luka and Felix
> * The proposed open source TR-069 stacks from SoftAtHome and
> Technicolor, as well as the potential for reuse between stacks
> * The potential for a standard TR-069 stack interface in OpenWrt
> * A standard interface in OpenWrt for protocols like TR-069, as proposed
> by Felix
> * A face-to-face meeting for all of the core implementers to work
> through the technical details to develop a plan forward
> * Anything else related!
>
> Everyone interested is invited to join the meeting. I also plan to post
> a video of the meeting to Youtube for those who couldn't attend. To join
> the meeting using any WebRTC enabled browser, please follow the
> instructions below.
>
> Thanks a lot and I look forward to seeing many of you at the meeting.
>
> Thanks,
>
> Eric
>
> --
>
> Eric Schultz, Community Manager, prpl Foundation
> http://www.prplfoundation.org
> eschu...@prplfoundation.org <mailto:eschu...@prplfoundation.org>
> cell: 920-539-0404 
> skype: ericschultzwi
> @EricPrpl
>
> ---
>
>  
> To join the web meeting click or copy and paste this URL into your browser:
>  
> _http://fuze.me/32924366_
>  
> To join the audio portion of this meeting:
>  
> Internet Audio: Simply select the internet audio option after joining.
> Toll / Intl #: +12014794595
> Toll free #: +18553463893
> You can find international access numbers at
> _https://www.fuze.com/extras/symphony_
> If prompted, enter the meeting number: 32924366, then press #.
>  
> For the optimal experience, download Fuze: 
> _www.fuzebox.com/products/download_
>  
> Need help? You can connect to our Customer Support Team or access self-help
> tools at _www.fuzebox.com/support_ <http://www.fuzebox.com/support>.
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Meeting on TR-069 Work - Friday, June 10 - 7 AM PT

[Eric Schultz]

I'm excited to see so many people interested in TR-069 support! As a
follow up to the previous TR-069 email, I've set up a meeting on TR-069
support for OpenWrt. The meeting is on Friday, June 10 at 7 AM PT.

I expect the meeting will discuss:

* The proposals for creating/integrating TR-069 support into OpenWrt
from Luka and Felix
* The proposed open source TR-069 stacks from SoftAtHome and
Technicolor, as well as the potential for reuse between stacks
* The potential for a standard TR-069 stack interface in OpenWrt
* A standard interface in OpenWrt for protocols like TR-069, as proposed
by Felix
* A face-to-face meeting for all of the core implementers to work
through the technical details to develop a plan forward
* Anything else related!

Everyone interested is invited to join the meeting. I also plan to post
a video of the meeting to Youtube for those who couldn't attend. To join
the meeting using any WebRTC enabled browser, please follow the
instructions below.

Thanks a lot and I look forward to seeing many of you at the meeting.

Thanks,

Eric

--

Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschu...@prplfoundation.org <mailto:eschu...@prplfoundation.org>
cell: 920-539-0404 
skype: ericschultzwi
@EricPrpl

---

 
To join the web meeting click or copy and paste this URL into your browser:
 
_http://fuze.me/32924366_
 
To join the audio portion of this meeting:
 
Internet Audio: Simply select the internet audio option after joining.
Toll / Intl #: +12014794595
Toll free #: +18553463893
You can find international access numbers at
_https://www.fuze.com/extras/symphony_
If prompted, enter the meeting number: 32924366, then press #.
 
For the optimal experience, download Fuze: 
_www.fuzebox.com/products/download_
 
Need help? You can connect to our Customer Support Team or access self-help
tools at _www.fuzebox.com/support_ <http://www.fuzebox.com/support>.

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev