Re: [OpenWrt-Devel] [PROPOSAL] move OpenWrt codebase to Git and GitHub

[Saverio Proto]

Hello,

I am very happy about moving to Github.

Saverio

2016-05-24 16:06 GMT+02:00 Luka Perkov :
> Dear OpenWrt mailing list readers,
>
> as the subject says I'd like to make proposal to move the OpenWrt
> codebase to Git. This was already discussed before [1] and now when
> there are no blockers [2] for this change I'd like that we as a
> community move forward with this switch.
>
> Also, I'd like to propose that we move the project to GitHub and here
> are the reasons why I see this as a good decision:
>
> * GitHub will allow people to contribute more easily
>
> The bigger amount of contributions has already happened and can be seen
> on the packages feed which is already hosted on GitHub. With this I'm
> also hoping to avoid comments regarding invalid patches on the mailing
> list.
>
> For now I am proposing that the current development workflow is also
> accepted - aka. patches that are sent to the mailing list are also
> accepted.
>
> * GitHub and similar services will allow us to integrate more easily
> with other projects
>
> Here specifically I mean integration with modern CI. Here is an example
> of integration with drone.io [3][4]. At the moment this is only in the
> POC stage but what I'd like to do down the line is to:
>
>  - build OpenWrt images for all architectures for every pull request
>
>  - build OpenWrt package binary for every package pull request for all
> architectures and make it available for download
>
>  - build and host OpenWrt qemu and/or Docker image for every pull request
>
> This will allow easy review of the work since flags will be shown in the
> pull request if the build was sucessful or not. Also, this will allow
> people to test changes without building the image and thus lowering the
> time that needs to be spent on maintenance work.
>
> If this proposal gets accepted I'll be sending out an email to get
> access to more build servers so this new build infrastructure can
> properly support the project in a timely fashion.
>
> Please share your thoughts regarding this proposal.
>
> Regards,
> Luka
>
> [1] https://lists.openwrt.org/pipermail/openwrt-devel/2015-October/036390.html
> [2] https://lists.openwrt.org/pipermail/openwrt-devel/2016-May/041329.html
> [3] https://github.com/makkrnic/openwrt-qemu-x86
> [4] http://sartura-drone.makkrnic.com/makkrnic/openwrt-qemu-x86/5
> ___
> 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] Chaos Calmer - ramips: Fix IPv6 neighbor discovery on RT5350

[Saverio Proto]

I attach the patch in this email so should be without whitespace problem.

thank you

Saverio


