Re: [OpenWrt-Devel] Introducing the LEDE project

[Jonathan Bennett]

On Thu, May 5, 2016 at 10:58 AM Daniel Dickinson <
open...@daniel.thecshore.com> wrote:

> On 16-05-05 11:38 AM, Jonathan Bennett wrote:
> > There is plenty of blame to go around, I think.  Seems like the Lede
> > guys should have had the decency to at least inform the Openwrt
> > leadership privately that they were planning this venture.  The surprise
>
> The problem is that LEDE is pretty much who should be considered
> "OpenWrt Leadership" IMO as they are the majority of ones doing the
> actual work.  This isn't like working for some bad corp (I currently
> have good managers so it's better than for me even at work) where there
> are (supposed to be) execs making the decisions regardless of what those
> doing the work think.
>
> > announcement must have felt very much like a stab in the back. "Et tu,
> > brute?" and all that.  I think they want a "friendly fork" as much as
> > possible, but they dropped the ball in how they announced it.  I suspect
> > that a private email to mbm and kaloz could have gone a long ways
> > towards heading off problems.  As has been pointed out, the public
>
> I think the reason for no private email was either fear of retaliation
> or something major had already happened 'behind-the-scenes' that made
> that moot.
>
> I'm not sure their silence is entirely their choice as well (as in I
> find the lack of any posts has me wondering if they can post).
>
> > announcement should not have come from an @openwrt.org
> > <http://openwrt.org> email.
>
> That much I agree with.
>
> >
> > That said, deleting their emails was totally uncalled for.  Seems that
> > those should be restored, perhaps with the caveat that they are more
> > carefully used with regards to Lede, aka, not for publicizing or
> > promoting it.
> >
> > Guys, for the love of the project, the users, and all else that is good,
> > please don't make this a ffmpeg/libav split.  Openwrt has been an
> > amazing thing for a long time, and if mishandled, this has the potential
> > to actually kill it.
> >
> > The changes that the Lede guys are suggesting would be welcome, but
> > splitting the project and community with an ugly fork is very much not
> > welcome.
>
> Let's just say that there are strong personalities who haven't been
> working well together and that this has been a long time coming; perhaps
> if something like using a mediator had been considered before things got
> to this point it would have helped.  At this point I'm not sure there is a
> solution unless both sides are willing to bend a little (I'm really not
> sure who has been flexible and who has not, but as I have said I suspect
> a large part of the issue is that 'management' (who aren't and don't,
> really) has overruled those doing the majority of the work and in an
> open source project that doesn't fly).
>
I don't disagree.  I just see the current state of Openwrt/Lede as a mess
for the community.

>
> Regards,
>
> Daniel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Introducing the LEDE project

[Jonathan Bennett]

There is plenty of blame to go around, I think.  Seems like the Lede guys
should have had the decency to at least inform the Openwrt leadership
privately that they were planning this venture.  The surprise announcement
must have felt very much like a stab in the back. "Et tu, brute?" and all
that.  I think they want a "friendly fork" as much as possible, but they
dropped the ball in how they announced it.  I suspect that a private email
to mbm and kaloz could have gone a long ways towards heading off problems.
As has been pointed out, the public announcement should not have come from
an @openwrt.org email.

That said, deleting their emails was totally uncalled for.  Seems that
those should be restored, perhaps with the caveat that they are more
carefully used with regards to Lede, aka, not for publicizing or promoting
it.

Guys, for the love of the project, the users, and all else that is good,
please don't make this a ffmpeg/libav split.  Openwrt has been an amazing
thing for a long time, and if mishandled, this has the potential to
actually kill it.

The changes that the Lede guys are suggesting would be welcome, but
splitting the project and community with an ugly fork is very much not
welcome.

--Jonathan Bennett

On Thu, May 5, 2016 at 10:12 AM John Clark <inin...@gmail.com> wrote:

>  >>the sudden deletion of our widely published openwrt.org email
> addresses somewhat undermines this
>
> Just so I am not jumping to wrong conclusions, their *.openwrt.org email
> addresses were deleted in retaliation for forking OpenWrt? Seriously?
> How did you not think that wasn't going to go well after all they have
> done for OpenWrt?
>
> --John
>
>
> On 5/5/16 11:04 AM, Roman Yeryomin wrote:
> > On 5 May 2016 at 17:43, Daniel Dickinson <open...@daniel.thecshore.com>
> wrote:
> >> On 16-05-05 05:34 AM, Roman Yeryomin wrote:
> >>> On 5 May 2016 at 06:48, Daniel Dickinson <open...@daniel.thecshore.com>
> wrote:
> >>>> On 16-05-04 04:01 PM, mbm wrote:
> >>>>> Dear OpenWrt community,
> >>>>>
> >> [snip]
> >>> One simple question:
> >>> If LEDE team members are the ones who were suffering from some
> >>> non-democratic decisions, why didn't they bring it to public
> >>> discussion for community? At least on devel maillist?
> >>>
> >>> If it was clear problem in remaining OpenWrt team then LEDE would win
> >>> the community right away or maybe problematic people would just go
> >>> away. Either way it would be more fair and open. And this is one of my
> >>> biggest concerns - LEDE team is promoting openness but didn't do their
> >>> moves openly (looking at maillists it seems they were hiding it for
> >>> month at least). Hate double standards.
> >> Perhaps for fear of repercussions such as what has happened since the
> >> fork where all LEDE members @openwrt.org email addresses have been
> deleted?
> > AFAIK, that was done after LEDE announcement but IMO was a wrong move
> anyway.
> >
> >> There are a number of people in the LEDE group I've found to be pretty
> >> decent people, and great to work with, so I find it unlikely that they
> >> simply acted without good reason.
> > This only add more shock to the announcement.
> >
> > Regards,
> > Roman
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Contributing to OpenWrt

[Jonathan Bennett]

Also worth noting is the 3rd party packages feed over at
https://github.com/openwrt/packages This could be a good place to get
started hacking on code for the OpenWrt project.

On Wed, Dec 16, 2015 at 11:47 PM Rafał Miłecki  wrote:

> On 17 December 2015 at 01:28, Mohammed Billoo 
> wrote:
> > I'm interesting in contributing to OpenWrt by initially working on bug
> > fixes. However, it wasn't obvious from the Wiki what is the correct
> process
> > in asking to be assigned to work on a bug, testing a fix, and submitting
> the
> > fix for review. Can anyone point me in the right direction?
>
> You don't need to have any bug officially assigned to you. Just work
> on some fix and send it as explained in:
> https://dev.openwrt.org/wiki/SubmittingPatches
>
> --
> Rafał
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SVN to GIT transition

[Jonathan Bennett]

On Mon, Oct 12, 2015 at 2:11 PM David Lang <da...@lang.hm> wrote:

> On Mon, 12 Oct 2015, Felix Fietkau wrote:
>
> > On 2015-10-12 16:11, Roman Yeryomin wrote:
> >> On 12 October 2015 at 16:34, Felix Fietkau <n...@openwrt.org> wrote:
> >>> On 2015-10-12 15:09, Javier Domingo Cansino wrote:
> >>>> Right now, the revision number (r) is really useful to
> figure
> >>>> out what particular openwrt version is being used, when people
> report
> >>>> bugs. The commit hash cannot be used as a replacement, since it
> might be
> >>>> one that isn't present in the official repo.
> >>>> When using tags as a starting point (via git describe), somebody
> has to
> >>>> create those tags, which is cumbersome (and would mean adding
> lots of
> >>>> useless ones).
> >>>>
> >>>> The tags would be the major versions and RCs. I don't believe other
> tags
> >>>> should be used.
> >>>>
> >>>> Apart from that, I understand that if someone cloned the SVN repo
> (full
> >>>> svn history), created it's own server, and developed on top of a given
> >>>> revision X, the same problem would arise.
> >>> I haven't seen a single instance of somebody doing this, and in my
> >>> opinion it would be kind of stupid anyway :)
> >>> We don't even advertise the SVN server URL to users anymore for a
> reason.
> >>>
> >>
> >> IMO git describe --dirty would work perfectly. You would see a short
> >> hash and if user modified it or not.
> > If the user made a local commit, the short hash becomes useless.
>
> if the user does a SVN checkout and then modifies things, the r is
> also
> not valid (although it does give you an idea where things branched)
>
> David Lang

His point is that users don't ever do an SVN checkout. Because the r number
is baked into the image, it's a really easy and obvious way for an end user
to report the revision in a bug report.  I can see the advantage in this.
If we are to move to git, we would want some way to preserve this feature,
that is a super easy way for a user to report the revision.  We could bake
the short hash into the image, but this would not be useful if any commits
were added locally, whereas the r number would still show some useful
information.

Would it be possible to track the revision number in an automated way even
in a git repo?  So store the r number, and automatically increment on
commits.  Not sure if that's an option, but it seems like it might address
the problem.

--Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SVN to GIT transition

[Jonathan Bennett]

Certain things are certainly broken.  The body of kernel code that OpenWrt
maintains (allows to bitrot) outside the upstream kernel tree is broken.

Regarding downstream forks, would using Git also make it easier for people
like project turris to push appropriate changes back into OpenWrt proper?

On Sun, Oct 11, 2015 at 1:38 PM L. D. Pinney  wrote:

> Just my 2-cents
>
> IF it isn't BROKENplease DON'T fix it.
>
>
>
> On Sun, Oct 11, 2015 at 1:26 PM, Nemesis  wrote:
>
>> On 10/10/2015 07:45 PM, nemesis wrote:
>>
>> On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin
>>  
>> wrote:
>>
>> On 9 October 2015 at 21:22, Jo-Philipp Wich 
>>  wrote:
>>
>> Hi.
>>
>> Moving to Git seemed to have lots of traction at the summit, and I'll
>> add my voice that this sounds like a step in the right direction for
>> OpenWrt.  I'm assuming that we would want to do a proper SVN to Git
>> conversion, and Eric's help on this would be great, I think.  My
>> discussion with Eric is over on Google+ and marked public:
>> https://plus.google.com/+JonathanBennett87/posts/bMPMjn7ZcJS
>>
>>
>> Why does the core system need to migrate from svn to git?
>>
>>
>> I thought everybody is using git anyway already. Are there people
>> still using svn?
>>
>>
>> doing something because everybody is doing so is not the best argument
>> IMHO.
>>
>> I would say that using git would improve quite a few things:
>>
>> * it would be easier to send upstream patches
>> * having a good git web interface like gitlab or github would allow
>> newcomers to participate more easily
>> * it would make life easier to the core contributors that prefer to work
>> with git because git allows a very powerful development workflow compared
>> to SVN
>>
>>
>> I remember somebody also mentioned sending patches to the linux kernel
>> would be easier.
>>
>> What do you people think about this point?
>>
>> Federico
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SVN to GIT transition

[Jonathan Bennett]

On 11 Oct 2015, at 14:48, John Crispin <blo...@openwrt.org> wrote:

patches will linger in mailing list until someone has time to look at
them. the version control system used is completely irrelevant

Which is true enough if the switch just encompasses moving to another VCS.
However, what has not been made explicit enough is that switching to git
_and_ a git web interface like Github/Gitlab may make it easier to
contribute. My understanding is that it would be much easier to test
proposed changes as people can simply do a checkout on a pull request and
run the proposed code. Currently (unless I am missing something which is
unfortunately quite possible), one would have to manually insert the
patches to test.

Someone said earlier that switching to github for the packages made a
positive difference in contributions. I would like to see that supported by
some numbers, or possibly a contributor can elaborate a bit on the process
and whether they perceive any benefits. That way, the migration of the
packages might show a practical use case in the context of this project and
its workflows.


I can comment on this last question.  I maintain fwknop, and before the
move of the third party packages to github, I had major issues trying to
get my patches committed.  The thing that was most frustrating is that I
was the maintainer for the package, and my patches that only touched that
package were not committed.  It was bad enough that I actually gave up and
wasn't doing anything related to OpenWrt development for over a year.

When the packages feed moved to github, I decided to come back and try
pushing patches again.  The experience has been much better.  I've had 24
hour turnarounds for many pull requests.  I think there are several factors
that led to such an improvement.  One is the easy interface to see changes
and the ability for someone with commit access to accept them so
trivially.  Expanding who has commit access to that repository has helped
as well.

Another big problem we see quite often is mangled patches in emails.  If
trivial patches could be pull requests instead of emails, it would lower
the noise level of mangled patches, and help new committers get their
patches in with less frustration.

Realistically, I think it's obvious that at some point we will have to move
away from SVN, if only because so many other projects are also doing so.
Because of the mass exodus from SVN, it seems destined to become legacy and
eventually unmaintained.  The sooner we commit to transitioning to git, and
start that transition, the easier it will be in the long run.

This brings another question to mind.  If we move to github/gitlab, do we
want to do bug tracking there as well, and retire trac altogether?

--Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] SVN to GIT transition

[Jonathan Bennett]

I just received word back from Eric Raymond, author of reposurgeon and
known for many other projects.  He has limited time, but will be willing to
offer some help if we want to do a full svn to git conversion of the core
OpenWrt codebase.

Moving to Git seemed to have lots of traction at the summit, and I'll add
my voice that this sounds like a step in the right direction for OpenWrt.
I'm assuming that we would want to do a proper SVN to Git conversion, and
Eric's help on this would be great, I think.  My discussion with Eric is
over on Google+ and marked public:
https://plus.google.com/+JonathanBennett87/posts/bMPMjn7ZcJS

--Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SVN to GIT transition

[Jonathan Bennett]

On Oct 9, 2015 2:21 PM, "Jo-Philipp Wich"  wrote:
>
> Hi.
>
> > Moving to Git seemed to have lots of traction at the summit, and I'll
> > add my voice that this sounds like a step in the right direction for
> > OpenWrt.  I'm assuming that we would want to do a proper SVN to Git
> > conversion, and Eric's help on this would be great, I think.  My
> > discussion with Eric is over on Google+ and marked public:
> > https://plus.google.com/+JonathanBennett87/posts/bMPMjn7ZcJS
>
> Why does the core system need to migrate from svn to git?
>
> ~ Jow

Several points were made at the meetup. I'm not the best to recap, as I
work more with the github community packages repos.

One point that was made is that upstreaming kernel patches would be
easier.  Also, most of the community uses git instead of svn, so there is
some advantage in using the more familiar tool.  Again, I'm not the best to
make the case.  Hopefully some others will jump in and contribute to the
conversation.

--Jonathan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Backporting from dev branch to stable

[Jonathan Bennett]

Guys with more experience will certainly be better suited to answer, but
from what I've observed, something like new device support wouldn't be
appropriate to backport into a released branch.  Usually only critical
security patches are backported.  There has been discussion of 15.05
working as a LTS sort of release, with minor version updates, so a 15.05.1
might happen in a few months.  You *might* get your patches included for
that maintenance release.  That's certainly not for me to decide, though.

--Jonathan Bennett

On Tue, Sep 29, 2015 at 2:15 PM Drasko DRASKOVIC <drasko.drasko...@gmail.com>
wrote:

> Hi all,
> how are the patches from main development branch backported to Chaos
> Calmer branch from dev branch?
>
> Do I have to re-post this patch-set
>
> http://git.openwrt.org/?p=openwrt.git;a=commit;h=c84682a79e36bb57f4f78d51aa589f7bfe3fb5e8
> against this branch:
> http://git.openwrt.org/?p=15.05/openwrt.git;a=summary?
>
> BR,
> Drasko
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Removing Telnet

[Jonathan Bennett]

Nak on setting a default password. The blank password has served its
purpose well for years now. Any preset password is asking for users to
leave it default. The only problem with blank ssh logins is it removes one
of the ways openwrt encouraged the user to set a password.

A banner that warns about a blank password would be fine, similar to what
Luci does. Any thoughts about forcing a password change on first ssh login?
I haven't thought through the idea fully myself.

On Tue, Sep 8, 2015 at 1:35 PM Vittorio G (VittGam) 
wrote:

> Il 08.09.2015 10:15 Steven Barth ha scritto:
> > as of https://dev.openwrt.org/changeset/46809 telnet is no longer part
> of
> > the base images. As a replacement, it is now possible to login to the
> root-
> > account via SSH without a password prompt whenever no root password is
> set,
> > e.g. after a flash without keeping config, factory reset or in failsafe.
>
> What about empty root password but authorized_keys for root present? This
> behavior is not clear from the patch...
>
> Maybe it would just be better to set the default root password to 'openwrt'
> or 'insecure' or 'change_me!'?
>
> Cheers,
> Vittorio
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2 00/25] ramips: massive code cleanups

[Jonathan Bennett]

Those sort of emails are always just a bit discouraging. Keep in mind that
they tend to come from people that are slightly autistic or have Aspergers.

From the rest of us, though, thank you for your hard work.

--Jonathan Bennett

On Mon, Aug 17, 2015 at 6:24 AM Piotr Dymacz pep...@gmail.com wrote:

 2015-08-17 8:28 GMT+02:00 John Crispin blo...@openwrt.org:
  Hi,
 
  just merged the whole lot. thanks a lot. what do you want to do next
  lantiq or ar71xx ? :) personally i would prefer ar71xx ;)
  [...]

 Hello John,

 It seems that there are some people who don't like the changes (see
 below), but they don't have enough courage to use their real name and
 post their comments on the list.

 I will back with answers for your and Michael Heimpold (I'm sorry, I
 didn't spot your e-mail before!) questions in few days. Now I'm really
 busy with other things.

 Cheers,
 Piotr Dymacz

 ---

 2015-08-17 13:05 GMT+02:00 West Fuck deutch...@anonmail.de:
  https://dev.openwrt.org/changeset/46617
 
  of all the bugs on related system you have choosen to change board and
 led
  names? why do you stick your nose into something that is not relevant?
 is it
  because your'e stupid fucking excuse for human being? you couldn't even
 make
  your uboot work without errors on some boards so why don't you stick to
 your
  own crap instead of acting like your're doing something
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] openwrt.org down due to expired certificate

[Jonathan Bennett]

I'm sure it's been noticed already, but the ssl cert for openwrt.org seems
to have expired, and due to hsts being enabled, the site is impossible to
access.

--Jonathan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] firmware-utils mktplinkfw: print amount of exceeding bytes

[Jonathan Bennett]

My comments weren't a critique of your patch, and probably belong in a
separate thread, or even a bug report on dev.openwrt.org.

Apparently the behavior my machine is showing is not the normal or intended
behavior. On my machine (Fedora 22, but also had the issue in Fedora 21, if
I remember correctly), there is no error message printed when the image
generation fails due to being too large. Running V=s shows:

[mktplinkfw] *** error: images are too big
Makefile:2244: recipe for target 'install' failed
make[5]: [install] Error 255 (ignored)

So, the real problem is that for some reason, my system is ignoring the
make error. This is unrelated to your patch. My thinking is that it was
intended behavior, and would make sense to change it in the same patch.
Sorry about the confusion.


--Jonathan

On Mon, Jul 13, 2015 at 10:46 AM Stephan Maka step...@spaceboyz.net wrote:

 Jonathan Bennett wrote:
  Tested and seems to work as intended. However, I think the image too big
  messages should be printed at the default verbosity.

 The patch doesn't change any levels.

  Currently, if make fails to generate the final image, it doesn't give any
  message to acknowledge, and appears to have succeeded, there are just
  mysteriously missing files in the output directory.

 All the ERR() outputs are followed by return -1, causing check_options()
 and therefore the process and make to fail.

 Sorry if I don't see your point but I'll be happy about follow-up
 patches. :)


 Cheers,
 Stephan

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] firmware-utils mktplinkfw: print amount of exceeding bytes

[Jonathan Bennett]

Tested and seems to work as intended. However, I think the image too big
messages should be printed at the default verbosity.

Currently, if make fails to generate the final image, it doesn't give any
message to acknowledge, and appears to have succeeded, there are just
mysteriously missing files in the output directory.

--Jonathan


On Mon, Jul 13, 2015 at 9:16 AM Stephan Maka step...@spaceboyz.net wrote:

 This is very useful for trimming images towards 4 MiB flash size.

 Signed-off-by: Stephan Maka step...@spaceboyz.net
 ---
  tools/firmware-utils/src/mktplinkfw.c | 20 ++--
  1 file changed, 10 insertions(+), 10 deletions(-)

 diff --git a/tools/firmware-utils/src/mktplinkfw.c
 b/tools/firmware-utils/src/mktplinkfw.c
 index 09536c6..850aff4 100644
 --- a/tools/firmware-utils/src/mktplinkfw.c
 +++ b/tools/firmware-utils/src/mktplinkfw.c
 @@ -657,10 +657,10 @@ static int check_options(void)
 kernel_len = kernel_info.file_size;

 if (combined) {
 -   if (kernel_info.file_size 
 -   fw_max_len - sizeof(struct fw_header)) {
 +   int exceed_bytes = kernel_info.file_size - (fw_max_len -
 sizeof(struct fw_header));
 +   if (exceed_bytes  0) {
 if (!ignore_size) {
 -   ERR(kernel image is too big);
 +   ERR(kernel image is too big by %i bytes,
 exceed_bytes);
 return -1;
 }
 layout-fw_max_len = sizeof(struct fw_header) +
 @@ -684,20 +684,20 @@ static int check_options(void)

 DBG(kernel length aligned to %u, kernel_len);

 -   if (kernel_len + rootfs_info.file_size 
 -   fw_max_len - sizeof(struct fw_header)) {
 -   ERR(images are too big);
 +   int exceed_bytes = kernel_len +
 rootfs_info.file_size - (fw_max_len - sizeof(struct fw_header));
 +   if (exceed_bytes  0) {
 +   ERR(images are too big by %i bytes,
 exceed_bytes);
 return -1;
 }
 } else {
 -   if (kernel_info.file_size 
 -   rootfs_ofs - sizeof(struct fw_header)) {
 +   int exceed_bytes = kernel_info.file_size -
 (rootfs_ofs - sizeof(struct fw_header));
 +   if (exceed_bytes  0) {
 ERR(kernel image is too big);
 return -1;
 }

 -   if (rootfs_info.file_size 
 -   (fw_max_len - rootfs_ofs)) {
 +   exceed_bytes = rootfs_info.file_size - (fw_max_len
 - rootfs_ofs);
 +   if (exceed_bytes  0) {
 ERR(rootfs image is too big);
 return -1;
 }
 --
 2.1.4
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Dualradio 2.4/5GHz ath9k-Hardware which is deliverable?

[Jonathan Bennett]

I have had great success with the tp-link Archer c7. It fits the bid
nicely, if it is available.

On Wed, Jul 1, 2015, 1:06 PM Bastian Bittorf bitt...@bluebottle.com wrote:

 In our community we are struggling now, what we can buy.
 TP-Link 4900 and 4300 are EOL now in Germany. What else is there?

 - 8mb+ flash
 - 450 mbit ath9k 2.4 GHz
 - 450 mbit ath9k 5 GHz
 - 128mb ram
 - 5 gigabit ports
 - OpenWrt 8-)

 bye, bastian
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] config for WNDR3800

[Jonathan Bennett]

Instead of using a premade .config, you'll want to use make menuconfig.
Under Target profile, you'll find the netgear WNDR3800.

Also, you will probably want to first run ./scripts/feeds update and
./scripts/feeds install -a in order to get the extra packages and luci.
Then if you want luci in your image, make sure you select Luci --
Collections -- Luci as builtin.

On Wed, Jul 1, 2015 at 10:51 AM Maciej Soltysiak mac...@soltysiak.com
wrote:

 Hi,

 I was planning to try and build openwrt on my box. Is there an official
 .config file that's used when building the snapshots?

 I'm looking for .config for Netgear WNDR3800.

 Best regards,
 Maciej

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] An interesting feature request

[Jonathan Bennett]

A couple lines of thought collided today during a conversation with a
friend who is also an fwknop user. Sending a knock over http is a clever
feature, and the hidden service idea is really cool. For example, I have a
web server that also has a cacti service in order to monitor that service.
However, I don't really want to log into cacti over http, as it would send
my username and password in the clear.

An https request sends an encrypted url request. Pcap cannot sniff this
encrypted url. While doing some work on the http support in the android
client, I observed that an http request (or an https request) will write
the requested url to the apache access_log file.

So, what if instead of using pcap to sniff incoming connections, we added
an option to watch an Apache access_log for an http or https request that
contained a valid SPA string.

The use case would be a hidden service that is accessed entirely over the
encrypted ssl channel. To anyone watching, all the traffic would look like
https access to the public web site, but we could send an spa packet and
access a hidden service all using ssl over port 443.

--Jonathan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] An interesting feature request

[Jonathan Bennett]

Oh dear. Sent to the wrong mailing list. Please disregard.

On Sat, Jun 27, 2015 at 1:52 PM Jonathan Bennett jbscienc...@gmail.com
wrote:

 A couple lines of thought collided today during a conversation with a
 friend who is also an fwknop user. Sending a knock over http is a clever
 feature, and the hidden service idea is really cool. For example, I have a
 web server that also has a cacti service in order to monitor that service.
 However, I don't really want to log into cacti over http, as it would send
 my username and password in the clear.

 An https request sends an encrypted url request. Pcap cannot sniff this
 encrypted url. While doing some work on the http support in the android
 client, I observed that an http request (or an https request) will write
 the requested url to the apache access_log file.

 So, what if instead of using pcap to sniff incoming connections, we added
 an option to watch an Apache access_log for an http or https request that
 contained a valid SPA string.

 The use case would be a hidden service that is accessed entirely over the
 encrypted ssl channel. To anyone watching, all the traffic would look like
 https access to the public web site, but we could send an spa packet and
 access a hidden service all using ssl over port 443.

 --Jonathan

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt switches to musl by default

[Jonathan Bennett]

On Mon, Jun 15, 2015 at 11:37 PM Rafał Miłecki zaj...@gmail.com wrote:

 On 16 June 2015 at 01:31, Jonathan Bennett jbscienc...@gmail.com wrote:
  Just to clarify, this is only for trunk, not for the CC branch, correct?

 Read again: in OpenWrt trunk


Sometimes, even apparently obvious things are important enough to be stated
explicitly.

It was just a couple days ago that CC was branched from trunk, and without
a lot of fanfare. I understood that the musl change was not for CC, but
thought it was worth stating explicitly.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt switches to musl by default

[Jonathan Bennett]

Just to clarify, this is only for trunk, not for the CC branch, correct?

On Mon, Jun 15, 2015 at 6:24 PM Felix Fietkau n...@openwrt.org wrote:

 Hi,

 I just committed a change making musl the new default libc in OpenWrt
 trunk, replacing uclibc. We've been preparing this for quite a while.
 Some packages might still be broken, so please test and open up bug
 reports for any issues that you find.
 Please remember to open up trac tickets only for packages from trunk;
 send reports of broken feed packages as PR on the relevant github project.

 Cheers,

 - Felix
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH,v2] dnsmasq: bump to dnsmasq2.73rc9

[Jonathan Bennett]

Hey, Kevin, I know how much of a pain it is to get patches to send without
getting mangled. You ought to stick with this, though, and work out how you
can send patches that don't get mangled. I'm sure Steven doesn't mind
pinging you back to let you know what the patches look like. Honestly, it's
better to work with a simple patch to get it figured out. Git send-email is
probably the way to go. Once you get it set up and working, it makes this
much less painful.

~Jonathan

On Mon, Jun 8, 2015 at 2:55 AM Kevin Darbyshire-Bryant 
ke...@darbyshire-bryant.me.uk wrote:

 I've no idea and giving up to be honest.  By producing bad patches I'm not
 being helpful and wasting experienced people's time.  Updating a Makefile
 is about as simple as it gets!


 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc1 / git-checkout

[Jonathan Bennett]

On May 28, 2015 12:14 PM, John Crispin blo...@openwrt.org wrote:



 On 28/05/2015 19:11, Jonathan Bennett wrote:
  On Wed, May 20, 2015 at 2:32 PM, Bastian Bittorf bitt...@bluebottle.com
wrote:
  * Steven Barth cy...@openwrt.org [20.05.2015 19:43]:
  http://downloads.openwrt.org/chaos_calmer/15.05-rc1/
 
  Thank you!
 
  when will this work?:
  git clone git://git.openwrt.org/15.05/openwrt.git
 
  Is there any update on when the 15.05 branch will be available via git?
 

 we will stay in trunk until at least rc2. depending on how that goes
 maybe even rc3.

 John

Ah, so we haven't branched at all yet. Is there anything specific that
needs work or testing before that happens?


  ~Jonathan bennett
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc1 / git-checkout

[Jonathan Bennett]

On Wed, May 20, 2015 at 2:32 PM, Bastian Bittorf bitt...@bluebottle.com wrote:
 * Steven Barth cy...@openwrt.org [20.05.2015 19:43]:
 http://downloads.openwrt.org/chaos_calmer/15.05-rc1/

 Thank you!

 when will this work?:
 git clone git://git.openwrt.org/15.05/openwrt.git

Is there any update on when the 15.05 branch will be available via git?

~Jonathan bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] libqrcode