2016-05-02 10:09 GMT+02:00 Vittorio G (VittGam) :
> On 02/05/2016 10:06:49 CEST, John Crispin wrote:
>>
>> On 02/05/2016 09:55, Vittorio G (VittGam) wrote:
>>>
>>> Actually there's a problem with this patch: the tabs have been converted
>>> to spaces by your mailer, so it does not apply directly...
>>>
>>> The patch on GitHub is fine by the way.
>>>
>>> Cheers,
>>> Vittorio
>>
>>
>> you seem to have sent the same patch which does not look whitespace
>> broken. i'll use that one instead.
>
>
> My patch is not for CC... it's for trunk which uses the newer rt305x driver.
>
> Cheers,
> Vittorio
>
>
>>
>> John
>>
>>>
>>> On 01/05/2016 23:59:27 CEST, Vittorio G (VittGam) wrote:
>>>>
>>>> On 01/05/2016 23:36:05 CEST, Saverio Proto wrote:
>>>>>
>>>>> This patch is also available here:
>>>>>
>>>>> https://github.com/zioproto/openwrt15051-batman/commit/0281382bcaa139f0d1d3b589797af4c434747f3e
>>>>>
>>>>>
>>>>> commit 0281382bcaa139f0d1d3b589797af4c434747f3e
>>>>> Author: Saverio Proto 
>>>>> Date:   Sun May 1 23:14:19 2016 +0200
>>>>>
>>>>> ramips: Fix IPv6 neighbor discovery on RT5350
>>>>>
>>>>> IPv6 neighbor discovery needs working IPv6 multicast. The
>>>>> register FCT2
>>>>> should be set to 0x2500C to let through "unknown IPv6 multicast" to
>>>>> all ports. This is based on datasheet information:
>>>>> https://cdn.sparkfun.com/datasheets/Wireless/WiFi/RT5350.pdf
>>>>>
>>>>> Signed-off-by: Saverio Proto 
>>>>
>>>>
>>>> Reviewed-by: Vittorio Gambaletta 
>>>>
>>>>>
>>>>> diff --git
>>>>> a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
>>>>> b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
>>>>> index ef13d23..d09eaf3 100644
>>>>> ---
>>>>> a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
>>>>> +++
>>>>> b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
>>>>> @@ -1360,7 +1360,7 @@ static const struct switch_dev_ops esw_ops = {
>>>>>  static struct rt305x_esw_platform_data rt3050_esw_data = {
>>>>> /* All ports are LAN ports. */
>>>>> .vlan_config= RT305X_ESW_VLAN_CONFIG_NONE,
>>>>> -   .reg_initval_fct2   = 0x00d6500c,
>>>>> +   .reg_initval_fct2   = 0x0002500c,
>>>>> /*
>>>>>  * ext phy base addr 31, enable port 5 polling, rx/tx clock
>>>>> skew 1,
>>>>>  * turbo mii off, rgmi 3.3v off
>>>>> ___
>>>>> 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
>>
>> ___
>> 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


fix-ipv6-multicast-rt3050.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] Chaos Calmer - ramips: Fix IPv6 neighbor discovery on RT5350

[Saverio Proto]

This patch is also available here:
https://github.com/zioproto/openwrt15051-batman/commit/0281382bcaa139f0d1d3b589797af4c434747f3e

commit 0281382bcaa139f0d1d3b589797af4c434747f3e
Author: Saverio Proto 
Date:   Sun May 1 23:14:19 2016 +0200

ramips: Fix IPv6 neighbor discovery on RT5350

IPv6 neighbor discovery needs working IPv6 multicast. The register FCT2
should be set to 0x2500C to let through "unknown IPv6 multicast" to
all ports. This is based on datasheet information:
https://cdn.sparkfun.com/datasheets/Wireless/WiFi/RT5350.pdf

Signed-off-by: Saverio Proto 

diff --git a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
index ef13d23..d09eaf3 100644
--- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
+++ b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c
@@ -1360,7 +1360,7 @@ static const struct switch_dev_ops esw_ops = {
 static struct rt305x_esw_platform_data rt3050_esw_data = {
/* All ports are LAN ports. */
.vlan_config= RT305X_ESW_VLAN_CONFIG_NONE,
-   .reg_initval_fct2   = 0x00d6500c,
+   .reg_initval_fct2   = 0x0002500c,
/*
 * ext phy base addr 31, enable port 5 polling, rx/tx clock skew 1,
 * turbo mii off, rgmi 3.3v off
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 15.05.1 - Chaos Calmer

[Saverio Proto]

Who has commit rights on the other tree ? So we can send an email to
have it fixed ?

thank you :)

Saverio


2016-04-05 15:42 GMT+02:00 John Crispin :
>
>
> On 05/04/2016 15:33, Saverio Proto wrote:
>> Thanks Bruno,
>>
>> I am sorry I am coming back to OpenWrt after a long break.
>>
>> I expected the tag also on the Release repo
>>
>> http://git.openwrt.org/?p=15.05/openwrt.git;a=summary
>>
>> Here I see only a 15.05 tag. I dont understand the logic. I expect the
>> 15.05.1 to be release from the Release-repo ?
>>
>> thank you
>>
>> Saverio
>>
>
> the logic is that i can push a tag to one tree but not to the other and
> whoever can is not reading this thread
>
> John
>
>
>>
>> 2016-04-04 22:38 GMT+02:00 Bruno Randolf :
>>> On 04/04/2016 09:34 PM, Saverio Proto wrote:
>>>>> Great! Thanks for your good work!
>>>>> Could you please add a tag for 15.05.1 in the git repo?
>>>>
>>>> That would be great. I am trying to git bisect a bug and I have no
>>>> idea on top of what commit is 15.05.1 built.
>>>
>>> There is a tag for it already:
>>>
>>> https://github.com/openwrt/openwrt/tags
>>>
>>> bruno
>>>
>> ___
>> 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] 15.05.1 - Chaos Calmer

[Saverio Proto]

Thanks Bruno,

I am sorry I am coming back to OpenWrt after a long break.

I expected the tag also on the Release repo

http://git.openwrt.org/?p=15.05/openwrt.git;a=summary

Here I see only a 15.05 tag. I dont understand the logic. I expect the
15.05.1 to be release from the Release-repo ?

thank you

Saverio


2016-04-04 22:38 GMT+02:00 Bruno Randolf :
> On 04/04/2016 09:34 PM, Saverio Proto wrote:
>>> Great! Thanks for your good work!
>>> Could you please add a tag for 15.05.1 in the git repo?
>>
>> That would be great. I am trying to git bisect a bug and I have no
>> idea on top of what commit is 15.05.1 built.
>
> There is a tag for it already:
>
> https://github.com/openwrt/openwrt/tags
>
> bruno
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 15.05.1 - Chaos Calmer

[Saverio Proto]

> Great! Thanks for your good work!
> Could you please add a tag for 15.05.1 in the git repo?

That would be great. I am trying to git bisect a bug and I have no
idea on top of what commit is 15.05.1 built.

thank you :)

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

Re: [OpenWrt-Devel] [Battlemesh] Request for Feedback - prplwrt Software Support Program - initial draft

[Saverio Proto]

> who says that we have to involve them into a decisional process? All they do
> is offer money for some projects in which industry partners are interested in
> as well. Of course, bringing the contributions back to upstream should be made
> a requirement, but I don't really see anything bad in this.

did you read this ?
PSSP proposal: 
https://docs.google.com/document/d/1b5LwqNPUasSafP-3NLwnV7rXRRUPDfj5yrU772dkpoc/edit?usp=sharing


> if I remember correctly there was quite some interest on GSoC all over the
> communities as well, where many people worked on various things for 5k per
> student. One of the restrictions there was the limited time/money available,
> which kept some interesting ideas out and focused on students with less
> experience, but in general I think its a good program (especially the
> requirement to give back the results).

Google just filtered the organizations to decide which ones where
eligible. There was no review by google to decide which idea was good
or not. And it was a scholarship program, so it is not really
comparable with this industry proposal.

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

Re: [OpenWrt-Devel] Request for Feedback - prplwrt Software Support Program - initial draft

[Saverio Proto]

> I don't have a number off hand, that's still being decided. My feeling has
> been that's it'd be in the tens of thousands USD total. I'll try to get more
> of finalized amount as soon as possible.

Hello Eric,

considering that a Senior Engineer in the SF Bay Area has an average
income of 120.000 USD per year... a contribution on terms of tens of
thousands dollars does not cover even the work of one person for one
year. Should we for this little money involve an american foundation
in the decisional processes ?

My feeling is that prpl is an American foundation that is throwing
penauts to a successfull open source project to have development at
low cost.
A company that hires a team of developer for a Carrier Grade OpenWrt
spends more than 100.000 USD per year in development cost.

You are right, there is a conflict between the community and prpl, so
you have to convince us better :)

Best regards

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

Re: [OpenWrt-Devel] Request for Feedback - prplwrt Software Support Program - initial draft

[Saverio Proto]

Wow,
I received your email on so many mailing lists that I could not stop
from answering.

Could you please give some context about what is prplwrt ?
I have been working with OpenWrt since 2006 and it is the first time I
hear about prplwrt.

The website did not help, and all this people are unknown to me:
http://prplfoundation.org/board-of-directors/

I guess your email needs a proper introduction.

thanks !

Saverio

2016-03-03 22:07 GMT+01:00 Eric Schultz :
> As discussed in prplwrt meetings, prpl is interested in funding development
> work on OpenWrt. In order to make this as fair as possible, I'm proposing a
> process which I'm tentatively calling the prplwrt Software Support Program
> (PSSP)
>
> PSSP will fund innovative OpenWrt development work that is responsive to the
> needs of the OpenWrt community and industry. To make sure the process
> benefits the community as much as possible, I'm asking for your feedback.
> Please look through the document I've linked below and provide feedback,
> either as comments on the document or as a reply to this message.
>
> As a quick summary, the process would go as follows:
>
> * prpl and its members, as funders, would set initial themes that all
> projects would be expected to fit into.
> * the community, prpl members, and others would submit and comment on ideas
> for projects that fit those themes
> * potential implementers would then submit proposals for implementations,
> including a budget, timeline and general plan for implementation
> * an OpenWrt community committee, the prpl TSC and prpl Board would finalize
> which implementations are selected and funded.
>
> More details are in the linked document. I want to make sure everyone in the
> OpenWrt community has had a chance to provide their thoughts on the program
> so please provide your feedback as soon as possible and no later than March
> 17.
>
> Thanks,
>
> Eric
>
> PSSP proposal:
> https://docs.google.com/document/d/1b5LwqNPUasSafP-3NLwnV7rXRRUPDfj5yrU772dkpoc/edit?usp=sharing
>
> --
> Eric Schultz, Community Manager, prpl Foundation
> http://www.prplfoundation.org
> eschu...@prplfoundation.org
> cell: 920-539-0404
> skype: ericschultzwi
> @EricPrpl
>
> ___
> 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] watchping

[Saverio Proto]

Hello Bruno,

yet another tool used in Ninux.org:

https://github.com/ninuxorg/misc_tools/tree/master/adsl_check

What you want to implement is a generic tool... that checks a network
condition and if this condition happens triggers an event.

Yes it would be a nice tool. However routing protocols implementations
have to provide some kind of API to make possible for the tool to make
some actions once a condition is met.

Saverio



2015-07-06 20:54 GMT+02:00 Bruno Randolf :
> Hi Juliusz and all,
>
> Exporting a route to a routing protocol was just one example of what
> could be done based on the fact that internet connectivity is available
> on an interface. There are other uses one could imagine:
>  - Activate a backup interface, say a 3G connection
>  - Announce a default GW or not (routing proto or DHCP).
>  - Check for firmware upgrades on a public server
>  - Start or reconfigure a service
>
> Second, a default route is not enough: what counts is wether inernet
> connectivity is available thru that route. Sometimes a router announces
> a default route but is not connected itself, or problems exist
> "upstream". In that sense it's probably like your "babel-pinger" but
> more generic.
>
> The mwan3 package seems do do a similar thing in a script. Do you think
> it could profit from a C-based ubus service? Would it make sense?
>
> bruno
>
>
>
> On 07/03/2015 09:19 PM, Juliusz Chroboczek wrote:
>> Hi Bruno,
>>
>>> Sometimes it's necessary to re-configure an OpenWRT system based on the
>>> fact wether Internet connectivity is available on a certain interface.
>> [...]
>>> One example where this is useful is: When Internet is available, we
>>> configure BATMAN to act as a gateway 'server', if not as a gateway
>>> 'client'.
>>
>> I think that a solution that relies on distribution scripts is inherently
>> brittle.  The routing daemon should be able to detect the current
>> configuration, in a distribution-independent manner, and automatically
>> adapt to the current situation.  This is what happens with babeld -- it is
>> able to automatically redistribute a kernel route (typically the default
>> route, but not necessarily) into the routing protocol.
>>
>> I know of three ways of automatically obtaining a default route, in
>> descending order of preference:
>>
>>   - if the other end of the Internet connection speaks RIP, RIPng or OSPF,
>> we run Quagga on the gateway and redistribute into Babel;
>>
>>   - if DHCPv4 is reliable (it usually is), then we simply redistribute the
>> DHCP-provided route into the routing protocol;
>>
>>   - if DHCPv4 is unreliable, we use the "babel-pinger" utility which
>> pings a remote host and installs a route depending on its availability.
>>
>> Additionally, there is some very promising but still experimental work to
>> provide a fully general and highly integrated solution in the "hnetd-full"
>> package.
>>
>> -- Juliusz
>> ___
>> 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] Multiple OpenWrt devices collectively managed?

[Saverio Proto]

Have a look at this repo:
https://github.com/libre-mesh/ruci

Small utility for mass backup / restoring of OpenWrt routers configurations.

Saverio


2015-03-21 15:49 GMT+01:00 Janne Cederberg :
> Greetings all!
> Been searching around and found for example OpenWISP but thought I'd
> ask the list as well: is there some opensource management software for
> OpenWrt that could control a set of multiple OpenWrt AP's on the same
> SSID; so basically controlling their channels based on channel use and
> actively avoiding crowded/DOS'sed channels for example?
>
> Best regards, Janne Cederberg
> ___
> 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] Ubiquiti Rocket M5 build

[Saverio Proto]

I think the one for the NanoStation should work as well:
http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin

I never tested, but ubnt devices are all similar.

Saverio


2015-02-12 21:27 GMT+01:00 Ken Buska :
> Is there anyone that is able to help create a build for the Rocket M5 XW
> build?
>
> --
> Thank you,
> Ken Buska
>
>
> ___
> 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] wiki.openwrt.org uses an invalid security certificate / expired on 12.2.2015 17:18

[Saverio Proto]

I think the business model of StartSSL and others, is that they give
certificates for free, but you have to pay a lot in case you need to
revoke a certificate.

my 2 cents

Saverio



2015-02-14 19:31 GMT+01:00 Alessandro Di Federico :
> On Sat, 14 Feb 2015 18:21:41 +0100
> phaidros  wrote:
>
>> Nope, I would vote against StartSSL. I know it is free, but the
>> procedure sucks, and honestly: there is *one* company on the planet
>> givin out *free* SSL Certs .. if that doesn't ring bells, I dunno what
>> could :)
>
> They just say you're who you say you are, they don't have your private
> key. In any case, if you don't trust them, it doesn't matter, because
> they're part of the trusted set of the PKI, so everyone trusts them
> (and can be fooled by them). We could start talking about
> certificate pinning, but I don't think it's a priority right now.
>
> On Sat, 14 Feb 2015 09:35:29 -0800
> "Constantine A. Murenin"  wrote:
>> No, WoSign also does.
>>
>> https://www.wosign.com/english/price.htm
>>
>> In fact, WoSign gives out free certificates valid for 2-years, and
>> they also even let you have multiple CNs in the same cert (although
>> wildcast for free is not supported).
>
> Never tried them. StartSSL certificates last one year and are valid for
> one second level domain (e.g. openwrt.org) and a third level
> domain(e.g. wiki.openwrt.org), but you can have as many of them as you
> want (e.g. one for openwrt.org+wiki.openwrt.org and one for
> openwrt.org+www.openwrt.org).
>
> If the admins are interested in *my* help I'd go for StartSSL, for the
> simple reason that it takes 30 seconds to generate a new certificate,
> since I'm already using it.
>
> In the future, we'll all use Let's encrypt and be happy [1].
>
> In any case, I'd avoid CACert [2].
>
> --
> Alessandro Di Federico
>
> [1] https://letsencrypt.org/
> [2] https://bugzilla.mozilla.org/show_bug.cgi?id=215243
> ___
> 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] Open source & open process

[Saverio Proto]

Hello everyone !

Relax :) If we are reading this list it is because we all want a
better OpenWrt, and we all do the best we can for it.

Etienne in my experience the OpenWrt group is really open. The problem
is the that core people have to face thousands of contacts over the
Internet from unknown people. It is really hard to manage all this
incoming requests.

If you work on OpenWrt over the years, it is a good idea to come once
a while to some developer meeting. We have so many. Battlemesh.org,
FOSDEM, Freifunk WCW, CCC Camping 

Meet the people face to face it always helps to decode better the
emails at a later time. It is not just emails and forums, dont lose
the contact with the real life :)

Cheers !!!

Saverio




2014-10-02 9:20 GMT+02:00 Etienne Champetier :
> Hi and sorry John and all other that i could have offended.
> That was really not the goal of my mail, and me being a bit tired and not so
> good in english,
> i wrote an awful rant without noticing.
>
> Thanks for all the work that you are doing. I know that you and other are
> working hard
> to provide us the best router distribution out there
> (i really mean it: infinite uptime (between power surge :) ), endless
> customisation, great hardware support).
>
> I originaly wrote this mail because i read a ticket on github asking to
> backport some stuff to for-14.07,
> but maybe it's too late for BB ... and was thinking why isn't BB out?
> RC1 RC2 RC3 were quick but after that very few news
> 31 Jul - RC3, RC4 or final in 2 weeks
> 8 Sep - tests builds done, some more bugs fixed
> 18Sep - BB 14.07 is using 533282da863c27be4805fc1655f82f
> 5d9550194b
> 1Oct ...
>
> Thanks for everything and sorry again for this useless rant
> Etienne
>
> 2014-10-02 7:30 GMT+02:00 John Crispin :
>>
>>
>> no its certainly farting. i have you 2 and about 1 other person
>> complain. the other 95% sent me mails with nice and simple questions and
>> input and so forth.
>>
>> i just had a look, yesterday i got related to BB
>>
>> * 8 "thank you" mails
>> * 6 mails asking for various support things
>> * 4 pkg maintainers ask for help/logs
>> * 2 devs asking for root on the build server
>> * 2 people reminded me that now BB is out of the way that i promised to
>> fix NCM, hwdetect, ...
>> * 2 mails of people voicing wishes for CC
>> * 2 driver fixes for i2c on mediatek  .
>> * and etiennes mails and your reply
>>
>> sorry but looking at those numbers it is farting that you are doing.
>>
>> John
>>
>>
>> On 02/10/2014 07:01, Hanno Schupp wrote:
>> > I think this is his point, mate: You work hard (in isolation), but
>> > don't communicate.
>> > If you want to avoid emails that smell like farts to you, why not tell
>> > people what's going on?
>> >
>> > On 2 October 2014 17:51, John Crispin > > > wrote:
>> >
>> > nice rant, what happened at mignight that you got so angry that you
>> > feel you needed to vent it out on us ?
>> >
>> > i would like to point out that the BB-final binaries have been
>> > online
>> > for over a day. currently the root filesystems only hold a opkg.conf
>> > with base and luci. last night we regenerated the files so that the
>> > opkg.conf holds all feeds.
>> >
>> > while you were busy farting we were busy working. but thanks for the
>> > nice mail.
>> >
>> >
>> > On 01/10/2014 23:59, Etienne Champetier wrote:
>> > > Hi,
>> > >
>> > > OpenWRT is a wonderfull piece of open source code, and it would be
>> > > really great if the project management could be as open as the
>> > > code. BB should be out now but for an unknow reason, it's not, and
>> > > it's frustating. If some feature are missing, let people know. If
>> > > some bugs need to be killed, let the community help. If buildbots
>> > > are broken, let someone provide new ones. Open a TODO list on an
>> > > etherpad, involve people. Whatever the reasons are, i'm sure some
>> > > people can help.
>> > >
>> > > When you open the process, you get more work done (see new
>> > packages
>> > > feed).
>> > >
>> > > Please communicate!!!
>> > >
>> > > Thanks Etienne
>> > >
>> > >
>
>
>
> ___
> 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] Barrier Breaker 14.07-rc1

[Saverio Proto]

Hello John,

there will be no release branch here ?
http://git.openwrt.org/

thanks

Saverio


2014-07-14 11:12 GMT+02:00 John Crispin :
>
> 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
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Latest AA introduces a bug: not working as STA when AP is AirOS

[Saverio Proto]

Hello Gui,

AirMax is disabled.

The configuration on the AirOS node is always the same with AirMax disabled.

I can associate with the good commit and I cannot when I use the bad commit

Saverio


2014-05-20 18:06 GMT+02:00 Gui Iribarren :
> On 20/05/14 05:25, Saverio Proto wrote:
>> we upgraded the ninux firmware to the latest OpenWrt AA.
>>
>> We run into a possible bug. When STA is OpenWrt and AP is AirOS we are
>> not able to associate to the Access Point. We tested with the same
>> configuration and device the two versions of the firmware. Here the
>> commits:
>>
>> Bad:
>> 6deba98c3814ca9414ef5f2500c71942b210aa83
>>
>> Good:
>> 794897c318c3388db57bf0da34e61e0041cf0306
>>
>> it is too many commits in between to quickly do git bisect.
>>
>> I append the logs and the configuration of the OpenWrt host.
>
> Is airMAX enabled on the AirOS side?
> i was unable to associate from an openwrt trunk r36140 acting as a STA
> to an airgrid with airOS v5.5.4 acting as AP
> until i disabled airMAX on the airOS
> authentication went fine according to logread, but association failed
> (similar to your logs)
>
> i didn't try with an older version tho, just disabled airMax and let it be.
>
> cheers!
>
> gui
>
>> Please let me know what kind of information I can share to track down the 
>> bug.
>>
>> Anyone had similiar issues ?
>>
>> thanks
>>
>> Saverio
>>
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.23]
>> wlan0: authenticate with 00:15:6d:8e:a8:72
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.24]
>> wlan0: send auth to 00:15:6d:8e:a8:72 (try 1/3)
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.25]
>> wlan0: authenticated
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.25]
>> wlan0: AP has invalid WMM params (AIFSN=1 for ACI 2), disabling WMM
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.27]
>> wlan0: associate with 00:15:6d:8e:a8:72 (try 1/3)
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.27]
>> wlan0: RX AssocResp from 00:15:6d:8e:a8:72 (capab=0x401 status=37
>> aid=15241)
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.28]
>> wlan0: 00:15:6d:8e:a8:72 denied association (code=37)
>> May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.30]
>> wlan0: deauthenticating from 00:15:6d:8e:a8:72 by local choice
>> (reason=3)
>>
>> root@M5GalliaBramante:~# uci show wireless
>> wireless.radio0=wifi-device
>> wireless.radio0.type=mac80211
>> wireless.radio0.hwmode=11na
>> wireless.radio0.distance=1000
>> wireless.radio0.macaddr=00:27:
>> 22:38:d0:f1
>> wireless.radio0.ht_capab=SHORT-GI-40 TX-STBC RX-STBC1 DSSS_CCK-40
>> wireless.radio0.htmode=HT40+
>> wireless.radio0.noscan=1
>> wireless.@wifi-iface[0]=wifi-iface
>> wireless.@wifi-iface[0].device=radio0
>> wireless.@wifi-iface[0].network=backbone
>> wireless.@wifi-iface[0].mode=sta
>> wireless.@wifi-iface[0].ssid=ninux.org
>> wireless.@wifi-iface[0].bssid=00:15:6D:8E:A8:72
>> wireless.@wifi-iface[0].encryption=none
>> root@M5GalliaBramante:~#
>>
>>
>> This is the log in AirOS side:
>> May 19 13:22:32 wireless: ath0 Sending assoc responce to
>> 00:27:22:38:d0:f1. Status: The request has been declined (37).
>> May 19 13:23:02 wireless: ath0 
>> MLME-AUTH.indication(addr=00:27:22:38:d0:f1)
>> May 19 13:23:02 wireless: ath0 Sending assoc responce to
>> 00:27:22:38:d0:f1. Status: The request has been declined (37).
>> May 19 13:23:32 wireless: ath0 
>> MLME-AUTH.indication(addr=00:27:22:38:d0:f1)
>> May 19 13:23:32 wireless: ath0 Sending assoc responce to
>> 00:27:22:38:d0:f1. Status: The request has been declined (37).
>> ___
>> 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

[OpenWrt-Devel] Latest AA introduces a bug: not working as STA when AP is AirOS

[Saverio Proto]

we upgraded the ninux firmware to the latest OpenWrt AA.

We run into a possible bug. When STA is OpenWrt and AP is AirOS we are
not able to associate to the Access Point. We tested with the same
configuration and device the two versions of the firmware. Here the
commits:

Bad:
6deba98c3814ca9414ef5f2500c71942b210aa83

Good:
794897c318c3388db57bf0da34e61e0041cf0306

it is too many commits in between to quickly do git bisect.

I append the logs and the configuration of the OpenWrt host.
Please let me know what kind of information I can share to track down the bug.

Anyone had similiar issues ?

thanks

Saverio

May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.23]
wlan0: authenticate with 00:15:6d:8e:a8:72
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.24]
wlan0: send auth to 00:15:6d:8e:a8:72 (try 1/3)
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.25]
wlan0: authenticated
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.25]
wlan0: AP has invalid WMM params (AIFSN=1 for ACI 2), disabling WMM
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.27]
wlan0: associate with 00:15:6d:8e:a8:72 (try 1/3)
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.27]
wlan0: RX AssocResp from 00:15:6d:8e:a8:72 (capab=0x401 status=37
aid=15241)
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.28]
wlan0: 00:15:6d:8e:a8:72 denied association (code=37)
May 19 11:18:58 M5GalliaBramante kern.info kernel: [  291.30]
wlan0: deauthenticating from 00:15:6d:8e:a8:72 by local choice
(reason=3)

root@M5GalliaBramante:~# uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type=mac80211
wireless.radio0.hwmode=11na
wireless.radio0.distance=1000
wireless.radio0.macaddr=00:27:
22:38:d0:f1
wireless.radio0.ht_capab=SHORT-GI-40 TX-STBC RX-STBC1 DSSS_CCK-40
wireless.radio0.htmode=HT40+
wireless.radio0.noscan=1
wireless.@wifi-iface[0]=wifi-iface
wireless.@wifi-iface[0].device=radio0
wireless.@wifi-iface[0].network=backbone
wireless.@wifi-iface[0].mode=sta
wireless.@wifi-iface[0].ssid=ninux.org
wireless.@wifi-iface[0].bssid=00:15:6D:8E:A8:72
wireless.@wifi-iface[0].encryption=none
root@M5GalliaBramante:~#


This is the log in AirOS side:
May 19 13:22:32 wireless: ath0 Sending assoc responce to
00:27:22:38:d0:f1. Status: The request has been declined (37).
May 19 13:23:02 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:38:d0:f1)
May 19 13:23:02 wireless: ath0 Sending assoc responce to
00:27:22:38:d0:f1. Status: The request has been declined (37).
May 19 13:23:32 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:38:d0:f1)
May 19 13:23:32 wireless: ath0 Sending assoc responce to
00:27:22:38:d0:f1. Status: The request has been declined (37).
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Fix VLAN on Atheros AR8327N

[Saverio Proto]

Hello Alvaro,

I have another user (Cc: in this email) reporting wdr4300 working with
the original patch.

I updated my tree with your changes, and rebased on current trunk:
https://github.com/zioproto/openwrt-trunk-zioproto/commits/ticket12181

You are just deleting this code right ?
https://github.com/zioproto/openwrt-trunk-zioproto/commit/c4a8e0a8f164d03074d55e649e883422ae03c905

Alvaro and Domantas MrVisata, can you please tell me your testing
setup? I would like to understand what is working for Domantas and
what is not working for Alvaro.

If you just post your /etc/config/network it would be enough. Thanks.

Saverio

2014-05-02 3:07 GMT+02:00 Álvaro Fernández Rojas :
> Hello,
>
> I've tested this patch but I couldn't get it completely fixed on AR8327 
> (TL-WDR4300).
>
> However, I've modified it and successfully configured the switch for untagged 
> + tagged.
> https://dl.dropboxusercontent.com/u/4708147/openwrt/patches/ar8327.patch
>
> The problem was in ar8327_sw_set_ports(), which I suspect was copied from 
> ar8216_sw_set_ports(), without removing the code that disables all tagged 
> ports if an untagged port is already present.
>
> P.S: @Saverio feel free to resend the patch yourself if you agree with the 
> changes.
>
> Regards,
> Álvaro.
>
> El 24/04/2014 12:56, Saverio Proto escribió:
>> Hello,
>>
>> the patch is attached to this email.
>>
>> thanks
>>
>> Saverio
>>
>>
>> 2014-04-24 12:47 GMT+02:00 John Crispin :
>>>
>>>
>>> On 24/04/2014 12:44, Saverio Proto wrote:
>>>> Hello,
>>>>
>>>> talking about: https://dev.openwrt.org/ticket/12181
>>>>
>>>> patch has been tested @ Ninux.org on TP-Link WDR3600. We are now
>>>> able to successfully have tagged and untagged frames together on
>>>> the same port.
>>>>
>>>> Here is the clean version of the patch rebased on current trunk:
>>>> https://github.com/zioproto/openwrt-trunk-zioproto/commit/e7226ba45d7198dff71fde3caa1be9962f9f4ef1
>>>>
>>>>  please review it and merge it into trunk.
>>>>
>>>> Saverio
>>>
>>> hi Saverio,
>>>
>>> can you send the cleaned up version to the -devel list ? that way its
>>> inside out patchwork and we can mark the old version superseeded
>>>
>>> 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
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Fix VLAN on Atheros AR8327N

[Saverio Proto]

Hello,

the patch is attached to this email.

thanks

Saverio


2014-04-24 12:47 GMT+02:00 John Crispin :
>
>
> On 24/04/2014 12:44, Saverio Proto wrote:
>> Hello,
>>
>> talking about: https://dev.openwrt.org/ticket/12181
>>
>> patch has been tested @ Ninux.org on TP-Link WDR3600. We are now
>> able to successfully have tagged and untagged frames together on
>> the same port.
>>
>> Here is the clean version of the patch rebased on current trunk:
>> https://github.com/zioproto/openwrt-trunk-zioproto/commit/e7226ba45d7198dff71fde3caa1be9962f9f4ef1
>>
>>  please review it and merge it into trunk.
>>
>> Saverio
>
> hi Saverio,
>
> can you send the cleaned up version to the -devel list ? that way its
> inside out patchwork and we can mark the old version superseeded
>
> John
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
commit bd9e08d75f72a8d91e361a1d38bf3c7728b25fb4
Author: Saverio Proto 
Date:   Mon Mar 10 14:22:05 2014 +0100

Fix VLAN on Atheros AR8327N
https://dev.openwrt.org/ticket/12181
With this patch tagged and untagger frames are working on the same port

diff --git a/target/linux/generic/files/drivers/net/phy/ar8216.c b/target/linux/generic/files/drivers/net/phy/ar8216.c
index 3f60878..51adc12 100644
--- a/target/linux/generic/files/drivers/net/phy/ar8216.c
+++ b/target/linux/generic/files/drivers/net/phy/ar8216.c
@@ -73,12 +73,11 @@ struct ar8xxx_chip {
 
 	void (*init_globals)(struct ar8xxx_priv *priv);
 	void (*init_port)(struct ar8xxx_priv *priv, int port);
-	void (*setup_port)(struct ar8xxx_priv *priv, int port, u32 egress,
-			   u32 ingress, u32 members, u32 pvid);
+	void (*setup_port)(struct ar8xxx_priv *priv, int port, u32 members);
 	u32 (*read_port_status)(struct ar8xxx_priv *priv, int port);
 	int (*atu_flush)(struct ar8xxx_priv *priv);
 	void (*vtu_flush)(struct ar8xxx_priv *priv);
-	void (*vtu_load_vlan)(struct ar8xxx_priv *priv, u32 vid, u32 port_mask);
+	void (*vtu_load_vlan)(struct ar8xxx_priv *priv, u32 vlan);
 
 	const struct ar8xxx_mib_desc *mib_decs;
 	unsigned num_mibs;
@@ -112,7 +111,12 @@ struct ar8327_led {
 	enum ar8327_led_pattern pattern;
 };
 
+struct ar8216_data {
+	u8 vlan_tagged;
+};
+
 struct ar8327_data {
+	u8 vlan_tagged[AR8X16_MAX_VLANS];
 	u32 port0_status;
 	u32 port6_status;
 
@@ -138,6 +142,7 @@ struct ar8xxx_priv {
 	u8 chip_rev;
 	const struct ar8xxx_chip *chip;
 	union {
+		struct ar8216_data ar8216;
 		struct ar8327_data ar8327;
 	} chip_data;
 	bool initialized;
@@ -159,7 +164,6 @@ struct ar8xxx_priv {
 	bool vlan;
 	u16 vlan_id[AR8X16_MAX_VLANS];
 	u8 vlan_table[AR8X16_MAX_VLANS];
-	u8 vlan_tagged;
 	u16 pvid[AR8X16_MAX_PORTS];
 
 	/* mirroring */
@@ -641,7 +645,7 @@ ar8216_mangle_rx(struct net_device *dev, struct sk_buff *skb)
 	port = buf[0] & 0xf;
 
 	/* no need to fix up packets coming from a tagged source */
-	if (priv->vlan_tagged & (1 << port))
+	if (priv->chip_data.ar8216.vlan_tagged & BIT(port))
 		return;
 
 	/* lookup port vid from local table, the switch passes an invalid vlan id */
@@ -695,11 +699,15 @@ ar8216_vtu_flush(struct ar8xxx_priv *priv)
 }
 
 static void
-ar8216_vtu_load_vlan(struct ar8xxx_priv *priv, u32 vid, u32 port_mask)
+ar8216_vtu_load_vlan(struct ar8xxx_priv *priv, u32 vlan)
 {
 	u32 op;
 
+	u32 vid = priv->vlan_id[vlan];
+	u32 port_mask = priv->vlan_table[vlan];
+
 	op = AR8216_VTU_OP_LOAD | (vid << AR8216_VTU_VID_S);
+
 	ar8216_vtu_op(priv, op, port_mask);
 }
 
@@ -722,10 +730,26 @@ ar8216_read_port_status(struct ar8xxx_priv *priv, int port)
 }
 
 static void
-ar8216_setup_port(struct ar8xxx_priv *priv, int port, u32 egress, u32 ingress,
-		  u32 members, u32 pvid)
+ar8216_setup_port(struct ar8xxx_priv *priv, int port, u32 members)
 {
 	u32 header;
+	u32 egress, ingress;
+	u32 pvid;
+
+	if (priv->vlan) {
+		pvid = priv->vlan_id[priv->pvid[port]];
+		if (priv->chip_data.ar8216.vlan_tagged & BIT(port))
+			egress = AR8216_OUT_ADD_VLAN;
+		else
+			egress = AR8216_OUT_STRIP_VLAN;
+		ingress = AR8216_IN_SECURE;
+	} else {
+		pvid = port;
+		egress = AR8216_OUT_KEEP;
+		ingress = AR8216_IN_PORT_ONLY;
+	}
+
+
 
 	if (chip_is_ar8216(priv) && priv->vlan && port == AR8216_PORT_CPU)
 		header = AR8216_PORT_CTRL_HEADER;
@@ -807,9 +831,24 @@ static const struct ar8xxx_chip ar8216_chip = {
 };
 
 static void
-ar8236_setup_port(struct ar8xxx_priv *priv, int port, u32 egress, u32 ingress,
-		  u32 members, u32 pvid)
+ar8236_setup_port(struct ar8xxx_priv *priv, int port, u32 members)
 {
+	u32 egress, ingress;
+	u32 pvid;
+
+	if (priv->vlan) {
+		pvid = priv->vlan_id[priv->pvid[port]];
+		if (priv->chip_data.ar8216.vlan_tagged & BIT(port))
+			egress = AR8216_OUT_ADD_VLAN;
+	

Re: [OpenWrt-Devel] Fix VLAN on Atheros AR8327N

[Saverio Proto]

Hello,

talking about:
https://dev.openwrt.org/ticket/12181

patch has been tested @ Ninux.org on TP-Link WDR3600. We are now able
to successfully have tagged and untagged frames together on the same
port.

Here is the clean version of the patch rebased on current trunk:
https://github.com/zioproto/openwrt-trunk-zioproto/commit/e7226ba45d7198dff71fde3caa1be9962f9f4ef1

please review it and merge it into trunk.

Saverio

2014-03-31 14:05 GMT+02:00 Saverio Proto :
> Hello,
>
> I cleaned up and rebased on current trunk the patch found on the
> following ticket:
> https://dev.openwrt.org/ticket/12181
>
> I ask for help for proper testing.
>
> I can provide binary images if needed.
> My git repository is here:
> https://github.com/zioproto/openwrt-trunk-zioproto/tree/ticket12181
>
> thanks
>
> Saverio
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Fix VLAN on Atheros AR8327N

[Saverio Proto]

Yes,
the patch makes possible to have tagged+untagged vlan on the same port
at the same time.
please read https://dev.openwrt.org/ticket/12181 for more details

Saverio

2014-03-31 16:05 GMT+02:00 Damian Kaczkowski
:
> On 31 March 2014 14:05, Saverio Proto  wrote:
>>
>> Hello,
>>
>> I cleaned up and rebased on current trunk the patch found on the
>> following ticket:
>> https://dev.openwrt.org/ticket/12181
>>
>> I ask for help for proper testing.
>
>
>
> Hello there.
>
> Have a question. What about those switch chips:
> - ar8316,
> - ar8227,
> - ar7240.
>
> Are they also capable of doing tagged+untagged vlan on the same port at the
> same time? Do they benefit from this pach? Could anyone with a deeper
> knowledge comment on this topic please? Many thanks in advance.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Fix VLAN on Atheros AR8327N

[Saverio Proto]

Hello,

I cleaned up and rebased on current trunk the patch found on the
following ticket:
https://dev.openwrt.org/ticket/12181

I ask for help for proper testing.

I can provide binary images if needed.
My git repository is here:
https://github.com/zioproto/openwrt-trunk-zioproto/tree/ticket12181

thanks

Saverio
commit c172caa7844b2d10e7c9d8ac574673a6451746ef
Author: Saverio Proto 
Date:   Mon Mar 10 14:22:05 2014 +0100

Fix VLAN on Atheros AR8327N
https://dev.openwrt.org/ticket/12181
With this patch tagged and untagger frames are working on the same port

diff --git a/target/linux/generic/files/drivers/net/phy/ar8216.c b/target/linux/generic/files/drivers/net/phy/ar8216.c
index 3f60878..51adc12 100644
--- a/target/linux/generic/files/drivers/net/phy/ar8216.c
+++ b/target/linux/generic/files/drivers/net/phy/ar8216.c
@@ -73,12 +73,11 @@ struct ar8xxx_chip {
 
 	void (*init_globals)(struct ar8xxx_priv *priv);
 	void (*init_port)(struct ar8xxx_priv *priv, int port);
-	void (*setup_port)(struct ar8xxx_priv *priv, int port, u32 egress,
-			   u32 ingress, u32 members, u32 pvid);
+	void (*setup_port)(struct ar8xxx_priv *priv, int port, u32 members);
 	u32 (*read_port_status)(struct ar8xxx_priv *priv, int port);
 	int (*atu_flush)(struct ar8xxx_priv *priv);
 	void (*vtu_flush)(struct ar8xxx_priv *priv);
-	void (*vtu_load_vlan)(struct ar8xxx_priv *priv, u32 vid, u32 port_mask);
+	void (*vtu_load_vlan)(struct ar8xxx_priv *priv, u32 vlan);
 
 	const struct ar8xxx_mib_desc *mib_decs;
 	unsigned num_mibs;
@@ -112,7 +111,12 @@ struct ar8327_led {
 	enum ar8327_led_pattern pattern;
 };
 
+struct ar8216_data {
+	u8 vlan_tagged;
+};
+
 struct ar8327_data {
+	u8 vlan_tagged[AR8X16_MAX_VLANS];
 	u32 port0_status;
 	u32 port6_status;
 
@@ -138,6 +142,7 @@ struct ar8xxx_priv {
 	u8 chip_rev;
 	const struct ar8xxx_chip *chip;
 	union {
+		struct ar8216_data ar8216;
 		struct ar8327_data ar8327;
 	} chip_data;
 	bool initialized;
@@ -159,7 +164,6 @@ struct ar8xxx_priv {
 	bool vlan;
 	u16 vlan_id[AR8X16_MAX_VLANS];
 	u8 vlan_table[AR8X16_MAX_VLANS];
-	u8 vlan_tagged;
 	u16 pvid[AR8X16_MAX_PORTS];
 
 	/* mirroring */
@@ -641,7 +645,7 @@ ar8216_mangle_rx(struct net_device *dev, struct sk_buff *skb)
 	port = buf[0] & 0xf;
 
 	/* no need to fix up packets coming from a tagged source */
-	if (priv->vlan_tagged & (1 << port))
+	if (priv->chip_data.ar8216.vlan_tagged & BIT(port))
 		return;
 
 	/* lookup port vid from local table, the switch passes an invalid vlan id */
@@ -695,11 +699,15 @@ ar8216_vtu_flush(struct ar8xxx_priv *priv)
 }
 
 static void
-ar8216_vtu_load_vlan(struct ar8xxx_priv *priv, u32 vid, u32 port_mask)
+ar8216_vtu_load_vlan(struct ar8xxx_priv *priv, u32 vlan)
 {
 	u32 op;
 
+	u32 vid = priv->vlan_id[vlan];
+	u32 port_mask = priv->vlan_table[vlan];
+
 	op = AR8216_VTU_OP_LOAD | (vid << AR8216_VTU_VID_S);
+
 	ar8216_vtu_op(priv, op, port_mask);
 }
 
@@ -722,10 +730,26 @@ ar8216_read_port_status(struct ar8xxx_priv *priv, int port)
 }
 
 static void
-ar8216_setup_port(struct ar8xxx_priv *priv, int port, u32 egress, u32 ingress,
-		  u32 members, u32 pvid)
+ar8216_setup_port(struct ar8xxx_priv *priv, int port, u32 members)
 {
 	u32 header;
+	u32 egress, ingress;
+	u32 pvid;
+
+	if (priv->vlan) {
+		pvid = priv->vlan_id[priv->pvid[port]];
+		if (priv->chip_data.ar8216.vlan_tagged & BIT(port))
+			egress = AR8216_OUT_ADD_VLAN;
+		else
+			egress = AR8216_OUT_STRIP_VLAN;
+		ingress = AR8216_IN_SECURE;
+	} else {
+		pvid = port;
+		egress = AR8216_OUT_KEEP;
+		ingress = AR8216_IN_PORT_ONLY;
+	}
+
+
 
 	if (chip_is_ar8216(priv) && priv->vlan && port == AR8216_PORT_CPU)
 		header = AR8216_PORT_CTRL_HEADER;
@@ -807,9 +831,24 @@ static const struct ar8xxx_chip ar8216_chip = {
 };
 
 static void
-ar8236_setup_port(struct ar8xxx_priv *priv, int port, u32 egress, u32 ingress,
-		  u32 members, u32 pvid)
+ar8236_setup_port(struct ar8xxx_priv *priv, int port, u32 members)
 {
+	u32 egress, ingress;
+	u32 pvid;
+
+	if (priv->vlan) {
+		pvid = priv->vlan_id[priv->pvid[port]];
+		if (priv->chip_data.ar8216.vlan_tagged & BIT(port))
+			egress = AR8216_OUT_ADD_VLAN;
+		else
+			egress = AR8216_OUT_STRIP_VLAN;
+		ingress = AR8216_IN_SECURE;
+	} else {
+		pvid = port;
+		egress = AR8216_OUT_KEEP;
+		ingress = AR8216_IN_PORT_ONLY;
+	}
+
 	ar8xxx_rmw(priv, AR8216_REG_PORT_CTRL(port),
 		   AR8216_PORT_CTRL_LEARN | AR8216_PORT_CTRL_VLAN_MODE |
 		   AR8216_PORT_CTRL_SINGLE_VLAN | AR8216_PORT_CTRL_STATE |
@@ -1696,12 +1735,16 @@ ar8327_vtu_flush(struct ar8xxx_priv *priv)
 }
 
 static void
-ar8327_vtu_load_vlan(struct ar8xxx_priv *priv, u32 vid, u32 port_mask)
+ar8327_vtu_load_vlan(struct ar8xxx_priv *priv, u32 vlan)
 {
-	u32 op;
-	u32 val;
+	u32 op, val;
 	int i;
 
+	u32 vid = priv->vlan_id[vlan];
+	u32 port_mask = priv->vlan_table[vlan];
+	u32 tagged = priv->chip_data.ar8327.vlan_tagged[vlan];
+
+
 	op = AR8327_VTU_FUNC1_OP_LOAD | 

Re: [OpenWrt-Devel] Testing Sunxi target with cubieboard

[Saverio Proto]

Hello,

today I tried to boot the latest trunk with my CubieboardA10, but I
cannot boot at all.

I followed this guide:
http://wiki.openwrt.org/doc/hardware/soc/soc.allwinner.sunxi

the most important stuff is:
dd if=openwrt-sunxi-Cubieboard-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8

then I formatted vfat the first partition and I copied the kernel file:

cp openwrt-sunxi-uImage-initramfs /mountpoint/uImage

Here is the boot log from serial console:
http://pastebin.com/CLAcNL91

it looks to me like the uboot configuration is messed up.

Zoltan any hint how to successfully boot ?

thanks

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

Re: [OpenWrt-Devel] Testing Sunxi target with cubieboard

[Saverio Proto]

> I've added only minimal support, it only worked with initramfs. Since
> last night (r38811) Zoltan took over the target and pushed 3.12 kernel.
> He should give you more information at this point as I have not tested
> it yet.

Thanks.
I see now r38785 that is even more important.

I compiled the new trunk and now I see also the uboot necessary bin
files to dd in the sd card before the first partition.

Just one more question about the script.bin file.

I have a script.bin I built my self following instructions here:
http://linux-sunxi.org/FirstSteps
is OpenWrt buildroot also going to compile this file ?

thanks

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

[OpenWrt-Devel] Testing Sunxi target with cubieboard

[Saverio Proto]

Hello Luka,

I tested before the Cubieboard with OpenWrt and and external kernel
tree, I had some notes here:
http://wiki.ninux.org/CubieboardOpenWrt

I built now a new openwrt trunk image with your latest patches.

https://dev.openwrt.org/changeset/38651

I have the kernel booting, but I am stucked here:
[0.45] Waiting for root device /dev/mmcblk0p2...

here the full boot log:
http://pastebin.com/HHkL2Bxs

I tried with the uboot setenv to change the name of the root device in
/dev/sda2 but it does not work, and I have no idea what kind of name
to guess.

can you give me some advice ?

thanks

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

Re: [OpenWrt-Devel] openwrt-routing feed

[Saverio Proto]

> *) we should not have feature or testing branches in feeds

what is the problem with testing branches ?

as long as the necessary branches are there with the correct names, I
dont see the drawback of the extra branches.

thanks

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

Re: [OpenWrt-Devel] openwrt-routing feed

[Saverio Proto]

Hello Luka,

my github name is zioproto and my email is correct in the MAINTAINERS file.

Saverio

2013/10/6 Luka Perkov :
> Dear openwrt-routing feed committers,
>
> I've added MAINTAINERS file to the openwrt-routing git repository.
> Please update that file with your real name and valid email address,
> reply to this email that you did so and tell us your github account
> name.
>
> I'm going to remove access to those of you who don't do the above in the
> next 7 days. In case your commit access gets removed don't worry, I'll
> re-enable it on request. I have CCed some of the recent committers.
>
> When committing use the name and email listed in MAINTAINERS file. Also,
> please do not push "test" or "feature" branches. The ones in question
> are:
>
> alfred-facters
> batman-adv-netifd
> bmx6_dev
> bmx6_testing
>
> If you think that your branch should be present tell us why you think
> so, otherwise I will drop them.
>
> Luka
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] softflowd version bump to 0.9.9

[Saverio Proto]

Hello,

the attached patch updates softflowd package.

the current version is broken and not working, so please apply this patch asap.

there is currently no maintainer, if community agrees we can move this
package to openwrt-routing feed so I can take care of it.

Saverio


softflowd-version-bump-0.9.9.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Has anyone ported the openwrt on beaglebone?

[Saverio Proto]

I used a port for a similar board (cubieboard).
It works good for me with a external kernel tree.
You might want to look at this:
https://github.com/zioproto/openwrt-sunxi/tree/sunxi-rebased

It is pretty similar board, with ARM Cortex processor.

Saverio



2013/6/24 Artur Wronowski :
> Thanks for reply.
>
> Here is kernel configuration: http://pastebin.com/fbMAhi0k
>
> I have enabled CONFIG_DEBUG_LL
>
> 2013/6/24 Florian Fainelli :
>> 2013/6/24 Artur Wronowski :
>>> I have enabled earlyprink and this not help.  I think there is a
>>> problem with toolchain or somethink else.
>>
>> Are you sure that you also enabled low-level debugging? I would rather
>> suspect a kernel configuration issue, or a memory configuration issue.
>> ARM kernels have a tendency to be able to crash every early if the
>> memory map is wrong, that includes both declaring the available
>> physical memory and the virtual memory layout.
>> --
>> Florian
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
>
> --
> Pozdrawiam, Artur
> Best regards, Artur
> http://artekw.net / http://digi-led.pl / GG: 1518171 / Jabber: 
> art...@jabbim.pl
> ___
> 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] [packages] polipo: Don't spuriously ignore CNAMEs after a DNS timeout. Polipo might quit with SIGPIPE without this patch

[Saverio Proto]

>> 2. The patch description is incorrect -- the bug symptom is not
>> SIGPIPE.  SIGPIPE is globally ignored by Polipo.
>
> I had polipo segfaulting before applying this patch. With gdb I
> thought to understand it was a SIGPIPE problem, but I can be wrong
> because I am not a experienced developer.

Juliusz you are right. SIGPIPE was completely wrong. I went to study.
I am very begineer gdb user and I did not have a good understanding of
signals.

The situation is the following:
version 1.0.4: eventually segfaults, but I was not able yet to
reproduce this bug in GDB
version 1.0.4: you should ignore SIGPIPE signal in GDB if you want to debug
version 1.0.4: debian applies this patch to the deb package on top of
1.0.4, so might have it also on OpenWRT because it should increase the
overall stability
git master: looks more stable, I have this version running now and it
is not crashing.

sorry for the confusion on the list. Making debug at late night after
long days of work did not help :))

ciao :)

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

Re: [OpenWrt-Devel] [packages] polipo: Don't spuriously ignore CNAMEs after a DNS timeout. Polipo might quit with SIGPIPE without this patch

[Saverio Proto]

> 1. That's commit 1144bc9a from Polipo master.  Please include proper
> cross-referencing information in the future.

I just got the patch from the Debian .deb package "as it was" and I
added it to the OpenWRT package. There is a reference to the commit in
the patch.
How can I cross-reference better ?

> 2. The patch description is incorrect -- the bug symptom is not
> SIGPIPE.  SIGPIPE is globally ignored by Polipo.

I had polipo segfaulting before applying this patch. With gdb I
thought to understand it was a SIGPIPE problem, but I can be wrong
because I am not a experienced developer.

> 3. Saverio, perhaps you should be running master instead of the old 1.0.4 
> branch?

yesterday it was my first day with polipo, I didn't feel ready for the
unstable version :)

> 4. Saverio, if anyone wants to put master into shape for a 1.1
> release, I'll be very grateful.  However, I do not have a lot of time
> to spend on Polipo any more.

OK, I will consider that. Maybe somebody in Ninux has time to do this.

thanks for everything

ciao :)

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