[Jonathan Bennett]

I see libqrencode still exists in the main openwrt repo, instead of being
moved over to the packages feed. There is also no maintainer tag in the
Makefile, and the project is a minor release behind. (
https://dev.openwrt.org/browser/packages/libs/qrencode/Makefile)

I am considering adding qr code support to a luci app. My thought it is to
take over maintaining of libqrencode, move it to the github packages repo,
and add the binary file, qrencode, as a second .ipk.

Is there a reason that libqrencode is still in the main project repo, and
is there a maintainer for the project?

Thanks,
Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Missing dependency on host sed?

[Jonathan Bennett]

Are you building with multiple processes (-j 2 or greater)? This reminds me
of an old bug that only popped up after a make distclean when building with
multiple build threads.

~Jonathan Bennett
On Sep 16, 2014 6:55 PM, John Szakmeister j...@szakmeister.net wrote:

 I'm finding that I'm running into an issue occasionally when trying to
 build.  It appears that Make is trying to build gcc, but the host sed
 hasn't been built yet so it ultimately fails:

 checking for i686-linux-gnu-gcc option to accept ISO C89... bash:
 /home/jszakmeister/projects/openwrt/staging_dir/host/bin
 /sed: No such file or directory
 (cached) make[2]: ***

 [/home/jszakmeister/projects/openwrt/build_dir/toolchain-arm_arm926ej-s_gcc-4.6-linaro_uClibc-0.9.33
 .2_eabi/gcc-linaro-4.6-2013.05/.prepared] Error 127


 Any ideas on how to fix this?

 -John
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Missing dependency on host sed?

[Jonathan Bennett]

In your tree, in the file tools/sed/Makefile, change HOST_BUILD_PARALLEL:=1
to HOST_BUILD_PARALLEL:=0 and see if that fixes the error.
On Sep 16, 2014 7:47 PM, John Szakmeister j...@szakmeister.net wrote:

 On Tue, Sep 16, 2014 at 8:32 PM, Jonathan Bennett jbscienc...@gmail.com
 wrote:
  Are you building with multiple processes (-j 2 or greater)? This reminds
 me
  of an old bug that only popped up after a make distclean when building
 with
  multiple build threads.

 Yes sir, I am.  On the machine this is failing on, I'm attempting to
 build with -j4.

 -John

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Missing dependency on host sed?

[Jonathan Bennett]

I'll throw a couple thoughts out, and then defer to someone that
understands the openwrt build env better than I do.
First, you do have sed installed on your host system, right? I don't think
this is the issue, but best to check the easy things first. Also, a make
distclean sometimes clears up these problems.

Try compiling without a -j flag. I suspect that this is a parallel build
issue. If you can recreate it without -j, then the rest of this message is
a moot point.

Now, what I think is happening here is that we have a race between a couple
of compilation threads, one of which is the sed utility. What happens is
something that uses sed is trying to compile before sed has finished
compiling. The build env queues up a bunch of programs to compile, and
because sed takes quite a while to compile, it chews through that queue and
hits something that calls sed before sed exists. It would be helpful if we
could discern exactly which package is failing.

That said, I have put a sleep 500 in my sed makefile, which basically
means that every other package that is allowed to do so will build and
install first, and I have been unable to reproduce.


If it's not cleared up shortly, go ahead and open a ticket on
dev.openwrt.org

~Jonathan Bennett

On Tue, Sep 16, 2014 at 8:43 PM, John Szakmeister j...@szakmeister.net
wrote:

 On Tue, Sep 16, 2014 at 9:32 PM, Jonathan Bennett jbscienc...@gmail.com
 wrote:
  In your tree, in the file tools/sed/Makefile, change
 HOST_BUILD_PARALLEL:=1
  to HOST_BUILD_PARALLEL:=0 and see if that fixes the error.

 Unfortunately, it didn't help.  I think the issue is that
 linux-headers needs the SED utility, but it's not being built ahead of
 toolchain/prepare rather than sed failing to build with multiple jobs.
 It seems like a dependency is getting filtered out somehow... perhaps
 as part of the tools_enabled line in tools/Makefile (towards the
 bottom)? :-(

 -John

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1

[Jonathan Bennett]

On Mon, Jul 14, 2014 at 4:12 AM, John Crispin j...@phrozen.org wrote:


 The OpenWrt developers are proud to announce the first release
 candidate of OpenWrt Barrier Breaker.
   ___ __
  |   |.-.-.-.|  |  |  |..|  |_
  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
  |___||   __|_|__|__||||__|  ||
   |__| W I R E L E S S   F R E E D O M
  -
  BARRIER BREAKER (14.07 RC1)
  -
   * 1/2 oz Galliano Pour all ingredients into
   * 4 oz cold Coffeean irish coffee mug filled
   * 1 1/2 oz Dark Rum   with crushed ice. Stir.
   * 2 tsp. Creme de Cacao
  -

 http://downloads.openwrt.org/barrier_breaker/14.07-rc1/

 ** Highlights since Attitude Adjustment **
 Default configuration and images

 * Linux kernel updated to version 3.10

 * Procd: new preinit, init, hotplug and event system written in C

 * Native IPv6-support
 - RA  DHCPv6+PD client and server
 - Local prefix allocation  source-restricted routes
   (multihoming)

 * Filesystem improvements
 - Added support for sysupgrade on NAND-flash
 - Added support for filesystem snapshot and rollback
 - Rewritten mounting system in C for rootfs and block devices

 * UCI configuration improvements
 - Support for testing configuration and rollback to working
   last working state
 - Unified change trigger system to restart services on-demand
 - Added a data validation layer

 * Networking improvements
 - Netifd now handles setup and configuration reload of
   wireless interfaces
 - Added reworked event support to allow obsoleting network
   hotplug-scripts
 - Added support for dynamic firewall rules and zones
 - Added support for transparent multicast to unicast
   translation for bridges
 - Various other fixes and improvements


 Additional highlights selectable in the package feeds or SDK
 * Extended IPv6-support
 - Added DS-Lite support and improved 6to4, 6in4 and 6rd-support
 - Experimental support for Lightweight 4over6, MAP-E and MAP-T
 - Draft-support for self-managing home networks (HNCP)

 * rpcd: new JSONRPC over HTTP-frontend for remote access to ubus

 * mdns: new lightweight mdns daemon (work in progress)

 * Initial support for the musl C standard library

 * Support for QMI-based 3g/4g modems

 * Support for DNSSEC validation

 * Added architecture for package signing and SHA256 hashing

 * ... and many more cool things

 Package feed reorganization
 For quite a while already we are not very satisfied with the quality
 of the packages-feed. To address this, we decided to do a fresh start
 on GitHub. The new feed https://github.com/openwrt/packages should be
 used from now on and package maintainers are asked to move their
 packages there. For the final release we will still build the old
 packages feed but it will be necessary to enable it manually in the
 opkg package list to be usable. All current feeds should not have any
 dependencies on the old.packages feed. Currently a few packages still
 fail, mainly due to these cross feed dependencies. We will contact the
 respective maintainers to help resolve these issues for RC2.


 New build servers
 We would like to express our gratitude to Imagination Technology for
 funding the 2 build servers that we used for the release.


 Whats next ?
 We aim at releasing Chaos Calmer (CC) before the end of the year. The
 CC release will use 3.14 or a newer LTS kernel as baseline.


 Have fun!
 The OpenWrt developer team
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Is Barrier Breaker actually a branched release, or is this more of a trunk
snapshot?

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [Patch] [Resend] Add terminfo file in ncurses

[Jonathan Bennett]

Didn't hear back on this, and realized I didn't quite format the previous
email correctly.


Ran into a problem SSHing into an Openwrt router from a Fedora machine.
Fedora sets terminfo to xterm-256color, but ncurses installed in openwrt
doesn't include that file in the firmware. This causes a few unintended
problems, namely nano fails to launch.
Attached patch adds xterm-256color to the files installed by ncurses.

Signed-off-by: Jonathan Bennett jbscienc...@gmail.com

diff --git a/package/libs/ncurses/Makefile b/package/libs/ncurses/Makefile
index 62ffdfb..26b7bf5 100644
--- a/package/libs/ncurses/Makefile
+++ b/package/libs/ncurses/Makefile
@@ -101,7 +101,7 @@ ifneq ($(HOST_OS),FreeBSD)
  mv dir (echo -ne \xdir); \
  done \
  )
- for file in a/ansi d/dumb l/linux r/rxvt r/rxvt-unicode s/screen v/vt100
v/vt102 x/xterm x/xterm-color; do \
+ for file in a/ansi d/dumb l/linux r/rxvt r/rxvt-unicode s/screen v/vt100
v/vt102 x/xterm x/xterm-color x/xterm-256color; do \
  $(INSTALL_DIR) $(1)/usr/share/terminfo/`dirname file`; \
  $(CP) $(PKG_INSTALL_DIR)/usr/share/terminfo/file \
  $(1)/usr/share/terminfo/file; \
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Add terminfo file in ncurses

[Jonathan Bennett]

Ran into a problem with my Fedora Linux machine, SSHing into an Openwrt
router. Fedora sets terminfo to xterm-256color, but ncurses doesn't include
that file in the firmware. This causes a few unintended problems, namely
nano fails to launch. Attached patch adds xterm-256color to the files
installed by ncurses.

Signed-off-by: Jonathan Bennett jbscienc...@gmail.com



diff --git a/package/libs/ncurses/Makefile b/package/libs/ncurses/Makefile
index 62ffdfb..26b7bf5 100644
--- a/package/libs/ncurses/Makefile
+++ b/package/libs/ncurses/Makefile
@@ -101,7 +101,7 @@ ifneq ($(HOST_OS),FreeBSD)
  mv dir (echo -ne \xdir); \
  done \
  )
- for file in a/ansi d/dumb l/linux r/rxvt r/rxvt-unicode s/screen v/vt100
v/vt102 x/xterm x/xterm-color; do \
+ for file in a/ansi d/dumb l/linux r/rxvt r/rxvt-unicode s/screen v/vt100
v/vt102 x/xterm x/xterm-color x/xterm-256color; do \
  $(INSTALL_DIR) $(1)/usr/share/terminfo/`dirname file`; \
  $(CP) $(PKG_INSTALL_DIR)/usr/share/terminfo/file \
  $(1)/usr/share/terminfo/file; \
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [packages] Update Fwknop to 2.5.1

[Jonathan Bennett]

Ping. This patch is on the tracker: http://patchwork.openwrt.org/patch/3861/
As I am the maintainer, but have no commit access, I would ask that someone
with commit access would commit this patch to trunk and 12.09.

Thanks,
Jonathan Bennett


On Thu, Jul 25, 2013 at 11:38 PM, Jonathan Bennett jbscienc...@gmail.comwrote:

 This is a minor update to fwknop that just released. This supersedes the
 previously submitted patch.
 Again, if this could be pushed into 12.09, it would be great.
 Signed-off-by: Jonathan Bennett jbscienc...@gmail.com

 diff --git a/net/fwknop/Makefile b/net/fwknop/Makefile
 index 24d7385..a0d0454 100644
 --- a/net/fwknop/Makefile
 +++ b/net/fwknop/Makefile
 @@ -8,12 +8,12 @@
  include $(TOPDIR)/rules.mk

  PKG_NAME:=fwknop
 -PKG_VERSION:=2.0
 +PKG_VERSION:=2.5.1
  PKG_RELEASE:=1

  PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
  PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
 -PKG_MD5SUM:=96de4c5a4ae75a8618ef80269c6a70ad
 +PKG_MD5SUM:=f4661c6c8f3e03bd58b8b022adeef240

  PKG_INSTALL:=1

 diff --git a/net/fwknop/patches/001-fix_config.patch
 b/net/fwknop/patches/001-fix_config.patch
 index 5ae4a94..93a261f 100644
 --- a/net/fwknop/patches/001-fix_config.patch
 +++ b/net/fwknop/patches/001-fix_config.patch
 @@ -1,20 +1,20 @@
  a/server/fwknopd.conf
 -+++ b/server/fwknopd.conf
 -@@ -29,7 +29,12 @@
 - # Define the ethernet interface on which we will sniff packets.
 - # Default if not set is eth0.
 +--- a/server/fwknopd.conf.inst
  b/server/fwknopd.conf.inst
 +@@ -37,7 +37,12 @@
 + # Default if not set is eth0.  The '-i intf' command line option
 overrides
 + # the PCAP_INTF setting.
   #
  -#PCAP_INTF   eth0;
 -+
  +# The following line is changed specifically for Openwrt.
  +# Openwrt defaults to using eth1 as its wan port. If using PPPoE,
  +# Then this needs to be set to pppoe-wan.
  +
  +PCAP_INTF   eth1;
 ++

   # By default fwknopd does not put the pcap interface into promiscuous
 mode.
   # Set this to 'Y' to enable promiscuous sniffing.
 -@@ -252,8 +257,13 @@
 +@@ -279,8 +284,13 @@
   # The IPT_FORWARD_ACCESS variable is only used if ENABLE_IPT_FORWARDING
 is
   # enabled.
   #

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [packages] Update Fwknop to 2.5.1