[OpenWrt-Devel] [packages] polipo: Don't spuriously ignore CNAMEs after a DNS timeout. Polipo might quit with SIGPIPE without this patch

[Saverio Proto]

Patch is attached,
please commit at least to trunk packages.

ciao :)

Saverio


polipo-openwrt.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] snmpd 5.4.2.1 IPv6

[Saverio Proto]

do you have a version of snmpwalk that works with IPv6 ? :)
I tried to dive into that about a year ago but then I gave up because
IPv6 and snmp is not yet well supported on Linux. Please if you have
better news tell me ! :)

ciao,

Saverio


2013/4/25 Pietro Paolini :
> Hello all,
>
> I am experiencing a problem on configuring the snmpd with this configuration:
>
> agentaddress UDP:161
> agentaddress UDP6:161
> authtrapenable 2
> sysObjectID 1.3.6.1.4.1.9303.1.6.4
> com2sec public default public
> com2sec6 public default public
> group grp_dEFaUlt_2_public v2c public
> view all included .1
> access grp_dEFaUlt_2_public "" v2c noauth exact all all none
>
>
> Using that I am not able to reach the SNMP "server"  by IPv6 and I have this 
> output :
>
> Received 45 bytes from UDP/IPv6: [fe80::a00:27ff:fe25:5b52]:40490
> : 30 2B 02 01  00 04 06 70  75 62 6C 69  63 A1 1E 020+.public...
> 0016: 04 67 E2 48  20 02 01 00  02 01 00 30  10 30 0E 06.g.H ..0.0..
> 0032: 0A 2B 06 01  04 01 C8 57  01 01 01 05  00 .+.W.
>
> Received SNMP packet(s) from UDP/IPv6: [fe80::a00:27ff:fe25:5b52]:40490
> GETNEXT message
>  -- iso.3.6.1.4.1.9303.1.1.1
>
> But the SNMP agent does not answer at the request, I can solve this problem 
> using the adding line
>
> rocommunity6 public [http://marc.info/?l=net-snmp-users&m=117009730030108]
>
> but in this way I can't write anymore … it seems that the
>
> rocommunity6 public
>
> override the
>
> access grp_dEFaUlt_2_public "" v2c noauth exact all all none
>
>
> Someone already meet that problem or knows how enable the IPv6 access ?
> Thanks,
> Pietro.
>
>
>
> ___
> 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] buildroot not building for specific models

[Saverio Proto]

This models that are not built have 4Mb flash ? maybe you are trying
to build an image that is too big, so only the images of the models
with 8Mb of flash are generated. This is a common question.

Saverio


2013/4/8 cmsv :
> I have had this problem in the past for a couple router models/version
> while trying to make an image for them.
> The last time i had this issue was with the tplink wr841n v8 and with
> some AA revisions even the tl-wr 1043nd. (all routers that i use)
>
> Now i am unable to build firmware images for several other models like
> for example dlink. In specific dir 600/601 and dir 615 among many others.
>
> Target System (Atheros AR7xxx/AR9xxx)  --->
> (X) Atheros AR7xxx/AR9xxx
> Subtarget (Generic)  --->
> (X) Generic
> Target Profile (Default Profile (all drivers))  --->
> (X) Default Profile (all drivers)
>
> Trying to build am image for s apecific model that does not build while
> selecting all drivers; also doe snot build that image but everything
> else that comes with it.
>
>
> OpenWrt Attitude Adjustment (r36088)
>
> svn info
> Path: .
> URL: svn://svn.openwrt.org/openwrt/branches/attitude_adjustment
> Repository Root: svn://svn.openwrt.org/openwrt
> Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73
> Revision: 36256
> Node Kind: directory
> Schedule: normal
> Last Changed Author: florian
> Last Changed Rev: 36088
> Last Changed Date: 2013-03-19 09:36:32 -0400 (Tue, 19 Mar 2013)
>
> Build platform is gentoo 64bit
> Thread model: posix
> gcc version 4.5.4 (Gentoo 4.5.4 p1.0, pie-0.4.7)
> sys-devel/make 3.82-r4
>
> Any suggestions about how to fix this ?
>
>
>
>
>
>
>
>
>
>
> --
>
>
>
>
>
> Site:  http://wirelesspt.net
> Mesh: http://tinyurl.com/wirelesspt
> Admin: http://wirelesspt.net/wiki/Cmsv
> Suporte técnico via sms: 91 19 11 798
> Chave publica PGP/SSH: http://wirelesspt.net/arquivos/pk
> Email assinado digitalmente pelo emissor assegurando autenticidade
>
>
>
>
> ___
> 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] Question on conffiles define / nodogsplash

[Saverio Proto]

Hello,

I have a personal version of nodogsplash OpenWRT package and I noticed
today I was missing this patch from the main tree:

https://github.com/ninuxorg/ninux-openwrt-packages/commit/92f90fae6ef6e29f789c2c7a539c4a3efb31b70d

when I added this:

define Package/nodogsplash/conffiles
/etc/nodogsplash/nodogsplash.conf
endef

did I made my system smarter so that the file
/etc/nodogsplash/nodogsplash.conf is saved automatically when I do
sysupgrade ?
if not, what is the difference without this patch ?

thanks

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

Re: [OpenWrt-Devel] [packages] olsrd: init: patchset for download

[Saverio Proto]

> Anything i can do to speedup things?