[Jonathan Bennett]

Setting a mostly sane default value there has been perfectly fine for the
last 3 versions of fwknop included with Openwrt. I understand that this
default value will not always be correct. That said, fwknop *always*
requires modifications to the config files. To set up the ports and set the
password, one has to modify the config files.

I would like to eventually build a uci based config for fwknop and a luci
module. Until then, it remains the flat config file. And just like a
desktop install, we've put a sane default in the config file. And just like
a desktop install, if it's wrong, the user can change it.

The routers I use default to eth1. If the consensus is that eth1 is not a
sane default, I can drop the config patch altogether. It will default to
eth0, which makes sense for most desktops. In that case, the same idea
applies: the user can change it if needed.

I'm not willing to put a kludge in the firstboot scripts, or even worse, a
wrapper script that tries to figure out if it's been run before, and
detects and writes to the config. The last thing we need is a config file
that thinks it's smarter than the user.

So RFC here. Should I retain the patch that sets the capture port to eth1
or drop the patch and let it default to eth0? Or is there a good way to
detect the wan port and write it to the config, but only on firstboot?


On Fri, Aug 2, 2013 at 8:34 AM, Bastian Bittorf bitt...@bluebottle.comwrote:

 * Jonathan Bennett jbscienc...@gmail.com [02.08.2013 15:22]:
+# The following line is changed specifically for Openwrt.
+# Openwrt defaults to using eth1 as its wan port. If using PPPoE,
+# Then this needs to be set to pppoe-wan.
+
+PCAP_INTF   eth1;

 nobody will commit this.
 there is no easy way to detect

 a)
 is there any wan port?

 b)
 which wan (if there is more than one) you want to use

 you can guess your wan during first run via something like.

 get_wandev()
 {
 local wandev

 # e.g.
 # 0.0.0.0  10.63.76.1  0.0.0.0  UG  2  0  0 wlan0-1

 set -- $( route -n | grep ^'0\.0\.0\.0' | head -n1 )
 while [ -n $1 ]; do wandev=$1; shift; done  # lastword

 echo wandev
 }

 but this is not 100% - any other suggestions?

 best would be to write a wrapper, which takes uci-vars and builds a
 correct config for you program out of this.

 bye, bastian
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] [packages] Update Fwknop to 2.5.1

[Jonathan Bennett]

This is a minor update to fwknop that just released. This supersedes the
previously submitted patch.
Again, if this could be pushed into 12.09, it would be great.
Signed-off-by: Jonathan Bennett jbscienc...@gmail.com

diff --git a/net/fwknop/Makefile b/net/fwknop/Makefile
index 24d7385..a0d0454 100644
--- a/net/fwknop/Makefile
+++ b/net/fwknop/Makefile
@@ -8,12 +8,12 @@
 include $(TOPDIR)/rules.mk

 PKG_NAME:=fwknop
-PKG_VERSION:=2.0
+PKG_VERSION:=2.5.1
 PKG_RELEASE:=1

 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
 PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
-PKG_MD5SUM:=96de4c5a4ae75a8618ef80269c6a70ad
+PKG_MD5SUM:=f4661c6c8f3e03bd58b8b022adeef240

 PKG_INSTALL:=1

diff --git a/net/fwknop/patches/001-fix_config.patch
b/net/fwknop/patches/001-fix_config.patch
index 5ae4a94..93a261f 100644
--- a/net/fwknop/patches/001-fix_config.patch
+++ b/net/fwknop/patches/001-fix_config.patch
@@ -1,20 +1,20 @@
 a/server/fwknopd.conf
-+++ b/server/fwknopd.conf
-@@ -29,7 +29,12 @@
- # Define the ethernet interface on which we will sniff packets.
- # Default if not set is eth0.
+--- a/server/fwknopd.conf.inst
 b/server/fwknopd.conf.inst
+@@ -37,7 +37,12 @@
+ # Default if not set is eth0.  The '-i intf' command line option
overrides
+ # the PCAP_INTF setting.
  #
 -#PCAP_INTF   eth0;
-+
 +# The following line is changed specifically for Openwrt.
 +# Openwrt defaults to using eth1 as its wan port. If using PPPoE,
 +# Then this needs to be set to pppoe-wan.
 +
 +PCAP_INTF   eth1;
++

  # By default fwknopd does not put the pcap interface into promiscuous
mode.
  # Set this to 'Y' to enable promiscuous sniffing.
-@@ -252,8 +257,13 @@
+@@ -279,8 +284,13 @@
  # The IPT_FORWARD_ACCESS variable is only used if ENABLE_IPT_FORWARDING is
  # enabled.
  #
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] fwknop package update

[Jonathan Bennett]

On Jul 24, 2013 1:19 AM, Etienne Champetier etienne.champet...@free.fr
wrote:

 Hi

 Le 24/07/2013 02:10, Jonathan Bennett a écrit :

 The following patch updates fwknop to the newest release, v 2.5. I`m not
familiar with the standard procedures for package updates after the
official release. If possible, it would be great to update the package in
12.09 as well.

 Signed-off-by: Jonathan Bennett jbscienc...@gmail.com


 diff --git a/net/fwknop/Makefile b/net/fwknop/Makefile
 index 24d7385..80575a8 100644
 --- a/net/fwknop/Makefile
 +++ b/net/fwknop/Makefile
 @@ -8,12 +8,12 @@
  include $(TOPDIR)/rules.mk

  PKG_NAME:=fwknop
 -PKG_VERSION:=2.0
 +PKG_VERSION:=2.5
  PKG_RELEASE:=1

  PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
  PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
 -PKG_MD5SUM:=96de4c5a4ae75a8618ef80269c6a70ad
 +PKG_MD5SUM:=b9f28aba92c959946e540a822a623964

  PKG_INSTALL:=1

 diff --git a/net/fwknop/patches/001-fix_config.patch
b/net/fwknop/patches/001-fix_config.patch
 index 5ae4a94..93a261f 100644
 --- a/net/fwknop/patches/001-fix_config.patch
 +++ b/net/fwknop/patches/001-fix_config.patch
 @@ -1,20 +1,20 @@
  a/server/fwknopd.conf
 -+++ b/server/fwknopd.conf
 -@@ -29,7 +29,12 @@
 - # Define the ethernet interface on which we will sniff packets.
 - # Default if not set is eth0.
 +--- a/server/fwknopd.conf.inst
  b/server/fwknopd.conf.inst
 +@@ -37,7 +37,12 @@
 + # Default if not set is eth0.  The '-i intf' command line option
overrides
 + # the PCAP_INTF setting.
   #
  -#PCAP_INTF   eth0;
 -+
  +# The following line is changed specifically for Openwrt.
  +# Openwrt defaults to using eth1 as its wan port. If using PPPoE,
  +# Then this needs to be set to pppoe-wan.

 It depends on router model (it can also be eth0.1, ...). At runtime you
can
 execute uci -P/var/state get network.wan.ifname to get the ifname

That is a good point, but as the config files always need to be edited by
the end user to include the password, etc, I'm not inclined to add a sed or
awk command to firstboot to tweak that config.

I hope to eventually write a uci config for fwknop, which would allow for a
luci module. This seems like the better way to deal with unusual setups.

  +
  +PCAP_INTF   eth1;
 ++

   # By default fwknopd does not put the pcap interface into promiscuous
mode.
   # Set this to 'Y' to enable promiscuous sniffing.
 -@@ -252,8 +257,13 @@
 +@@ -279,8 +284,13 @@
   # The IPT_FORWARD_ACCESS variable is only used if
ENABLE_IPT_FORWARDING is
   # enabled.
   #



 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] fwknop package update

[Jonathan Bennett]

The following patch updates fwknop to the newest release, v 2.5. I`m not
familiar with the standard procedures for package updates after the
official release. If possible, it would be great to update the package in
12.09 as well.

Signed-off-by: Jonathan Bennett jbscienc...@gmail.com


diff --git a/net/fwknop/Makefile b/net/fwknop/Makefile
index 24d7385..80575a8 100644
--- a/net/fwknop/Makefile
+++ b/net/fwknop/Makefile
@@ -8,12 +8,12 @@
 include $(TOPDIR)/rules.mk

 PKG_NAME:=fwknop
-PKG_VERSION:=2.0
+PKG_VERSION:=2.5
 PKG_RELEASE:=1

 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
 PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
-PKG_MD5SUM:=96de4c5a4ae75a8618ef80269c6a70ad
+PKG_MD5SUM:=b9f28aba92c959946e540a822a623964

 PKG_INSTALL:=1

diff --git a/net/fwknop/patches/001-fix_config.patch
b/net/fwknop/patches/001-fix_config.patch
index 5ae4a94..93a261f 100644
--- a/net/fwknop/patches/001-fix_config.patch
+++ b/net/fwknop/patches/001-fix_config.patch
@@ -1,20 +1,20 @@
 a/server/fwknopd.conf
-+++ b/server/fwknopd.conf
-@@ -29,7 +29,12 @@
- # Define the ethernet interface on which we will sniff packets.
- # Default if not set is eth0.
+--- a/server/fwknopd.conf.inst
 b/server/fwknopd.conf.inst
+@@ -37,7 +37,12 @@
+ # Default if not set is eth0.  The '-i intf' command line option
overrides
+ # the PCAP_INTF setting.
  #
 -#PCAP_INTF   eth0;
-+
 +# The following line is changed specifically for Openwrt.
 +# Openwrt defaults to using eth1 as its wan port. If using PPPoE,
 +# Then this needs to be set to pppoe-wan.
 +
 +PCAP_INTF   eth1;
++

  # By default fwknopd does not put the pcap interface into promiscuous
mode.
  # Set this to 'Y' to enable promiscuous sniffing.
-@@ -252,8 +257,13 @@
+@@ -279,8 +284,13 @@
  # The IPT_FORWARD_ACCESS variable is only used if ENABLE_IPT_FORWARDING is
  # enabled.
  #
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Kernel test

[Jonathan Bennett]

On May 6, 2012 11:55 AM, Alberich de megres alberich...@gmail.com wrote:

 And for the Jtag?

Never had to use jtag, so no idea, honestly. Sorry.


 On Sun, May 6, 2012 at 7:41 AM, Jonathan Bennett jbscienc...@gmail.com
wrote:
  https://www.adafruit.com/products/70 is a great serial cable. It's
  used for ttl level serial. (If you have to solder to the board, it's
  probably ttl. If there is an actual serial port, then it's 12 v
  serial. Different device)
 
  On Sat, May 5, 2012 at 9:16 AM, Alberich de megres
  alberich...@gmail.com wrote:
  One more last question:
 
  which serial/jtag cable do you use? (if it is cheap, better)
 
  thanks!
 
 
  On Wed, May 2, 2012 at 5:55 PM, Jonathan Bennett jbscienc...@gmail.com
wrote:
  On Sat, Apr 28, 2012 at 9:22 AM, Alberich de megres
  alberich...@gmail.com wrote:
  Hi,
 
  @Jonathan,
  how get access to the bootloader?
  do you send it to the router by streaming, or write it and then boot
it?
 
  Get a serial port and watch the output as you turn it on. Normally
  there will be a message about how to interrupt the boot loader. Then
  you send your image to ram, either over tftp or the serial connection.
  then you just boot from where you loaded it in ram.
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/mailman/listinfo/openwrt-devel
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/mailman/listinfo/openwrt-devel
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Kernel test

[Jonathan Bennett]

https://www.adafruit.com/products/70 is a great serial cable. It's
used for ttl level serial. (If you have to solder to the board, it's
probably ttl. If there is an actual serial port, then it's 12 v
serial. Different device)

On Sat, May 5, 2012 at 9:16 AM, Alberich de megres
alberich...@gmail.com wrote:
 One more last question:

 which serial/jtag cable do you use? (if it is cheap, better)

 thanks!


 On Wed, May 2, 2012 at 5:55 PM, Jonathan Bennett jbscienc...@gmail.com 
 wrote:
 On Sat, Apr 28, 2012 at 9:22 AM, Alberich de megres
 alberich...@gmail.com wrote:
 Hi,

 @Jonathan,
 how get access to the bootloader?
 do you send it to the router by streaming, or write it and then boot it?

 Get a serial port and watch the output as you turn it on. Normally
 there will be a message about how to interrupt the boot loader. Then
 you send your image to ram, either over tftp or the serial connection.
 then you just boot from where you loaded it in ram.
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Update fwknop, fwknopd to latest version, use new startup commands

[Jonathan Bennett]

Following patch updates fwknop to v2.0

Signed off by Jonathan Bennett jbscienc...@gmail.com


Index: net/fwknop/patches/002-fix_init.patch
===
--- net/fwknop/patches/002-fix_init.patch   (revision 0)
+++ net/fwknop/patches/002-fix_init.patch   (revision 0)
@@ -0,0 +1,17 @@
+--- a/extras/openwrt/package/fwknop/files/fwknopd.init
 b/extras/openwrt/package/fwknop/files/fwknopd.init