no :(
I have to find some free time for the testing :(

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

Re: [OpenWrt-Devel] [packages] olsrd: init: patchset for download

[Saverio Proto]

Hello Bastian,

I successfully imported the patches in my tree.
Give me a little time for testing.

ciao,

Saverio


2013/3/11 Bastian Bittorf :
> these inline patches are also here for download them:
> https://github.com/bittorf/kalua/blob/master/openwrt-patches/0001-packages-olsrd-init-for-better-reuse-make-a-function.patch
> https://github.com/bittorf/kalua/blob/master/openwrt-patches/0002-packages-olsrd-init-parse-new-var-speed-which-transl.patch
> https://github.com/bittorf/kalua/blob/master/openwrt-patches/0003-packages-olsrd-init-reduce-code-duplication-by-reusi.patch
>
> bye, bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ping to the list

[Saverio Proto]

Yes,
somebody wrote directly to me with Cc list.openwrt.org, and my reply
to all started to generate this bounce.

thanks

Saverio


2013/2/8 Florian Fainelli :
> On 02/08/2013 10:46 AM, Saverio Proto wrote:
>>
>> Hello list,
>>
>> do you get this email ? I got some bounces to my emails to the list
>> from Mailer Demon of Google with this reason:
>>
>>
>> The recipient server did not accept our requests to connect. Learn
>> more at http://support.google.com/mail/bin/answer.py?answer=7720
>> [(0) list.openwrt.com. [173.212.56.232]:25: Connection timed out]
>
>
> You probably made a typo and sent a mail to list.openwrt.com instead of:
> lists.openwrt.org (mind the trailing 's' and .org domain).
> --
> Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] ping to the list

[Saverio Proto]

Hello list,

do you get this email ? I got some bounces to my emails to the list
from Mailer Demon of Google with this reason:


The recipient server did not accept our requests to connect. Learn
more at http://support.google.com/mail/bin/answer.py?answer=7720
[(0) list.openwrt.com. [173.212.56.232]:25: Connection timed out]

ciao,

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

Re: [OpenWrt-Devel] Compiling Problem

[Saverio Proto]

Hello,

you need to post what svn revision of OpenWRT you are compiling.

best regards

Saverio Proto


2013/2/4 Pietro Paolini :
> Hi all,
>
> I catch a problem in compiling the toolchain, I am under a:
>
> Linux pedr0debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686
> GNU/Linux
>
>
> And error is :
>
>
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//math.texi:1369: warning: @strong{Note...} produces a spurious
> cross-reference in Info; reword to avoid that.
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:2: `Language Features' has no Up field (perhaps
> incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//contrib.texi:1: Prev reference to nonexistent node
> `Maintenance' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//libc.texinfo:86: Node `Top' lacks menu item for
> `Contributors' despite being its Up target.
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//install.texi:5: Next reference to nonexistent node
> `Maintenance' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//install.texi:5: Prev reference to nonexistent node `Library
> Summary' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//libc.texinfo:86: Node `Top' lacks menu item for
> `Installation' despite being its Up target.
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//crypt.texi:2: `Cryptographic Functions' has no Up field
> (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//debug.texi:1: `Debugging Support' has no Up field (perhaps
> incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//conf.texi:1: Next field of node `System Configuration' not
> pointed to (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//crypt.texi:2: This node (Cryptographic Functions) has the bad
> Prev.
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//conf.texi:1: Prev reference to nonexistent node `System
> Management' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//libc.texinfo:86: Node `Top' lacks menu item for `System
> Configuration' despite being its Up target.
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//math.texi:30: Next reference to nonexistent node `Arithmetic'
> (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//math.texi:30: Prev reference to nonexistent node `Syslog'
> (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//libc.texinfo:86: Node `Top' lacks menu item for `Mathematics'
> despite being its Up target.
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//libc.texinfo:86: Next reference to nonexistent node
> `Introduction' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:874: Cross reference to nonexistent node `I/O on
> Streams' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:852: Cross reference to nonexistent node `Extended
> Char Intro' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:631: Cross reference to nonexistent node `Copying
> and Concatenation' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:630: Cross reference to nonexistent node
> `Unconstrained Allocation' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:364: Cross reference to nonexistent node `Executing
> a File' (perhaps incorrect sectioning?).
> /home/ppaolini/repo/drgos/build_dir/toolchain-arm_gcc-4.1.2_glibc-2.7/glibc
> -2.7/manual//lang.texi:3

Re: [OpenWrt-Devel] [Patch] Tinc: Remove temporary config on net start and stop in initscript

[Saverio Proto]

Hello Manuel,

I tested on my router and now the patch is committed in r35053

https://dev.openwrt.org/changeset/35053

thanks

Saverio


2013/1/3 Saverio Proto :
> Hello Manuel,
>
> I will test your patch as soon as possible.
>
> thanks
>
> Saverio
>
>
> 2012/12/22 Manuel Munz :
>> The initscript for tinc writes a temporary config into /tmp/tinc. In the
>> prepare_net function it appends flags and params from the uci config to
>> the temporary tinc.conf for each net. These values are appended to the
>> config file on each /etc/init.d/tinc restart and the file grows. By
>> removing all old temporary config this problem is solved. Then we should
>> also remove the temporary config for a net which is stopped to free up
>> some bytes in memory.
>>
>> Signed-off-by: Manuel Munz 
>>
>>
>> ___
>> 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] [PATCH] [packages] mini_snmpd: Add wireless signal and noise data

[Saverio Proto]

Hello Jack,

did you send this patch also to the mini_snmpd developers to have this
patch in the next releases ?

thanks

Saverio Proto


2012/12/21 Jack Bates :
> Support monitoring wireless signal and noise with SNMP. This is based on
> the demo example distributed with Mini SNMP Daemon. Here is a recipe for
> configuring Cacti to graph this data:
> http://jdbates.blogspot.com/2012/12/heres-patch-for-mini-snmp-daemon-to.html
>
> Signed-off-by: Jack Bates 
> ---
> We have been successfully running this patch on 32 devices for a month,
> to monitor signal and noise with Cacti. I am happy to make any changes
> that you request.
>
> Index: packages/net/mini_snmpd/patches/104-wireless.patch
> ===
> --- packages/net/mini_snmpd/patches/104-wireless.patch  (revision 0)
> +++ packages/net/mini_snmpd/patches/104-wireless.patch  (working copy)
> @@ -0,0 +1,223 @@
> +--- a/globals.c
>  b/globals.c
> +@@ -47,6 +47,10 @@
> + int g_disk_list_length = 0;
> + char *g_interface_list[MAX_NR_INTERFACES];
> + int g_interface_list_length = 0;
> ++#ifdef __WIRELESS__
> ++char *g_wireless_list[MAX_NR_INTERFACES];
> ++int g_wireless_list_length = 0;
> ++#endif
> + client_t g_udp_client = { 0, };
> + client_t *g_tcp_client_list[MAX_NR_CLIENTS];
> + int g_tcp_client_list_length = 0;
> +--- a/Makefile
>  b/Makefile
> +@@ -34,7 +34,7 @@
> + VENDOR= .1.3.6.1.4.1
> + OFLAGS= -O2
> + CFLAGS= -Wall -Werror -DVERSION="\"$(VERSION)\"" 
> -DVENDOR="\"$(VENDOR)\"" \
> +-$(OFLAGS) -D__TRAPS__ -D__LINUX__
> ++$(OFLAGS) -D__TRAPS__ -D__LINUX__ -D__WIRELESS__
> + LDFLAGS   = $(OFLAGS)
> + TARGET= mini_snmpd
> + MAN   = mini_snmpd.8
> +--- a/mib.c
>  b/mib.c
> +@@ -46,6 +46,9 @@
> + static const oid_t m_if_1_oid = { { 1, 3, 6, 1, 2, 1, 2 
>   }, 7, 8  };
> + static const oid_t m_if_2_oid = { { 1, 3, 6, 1, 2, 1, 2, 2, 1   
>   }, 9, 10 };
> + static const oid_t m_host_oid = { { 1, 3, 6, 1, 2, 1, 25, 1 
>   }, 8, 9  };
> ++#ifdef __WIRELESS__
> ++static const oid_t m_wireless_oid = { { 1, 3, 6, 1, 4, 1, 762, 2, 5, 2, 
> 1 }, 11, 13 };
> ++#endif
> + static const oid_t m_memory_oid   = { { 1, 3, 6, 1, 4, 1, 2021, 
> 4,}, 8, 10 };
> + static const oid_t m_disk_oid = { { 1, 3, 6, 1, 4, 1, 2021, 9, 1
>   }, 9, 11 };
> + static const oid_t m_load_oid = { { 1, 3, 6, 1, 4, 1, 2021, 10, 1   
>   }, 9, 11 };
> +@@ -527,6 +530,25 @@
> +   return -1;
> +   }
> +
> ++#ifdef __WIRELESS__
> ++  if (g_wireless_list_length > 0) {
> ++  for (i = 0; i < g_wireless_list_length; i++) {
> ++  if (mib_build_entry(&m_wireless_oid, 1, i + 1, 
> BER_TYPE_INTEGER, (const void *)(i + 1)) == -1) {
> ++  return -1;
> ++  }
> ++  }
> ++  for (i = 0; i < g_wireless_list_length; i++) {
> ++  if (mib_build_entry(&m_wireless_oid, 3, i + 1, 
> BER_TYPE_OCTET_STRING, g_wireless_list[i]) == -1) {
> ++  return -1;
> ++  }
> ++  }
> ++  if (mib_build_entries(&m_wireless_oid, 7, 1, 
> g_wireless_list_length, BER_TYPE_INTEGER, (const void *)0) == -1
> ++  || mib_build_entries(&m_wireless_oid, 8, 1, 
> g_wireless_list_length, BER_TYPE_INTEGER, (const void *)0) == -1) {
> ++  return -1;
> ++  }
> ++  }
> ++#endif
> ++
> +   /* The memory MIB: total/free memory (UCD-SNMP-MIB.txt)
> +* Caution: on changes, adapt the corresponding mib_update() section 
> too!
> +*/
> +@@ -621,6 +643,9 @@
> +   meminfo_t meminfo;
> +   cpuinfo_t cpuinfo;
> +   netinfo_t netinfo;
> ++#ifdef __WIRELESS__
> ++  wirelessinfo_t wirelessinfo;
> ++#endif
> + #ifdef __DEMO__
> +   demoinfo_t demoinfo;
> + #endif
> +@@ -700,6 +725,24 @@
> +   return -1;
> +   }
> +
> ++#ifdef __WIRELESS__
> ++  if (full) {
> ++  if (g_wireless_list_length > 0) {
> ++  get_wirelessinfo(&u.wirelessinfo);
> ++  for (i = 0; i < g_wireless_list_length; i++) {
> ++  if (mib_update_entry(&m_wireless_oid, 7, i + 
> 1, &pos, BER_TYPE_INTEGER, (const void *)u.wirelessinfo

Re: [OpenWrt-Devel] [Patch] Tinc: Remove temporary config on net start and stop in initscript

[Saverio Proto]

Hello Manuel,

I will test your patch as soon as possible.

thanks

Saverio


2012/12/22 Manuel Munz :
> The initscript for tinc writes a temporary config into /tmp/tinc. In the
> prepare_net function it appends flags and params from the uci config to
> the temporary tinc.conf for each net. These values are appended to the
> config file on each /etc/init.d/tinc restart and the file grows. By
> removing all old temporary config this problem is solved. Then we should
> also remove the temporary config for a net which is stopped to free up
> some bytes in memory.
>
> Signed-off-by: Manuel Munz 
>
>
> ___
> 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] RADVD Excessive Reloading of Configuration File

[Saverio Proto]

Hello,

did you notify this problem upstream to radvd developers also ?

thanks

Saverio Proto


2013/1/2 Nathan Hintz :
> When running 'top', I sometimes see RADVD consuming a lot of CPU (some times
> close to 50%).  I put some debug statements into RADVD, and have found that
> RADVD listens to a netlink socket, and basically reloads the configuration 
> file
> for every netlink message it receives, regardless of content.  I have seen 
> more
> than 60 reloads in a single second, which are generally triggered for Wireless
> Extension events for one of the wireless interfaces.  There currently is a 
> patch
> (feeds/packages/ipv6/radvd/patches/100-silent-netlink-config-reload.patch) 
> that
> attempts to silence the logging of the reloads, but this is really just 
> masking
> the problem, and poorly at that.  It seems like RADVD should be filtering the
> netlink messages down to what it cares about, and only then triggering the
> reload.
>
> I took a cut at a patch (attached) that seems reasonable to me; but since I
> have just a very basic understanding of RADVD and netlink, the patch is likely
> incomplete/wrong.
>
> Any feedback would be appreciated; or if someone would like to expand on this,
> feel free.
>
> Thanks,
>
> Nathan
>
> --- /dev/null   1982-12-26 14:57:26.236767395 -0800
> +++ feeds/packages/ipv6/radvd/patches/101-reduce-netlink-config-reload.patch  
>   2013-01-01 19:06:30.543780805 -0800
> @@ -0,0 +1,48 @@
> +--- a/netlink.c
>  b/netlink.c
> +@@ -41,7 +41,10 @@
> +   struct msghdr msg = { (void *)&sa, sizeof(sa), &iov, 1, NULL, 0, 0 };
> +   struct nlmsghdr *nh;
> +   struct ifinfomsg * ifinfo;
> ++  struct rtattr *rta;
> ++  int rta_len;
> +   char ifname[IF_NAMESIZE] = {""};
> ++  int reloaded = 0;
> +
> +   len = recvmsg (sock, &msg, 0);
> +   if (len == -1) {
> +@@ -59,15 +62,26 @@
> +   }
> +
> +   /* Continue with parsing payload. */
> +-  ifinfo = NLMSG_DATA(nh);
> +-  if_indextoname(ifinfo->ifi_index, ifname);
> +-  if (ifinfo->ifi_flags & IFF_RUNNING) {
> +-  dlog(LOG_DEBUG, 3, "%s, ifindex %d, flags is 
> running", ifname, ifinfo->ifi_index);
> ++  if (nh->nlmsg_type == RTM_NEWLINK || nh->nlmsg_type == 
> RTM_DELLINK || nh->nlmsg_type == RTM_SETLINK) {
> ++  ifinfo = (struct ifinfomsg *)NLMSG_DATA(nh);
> ++  if_indextoname(ifinfo->ifi_index, ifname);
> ++  rta = IFLA_RTA(NLMSG_DATA(nh));
> ++  rta_len = nh->nlmsg_len - NLMSG_LENGTH(sizeof(struct 
> ifinfomsg));
> ++  for (; RTA_OK(rta, rta_len); rta = RTA_NEXT(rta, 
> rta_len)) {
> ++  if (rta->rta_type == IFLA_OPERSTATE || 
> rta->rta_type == IFLA_LINKMODE) {
> ++  if (ifinfo->ifi_flags & IFF_RUNNING) {
> ++  dlog(LOG_DEBUG, 3, "%s, 
> ifindex %d, flags is running", ifname, ifinfo->ifi_index);
> ++  }
> ++  else {
> ++  dlog(LOG_DEBUG, 3, "%s, 
> ifindex %d, flags is *NOT* running", ifname, ifinfo->ifi_index);
> ++  }
> ++  if (!reloaded) {
> ++  reload_config(LOG_DEBUG);
> ++  reloaded = 1;
> ++  }
> ++  }
> ++  }
> +   }
> +-  else {
> +-  dlog(LOG_DEBUG, 3, "%s, ifindex %d, flags is *NOT* 
> running", ifname, ifinfo->ifi_index);
> +-  }
> +-  reload_config(LOG_DEBUG);
> +   }
> + }
> +
>
> ___
> 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] AR71 ath: phy0: Failed to stop TX DMA, queues=0x100! Was: Fwd: [OpenWrt-Users] Wifi trouble

[Saverio Proto]

FYI


-- Forwarded message --
From: Justin Vallon 
Date: 2012/10/29
Subject: [OpenWrt-Users] Wifi trouble
To: openwrt-us...@lists.openwrt.org


Found this in system log, wifi stopped working:

Oct 29 04:03:43 kiwi kern.err kernel: [14858.50] ath: phy0: Failed
to stop TX DMA, queues=0x100!
Oct 29 04:03:45 kiwi kern.err kernel: [14859.69] ath: phy0: Failed
to stop TX DMA, queues=0x100!
Oct 29 04:03:45 kiwi kern.err kernel: [14860.28] ath: phy0: Failed
to stop TX DMA, queues=0x100!
Oct 29 04:03:59 kiwi kern.err kernel: [14874.13] ath: phy0: Failed
to stop TX DMA, queues=0x100!

I have been running this for a couple of days.  This is the first time
wifi has died.

Model is "TP-Link TL-WR1043N/ND v1", firmware "OpenWrt Attitude
Adjustment 12.09-beta2 / LuCI 0.11 Branch (0.11+svn9402)".

BTW, the log in luci (in this case) did not show enough data.  Where
is OpenWRT's /var/log/messages, etc?

--
-Justin
justinval...@gmail.com

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

Re: [OpenWrt-Devel] openwrt-atheros-ubnt5-squashfs.bin not generated in openwrt trunk

[Saverio Proto]

The image that is not generated is for a device with 4Mb flash ? If
your build makes a larger image you will find only 8Mb images
generated but not the smaller ones.

I hope this help.

best regards

Saverio Proto


2012/10/25 Sivateja Patibandla :
> Hey guys,
>
> I've updated my openWRT trunk build environment to the latest release
> yesterday by "make dirclean and svn update". Now I configure and compile the
> kernel as before. But now the binary file for my Atheros based Ubiquiti
> device (openwrt-atheros-ubnt5-squashfs.bin) is not being generated. Although
> I've other files like openwrt-atheros-root.squashfs in bin directory being
> generated. Can you guys tell me if I'm missing something?
>
> Regards,
>
> Siva.
>
> ___
> 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] Problem with underscores and dashes in the OpenWRT Uci configuration of olsrd

[ZioPRoTo (Saverio Proto)]

Hello,

I found a bug ! :)

I need this block of configuration for olsrd:

LoadPlugin "olsrd_mdns.so.1.0.1"
{
PlParam "NonOlsrIf" "br-lan"
PlParam "TTL_Check" "true"
PlParam "MDNS_TTL" "20"
}

So I write this UCI syntax

config LoadPlugin
option library 'olsrd_mdns.so.1.0.1'
option "NonOlsrIf"  "lan"
option "TTL_Check"  "true"
option "MDNS_TTL"   "20"

But I find this wrong block when I check the /var/etc/olsrd.conf
(where underscores _ are changed with dashes - )

LoadPlugin "olsrd_mdns.so.1.0.1"
{
PlParam "NonOlsrIf" "br-lan"
PlParam "TTL-Check" "true"
PlParam "MDNS-TTL" "20"
}

This was tested both with trunk (git commit
05358e592055bbddbbf56dd656903902b1e9d80f) and backfire branch

This should be fixed in UCI ? Or I should patch olsrd ?

thanks

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

Re: [OpenWrt-Devel] [PATCH] nodogsplash uses deprecated iptables syntax

[ZioPRoTo (Saverio Proto)]

Thanks !

I included the patch in the Ninux firmware, as soon as I have it
tested I will report. However the patch looks so trivial that I would
ask to package maintainer to commit it immediatly :)

Moritz maybe you are interested in forking our git repository:
https://github.com/ninuxorg/nodogsplashninux

Saverio


2012/6/10 Moritz Warning :
> Starting nodogsplash there is the following warning on the console:
>
> Using intrapositioned negation (`--option ! this`) is deprecated in
> favor of extrapositioned (`! --option this`).
>
> Attached is a trivial patch to fix the issue.
>
>
> ___
> 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] openwrt backfire 10.03.2 + batman-adv

[ZioPRoTo (Saverio Proto)]

> No release is necessary. The OpenWrt stable maintainer(s) need to backport
> that fix to stable or you do it yourself or you use trunk.

Hello,

this conversation come out to be very interesting to me. I finally
realize why Ninux Pisa uses OpenWRT trunk and not a stable realease.

Marek may I ask if the matter is just this bug with the start/stop
scripts not working correctly at boot, or if there are more issues in
using the batman-adv package with the backfire branch ?

The one million dollar question is if we identify all this problems
can we make sure the OpenWRT developers backport all the necessary
stuff from trunk in the next stable release ?

thanks

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

Re: [OpenWrt-Devel] openwrt backfire 10.03.2 + batman-adv

[ZioPRoTo (Saverio Proto)]

Looks like the committer for the OpenWRT package is Marek:
https://dev.openwrt.org/browser/packages/net/batman-adv

did you report this problem to him ?

bye :)

Saverio

2012/5/23 Pedro Nuno Costa Rodrigues :
>
> Hello, my name is Pedro, and I'm writing from Portugal.
>
> I would like to ask some questions about batman-adv in openwrt backfire
> 10.03.2.
>
> I already wrote to http://www.open-mesh.org/wiki/open-mesh/MailingList (the
> mailing list of batman-adv routing protocol) but the developers of the
> batman-adv said to me, after some chat and replies, that this issue could be
> solved asking in the openwrt forum, because they didn't know how to solve
> the problem.
>
> The problem happens when i build the openwrt image to use in my routers (i'm
> trying to build a batman-adv mesh network), the definitions of batman-adv
> protocol don't start when the routers boot, as i wish.
>
> In /etc/config/ there are some configuration files, like dhcp, network,
> wireless, etc... and the file that i'm talking about is the "batman-adv"
> file configuration.
> In that "batman-adv" file we can define if this specific router is a gateway
> server or client... if the visualization mode is server or client... etc...
>
> After my definitions are saved and after rebooting the routers, the
> definitions don't start as i defined, but starts as defined by default...
>
> It is necessary to do "batman-adv restart" to the changes take place...
> All i want is the definitions start on boot and permanently...
> Why after saving the parameters and rebooting the router, the batman-adv
> changes don't take effect?
>
>
> This is the batman-adv configuration example for 1 of the routers:
>
> config 'mesh' 'bat0'
>            option 'interfaces' 'wifi'
>            option 'aggregated_ogms' '1'
>            option 'ap_isolation' '0'
>            option 'bonding' '0'
>            option 'fragmentation' '1'
>            option 'gw_bandwidth' '5mbit/1024kbit'
>            option 'gw_mode' 'server'
>            #option 'gw_sel_class'
>            option 'log_level' 'all'
>            option 'orig_interval' '1000'
>            option 'vis_mode' 'server'
>
>
> When the router boots the definitions don't take effect, but after doing
> "batman-adv", everything works fine.
>
> I know the issue "batman-adv" is not a issue to be discussed here, but i was
> thinking if the problem could be solved by changing something in the build
> process... (?)
>
>
>
> Thank you very much.
>
> I'm a portuguese student in telecomunications eletrotecnical engineering, in
> ISEP school-Oporto.
> This about my final work for my master thesis.
> I need some help.
>
> Best regards.
> Pedro Rodrigues
> ___
> 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] [PATCH] Update tinc init script with new variable names

[ZioPRoTo (Saverio Proto)]

I applied your patch
https://dev.openwrt.org/changeset/31837

Saverio

2012/5/17 Moritz Warning :
> On 05/17/2012 09:56 AM, ZioPRoTo (Saverio Proto) wrote:
>> Hello,
>>
>> please can you resend to me the patch as attachment ? my email client
>> mangled the patch.
>>
>> I will review it today. thanks
>>
>> Saverio
>>
>>
>> 2012/5/17 Moritz Warning :
>>> The tinc init script needs to know all valid options used in /etc/conf/tinc.
>>> This patch updates that list to tinc 0.18 (current version).
>>>
>>> Signed-off-by: Moritz Warning 
>>>
>>> ---
> [..]
>
> See attachment.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Update tinc init script with new variable names

[ZioPRoTo (Saverio Proto)]

Hello,

please can you resend to me the patch as attachment ? my email client
mangled the patch.

I will review it today. thanks

Saverio


2012/5/17 Moritz Warning :
> The tinc init script needs to know all valid options used in /etc/conf/tinc.
> This patch updates that list to tinc 0.18 (current version).
>
> Signed-off-by: Moritz Warning 
>
> ---
>
> Index: net/tinc/files/tinc.init
> ===
> --- net/tinc/files/tinc.init    (revision 31761)
> +++ net/tinc/files/tinc.init    (working copy)
> @@ -98,11 +98,12 @@
>
>        # append flags
>        append_conf_bools "$s" "$TMP_TINC/$n/hosts/$s" \
> -               ClampMSS IndirectData PMTUDiscovery
> +               ClampMSS IndirectData PMTUDiscovery TCPOnly
>
>        # append params
>        append_conf_params "$s" "$TMP_TINC/$n/hosts/$s" \
> -               Address Cipher Compression Digest MACLength PMTU Port Subnet
> +               Address Cipher Compression Digest MACLength PMTU \
> +               Port PublicKey PublicKeyFile Subnet
>  }
>
>  check_gen_own_key() {
> @@ -139,17 +140,20 @@
>
>        # append flags
>        append_conf_bools "$s" "$TMP_TINC/$s/tinc.conf" \
> -               DirectOnly Hostnames IffOneQueue PriorityInheritance \
> -               StrictSubnets TunnelServer \
> -               ClampMSS IndirectData PMTUDiscovery
> +               DecrementTTL DirectOnly Hostnames IffOneQueue \
> +               LocalDiscovery PriorityInheritance StrictSubnets TunnelServer 
> \
> +               ClampMSS IndirectData PMTUDiscovery TCPOnly
>
>        # append params
>        append_conf_params "$s" "$TMP_TINC/$s/tinc.conf" \
> -               AddressFamily BindToAddress ConnectTo BindToInterface \
> -               Forwarding GraphDumpFile Interface KeyExpire MACExpire \
> -               MaxTimeout Mode Name PingInterval PingTimeout PrivateKeyFile \
> -               ProcessPriority ReplayWindow UDPRcvBuf UDPSndBuf \
> -               Address Cipher Compression Digest MACLength PMTU Port Subnet
> +               AddressFamily BindToAddress BindToInterface \
> +               Broadcast ConnectTo Device DeviceType Forwarding \
> +               GraphDumpFile Interface KeyExpire MACExpire \
> +               MaxTimeout Mode Name PingInterval PingTimeout \
> +               PrivateKey PrivateKeyFile ProcessPriority ReplayWindow \
> +               UDPRcvBuf UDPSndBuf \
> +               Address Cipher Compression Digest MACLength PMTU \
> +               Port PublicKey PublicKeyFile Subnet
>
>        check_gen_own_key "$s" && return 0
>  }
> ___
> 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] bug in selecting packages in the backfire buildroot