+@@ -8,12 +8,12 @@ FWKNOPD_BIN=/usr/sbin/fwknopd
+
+ start()
+ {
+-  $FWKNOPD_BIN
++  service_start $FWKNOPD_BIN
+ }
+
+ stop()
+ {
+-  $FWKNOPD_BIN -K
++  service_stop $FWKNOPD_BIN -K
+ }
+
+ restart()
Index: net/fwknop/patches/001-fix_config.patch
===
--- net/fwknop/patches/001-fix_config.patch (revision 31494)
+++ net/fwknop/patches/001-fix_config.patch (working copy)
@@ -1,6 +1,6 @@
 --- a/server/fwknopd.conf
 +++ b/server/fwknopd.conf
-@@ -30,7 +30,12 @@
+@@ -29,7 +29,12 @@
  # Define the ethernet interface on which we will sniff packets.
  # Default if not set is eth0.
  #
@@ -14,7 +14,7 @@

  # By default fwknopd does not put the pcap interface into promiscuous mode.
  # Set this to 'Y' to enable promiscuous sniffing.
-@@ -239,8 +244,13 @@
+@@ -252,8 +257,13 @@
  # The IPT_FORWARD_ACCESS variable is only used if ENABLE_IPT_FORWARDING is
  # enabled.
  #
Index: net/fwknop/Makefile
===
--- net/fwknop/Makefile (revision 31494)
+++ net/fwknop/Makefile (working copy)
@@ -8,12 +8,12 @@
 include $(TOPDIR)/rules.mk

 PKG_NAME:=fwknop
-PKG_VERSION:=2.0.0rc4
+PKG_VERSION:=2.0
 PKG_RELEASE:=1

 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
 PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
-PKG_MD5SUM:=4f5d45187429ca56d3b444ab96c57fb6
+PKG_MD5SUM:=96de4c5a4ae75a8618ef80269c6a70ad

 PKG_INSTALL:=1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Kernel test

[Jonathan Bennett]

On Sat, Apr 28, 2012 at 9:22 AM, Alberich de megres
alberich...@gmail.com wrote:
 Hi,

 @Jonathan,
 how get access to the bootloader?
 do you send it to the router by streaming, or write it and then boot it?

Get a serial port and watch the output as you turn it on. Normally
there will be a message about how to interrupt the boot loader. Then
you send your image to ram, either over tftp or the serial connection.
then you just boot from where you loaded it in ram.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 1/3 V1] correct eglibc version numbers

[Jonathan Bennett]

On Mon, Apr 30, 2012 at 4:45 AM, Emmanuel Deloget
emmanuel.delo...@efixo.com wrote:
 Le 28/04/2012 22:50, Mirko Vogt a écrit :

 By the way: All your patches didn't apply out of the box due to
 whitespace errors.


 My bad. I think I did a straight svn diff + select the text in my
 xterm and copy it using the middle button. That may have changed
 the whitespaces here and there. I'll do somethign better for my
 next patches.

I've found that problem, too. What works for me is using the redirect symbol 
So something like
svn diff  new_feature.patch

Open that file with kwrite, and then copy the code. This seems to
preserve correct whitespace.

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Kernel test

[Jonathan Bennett]

Do you have a serial port, and access to the bootloader? First step,
generally, is to try a ramboot image. You transfer it and boot from
ram using the boot loader. Watch the serial output to get an idea of
what changes you need to support the board.

~Jonathan Bennett

On Sat, Apr 28, 2012 at 6:58 AM, Alberich de megres
alberich...@gmail.com wrote:
 Hello Guys,

 I'm newbie at openwrt, since now I've used allways boards with jtag.
 I have a cisco e3000 router, which I bought some time ago, and I think
 is time to give it a try with openwrt.

 I saw there's no official build for the router, but some promising
 test. My question is how you test/develop the kernel for this routers?

 Let's suppose I don't have the jtag access, and normally we don't hit
 with the first try (on a new kernel porting) a full working kernel.
 How you test those new kernels?

 Thanks!!!
 Alberich
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Buildbot

[Jonathan Bennett]

Do we still have need for more buildbot machines? I have a Phenom II 4
core that is set up just for building openwrt. I'm willing to add it
to the build bot if it's still needed. Let me know.

Thanks,
Jonathan Bennett
Incom Systems
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] netifd

[Jonathan Bennett]

Just for kicks, I decided to compile bleeding edge trunk and try out
the new netifd system. I attempted to connect to my cable modem via
dhcp, and this error showed up in the log:
Sep  8 15:44:59 OpenWrt daemon.notice netifd: wan (1223): ./dhcp.sh:
eval: line 1: proto_dhcp_setup: not found

After a bit of digging, I made a change to /lib/netifd/proto/dhcp.sh
Changing the function name from dhcp_setup() to proto_dhcp_setup().
I'm not sure if this is the correct fix, but dhcp is currently broken
in nefifd.

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] assistance with porting to TEW-634GRU

[Jonathan Bennett]

On Fri, Sep 30, 2011 at 11:35 PM, Samuel Sieb sam...@sieb.net wrote:
 I have a bunch of TEW-634GRU access points that I would like to port openwrt
 to.  I have serial access and I can read and write the flash from the
 current embedded Linux system.  As far as I can tell all the parts are
 supported, I believe it is very similar to the TL-WR1043ND which I currently
 have running openwrt.  Would someone be able to explain what steps I need to
 add support?

 Specs:
 Flash: 4MB
 RAM: 32MB
 switch: rtl8366
 CPU: AR9100
 WIFI: AR5416 (?)

 Any other information that would be useful?
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel



You should be able to get something running fairly easily. First step
is to get serial access and access to the bootloader. To start, try
compiling a ramdisk version of the 1043, uploading it to ram, and
booting it from there. Start with the 1043 code, and see how much of
it works.

To write the actual support into openwrt, take a look at the changes
that others have made to add new devices. Juhosg has added several
devices in the last few months, and I've used those as templates for
working on new devices.

It's also useful to start a thread on the forums and report your
progress there. Some will chip in with help and advice.

Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Ath9k/hostapd connection dropping problems

[Jonathan Bennett]

Peter, on your Linux machine, you can connect from the command line using
wpasupplicant and get much more detailed info about what is going on.
On Sep 16, 2011 1:26 PM, Peter Naulls pe...@chocky.org wrote:

 Some of this is speculation. I wish I had more precise details. This is
true
 of all trunk versions in last few weeks, when I started using my G300H
(v2)
 as an AP. This includes upto version r28254, which includes yesterday's
 mac80211 patches, but not today's spam fixes.

 I have two Linux machines connecting to it. After some amount of time - or
 what seems more likely, data, the WiFi connections will drop. If left
 alone, they will come back after about 5 minutes. But it's usually
 faster to reboot the router.

 I believe that:

 * LAN side is unaffected.
 * It happens after a certain about of traffic, rather than time, since
it'll
 be fine during the night when not much is happening, but be triggered
during
 a download etc during the day.
 * Attempts to reproduce by running large amounts of traffic with iperf
from
 WiFi - Wired LAN have been inconsistent.
 * In one case where I saw it triggered, I restarted hostapd, and it seemed
to
 come back, although NetworkManager on Ubuntu become confused, so I'm
 not certain.
 * There is nothing of consequence in kernel logs, apart from regular
messages
 from hostapd about group key handshake.

 So, I'm after ideas about more precise information I can gather, debug
 I can turn on, etc, etc.


 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Any recent changes to wireless that would explain problems with wireless?

[Jonathan Bennett]

On Sun, Aug 28, 2011 at 1:55 PM, Jim Henderson hende...@gmail.com wrote:
 I updated to r28089 yesterday and have noticed a significant number of
 problems with wireless since then.

 The hardware is a D-Link DIR-825.  I only use Radio0 for my wireless.

 Normally, I can stream video without any problems to our Playstation over
 the wireless network, but yesterday when I tried (after updating), I kept
 getting the dreaded DLNA 2104 error, and the PS3 kept dropping off
 Playstation Network as well.

 I also tried extended network operations using a Dell D610 laptop running
 openSUSE 11.4, and it also kept getting knocked off the network.  It also
 intermittently couldn't even get an IP address.


I've seen similar issues with a similar revision. I'm currently
testing 28096, and I'm not yet seeing any issues. Hopefully the bump
to the newest wireless drivers has improved the situation.

Out of curiosity, are you using wpa or wpa2 encryption? Does your
router log show any strange errors?

 When I started updating from SVN today, I noticed the first couple of
 files changed since building yesterday seemed related to wireless, so I
 thought I'd ask if anyone else is seeing similar issues.

 Jim


~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Package update: fwknop

[Jonathan Bennett]

This patch updates fwknop to the newest version: 2.0.0rc4 and includes
a few tweaks suggested by swalker. It also adds the fwknop client to
openwrt and includes a patch that changes a few default fwknopd
configuration options to more sane values for Openwrt.

Signed off by: Jonathan Bennett jbscienc...@gmail.com


Index: net/fwknop/patches/001-fix_config.patch
===
--- net/fwknop/patches/001-fix_config.patch (revision 0)
+++ net/fwknop/patches/001-fix_config.patch (revision 0)
@@ -0,0 +1,32 @@
+--- a/server/fwknopd.conf
 b/server/fwknopd.conf
+@@ -30,7 +30,12 @@
+ # Define the ethernet interface on which we will sniff packets.
+ # Default if not set is eth0.
+ #
+-#PCAP_INTF   eth0;
++
++# The following line is changed specifically for Openwrt.
++# Openwrt defaults to using eth1 as its wan port. If using PPPoE,
++# Then this needs to be set to pppoe-wan.
++
++PCAP_INTF   eth1;
+
+ # By default fwknopd does not put the pcap interface into promiscuous mode.
+ # Set this to 'Y' to enable promiscuous sniffing.
+@@ -239,8 +244,13 @@
+ # The IPT_FORWARD_ACCESS variable is only used if ENABLE_IPT_FORWARDING is
+ # enabled.
+ #
+-#IPT_FORWARD_ACCESS  ACCEPT, filter, FORWARD, 1, FWKNOP_FORWARD, 1;
+-#IPT_DNAT_ACCESS DNAT, nat, PREROUTING, 1, FWKNOP_PREROUTING, 1;
++
++# These two lines are changed specifically for Openwrt, due to
++# different naming conventions. IPT_FORWARD is still disabled
++# by default, and must be enabled earlier in this file to be used.
++
++IPT_FORWARD_ACCESS  ACCEPT, filter, zone_wan_forward, 1,
FWKNOP_FORWARD, 1;
++IPT_DNAT_ACCESS DNAT, nat, zone_wan_prerouting, 1,
FWKNOP_PREROUTING, 1;
+
+ # The IPT_SNAT_ACCESS variable is not used unless both ENABLE_IPT_SNAT and
+ # ENABLE_IPT_FORWARDING are enabled.  Also, the external static IP must be
Index: net/fwknop/Makefile
===
--- net/fwknop/Makefile (revision 28080)
+++ net/fwknop/Makefile (working copy)
@@ -1,27 +1,30 @@
+# Copyright (C) 2011 OpenWrt.org
+#
+# This is free software, licensed under the GNU General Public License v2.
+# See /LICENSE for more information.
+#
+
 include $(TOPDIR)/rules.mk

-PKG_NAME:=fwknopd
-PKG_VERSION:=2.0.0rc2
+PKG_NAME:=fwknop
+PKG_VERSION:=2.0.0rc4
 PKG_RELEASE:=1

 PKG_BUILD_DIR:=$(BUILD_DIR)/fwknop-$(PKG_VERSION)
 PKG_SOURCE:=fwknop-$(PKG_VERSION).tar.gz
 PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
-PKG_MD5SUM:=c78252216fa9627cacf61b453da915a8
+PKG_MD5SUM:=13ee56d5f9b9cfb37cb994f6df39f5c2
 PKG_CAT:=zcat
 include $(INCLUDE_DIR)/package.mk

-define Package/fwknopd
-  SECTION:=net
-  CATEGORY:=Network
-  TITLE:=Firewall Knock Operator Daemon
+define Package/fwknop/Default
+  TITLE:=Firewall Knock Operator
   URL:=http://http://www.cipherdyne.org/fwknop/
   MAINTAINER:=Jonathan Bennett jbscienc...@gmail.com
-  DEPENDS:=+libpcap +libgdbm +iptables
 endef

-define Package/fwknopd/description
-  Firewall Knock Operator Daemon
+define Package/fwknop/Default/description
+  Firewall Knock Operator
   Fwknop implements an authorization scheme known as Single Packet
   Authorization (SPA) for Linux systems running iptables.  This
   mechanism requires only a single encrypted and non-replayed
@@ -33,28 +36,77 @@
   (both 0-day and unpatched code) much more difficult.
 endef

-define Package/conffiles
+define Package/fwknopd
+  $(call Package/fwknop/Default)
+  SECTION:=net
+  CATEGORY:=Network
+  TITLE+= Daemon
+  DEPENDS:=+iptables +libfko +libpcap
+endef
+
+define Package/fwknopd/description
+  $(call Package/fwknop/Default/description)
+  This package contains the fwknop daemon.
+endef
+
+define Package/fwknopd/conffiles
 /etc/fwknop/fwknopd.conf
 /etc/fwknop/access.conf
 endef

+define Package/fwknop
+  $(call Package/fwknop/Default)
+  SECTION:=net
+  CATEGORY:=Network
+  TITLE+= Client
+  DEPENDS:=+libfko
+endef
+
+define Package/fwknop/description
+  $(call Package/fwknop/Default/description)
+  This package contains the fwknop client.
+endef
+
+define Package/libfko
+  $(call Package/fwknop/Default)
+  SECTION:=libs
+  CATEGORY:=Libraries
+  TITLE+= Library
+endef
+
+define Package/libfko/description
+  $(call Package/fwknop/Default/description)
+  This package contains the libfko shared library.
+endef
+
+
+
 CONFIGURE_ARGS += \
-   --disable-client \
--without-gpgme \
--with-iptables=/usr/sbin/iptables

+
 define Package/fwknopd/install
$(INSTALL_DIR) $(1)/etc/init.d
$(INSTALL_BIN) $(PKG_BUILD_DIR)/extras/fwknop.init.openwrt \
$(1)/etc/init.d/fwknopd
$(INSTALL_DIR) $(1)/usr/sbin
$(INSTALL_BIN) $(PKG_BUILD_DIR)/server/.libs/fwknopd $(1)/usr/sbin/
-   $(INSTALL_DIR) $(1)/usr/lib
-   $(CP) $(PKG_BUILD_DIR)/lib/.libs/libfko.so* $(1)/usr/lib/
$(INSTALL_DIR) $(1)/etc/fwknop
$(INSTALL_CONF) $(PKG_BUILD_DIR)/server

Re: [OpenWrt-Devel] [Fwknop-discuss] fwknop in openwrt

[Jonathan Bennett]

Not sure why, but it's taking the openwrt folks a while to pull fwknop
into trunk. Until that happens, if any of you want to play around with
the binaries, let me know what target you're running on, and I'll be
happy to send you the .ipk file.

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] New package: fwknopd

[Jonathan Bennett]

On Aug 10, 2011 6:59 PM, Stephen Walker stephendwal...@gmail.com wrote:

 Is there a reason for the client being disabled?

The main reason is to save space. I have no problem adding it as a second
package. As they result in seperate binaries, it would make more sense to
roll them as separate packages, IMHO. I don't expect the client to be of
much use in an embedded/router setting, but if there is interest, I can
package the client as well.

Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] New package: fwknopd

[Jonathan Bennett]

Ping

Not sure who exactly clears new packages for the packages feed, but it
would be great if we could get my patch for fwknopd applied. It is
#1233 in patchwork. Several of the fwknop guys are looking forward to
using this in openwrt, and it's easier for them to use it if it's in
the packages feed. Let me know if you need anything from me.

~Jonathan Bennett

On Wed, Jul 27, 2011 at 12:36 PM, Jonathan Bennett
jbscienc...@gmail.com wrote:
 Ping

 Any progress on getting this approved? Do I need to supply any
 additional information?

 Thanks,
 Jonathan Bennett

 On Thu, Jul 21, 2011 at 5:06 PM, Jonathan Bennett jbscienc...@gmail.com 
 wrote:
 That time was my fault. Should be fixed now.
 Signed off by Jonathan Bennett jbscienc...@gmail.com


 Index: net/fwknop/Makefile
 ===
 --- net/fwknop/Makefile (revision 0)
 +++ net/fwknop/Makefile (revision 0)
 @@ -0,0 +1,65 @@
 +include $(TOPDIR)/rules.mk
 +
 +PKG_NAME:=fwknopd
 +PKG_VERSION:=2.0.0rc2
 +PKG_RELEASE:=1
 +
 +PKG_BUILD_DIR:=$(BUILD_DIR)/fwknop-$(PKG_VERSION)
 +PKG_SOURCE:=fwknop-$(PKG_VERSION).tar.gz
 +PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
 +PKG_MD5SUM:=c78252216fa9627cacf61b453da915a8
 +PKG_CAT:=zcat
 +include $(INCLUDE_DIR)/package.mk
 +
 +define Package/fwknopd
 +       SECTION:=net
 +       CATEGORY:=Network
 +       DEFAULT:=n
 +       TITLE:=Firewall Knock Operator Daemon
 +       URL:=http://http://www.cipherdyne.org/fwknop/
 +       MAINTAINER:=Jonathan Bennett jbscienc...@gmail.com
 +       DEPENDS:=+libpcap +libgdbm +iptables
 +endef
 +
 +define Package/fwknopd/description
 +       Firewall Knock Operator Daemon
 +       Fwknop implements an authorization scheme known as Single Packet
 +       Authorization (SPA) for Linux systems running iptables.  This
 +       mechanism requires only a single encrypted and non-replayed
 +       packet to communicate various pieces of information including
 +       desired access through an iptables policy. The main application
 +       of this program is to use iptables in a default-drop stance to
 +       protect services such as SSH with an additional layer
 +       of security in order to make the exploitation of vulnerabilities
 +       (both 0-day and unpatched code) much more difficult.
 +endef
 +
 +define Package/Conffiles
 +       fwknopd.conf
 +endef
 +
 +CONFIGURE_ARGS += \
 +       --disable-client \
 +       --without-gpgme \
 +       --with-iptables=/usr/sbin/iptables
 +
 +
 +
 +define Package/fwknopd/install
 +       $(INSTALL_DIR) $(1)/usr/sbin
 +       $(INSTALL_DIR) $(1)/etc/fwknop
 +       $(INSTALL_DIR) $(1)/etc/init.d
 +       $(INSTALL_DIR) $(1)/usr/lib
 +       $(INSTALL_BIN) $(PKG_BUILD_DIR)/extras/fwknop.init.openwrt \
 +               $(1)/etc/init.d/fwknopd
 +       $(INSTALL_BIN) $(PKG_BUILD_DIR)/server/.libs/fwknopd $(1)/usr/sbin/
 +       $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2 \
 +               $(1)/usr/lib/libfko.so.0
 +       $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2 \
 +               $(1)/usr/lib/libfko.so.0.0.2
 +       $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/fwknopd.conf $(1)/etc/fwknop/
 +       $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/access.conf $(1)/etc/fwknop/
 +
 +endef
 +
 +$(eval $(call BuildPackage,fwknopd))


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Fwd: Open WRT on TP-Link TL WR940N

[Jonathan Bennett]

On Aug 2, 2011 3:13 PM, Hartmut Knaack knaac...@gmx.de wrote:

 TP-Link offers only one firmware version for the 940nd, so most likely
 it will work. But you might be the first one to test.
Tp-link uses the minor version to refer to firmware upgrades. The hardware
is identical to 1.0

 Krisztián Szabolcs Erdélyi schrieb:
 
 
  Dear All!
 
  I'm looking for a solution with open WRT.
  I find the description
  on http://wiki.openwrt.org/toh/tp-link/tl-wr940n says 'Hardware
  Version: WR940N v1'
 
  openwrt-ar71xx-tl-wr941nd-v4-squashfs-factory.bin image works well.
 
 
  Supported Versions
 
  Version/Model OpenWrt Version Supported   Model Specific
Notes
  v1.0  Backfire 10.03 WR941NDv4Similar to WR941NDv4
 
 
  But I can only buy WR940N v1.2
  Does the openwrt-ar71xx-tl-wr941nd-v4-squashfs-factory.bin work well
  on the v1.2 as well??
 
  Thanks a lot, Best Regards, Krisztian.
 
 
 
 
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] New package: fwknopd

[Jonathan Bennett]

Previous submission mangled a few lines. Fixed (hopefully ) here.
Signed off by Jonathan Bennett jbscienc...@gmail.com


Index: net/fwknop/Makefile
===
--- net/fwknop/Makefile (revision 0)
+++ net/fwknop/Makefile (revision 0)
@@ -0,0 +1,65 @@
+include $(TOPDIR)/rules.mk
+
+PKG_NAME:=fwknopd
+PKG_VERSION:=2.0.0rc2
+PKG_RELEASE:=1
+
+PKG_BUILD_DIR:=$(BUILD_DIR)/fwknop-$(PKG_VERSION)
+PKG_SOURCE:=fwknop-$(PKG_VERSION).tar.gz
+PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
+PKG_MD5SUM:=c78252216fa9627cacf61b453da915a8
+PKG_CAT:=zcat
+include $(INCLUDE_DIR)/package.mk
+
+define Package/fwknopd
+   SECTION:=net
+   CATEGORY:=Network
+   DEFAULT:=n
+   TITLE:=Firewall Knock Operator Daemon
+   URL:=http://http://www.cipherdyne.org/fwknop/
+   MAINTAINER:=Jonathan Bennett jbscienc...@gmail.com
+   DEPENDS:=+libpcap +libgdbm +iptables
+endef
+
+define Package/fwknopd/description
+   Firewall Knock Operator Daemon
+   Fwknop implements an authorization scheme known as Single Packet
+   Authorization (SPA) for Linux systems running iptables.  This
+   mechanism requires only a single encrypted and non-replayed
+   packet to communicate various pieces of information including
+   desired access through an iptables policy. The main application
+   of this program is to use iptables in a default-drop stance to
+   protect services such as SSH with an additional layer
+   of security in order to make the exploitation of vulnerabilities
+   (both 0-day and unpatched code) much more difficult.
+endef
+
+define Package/Conffiles
+   fwknopd.conf
+endef
+
+CONFIGURE_ARGS += \
+   --disable-client \
+   --without-gpgme \
+   --with-iptables=/usr/sbin/iptables
+
+
+
+define Package/fwknopd/install
+   $(INSTALL_DIR) $(1)/usr/sbin
+   $(INSTALL_DIR) $(1)/etc/fwknop
+   $(INSTALL_DIR) $(1)/etc/init.d
+   $(INSTALL_DIR) $(1)/usr/lib
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/extras/fwknop.init.openwrt \
+   $(1)/etc/init.d/fwknopd
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/server/.libs/fwknopd $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2 \
+   $(1)/usr/lib/libfko.so.0
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2 \
+   $(1)/usr/lib/libfko.so.0.0.2
+   $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/fwknopd.conf $(1)/etc/fwknop/
+   $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/access.conf $(1)/etc/fwknop/
+
+endef
+
+$(eval $(call BuildPackage,fwknopd))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] New package: fwknopd

[Jonathan Bennett]

Fwknopd is a firewall knock operator daemon written by Michael Rash.
It implements Single Packet Authentication to securely authorize
connections through a firewall.

I'm also volunteering to maintain the package in openwrt.

Thanks,
Jonathan Bennett

Index: net/fwknop/Makefile
===
--- net/fwknop/Makefile (revision 0)
+++ net/fwknop/Makefile (revision 0)
@@ -0,0 +1,61 @@
+include $(TOPDIR)/rules.mk
+
+PKG_NAME:=fwknopd
+PKG_VERSION:=2.0.0rc2
+PKG_RELEASE:=1
+
+PKG_BUILD_DIR:=$(BUILD_DIR)/fwknop-$(PKG_VERSION)
+PKG_SOURCE:=fwknop-$(PKG_VERSION).tar.gz
+PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
+PKG_MD5SUM:=c78252216fa9627cacf61b453da915a8
+PKG_CAT:=zcat
+include $(INCLUDE_DIR)/package.mk
+
+define Package/fwknopd
+       SECTION:=net
+       CATEGORY:=Network
+       DEFAULT:=n
+       TITLE:=Firewall Knock Operator Daemon
+       URL:=http://http://www.cipherdyne.org/fwknop/
+       MAINTAINER:=Jonathan Bennett jbscienc...@gmail.com
+       DEPENDS:=+libpcap +libgdbm +iptables
+endef
+
+define Package/fwknopd/description
+       Firewall Knock Operator Daemon
+       Fwknop implements an authorization scheme known as Single Packet
+       Authorization (SPA) for Linux systems running iptables.  This mechanism
+       requires only a single encrypted and non-replayed packet to communicate
+       various pieces of information including desired access through
an iptables
+       policy. The main application of this program is to use iptables in a
+       default-drop stance to protect services such as SSH with an additional
+       layer of security in order to make the exploitation of vulnerabilities
+       (both 0-day and unpatched code) much more difficult.
+endef
+
+define Package/Conffiles
+       fwknopd.conf
+endef
+
+CONFIGURE_ARGS += \
+       --disable-client \
+       --without-gpgme \
+       --with-iptables=/usr/sbin/iptables
+
+
+
+define Package/fwknopd/install
+       $(INSTALL_DIR) $(1)/usr/sbin
+       $(INSTALL_DIR) $(1)/etc/fwknop
+       $(INSTALL_DIR) $(1)/etc/init.d
+       $(INSTALL_DIR) $(1)/usr/lib
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/extras/fwknop.init.openwrt
$(1)/etc/init.d/fwknopd
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/server/.libs/fwknopd $(1)/usr/sbin/
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2
$(1)/usr/lib/libfko.so.0
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2
$(1)/usr/lib/libfko.so.0.0.2
+       $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/fwknopd.conf $(1)/etc/fwknop/
+       $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/access.conf $(1)/etc/fwknop/
+
+endef
+
+$(eval $(call BuildPackage,fwknopd))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] New package: fwknopd

[Jonathan Bennett]

Fwknopd is a firewall knock operator daemon written by Michael Rash.
It implements Single Packet Authentication to securely authorize
connections through a firewall.

I'm also volunteering to maintain the package in openwrt.

Thanks,
Jonathan Bennett