[ZioPRoTo (Saverio Proto)]

I found the following bug in the Backfire buildroot:

If package X is in a submenu, if it exist another package Y that
requires X, than X is not represented anymore in the submenu but at
the same hierarchy of this parent. Note that Y must exist and do not
need to be selected.

Because of this the subfolder of the plugins of the olsrd-package is
broken. As soon as you select olsrd, all the plugins will appear in
the list and _not_ in a subfolder.

This package has this behaviour:
https://dev.openwrt.org/browser/packages/net/olsrd

This package is identical,but with a different name, so not being
referenced by other packages it will not suffer from this bug.
https://github.com/ninuxorg/ninux-openwrt-packages/tree/stablepackages/olsrd-ninux

How can we fix this ?

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

Re: [OpenWrt-Devel] checkout backfire with git

[ZioPRoTo (Saverio Proto)]

> Nice! The era of git-svn is finished :D

it is actually started from my point of view :)

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

[OpenWrt-Devel] checkout backfire with git

[ZioPRoTo (Saverio Proto)]

Hello,

I starting to work with git, maybe this link:

git://nbd.name/backfire.git

should be published here:

https://dev.openwrt.org/wiki/GetSource

I don't have rights to edit this wiki :)

thanks

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

[OpenWrt-Devel] dev.openwrt.org 504 Gateway Time-out

[ZioPRoTo (Saverio Proto)]

Hello,

from about 16 hours now I cannot browse smoothly dev.openwrt.org ..

most of the time I get

504 Gateway Time-out

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

Re: [OpenWrt-Devel] mini_snmpd uci network interfaces support

[ZioPRoTo (Saverio Proto)]

Hello Nico,

I tested and reworked Gioacchino's mini_snmpd patch to support uci
interfaces names instead of real interface names.

please check and commit. I would commit myself but I do not have
permission for that folder

ciao :)

Saverio


mini_snmpd.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] olsrd init file in OpenWRT

[ZioPRoTo (Saverio Proto)]

Hello Nico,

i just applied a patch submitted by Manuel Munz.

https://dev.openwrt.org/changeset/29134

I tested this stuff in the last 24 hours and it works to me.

In the same time I was testing you updated the init.d file... I solved
the conflict ignoring your changes.

Using start-stop-daemon is as good as using service_stop and service_start ?

thanks

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

Re: [OpenWrt-Devel] olsrd package 200-txtinfo_gateways_formatting.patch

[ZioPRoTo (Saverio Proto)]

> can you check if you can add that patch? It includes improvements for
> 6and4 operation and also for syetup of smartgw. I'm running olsrd 0.6.1
> with this patch for about half a year now and it works as expected here.
> It should apply clean to the init file because nothing was changed there
> as far as i can see for 0.6.2.
>
> http://wgaugsburg.de/trac/export/452/kamikaze/contrib/imagebuilder/trunk/patches/backfire/302-olsrd.init_6and4-patches_and_smartgw.patch
>

Hello,

I flashed a olsrd.ipkg with this patch in my production system.

give me a couple of days for testing and the I will commit it into svn.

thanks

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

Re: [OpenWrt-Devel] mini_snmpd uci network interfaces support

[ZioPRoTo (Saverio Proto)]

> config mini_snmpd
>        option enabled 1
>        option ipv6 0
>        option community public
>        option location 'Via Gallia'
>        option contact 'ziopr...@gmail.com'
>        option interfaces 'lan'
>        option interfaces 'wan'

I found my self to add more than one interface syntax looks like this:

config mini_snmpd
option enabled 1
option ipv6 0
option community public
option location 'Via Gallia'
option contact 'ziopr...@gmail.com'
option interfaces 'lan wan'

I'm testing the patch, I'll come soon back to you.

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

Re: [OpenWrt-Devel] mini_snmpd uci network interfaces support

[ZioPRoTo (Saverio Proto)]

I'm trying the patch Gioacchino,

so now config should look something like this ?

config mini_snmpd
option enabled 1
option ipv6 0
option community public
option location 'Via Gallia'
option contact 'ziopr...@gmail.com'
option interfaces 'lan'
option interfaces 'wan'


Saverio



2011/10/15 Gioacchino Mazzurco :
> hu sorry that was an error!
>
> that was only a rename to not conflict between my testing repository
> and packages
>
> you can fix the patch or i can fix it and send a new patch as you prefer ;)
>
> thanks!
>
> 2011/10/15 Nico :
>> Hi Gioacchino,
>>
>> Your patch will also rename mini-snmpd to eigen-mini-snmpd, which is a
>> totally unrelated change ? Why ?
>>
>> --
>> -{Nico}
>>
>>
>> On Sat, Oct 15, 2011 at 3:50 PM, Gioacchino Mazzurco
>>  wrote:
>>> Last fixed patch ;)
>>> Please use only that and ignore the two patch before
>>>
>>> On Saturday 15 October 2011 10:39:13 Gioacchino Mazzurco wrote:
 Better patch also more openwrt styled makefile

 On Friday 14 October 2011 12:23:45 Gioacchino Mazzurco wrote:
 > I have done a patch that make mini_snmpd more uci style
 >
 > +Instead of one option with comma separated interfaces now use uci list
 > +Intestad of use only real interface name now can use also uci interface
 > name the init script check if the interface name specified is from uci
 > than traslate it to real name interface if not check if the interface
 > exist then add it if not exist print an error message and ignore the
 > interface
 >
 > suggestion are welcomed ;)
 >
 > On Friday 14 October 2011 11:04:20 you wrote:
 > > Hey all!
 > >
 > > I see that in mini_snmpd config you have to use a list of real name
 > > interfaces comma separated, that not the uci style...
 > >
 > > I am thinking to write a patch to use uci list instead of option and
 > > more over you can use uci network name also instead of real name
 > > interface only
 > >
 > > What do you thinks about that ?
>>>
>>> ___
>>> 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] OpenWRT packages, OLSRD - 910-quagga_workaround_remove.patch

[ZioPRoTo (Saverio Proto)]

Hello,

the following patch do not apply cleanly to olsrd 0.6.2

https://dev.openwrt.org/browser/packages/net/olsrd/patches/910-quagga_workaround_remove.patch

is the new version of olsrd fixing the problem so we can remove tha
patch from the OpenWRT feed, or the patch needs upgrading to compile
with the new version ?

thanks

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

[OpenWrt-Devel] olsrd package 200-txtinfo_gateways_formatting.patch

[ZioPRoTo (Saverio Proto)]

Hello,

I'm upgrading olsrd to 0.6.2

I should keep this patch ? It was introduced because the output is
parsed by some web interface ?
https://dev.openwrt.org/browser/packages/net/olsrd/patches/200-txtinfo_gateways_formatting.patch

The txtinfo plugin changed a bit in 0.6.2.

http://olsr.org/git/?p=olsrd.git;a=blob;f=lib/txtinfo/src/olsrd_txtinfo.c;h=eeb44c7912af7f018abb20a721f0fbd7f636b5a0;hb=stable

Is the new output okay so that we can remove the patch ?

Thanks

Saverio


200-txtinfo_gateways_formatting.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] DIR-601: ping latencies

[ZioPRoTo (Saverio Proto)]

Do you have qos-scripts enabled ? maybe they are not properly configured.

Saverio


2011/7/31 jerry M :
> I installed OpenWRT r.27797 on DIR-601 (hw.A1).
> All pings from LAN to WAN have very high latencies which also vary a lot.
> For example, outbound ping to www.google.com normally has latency ~15ms, but
> through OpenWRT it is 600-1300ms.
> Even ping of another host on the WAN network has latencies varying from 3ms
> to 30ms(!)
> Also many pings to google get lost.
> What may be a problem?
> How to troubleshoot?
> Jerry
> ___
> 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] [Ninux-Wireless] AR7141 e dispositivi UBNT

[ZioPRoTo (Saverio Proto)]

Hello,

at Ninux we bought a stock of new Ubiquiti Picostation m2hg and we
noticed that the radio does not work with backfire because the
processor is not anymore ar7140 rev 2 but AR7141 rev. 1 (at least this
is the only difference we spotted).

With trunk the radio works again, so we just wonder when this will be
backported to backfire to be able to use these device in our community
network with the stable firmware.

Does anybody in list can confirm our experience ?

thanks

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

[OpenWrt-Devel] TP-Link TL-WR1043ND with 16MB of RAM

[ZioPRoTo (Saverio Proto)]

Hello,

I just wanted to share that I found a version of the TP-Link
TL-WR1043ND with 16MB of RAM instead of 32MB. Watch out before buying
your router :)

I opened the case and the RAM chip is Hynix H5DU2562GTR-E3C

The version on the sticker in the outer case is v.1.0 (DE) but printed
in the inner board there is written v1.1

anyone else can confirm this version numbers ? I would like to update
the OpenWRT wiki, because this version with 16Mb of RAM is harder to
flash with sysupgrade considering you want to flash a ~7Mb image you
really have to be carefull about free RAM available.

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

[OpenWrt-Devel] please commit asap - [packages] tinc: update to 1.0.15

[ZioPRoTo (Saverio Proto)]

Hello,

following patch to Makefile updates tinc-vpn to upstream release 1.0.15.

I tested the patch and it compiles ok.

ciao,

Saverio

PS I have some issues with my svn+ssh access, looks like I cant commit
anymore :( Maybe I'm restricted only to olsrd folder ? How can I check
this out without doing stupid test commits on the repository ? thanks


Makefile.diff
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Nagios cleanup from packages/net

[ZioPRoTo (Saverio Proto)]

Hello,

I was trying to commit the following but looks like my SVN account
does not have enough privileges because I get a "Access denied".
Probably my SSH private key is good only for the olsrd package.

Here the change I was try to commit, basically just delete empty
folders from packages/net because the Nagios stuff has been moved long
time ago to packages/admin



[packages][nagios] deleting empty folders left in packages/net when
Nagios was moved to packages/admin in Changeset [26051]

D   net/nsca
D   net/nagios
D   net/nagios-plugins
D   net/nagios-plugins/patches
D   net/nrpe
D   net/nrpe/files
D   net/nrpe/patches



Please notice that the nagios-plugins will show up in the make
menuconfig only if the coreutils su has been previously selected in
the backfire branch.

This was fixed for trunk but backport for backfire would be appreciated
https://dev.openwrt.org/ticket/8943

ciao :)

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

Re: [OpenWrt-Devel] [Discussion] Device-specific configuration and firmware file wikipage

[ZioPRoTo (Saverio Proto)]

It is here:
http://wiki.openwrt.org/toh/start

Saverio

2011/4/28 Sven Bachmann :
> Hi there,
>
> I couldn't find an info on the web if this was already discussed, but
> does there exist a simple database (read: table in the wiki) which
> describes what target (AR7, BRCM...) to select for a specific device
> (Linksys WAG354G, ...) and which is the correct firmware file
> (openwrt-WA7A-jffs2-64k-code.bin) to flash this to the device?
>
> I don't talk about the wiki pages directly for the device which are full
> with developer information - what I mean is a short oneliner for
> beginners who just want to compile OpenWrt from trunk and maybe later
> dig a bit deeper into this stuff.
>
> An entry in the table could maybe look like this:
>
>  - Device:   Linksys WAG354G Version 2
>  - Variant:  DSL Annex B (mainly Germany)
>  - Target:   TI AR7
>  - Firmware: openwrt-WA7B-jffs2-64k-code.bin
>  - Flashing: scripts/flashing/flash.sh [Firmware] linksys
>
> If there doesn't exist such a database, would there be any interest to
> setup such a thing in the wiki?
>
> Bye
>  Sven
> ___
> 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] NetworkManager or connman?

[ZioPRoTo (Saverio Proto)]

> So the question - does anyone work on it already? Any results?

read from here:
http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg08779.html

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

Re: [OpenWrt-Devel] How to recognize if a default route is active

[ZioPRoTo (Saverio Proto)]

> I have however a designed issue. At the moment a bash daemon periodically
> checks if the wan interface is up. If the check is positive then the mesh
> daemon
> advertise this gateway, otherwise the mesh interface is set as default
> route.

in the OLSR routing protocol implementation, we have a dynamic gateway
plugin. It checks (with policy routing) if connectivity with the
Internet is actually working, before the router advertises a default
route.

you might want to check out the code on olsr.org

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

Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team

[ZioPRoTo (Saverio Proto)]

> I would like to suggest that everyone joins -devel on irc this next
> sunday at 19:00 UTC to discuss the topic.

IRC meetings are good, but I think what is missing in this community
is some meetup face to face. I think when people know each other
directly then is much easier to understand each other via email.

 Of course I don't claim this should be often, because I would be
impossible, we come from the all world. But I think it would be good
for example to have a face to face meeting of OpenWRT developers this
summer, maybe at the CCC Camping ? What you think ? :)

Ciao :)

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

Re: [OpenWrt-Devel] [PATCH] Initial Board Support for Aztech HW550-3G (Ralink rt3052, ramips)

[ZioPRoTo (Saverio Proto)]

> I do not understand: "we found this stuff:
> https://github.com/ago/openwrt";, "support to ralink, worthed to take a
> look ?".
>
> I have not tested theese patches. I have enabled my working copy of
> openwrt to support USB on ramips targets using DWC_OTG driver 2.72a
> 24-JUN-2008 avaliable in some vendor "gpl" sources.

ok. Sorry for misunderstanding

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

Re: [OpenWrt-Devel] [PATCH] Initial Board Support for Aztech HW550-3G (Ralink rt3052, ramips)

[ZioPRoTo (Saverio Proto)]

>> This patch adds initial support for the Aztech HW550-3G (Ralink RT3052f SoC,
>> 8MB flash, 32MB dram).  Ethernet is not working yet.  Wireless appears to
>> work fine.  USB does not work yet (as with other Ralink boards).

At Ninux we found this stuff:
https://github.com/ago/openwrt

USB patches for OpenWRT support to ralink, worthed to take a look ?

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

Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions

[ZioPRoTo (Saverio Proto)]

> The source tree is tagged. LuCI is tagged. But "packages" apparently isn't.

this thing of having packages feed tagged comes back from time to time.

in my opinion is that the developers community of OpenWRT has no
interest in keeping a tagged packages tree.

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

Re: [OpenWrt-Devel] [Ninux-Wireless] ath9k gsoc 2011

[ZioPRoTo (Saverio Proto)]

> I have found this http://wireless.kernel.org/en/developers/GSoC/2011/
> on ath9k page, i see that there isn't  ideas posted, is it a good idea
> to fix ad-hoc + ap VAP combination on ath9k for google summer of code?

Gioacchino post it here:
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

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

Re: [OpenWrt-Devel] 6to4 as a secondary tunnel

[ZioPRoTo (Saverio Proto)]

>>> Can I assume openwrt supports multiple routing tables?
>>
>> do you mean if OpenWRT supports to configure multiple routing tables
>> with the UCI schemas ?
>
> Yes. Or, if it does not, what could the best way to support this
> particular case.

I'm also interested in knowing this :)
Right now I have everything scripted in /etc/rc.local when there is
something that I don't know how to setup with UCI.

Also, I have no idea where to go find proper backfire documentation
for this kind of things.
here: http://wiki.openwrt.org/doc/uci/network#ipv4.routes
multiple routing tables are not mentioned

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

Re: [OpenWrt-Devel] 6to4 as a secondary tunnel

[ZioPRoTo (Saverio Proto)]

> Can I assume openwrt supports multiple routing tables?

do you mean if OpenWRT supports to configure multiple routing tables
with the UCI schemas ?

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

Re: [OpenWrt-Devel] Wireless Battle Mesh v4 (16-20 March 2011, Sant Bartomeu del Grau, Spain)

[ZioPRoTo (Saverio Proto)]

> I would really like to go - would there be interest in adding an
> adhoc-springtime-openwrt-developer meeting.
> I visited Guifi.net a few years ago, and it is a wonderful area with
> wonderful people.

even "user" meeting would be cool :) Because a lot of developers will
be there we can organize workshops on OpenWRT best practices for
users.
Something like, "what you always wanted to ask but you were to lazy to
write a too long email" :)

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

[OpenWrt-Devel] Announcing the Wireless Battle Mesh v4 (16-20 March 2011, Sant Bartomeu del Grau, Spain)

[ZioPRoTo (Saverio Proto)]

==
   Announcing the Wireless Battle Mesh v4
(16-20 March 2011, Sant Bartomeu del Grau, Spain)
==

The next 'Wireless Battle of the Mesh' will take place from
Wed 16th till Sun 20th of March in Sant Bartomeu del Grau
(80km far from Barcelona), Spain. The event aims to
bring together people from across Europe to test the
performance of different routing protocols for ad-hoc
networks, like Babel, B.A.T.M.A.N., BMX, and OLSR.

If you are a mesh networking enthusiast, community
networking activist, or have an interest in mesh networks
you have to check this out!

Informations about the event are gathered at:
http://battlemesh.org/BattleMeshV4

Location


The event will take place in the Can Roca turistic resort
in Sant Bartomeu del Grau, Catalunya, in the pre-Pyrenees
Lluçanès area, 80 km far from Barcelona.

Registration


Registrations will be available at different hackerspaces
(Fusolab, HSBXL, /tmp/lab, metalab, CCC, ...) and on the
official website for the event at
http://battlemesh.org/BattleMeshV4

Fees


Every participant needs to donate 50 EUR (this should cover
the costs for accomodation , and the infrastructure). To
finance this event, we ask you to pay when subscribing
(bank transfer or cash).

Contact
===

* Web: http://battlemesh.org/BattleMeshV4
* Email: wbmv4_aatt_exo_dot_cat
* IRC: irc.freenode.net #battlemesh
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] iptables hashlimit in backfire

[ZioPRoTo (Saverio Proto)]

>> any reason why this patch is not included in Backfire 10.03.1 ?
>
> Nobody demanded a backport yet.

At Ninux we are using hashlimit, and many times we recompile backfire
instead of using snapshots because we need that patch.

Backporting would be appreciated :)

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

[OpenWrt-Devel] iptables hashlimit in backfire

[ZioPRoTo (Saverio Proto)]

https://dev.openwrt.org/attachment/ticket/6696/tmp.diff

any reason why this patch is not included in Backfire 10.03.1 ?

I'm using this patch compiling my firmware on the backfire branch, all
seems working good.

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

Re: [OpenWrt-Devel] Target: UML fails to build on 64bit Host

[ZioPRoTo (Saverio Proto)]

Are you compiling trunk ?

Make sure this patch is in your build:
https://dev.openwrt.org/browser/trunk/target/linux/uml/patches-2.6.34/002-gcc4_unfortify_source.patch

I had problem before with UML and 64bit machines (I was not using
trunk), when I backported this patch everything went ok

Saverio



2010/12/4 Robert Wuttke :
> Hi,
>
> I am trying to build OpenWrt as User Mode Linux on a 64bit machine.
> The build fails with the following message:
>
> Do you have any suggestions on how to proceed? On a 32bit machine, the
> build is successful.
>
> i486-openwrt-linux-uclibc-gcc -c libc/sysdeps/linux/x86_64/crt1.S -o
> lib/crt1.o -include ./include/libc-symbols.h -Wall -Wstrict-prototypes
> -fno-strict-aliasing -O2 -pipe -march=i486 -funit-at-a-time -fhonour-
> copts -fno-stack-protector -fno-builtin -nostdinc -I./include -I.
> -I./libc/sysdeps/linux/x86_64 -fno-asm -DUCLIBC_INTERNAL -Os
> -funit-at-a-time -fno-tree-loop-optimize -fno-tree-dominator-opts
> -fno-strength-re duce
> -I./libpthread/linuxthreads.old/sysdeps/unix/sysv/linux/x86_64
> -I./libpthread/linuxthreads.old/sysdeps/x86_64
> -I./libpthread/linuxthreads.old/sysdeps/unix/sysv/linux
> -I./libpthread/linuxthreads.old/sysdep s/pthread
> -I./libpthread/linuxthreads.old -I./libpthread
> -I/home/builder/backfire/uml/build_dir/toolchain-i386_gcc-4.1.2_uClibc-0.9.30.1/linux-dev/usr/include/
> -I/home/builder/backfire/uml/staging_dir/toolchai
> n-i386_gcc-4.1.2_uClibc-0.9.30.1/usr/lib/gcc/i486-openwrt-linux-uclibc/4.1.2//include-fixed
> -I/home/builder/backfire/uml/staging_dir/toolchain-i386_gcc-4.1.2_uClibc-0.9.30.1/usr/lib/gcc/i486-openwrt-linux-ucli
> bc/4.1.2/include -DNDEBUG -MT lib/crt1.o -MD -MP -MF lib/.crt1.o.dep
> -D__ASSEMBLER__ -Wa,--noexecstack -DL_crt1
> libc/sysdeps/linux/x86_64/crt1.S: Assembler messages:
> libc/sysdeps/linux/x86_64/crt1.S:96: Error: bad register name `%rdx'
> libc/sysdeps/linux/x86_64/crt1.S:97: Error: bad register name `%rsi'
> libc/sysdeps/linux/x86_64/crt1.S:98: Error: bad register name `%rsp'
> libc/sysdeps/linux/x86_64/crt1.S:101: Error: bad register name `%rsp'
> libc/sysdeps/linux/x86_64/crt1.S:103: Error: bad register name `%rax'
> libc/sysdeps/linux/x86_64/crt1.S:107: Error: bad register name `%rsp'
> libc/sysdeps/linux/x86_64/crt1.S:121: Error: bad register name `%rdi'
> libc/sysdeps/linux/x86_64/crt1.S:124: Error: bad register name `%rcx'
> libc/sysdeps/linux/x86_64/crt1.S:125: Error: bad register name `%r8'
> make[4]: *** [lib/crt1.o] Error 1
>
>
> --
>
> Robert
> ___
> 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] Adding platforms as packages

[ZioPRoTo (Saverio Proto)]

> I'm thinking it would be nice to have a "macro" package that selects a
> platform, boot format, packages on that platform, etc.
>
> For instance, being able to build a target called
> "net5501-asterisk-squashfs"...  What are the steps to making this happen?

you can have a package that once selected changes your target arch ??
is this true ??

In the past I used DEPENDS to add more packages once one was selected,
and to make a package appear only for one target I used @TARGET_name

have a look here:
http://svn.ninux.org/ninuxdeveloping/browser/packages/zzz-ninux-ipkg-x86/Makefile

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

Re: [OpenWrt-Devel] Solos 4610 (conexant) adsl router, anyone?

[ZioPRoTo (Saverio Proto)]

Once you telnet into it try to type "uname -a" and see if it is Linux ! :)

Saverio


2010/7/29 Stefan Monnier :
> I inherited from a DSL modem+router whose firmware describe as a "Solos
> 4610 RD / Solos 461x CSP v1.0", and telnet shows me a big
> `conexant' banner.
>
> Does anyone know such a beast, what kind of system it might be running,
> nmap just tells me:
>
>   Device type: broadband router|WAP
>   Running: Allied Data embedded, Belkin embedded, Intracom embedded, Iskratel 
> embedded
>   OS details: Broadband router (Allied Data CopperJet 816-2P, Belkin 
> F5D7632-4, Intracom Jetspeed 500i, or Iskratel Proteus 932)
>
> which doesn't even help me figure out whether it's based on a Linux
> kernel or something else.
>
> and of course, I'd like to know whether OpenWRT might do something
> useful with it?
>
>
>        Stefan
>
> ___
> 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] [OFF] mipsel-linux-gcc

[ZioPRoTo (Saverio Proto)]

Why don't you use the OpenWRT toolchain and the OpenWRT packaging to
cross-compile ?

Saverio


2010/7/8 Airton Ishimori :
> Some problem with my Makefile ??
>
> OLSRD_PLUGIN =    true
> PLUGIN_NAME =    olsrd_test
> PLUGIN_VER =    0.1
>
> TOPDIR = ../..
> include $(TOPDIR)/Makefile.inc
>
> default_target: $(PLUGIN_FULLNAME)
>
> $(PLUGIN_FULLNAME): $(OBJS) version-script.txt
>         mipsel-linux-gcc $(LDFLAGS) -o $(PLUGIN_FULLNAME) $(OBJS) $(LIBS)
> -lc
>
> install:    $(PLUGIN_FULLNAME)
>       $(STRIP) $(PLUGIN_FULLNAME)
>       $(INSTALL_LIB)
>
> clean:
>         rm -f $(OBJS) $(SRCS:%.c=%.d) $(PLUGIN_FULLNAME)
>
>
> When I try compile occurr some problems:
>
> 
> 
>
> mipsel-linux-uclibc/bin/ld: src/test_plugin.o: Relocations in generic ELF
> (EM: 3)
> src/test_plugin.o: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make: ** [olsrd_test.so.0.1] Error 1
>
> The plugin is dinamic library for olsrd-0.6. When I use the line:
>
> $(CC) $(LDFLAGS) -o $(PLUGIN_FULLNAME) $(OBJS) $(LIBS) -lc
>
> instead of:
>
> mipsel-linux-gcc $(LDFLAGS) -o $(PLUGIN_FULLNAME) $(OBJS) $(LIBS) -lc
>
> It compile, but when I try execute olsrd -f /etc/olsrd.conf some problems
> returned how "ELF not executable MIPSEL".
> I think that this problems is because of the used compile.
>
>
> --
> Airton Ishimori
>
>
> ___
> 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] Openwrt package installation order

[ZioPRoTo (Saverio Proto)]

> I need to overwrite some configuration files, but the system overrides in
> alphabetical order.

Instead of overwriting config files that is not supported, you better
use the uci-defaults mechanism.
Put the script in /etc/uci-defaults/some-name and do the required uci stuff.
It will be evaluated once at firstboot and removed afterwards.
This way your specific config is set up on the first boot of the
router and you don't have to worry about the installation order of the
packages in the firmware.

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

Re: [OpenWrt-Devel] Public routable device behind router

[ZioPRoTo (Saverio Proto)]

> I've been trying to figure out how to setup a box behind my router (running
> Backfire) and make it publicly routable. This is needed since it is running
> services for which no properly working ALGs are available under Linux. I'm
> fairly sure there's something obvious I'm missing, so that's why I'm asking
> the experts here ;)
>
> This is a router with the WAN on a DSL connection, but with extra static IPs
> available from the provider.  The switch chip is supported by WRT, so I can
> configure VLANs and such if that's required.

I have the same setup, I have 8 public IP addresses from the provider.
I use one for the LAN port and the others are routed back to couple of
servers using Proxy Arp.

in /etc/sysctl.conf use
net.ipv4.conf.all.proxy_arp=1

and adjust your firewall.

Of course google a little bit to find the proper setup/configuration

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

Re: [OpenWrt-Devel] Package Maintainers Still Wanted

[ZioPRoTo (Saverio Proto)]

> OpenWrt is still looking for more package maintainers. A list of
> current maintainers is located at
> https://dev.openwrt.org/wiki/packages . If you are interested please
> let me know and I will get you setup.

I can volunteer to maintain the OLSR package.
Travis, I'm going to write you offlist, what do you need ? A ssh public key ?

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

[OpenWrt-Devel] OpenWRT workshops at Wireless Battle Mesh

[ZioPRoTo (Saverio Proto)]

Hello,

many of you already know about the Wireless Battle Mesh (2-6 June in Italy)

http://battlemesh.org/BattleMeshV3

Some devs from OpenWRT, like Nico, are in the organization of the event

the event has also a social character, we want to involve people in
free wireless, in community networks and so on.
We are inviting to participate Italian Linux User Groups, people
involved in variuos Free Software development and so on.
They are pretty good in using Linux envionment, but they have no idea
of what is Free Wireless.

During the BattleMesh, as side activities, we want to organize a
OpenWRT workshop for beginners (and advanced if needed).
if some OpenWRT devs are willing to come and help we would be very happy.

Is anyone in this mailing list making plans to come ? :)

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

[OpenWrt-Devel] Packaging OLSR for OpenWRT - Changes in configuration

[ZioPRoTo (Saverio Proto)]

Hello,

sorry for people receiving this email from different mailing list.

just to point out that olsr (stable) is changing a lot its
configuration file with new things/features.

UCI configuration and LuCI web interface should take care of new
configuration variable (like RtPolicy)

So next the update of the OLSR package in OpenWRT will not just be a
md5 checksum update and version number update for the new tarball.

By default now the stable branch of OLSR sets RtPolicy enabled, so by
default Policy Routing is used. Be aware ! :)

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

Re: [OpenWrt-Devel] eth1 not working in ubiquiti nanostation m

[ZioPRoTo (Saverio Proto)]

> And packets are sent by the laptop but not received by the nanostation
> according to tcpdump (attached) but they do if I use eth0 instead of eth1 to
> connect the laptop and the nanostation m5. Also I attach olsrd output with
> -d 3.

is eth1 inside the bridge ? Try without the bridge.

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

Re: [OpenWrt-Devel] libgcc on x86_64 compile problems

[ZioPRoTo (Saverio Proto)]

>> I'm trying to build OpenWrt for the UML-target on x86_64. While this works
>> fine on x86, on x86_64 machines I get the following error:

I had the same problem with UML, I fixed like this:

cd $trunk_dir$/staging_dir/toolchain-x86_64_gcc-4.1.2_uClibc-0.9.30.1/
ln -s lib lib64

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

Re: [OpenWrt-Devel] how to install erlang package?

[ZioPRoTo (Saverio Proto)]

> 1) get the erlang package
> ./scripts/feeds install erlang
> output --> WARNING! No feed for package 'erlang' found, maybe it's
> already part of the standard packages?

Hey, this are the packages you are getting with 8.09.2:
https://dev.openwrt.org/browser/branches/packages_8.09/lang

the erlang package looks to be only in trunk, so if you want to try it
on 8.09 branch you have to modify your feed.conf

so first thing to do is to modify the feeds.conf and then run
./scripts/feeds update

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

[OpenWrt-Devel] [PATCH] - IPv6 6scripts 6to4 tunnel bug fixed

[ZioPRoTo (Saverio Proto)]

The OpenWRT router was able to talk with other native IPv6 hosts (like
ipv6.google.com) because the traffic was arriving encapsulated in IPv4
packets with source $remoteip4.

But when you talk IPv6 with other 6to4 hosts the $remoteip4 is always
different. The following trivial patch fixes the problem.

Note that is was implemented like this before in here:
http://nuwiki.openwrt.org/oldwiki/IPv6_howto

Saverio



Index: 6scripts/files/6tunnel.init
===
--- 6scripts/files/6tunnel.init (revision 19228)
+++ 6scripts/files/6tunnel.init (working copy)
@@ -16,11 +16,11 @@
config_get localip6 "$section" localip6
config_get prefix "$section" prefix

-   ip tunnel add $tnlifname mode sit remote $remoteip4 local
$localip4 ttl 255
+   ip tunnel add $tnlifname mode sit remote any local $localip4 ttl 255
ifconfig $tnlifname up
ip addr add $localip6 dev $tnlifname
-   ip route add ::/0 dev $tnlifname
-   ip route add 2000::/3 dev $tnlifname
+   ip route add ::/0 via ::${remoteip4} dev $tnlifname
+   ip route add 2000::/3 via ::${remoteip4} dev $tnlifname
ip -6 addr add $prefix dev $LAN
 }
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] rsync closed ?

[ZioPRoTo (Saverio Proto)]

Is rsync at openwrt.org now closed ?

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

Re: [OpenWrt-Devel] [PATCH] dnsmasq: Fix setting the network-id for config host sections

[ZioPRoTo (Saverio Proto)]

> I applied your patch in r19069 - sorry for the delay.

I don't understand if this patch changes how to write the configuration file

For example I have some blocks like this in my /etc/config/dhcp

config host macprosaverio
option name macprosaverio
option mac 00:23:6c:99:87:be
option ip 192.168.69.10

is this syntax still going to work ? Or now instead of name we should
use networkid ?

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

[OpenWrt-Devel] UML target patches and x86_64 in the 8.09 branch

[ZioPRoTo (Saverio Proto)]

Hello Nico,

I'm still testing some UML stuff, I understand now why I was not able
to compile the 8.09.1 tag on my x86_64 host.

I was able to compile trunk because there is patch from trunk:
https://dev.openwrt.org/browser/trunk/target/linux/uml/patches/002-gcc4_unfortify_source.patch

that patches this file:
arch/um/Makefile-x86_64

if you look at the same patch on the 8.09 branch only the Makefile for
i386 is patched:
https://dev.openwrt.org/browser/branches/8.09/target/linux/uml/patches/002-gcc4_unfortify_source.patch

Can we add support for x86_64 also in the 8.09 branch ? thanks !

Well now I know the trick and I can patch my own buildroot, but I
think that is just too bad that anybody with a new x86_64 processor is
not able to compile in UML the 8.09 branch ! (also it took me quite a
long time to understand the problem)

have a good day ! :)

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

[OpenWrt-Devel] bug in scripts/kconfig.pl ?

[ZioPRoTo (Saverio Proto)]

I think I found a bug in scripts/kconfig.pl

looks like if I use the name openwrt-8.09.1-UML for the folder where I
have my buildroot the build process dies at "make target/linux"

look here:

save...@nordkapp ~/SORGENTI/openwrt-8.09.1-UML $ make V=99
make[1]: Entering directory `/home/saverio/SORGENTI/openwrt-8.09.1-UML'
make[2]: Entering directory `/home/saverio/SORGENTI/openwrt-8.09.1-UML'
make[3]: Entering directory
`/home/saverio/SORGENTI/openwrt-8.09.1-UML/target/linux'
make[4]: Entering directory
`/home/saverio/SORGENTI/openwrt-8.09.1-UML/target/linux/uml'
/home/saverio/SORGENTI/openwrt-8.09.1-UML/scripts/kconfig.pl +
/home/saverio/SORGENTI/openwrt-8.09.1-UML/target/linux/uml/config/x86_64
> /home/saverio/SORGENTI/openwrt-8.09.1-UML/build_dir/linux-uml/linux-2.6.30.10/.config.target
Parse error at /home/saverio/SORGENTI/openwrt-8.09.1-UML/scripts/kconfig.pl
line 119,  line 124.
make[4]: *** 
[/home/saverio/SORGENTI/openwrt-8.09.1-UML/build_dir/linux-uml/linux-2.6.30.10/.configured]
Error 255
make[4]: Leaving directory
`/home/saverio/SORGENTI/openwrt-8.09.1-UML/target/linux/uml'
make[3]: *** [compile] Error 2
make[3]: Leaving directory
`/home/saverio/SORGENTI/openwrt-8.09.1-UML/target/linux'
make[2]: *** [target/linux/compile] Error 2
make[2]: Leaving directory `/home/saverio/SORGENTI/openwrt-8.09.1-UML'
make[1]: *** 
[/home/saverio/SORGENTI/openwrt-8.09.1-UML/staging_dir/x86_64/stamp/.target_compile]
Error 2
make[1]: Leaving directory `/home/saverio/SORGENTI/openwrt-8.09.1-UML'
make: *** [world] Error 2

using the name openwrt809UML without dashes (-) and dots (.) fixes this problem.

Should this be fixed or maybe we should write somewhere in the
documentation not to use dashes and dots in the directory name ?

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

Re: [OpenWrt-Devel] [PATCH] Multiple IPv6-Addresses per Interface

[ZioPRoTo (Saverio Proto)]

Alina wrote:
> I think the one IP per interface principle is a legacy thinking.

I agree with that, long time ago I opened this ticket:

https://dev.openwrt.org/ticket/2829

is was IPv4 but it was the same problem.

Bastian wrote:
> PS: see you at 26c3!

I'll also be there ! :)

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