Index: net/fwknop/Makefile
===
--- net/fwknop/Makefile (revision 0)
+++ net/fwknop/Makefile (revision 0)
@@ -0,0 +1,61 @@
+include $(TOPDIR)/rules.mk
+
+PKG_NAME:=fwknopd
+PKG_VERSION:=2.0.0rc2
+PKG_RELEASE:=1
+
+PKG_BUILD_DIR:=$(BUILD_DIR)/fwknop-$(PKG_VERSION)
+PKG_SOURCE:=fwknop-$(PKG_VERSION).tar.gz
+PKG_SOURCE_URL:=http://www.cipherdyne.org/fwknop/download
+PKG_MD5SUM:=c78252216fa9627cacf61b453da915a8
+PKG_CAT:=zcat
+include $(INCLUDE_DIR)/package.mk
+
+define Package/fwknopd
+       SECTION:=net
+       CATEGORY:=Network
+       DEFAULT:=n
+       TITLE:=Firewall Knock Operator Daemon
+       URL:=http://http://www.cipherdyne.org/fwknop/
+       MAINTAINER:=Jonathan Bennett jbscienc...@gmail.com
+       DEPENDS:=+libpcap +libgdbm +iptables
+endef
+
+define Package/fwknopd/description
+       Firewall Knock Operator Daemon
+       Fwknop implements an authorization scheme known as Single Packet
+       Authorization (SPA) for Linux systems running iptables.  This mechanism
+       requires only a single encrypted and non-replayed packet to communicate
+       various pieces of information including desired access through
an iptables
+       policy. The main application of this program is to use iptables in a
+       default-drop stance to protect services such as SSH with an additional
+       layer of security in order to make the exploitation of vulnerabilities
+       (both 0-day and unpatched code) much more difficult.
+endef
+
+define Package/Conffiles
+       fwknopd.conf
+endef
+
+CONFIGURE_ARGS += \
+       --disable-client \
+       --without-gpgme \
+       --with-iptables=/usr/sbin/iptables
+
+
+
+define Package/fwknopd/install
+       $(INSTALL_DIR) $(1)/usr/sbin
+       $(INSTALL_DIR) $(1)/etc/fwknop
+       $(INSTALL_DIR) $(1)/etc/init.d
+       $(INSTALL_DIR) $(1)/usr/lib
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/extras/fwknop.init.openwrt
$(1)/etc/init.d/fwknopd
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/server/.libs/fwknopd $(1)/usr/sbin/
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2
$(1)/usr/lib/libfko.so.0
+       $(INSTALL_BIN) $(PKG_BUILD_DIR)/lib/.libs/libfko.so.0.0.2
$(1)/usr/lib/libfko.so.0.0.2
+       $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/fwknopd.conf $(1)/etc/fwknop/
+       $(INSTALL_CONF) $(PKG_BUILD_DIR)/server/access.conf $(1)/etc/fwknop/
+
+endef
+
+$(eval $(call BuildPackage,fwknopd))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Facilitating collaboration -- the labor exchange

[Jonathan Bennett]

On Sun, Jun 19, 2011 at 3:41 PM, Philip Prindeville
philipp_s...@redfish-solutions.com wrote:
 On 6/17/11 1:12 PM, Jonathan Bennett wrote:
 On Fri, Jun 17, 2011 at 1:56 PM, Philip Prindeville
 philipp_s...@redfish-solutions.com wrote:

 As for Asterisk, it handles NAT fairly well *unless* Asterisk happens to be 
 running on the machine providing NAT mapping itself (i.e. on your firewall 
 appliance).  Then... not so well.

 Hmm... That's exactly how I have a server set up. I maintain a small
 network at a church, and we have an Asterisk phone system. We use a
 remote Sip provider for incoming and outgoing calls. It works because
 Asterisk can talk to the provider without going through the NAT. It
 has the public IP on one of its ethernet ports. The disadvantage is
 that a bunch of UDP ports are open. I've always seen that as a
 downside of SIP.

 That's what I'm saying. If you look into the INVITE messages (as the 
 nf_conntrack_sip helper does), you can see the remote address and port # for 
 the media connection, and plumb an association for that dynamically... you 
 can also tear it down when you see the associated BYE message). If you do 
 that, then you don't need to have any ports open.

Ah, OK. That would be great. In fact, I wouldn't mind setting up a
test platform



 I'd like to see Asterisk punch holes for the media stream via ipt 
 on-the-fly so that the phones don't actually have to be NAT-aware.

 As apposed to leaving UDP 1 through 2 open in the firewall?
 That *would* be quite useful.

 Indeed.

 Now, if the phones are routing everything through Asterisk, they don't
 have to be NAT aware. Asterisk makes the connection internally. The
 phones talk to Asterisk, and Asterisk talks to the Remote server.

 Yeah, but I don't necessarily want Asterisk in the media path.  Especially 
 not on some of the slower processors.

Considering that we're speaking in the context of openwrt and and
embedded platforms, good point.



 If the sip stream is going to re-invite, would Asterisk know the
 incoming and outgoing ports to be able to open everything up?

 You leave Asterisk in the SIP stream... just not in the media stream.

 I'd be very interested in a solution more like this:
 http://www.iptel.org/sipalg/

 It claims to be a connection tracker for sip+rtp. Similar to how
 iptables can handle the FTP issues. This seems like a much better
 solution for most cases. Ideally it's as simple as
  iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

 IPtables should see the rtp stream as related, and let it through.

 That's how nf_conntrack_sip already works.
Not sure how I missed that when researching.
/me adds it to his bag of tricks

I would be very interested in seeing asterisk handle the firewall
stuff. Now that I understand exactly what you're describing, it seems
it would be the best solution for this particular problem. I'll gladly
set up a testbed server for this work. I'll also comment and
contribute to the administration side of the project as much as I am
able.

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Facilitating collaboration -- the labor exchange

[Jonathan Bennett]

Phillip,
What would be the advantage of ipsec over OpenVPN?

In my experience, if you have Asterisk deployed, the call is
routed through Asterisk, which handles the Nat traversal fairly well.
Are you describing a sip re-invite, where the local phone connects
directly to the remote end?

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] RT3052 and Telephone support

[Jonathan Bennett]

Try this one:
http://www.rowetel.com/blog/
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] how to change default IP in OpenWrt image

[Jonathan Bennett]

Larry,
Greetings from Lawton, OK. If you build from source, there is an
option to change that default ip address in menuconfig. It is under
Image Configuration -- Lan IP Address.
I'd obviously recommend testing it first on an ap that you have
physical access to. However, this should do exactly what you need.

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] TP-Link TL-WR841ND v7

[Jonathan Bennett]

Juhos, is there any chance we could backport the 841nd v7 support for
10.03.1 rc5? Trunk seems to run great on it.

Thanks,
Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] linker errors like ignoring invalid character `#' in expression

[Jonathan Bennett]

On Tue, Mar 29, 2011 at 9:06 AM, Madhavi Manchala
madhavi.li...@gmail.com wrote:
 On Tue, Mar 29, 2011 at 7:16 PM, Madhavi Manchala
 madhavi.li...@gmail.com wrote:
 Dear All,

 I am seeing the following linker error messages when I try to build
 the OpenWRT image for my board.

 arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284:
 ignoring invalid character `#' in expression
 arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: syntax 
 error

 I googled, but there is no much luck for me. I did not understand why
 am I getting this error.

 Any suggestions / hints would be appreciated.

 Thanks for your help, too.

 Thanks and Regards,
 Madhavi M.

 Dear All,

 It was resolved. Thanks.

That's great! However, a few words of explanation might be helpful in
case anyone else runs across this issue. (And I'm curious.)


 Regards,
 Madhavi M.

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [patch] resend: TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

This patch is refreshed for the most recent changes to trunk. It does
work as intended. Please commit to trunk when possible.

Cheers,
Jonathan Bennett



Index: target/linux/ar71xx/config-2.6.37
===
--- target/linux/ar71xx/config-2.6.37   (revision 25370)
+++ target/linux/ar71xx/config-2.6.37   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/files/arch/mips/ar71xx/Makefile
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (revision 25370)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (working copy)
@@ -48,6 +48,7 @@
 obj-$(CONFIG_AR71XX_MACH_TEW_632BRP)   += mach-tew-632brp.o
 obj-$(CONFIG_AR71XX_MACH_TL_MR3X20)+= mach-tl-mr3x20.o
 obj-$(CONFIG_AR71XX_MACH_TL_WA901ND)   += mach-tl-wa901nd.o
+obj-$(CONFIG_AR71XX_MACH_TL_WA901ND_V2)+= mach-tl-wa901nd-v2.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR741ND)   += mach-tl-wr741nd.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR841N_V1) += mach-tl-wr841n.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR941ND)   += mach-tl-wr941nd.o
Index: target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (revision 25370)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (working copy)
@@ -42,6 +42,7 @@
AR71XX_MACH_TL_MR3220,  /* TP-LINK TL-MR3220 */
AR71XX_MACH_TL_MR3420,  /* TP-LINK TL-MR3420 */
AR71XX_MACH_TL_WA901ND, /* TP-LINK TL-WA901ND */
+   AR71XX_MACH_TL_WA901ND_V2, /* TP-LINK TL-WA901ND v2 */
AR71XX_MACH_TL_WR741ND, /* TP-LINK TL-WR741ND */
AR71XX_MACH_TL_WR841N_V1, /* TP-LINK TL-WR841N v1 */
AR71XX_MACH_TL_WR941ND, /* TP-LINK TL-WR941ND */
Index: target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
@@ -0,0 +1,132 @@
+/*
+ *  TP-LINK TL-WA901ND board support
+ *
+ *  Copyright (C) 2009-2010 Gabor Juhos juh...@openwrt.org
+ *  Copyright (C) 2010 Pieter Hollants pie...@hollants.com
+ *  Copyright (C) 2011 Jonathan Bennett jbscienc...@gmail.com
+ *
+ *  This program is free software; you can redistribute it and/or modify it
+ *  under the terms of the GNU General Public License version 2 as published
+ *  by the Free Software Foundation.
+ */
+
+#include linux/mtd/mtd.h
+#include linux/mtd/partitions.h
+
+#include asm/mach-ar71xx/ar71xx.h
+
+#include machtype.h
+#include devices.h
+#include dev-m25p80.h
+#include dev-gpio-buttons.h
+#include dev-leds-gpio.h
+#include dev-ar913x-wmac.h
+
+#define TL_WA901ND_V2_GPIO_LED_QSS 4
+#define TL_WA901ND_V2_GPIO_LED_SYSTEM  2
+#define TL_WA901ND_V2_GPIO_LED_WLAN9
+
+
+#define TL_WA901ND_V2_GPIO_BTN_RESET   3
+#define TL_WA901ND_V2_GPIO_BTN_QSS 7
+
+#define TL_WA901ND_V2_BUTTONS_POLL_INTERVAL20
+
+#ifdef CONFIG_MTD_PARTITIONS
+static struct mtd_partition tl_wa901nd_v2_partitions[] = {
+   {
+   .name   = u-boot,
+   .offset = 0,
+   .size   = 0x02,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = kernel,
+   .offset = 0x02,
+   .size   = 0x14,
+   }, {
+   .name   = rootfs,
+   .offset = 0x16,
+   .size   = 0x29,
+   }, {
+   .name   = art,
+   .offset = 0x3f,
+   .size   = 0x01,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = firmware,
+   .offset = 0x02,
+   .size   = 0x3d,
+   }
+};
+#endif /* CONFIG_MTD_PARTITIONS */
+
+static struct flash_platform_data tl_wa901nd_v2_flash_data = {
+#ifdef CONFIG_MTD_PARTITIONS
+   .parts  = tl_wa901nd_v2_partitions,
+   .nr_parts   = ARRAY_SIZE(tl_wa901nd_v2_partitions),
+#endif
+};
+
+static struct gpio_led tl_wa901nd_v2_leds_gpio[] __initdata = {
+   {
+.name   = tl-wa901nd-v2:green:system,
+.gpio   = TL_WA901ND_V2_GPIO_LED_SYSTEM,
+.active_low = 1,
+}, {
+.name   = tl-wa901nd-v2:green:qss,
+.gpio   = TL_WA901ND_V2_GPIO_LED_QSS,
+}, {
+.name   = tl-wa901nd-v2

Re: [OpenWrt-Devel] Resend 3 [PATCH] TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

3rd time's the charm.

This patch fully supports the TP-Link tl-wa901nd v2. It removes the
mii-tool dependency, cleans up the mach file just a bit, and uses the
correct phy-mask.

Cheers,

Signed off by Jonathan Bennett jbscienc...@gmail.com



Index: target/linux/ar71xx/config-2.6.36
===
--- target/linux/ar71xx/config-2.6.36   (revision 25370)
+++ target/linux/ar71xx/config-2.6.36   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/config-2.6.37
===
--- target/linux/ar71xx/config-2.6.37   (revision 25370)
+++ target/linux/ar71xx/config-2.6.37   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/files/arch/mips/ar71xx/Makefile
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (revision 25370)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (working copy)
@@ -48,6 +48,7 @@
 obj-$(CONFIG_AR71XX_MACH_TEW_632BRP)   += mach-tew-632brp.o
 obj-$(CONFIG_AR71XX_MACH_TL_MR3X20)+= mach-tl-mr3x20.o
 obj-$(CONFIG_AR71XX_MACH_TL_WA901ND)   += mach-tl-wa901nd.o
+obj-$(CONFIG_AR71XX_MACH_TL_WA901ND_V2)+= mach-tl-wa901nd-v2.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR741ND)   += mach-tl-wr741nd.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR841N_V1) += mach-tl-wr841n.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR941ND)   += mach-tl-wr941nd.o
Index: target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (revision 25370)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (working copy)
@@ -42,6 +42,7 @@
AR71XX_MACH_TL_MR3220,  /* TP-LINK TL-MR3220 */
AR71XX_MACH_TL_MR3420,  /* TP-LINK TL-MR3420 */
AR71XX_MACH_TL_WA901ND, /* TP-LINK TL-WA901ND */
+   AR71XX_MACH_TL_WA901ND_V2, /* TP-LINK TL-WA901ND v2 */
AR71XX_MACH_TL_WR741ND, /* TP-LINK TL-WR741ND */
AR71XX_MACH_TL_WR841N_V1, /* TP-LINK TL-WR841N v1 */
AR71XX_MACH_TL_WR941ND, /* TP-LINK TL-WR941ND */
Index: target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
@@ -0,0 +1,132 @@
+/*
+ *  TP-LINK TL-WA901ND board support
+ *
+ *  Copyright (C) 2009-2010 Gabor Juhos juh...@openwrt.org
+ *  Copyright (C) 2010 Pieter Hollants pie...@hollants.com
+ *  Copyright (C) 2011 Jonathan Bennett jbscienc...@gmail.com
+ *
+ *  This program is free software; you can redistribute it and/or modify it
+ *  under the terms of the GNU General Public License version 2 as published
+ *  by the Free Software Foundation.
+ */
+
+#include linux/mtd/mtd.h
+#include linux/mtd/partitions.h
+
+#include asm/mach-ar71xx/ar71xx.h
+
+#include machtype.h
+#include devices.h
+#include dev-m25p80.h
+#include dev-gpio-buttons.h
+#include dev-leds-gpio.h
+#include dev-ar913x-wmac.h
+
+#define TL_WA901ND_V2_GPIO_LED_QSS 4
+#define TL_WA901ND_V2_GPIO_LED_SYSTEM  2
+#define TL_WA901ND_V2_GPIO_LED_WLAN9
+
+
+#define TL_WA901ND_V2_GPIO_BTN_RESET   3
+#define TL_WA901ND_V2_GPIO_BTN_QSS 7
+
+#define TL_WA901ND_V2_BUTTONS_POLL_INTERVAL20
+
+#ifdef CONFIG_MTD_PARTITIONS
+static struct mtd_partition tl_wa901nd_v2_partitions[] = {
+   {
+   .name   = u-boot,
+   .offset = 0,
+   .size   = 0x02,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = kernel,
+   .offset = 0x02,
+   .size   = 0x14,
+   }, {
+   .name   = rootfs,
+   .offset = 0x16,
+   .size   = 0x29,
+   }, {
+   .name   = art,
+   .offset = 0x3f,
+   .size   = 0x01,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = firmware,
+   .offset = 0x02,
+   .size   = 0x3d,
+   }
+};
+#endif /* CONFIG_MTD_PARTITIONS */
+
+static struct flash_platform_data tl_wa901nd_v2_flash_data = {
+#ifdef CONFIG_MTD_PARTITIONS

[OpenWrt-Devel] [PATCH] TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

OK, I've mapped the leds and the buttons. I've also moved the eth
fixup into the pre-init. If it's in the regular init, then failsafe
doesn't work, because the ethernet port never comes online. The mach
file is a bit cleaner, now, too. Failsafe is confirmed to work
correctly. Please push this patch into trunk rather than the earlier
submitted one.

For the record, flashing this board without mii-tool is a bad idea. It
is selected by default. If one doesn't update and install the package
feed, though, the firmware will not include mii-tool. Flashing an
image without mii-tool would semi-brick this board. It would require a
serial cable to recover.

To my knowledge, everything works as intended.

Cheers,
Signed off by Jonathan Bennett jbscienc...@gmail.com



Index: target/linux/ar71xx/config-2.6.36
===
--- target/linux/ar71xx/config-2.6.36   (revision 25355)
+++ target/linux/ar71xx/config-2.6.36   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/config-2.6.37
===
--- target/linux/ar71xx/config-2.6.37   (revision 25355)
+++ target/linux/ar71xx/config-2.6.37   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/files/arch/mips/ar71xx/Makefile
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (revision 25355)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (working copy)
@@ -48,6 +48,7 @@
 obj-$(CONFIG_AR71XX_MACH_TEW_632BRP)   += mach-tew-632brp.o
 obj-$(CONFIG_AR71XX_MACH_TL_MR3X20)+= mach-tl-mr3x20.o
 obj-$(CONFIG_AR71XX_MACH_TL_WA901ND)   += mach-tl-wa901nd.o
+obj-$(CONFIG_AR71XX_MACH_TL_WA901ND_V2)+= mach-tl-wa901nd-v2.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR741ND)   += mach-tl-wr741nd.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR841N_V1) += mach-tl-wr841n.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR941ND)   += mach-tl-wr941nd.o
Index: target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (revision 25355)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (working copy)
@@ -42,6 +42,7 @@
AR71XX_MACH_TL_MR3220,  /* TP-LINK TL-MR3220 */
AR71XX_MACH_TL_MR3420,  /* TP-LINK TL-MR3420 */
AR71XX_MACH_TL_WA901ND, /* TP-LINK TL-WA901ND */
+   AR71XX_MACH_TL_WA901ND_V2, /* TP-LINK TL-WA901ND v2 */
AR71XX_MACH_TL_WR741ND, /* TP-LINK TL-WR741ND */
AR71XX_MACH_TL_WR841N_V1, /* TP-LINK TL-WR841N v1 */
AR71XX_MACH_TL_WR941ND, /* TP-LINK TL-WR941ND */
Index: target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
@@ -0,0 +1,133 @@
+/*
+ *  TP-LINK TL-WA901ND board support
+ *
+ *  Copyright (C) 2009-2010 Gabor Juhos juh...@openwrt.org
+ *  Copyright (C) 2010 Pieter Hollants pie...@hollants.com
+ *  Copyright (C) 2011 Jonathan Bennett jbscienc...@gmail.com
+ *
+ *  This program is free software; you can redistribute it and/or modify it
+ *  under the terms of the GNU General Public License version 2 as published
+ *  by the Free Software Foundation.
+ */
+
+#include linux/mtd/mtd.h
+#include linux/mtd/partitions.h
+
+#include asm/mach-ar71xx/ar71xx.h
+
+#include machtype.h
+#include devices.h
+#include dev-m25p80.h
+#include dev-gpio-buttons.h
+#include dev-leds-gpio.h
+#include dev-ar913x-wmac.h
+
+#define TL_WA901ND_V2_GPIO_LED_QSS 4
+#define TL_WA901ND_V2_GPIO_LED_SYSTEM  2
+#define TL_WA901ND_V2_GPIO_LED_WLAN9
+
+
+#define TL_WA901ND_V2_GPIO_BTN_RESET   3
+#define TL_WA901ND_V2_GPIO_BTN_QSS 7
+
+#define TL_WA901ND_V2_BUTTONS_POLL_INTERVAL20
+
+#ifdef CONFIG_MTD_PARTITIONS
+static struct mtd_partition tl_wa901nd_v2_partitions[] = {
+   {
+   .name   = u-boot,
+   .offset = 0,
+   .size   = 0x02,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = kernel,
+   .offset = 0x02,
+   .size   = 0x14,
+   }, {
+   .name   = rootfs,
+   .offset = 0x16

Re: [OpenWrt-Devel] TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

Included patch adds support for the TP-link WA901ND-v2. I have yet to
map out the leds and buttons, but I don't anticipate having much
problem with that. I'll push that patch through once I get it done.

This patch also adds an init script to the ar71xx platform. It checks
to see if it is running on a wa901ndv2 and brings up the ethernet port
if it is. There may be a better way to reset that phy chip, but this
is the best I've found.

Cheers,
Signed off by: Jonathan Bennett jbscienc...@gmail.com


Index: target/linux/ar71xx/config-2.6.36
===
--- target/linux/ar71xx/config-2.6.36   (revision 25332)
+++ target/linux/ar71xx/config-2.6.36   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/config-2.6.37
===
--- target/linux/ar71xx/config-2.6.37   (revision 25332)
+++ target/linux/ar71xx/config-2.6.37   (working copy)
@@ -33,6 +33,7 @@
 CONFIG_AR71XX_MACH_TEW_632BRP=y
 CONFIG_AR71XX_MACH_TL_MR3X20=y
 CONFIG_AR71XX_MACH_TL_WA901ND=y
+CONFIG_AR71XX_MACH_TL_WA901ND_V2=y
 CONFIG_AR71XX_MACH_TL_WR1043ND=y
 CONFIG_AR71XX_MACH_TL_WR741ND=y
 CONFIG_AR71XX_MACH_TL_WR841N_V1=y
Index: target/linux/ar71xx/files/arch/mips/ar71xx/Makefile
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (revision 25332)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/Makefile (working copy)
@@ -48,6 +48,7 @@
 obj-$(CONFIG_AR71XX_MACH_TEW_632BRP)   += mach-tew-632brp.o
 obj-$(CONFIG_AR71XX_MACH_TL_MR3X20)+= mach-tl-mr3x20.o
 obj-$(CONFIG_AR71XX_MACH_TL_WA901ND)   += mach-tl-wa901nd.o
+obj-$(CONFIG_AR71XX_MACH_TL_WA901ND_V2)+= mach-tl-wa901nd-v2.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR741ND)   += mach-tl-wr741nd.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR841N_V1) += mach-tl-wr841n.o
 obj-$(CONFIG_AR71XX_MACH_TL_WR941ND)   += mach-tl-wr941nd.o
Index: target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (revision 25332)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/machtype.h   (working copy)
@@ -42,6 +42,7 @@
AR71XX_MACH_TL_MR3220,  /* TP-LINK TL-MR3220 */
AR71XX_MACH_TL_MR3420,  /* TP-LINK TL-MR3420 */
AR71XX_MACH_TL_WA901ND, /* TP-LINK TL-WA901ND */
+   AR71XX_MACH_TL_WA901ND_V2, /* TP-LINK TL-WA901ND v2 */
AR71XX_MACH_TL_WR741ND, /* TP-LINK TL-WR741ND */
AR71XX_MACH_TL_WR841N_V1, /* TP-LINK TL-WR841N v1 */
AR71XX_MACH_TL_WR941ND, /* TP-LINK TL-WR941ND */
Index: target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c
===
--- target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
+++ target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wa901nd-v2.c 
(revision 0)
@@ -0,0 +1,127 @@
+/*
+ *  TP-LINK TL-WA901ND board support
+ *
+ *  Copyright (C) 2009-2010 Gabor Juhos juh...@openwrt.org
+ *  Copyright (C) 2010 Pieter Hollants pie...@hollants.com
+ *
+ *  This program is free software; you can redistribute it and/or modify it
+ *  under the terms of the GNU General Public License version 2 as published
+ *  by the Free Software Foundation.
+ */
+
+#include linux/mtd/mtd.h
+#include linux/mtd/partitions.h
+
+#include asm/mach-ar71xx/ar71xx.h
+
+#include machtype.h
+#include devices.h
+#include dev-m25p80.h
+#include dev-gpio-buttons.h
+#include dev-leds-gpio.h
+#include dev-ar913x-wmac.h
+
+#define TL_WA901ND_GPIO_LED_QSS0
+#define TL_WA901ND_GPIO_LED_SYSTEM 1
+
+#define TL_WA901ND_GPIO_BTN_RESET  11
+#define TL_WA901ND_GPIO_BTN_QSS12
+
+#define TL_WA901ND_BUTTONS_POLL_INTERVAL   20
+
+#ifdef CONFIG_MTD_PARTITIONS
+static struct mtd_partition tl_wa901nd_partitions[] = {
+   {
+   .name   = u-boot,
+   .offset = 0,
+   .size   = 0x02,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = kernel,
+   .offset = 0x02,
+   .size   = 0x14,
+   }, {
+   .name   = rootfs,
+   .offset = 0x16,
+   .size   = 0x29,
+   }, {
+   .name   = art,
+   .offset = 0x3f,
+   .size   = 0x01,
+   .mask_flags = MTD_WRITEABLE,
+   }, {
+   .name   = firmware,
+   .offset = 0x02,
+   .size   = 0x3d,
+   }
+};
+#endif

Re: [OpenWrt-Devel] TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

OK, so, I was finally able to compile forcedeth support into the
kernel. It seems that the kernel compile process prompts whether to
actually compile that in. Without running V=99, I had no way of
telling it to actually include forcedeth support.

That said, I still have no ethernet support. Strangely enough,
absolutely no pci devices show up in /proc/bus/pci/devices. The file
is altogether empty.

A couple questions: First, should I continue to document my efforts
here, or create a thread in the forums?

Second, when I dumped the flash, I did a 'dd if=/dev/mtd[#]
of=/tmp/901V2dump[#].bin'  Should I have dd'ed from mtdblock instead?

The stock boot log is now up here:
http://oneru.dyndns.org/openwrt/WA901NDv2/901V2BootLog.txt

I do see one item that sticks out. There is a
'/lib/modules/2.6.15/net/ag7100_mod.ko' in the stock firmware. Could
it be a proprietary driver? I'd try to investigate it further, but I
can't think of a way to transfer the file off the router.

Cheers,
Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

The stock firmware is now up at http://oneru.dyndns.org/openwrt/WA901NDv2/

The driver for the ethernet chip appears to be the the forcedeth.c
driver that ships with the kernel. I haven't been successful in making
the build process include that file for compilation, though. I've
added CONFIG_FORCEDETH=Y it to
trunk/target/linux/generic/config-2.6.32 and
trunk/target/linux/ar71xx/config-2.6.32. That driver isn't added to
the firmware, and the actual .config file in the build directory has
it unset. What am I missing to make this driver compile?

~Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] TP-Link TL-WA901ND V2 support

[Jonathan Bennett]

I'm working on support for the new version of the WA901ND. TP-link
changed nearly every component from version 1.
32 megs of ram
proc: AR9132-BC1E
ethernet chip: RTL8201CP
Wireless AR5416
Flash: 4MB

I've gotten everything working but the Ethernet port. It's a RTL8201CP
chip that drives the port. In the stock firmware, obviously, it comes
right up. However, in the U-Boot bootloader and in the Openwrt image I
transfered across, I can't get the ethernet port to power up. It won't
light the link light on a switch, and it won't transfer any data. It
does show up in ifconfig, though.

I've started working from the TL-WR841ND-V3 binary, built from latest
trunk. This router used the same proc and similar hardware. I had to
transfer it across the serial line using ymodem. I've managed to bring
up the wireless interface and dump the stock rom (/dev/mtd0-4) to a
laptop. Sometime tomorrow I'll get these files online.

Any ideas on the lan port? I'm assuming it's a lack of the proper
driver. Any help or hints are appreciated.

Cheers,
Jonathan Bennett
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel