>From https://libremesh.org/docs/en_config.html
*The idea behind this structure is that the user only modifies
/etc/config/lime but /etc/config/lime-defaults always keeps the original
configuration.*
There is no /etc/config/lime anymore
--
Regards
Jürgen
Recorded with *Nat.app* <http://Nat.app>
My mesh consists of 3 Picostations and 4 Ape522II, all of them are
configured as originators.
1 Picostation and 2 Ape522II are connected to two different ISP routers.
Should they be configured as gateways? And if so how to do it?
Regards
Jürgen
Some more info:
The device with firmware: LiMe master development (master rev. 0e6dbe1f
20201019_1851) / LuCI openwrt-19.07 branch git-20.247.75781-0d0ab01 shows
the errors mentioned
The device with firmware: LiMe master development (master rev. 2c4b783
20201001_1200) / LuCI openwrt-19.07 branch git-20.247.75781-0d0ab01 shows
no error at all
Regards
Jürgen
Am Mi., 28. Okt. 2020 um 10:08 Uhr schrieb Juergen Kimmel <
juergenkimmel(a)gmail.com>:
> When I'm connected to this device "thisnode.info" doesn't work
> Regards
> Jürgen
>
> Am Mi., 28. Okt. 2020 um 10:03 Uhr schrieb Juergen Kimmel <
> juergenkimmel(a)gmail.com>:
>
>> Here are some excerpts from syslog which look suspicious to me:
>> Tue Oct 27 22:03:09 2020 daemon.err babeld[1491]: Warning: keyword
>> "wired" is deprecated -- please use "type" instead.
>> Tue Oct 27 22:03:09 2020 daemon.err babeld[1491]: Warning: keyword
>> "wired" is deprecated -- please use "type" instead.
>> Tue Oct 27 22:03:09 2020 daemon.err babeld[1491]: Warning: couldn't
>> determine channel of interface eth0-1_17.
>> Tue Oct 27 22:03:09 2020 user.notice mac80211: Failed command: iw phy
>> phy1 set antenna 0xffffffff 0xffffffff
>> Tue Oct 27 22:03:09 2020 daemon.notice netifd: radio1 (1153): command
>> failed: Not supported (-122)
>> Tue Oct 27 22:03:10 2020 user.notice mac80211: Failed command: iw phy
>> phy1 set distance 100
>>
>> Tue Oct 27 22:03:15 2020 user.notice ucitrack: Setting up
>> /etc/config/firewall reload dependency on /etc/config/miniupnpd
>> Tue Oct 27 22:03:15 2020 daemon.crit dnsmasq[2005]: directory
>> /tmp/resolv.conf.d/resolv.conf.auto for resolv-file is missing, cannot poll
>> Tue Oct 27 22:03:15 2020 daemon.crit dnsmasq[2005]: FAILED to start up
>> Tue Oct 27 22:03:15 2020 daemon.info procd: Instance dnsmasq::cfg01411c
>> s in a crash loop 6 crashes, 0 seconds since last crash
>>
>> Tue Oct 27 22:03:20 2020 daemon.notice procd: /etc/rc.d/S90batmand: uci:
>> Entry not found
>>
>> Tue Oct 27 22:03:21 2020 daemon.err hostapd: Using interface wlan0-ap
>> with hwaddr 7a:a3:51:16:da:89 and ssid "MarinaMalgrats"
>>
>> Tue Oct 27 22:03:22 2020 kern.warn kernel: [ 45.557225] ieee80211 phy1:
>> rt2800_config_channel: Warning - Using incomplete support for external PA
>>
>> Tue Oct 27 22:03:25 2020 daemon.err babeld[1491]: Warning: couldn't
>> determine channel of interface wlan0-mesh_17.
>>
>>
>> Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: Warning: couldn't
>> determine channel of interface wlan1-mesh_17.
>> Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: send: Address not
>> available
>> Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: send: Address not
>> available
>> Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: send: Operation not
>> permitted
>>
>> Wed Oct 28 08:32:56 2020 daemon.crit dnsmasq[3050]: directory
>> /tmp/resolv.conf.d/resolv.conf.auto for resolv-file is missing, cannot poll
>> Wed Oct 28 08:32:56 2020 daemon.crit dnsmasq[3050]: FAILED to start up
>>
>> Regards
>> Jürgen
>>
>>
>> Am Mi., 28. Okt. 2020 um 09:49 Uhr schrieb Juergen Kimmel <
>> juergenkimmel(a)gmail.com>:
>>
>>> *Juergen do you have the lime-proto-wan selected *
>>> Yes
>>>
>>> Am Di., 27. Okt. 2020 um 21:44 Uhr schrieb Daniel Golle <
>>> daniel(a)makrotopia.org>:
>>>
>>>> On Tue, Oct 27, 2020 at 05:25:32PM -0300, SAn via lime-users wrote:
>>>> > Hi!
>>>> >
>>>> > On 10/27/20 5:14 PM, Daniel Golle wrote:
>>>> > > On Mon, Oct 26, 2020 at 12:07:24PM +0100, Juergen Kimmel wrote:
>>>> > >> I learned from the config.buildinfo that firewall has not been
>>>> selected
>>>> > >> The settings of the switches are identical.
>>>> > >> May disabling the firewall have been the culprit?
>>>> > >> I flashed the same device again there is no error and client has
>>>> internet.
>>>> > >
>>>> > > Ah, of course, without any firewall installed there is also no
>>>> > > NAT / masquerading happening, so if you want that, you do need
>>>> > > something to configure that (such as OpenWrt's 'firewall' package').
>>>> >
>>>> > AFAIK we recommend in the docs to use the package
>>>> lime-hwd-openwrt-wan that selects lime-proto-wan.
>>>> > This package provides the NATing rules without the need of the
>>>> firewall package.
>>>>
>>>> It never matched my requirements and I never saw a reason not to use
>>>> OpenWrt's firewall package. I've heard some vague myths about OpenWrt's
>>>> firewall not working well with some of the routing protocols used in
>>>> libremesh, but all attempts to reproduce that or inquire what the
>>>> problem was or is remained without substancial results.
>>>> I guess there are some historic reasons for some people to still
>>>> hestitate using OpenWrt's firewall (ie. fw3 nowadays), maybe some bug
>>>> which has long been resolved or simply not (auto-)adding the rules
>>>> needed to also run routing protocols on the WAN interface (which I've
>>>> fixed some years ago).
>>>>
>>>> >
>>>> > Daniel maybe you are not using lime-proto-wan in your deploys?
>>>> Juergen do you have the lime-proto-wan selected?
>>>> > Maybe the automatic selection that is donde by lime-hwd-openwrt-wan
>>>> is not working in this device?
>>>> >
>>>> > Best!
>>>> > SAn
>>>> > _______________________________________________
>>>> > lime-users mailing list
>>>> > lime-users(a)lists.libremesh.org
>>>> > https://lists.libremesh.org/mailman/listinfo/lime-users
>>>> _______________________________________________
>>>> lime-users mailing list
>>>> lime-users(a)lists.libremesh.org
>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>
>>>
Hi SAn,
sounds ok for me ;-)
I am using Netgear ex6120 and ex6130 Adapters. they seem to be technically
the same but the 30er has in addition an power Outlet/throughput.
How is this backport fork working? Thank you!
Regards,
Andy
Am Mo., 26. Okt. 2020 um 15:06 Uhr schrieb SAn <spiccinini(a)altermundi.net>:
> Hi Andy!
>
> On 10/26/20 10:57 AM, Andy Schopf wrote:
> > Thanks for your feedback Ilario :-)
> > I think some new branch would be great, as the problem exist in a future
> openwrt release (not the actual 19.xx).
> > So it should only be corrected for the next release I think.
>
> I think that the policy should be that we always add support to
> openwrt/master (snapshots) in a backward compatible way when possible. If
> it is not possible then we ask ourselves what to do depending on the case,
> I mean, how much it will brake in each case.
>
> After the 20.09 release I think we can drop OpenWrt 18.x support and focus
> on 19.x and snapshot but prioritizing 19.x over openwrt/master (the
> rationale is to deliver the a stable experience).
>
> Andy, what device do you need that it is only in master? Some can be
> easily backported to 19.x in a local fork of openwrt. I know this have its
> pros/cons but relying in snapshots is also very unstable and time consuming.
>
>
> Best!
> SAn
>
Model ZBT-APE522II
Architecture MediaTek MT7620A ver:2 eco:6
Firmware Version LiMe master development (master rev. 0e6dbe1f
20201019_1851) / LuCI openwrt-19.07 branch git-20.247.75781-0d0ab01
Kernel Version 4.14.195
The device is connected to the ISP router and gets IP via DHCP
Ping of the network diagnostic is successful
No internet for clients
Where to look at?
--
Regards
Jürgen
What will this tell me?
[image: image.png]
I wondering I see this on a node being connected to my ISP router and
getting IP via DHCP
--
Mit freundlichen Grüssen
Jürgen Kimmel
-------- Forwarded Message --------
Subject: [gsoc-students-2019] (no subject)
Date: Mon, 26 Oct 2020 23:34:20 +0100
From: Andreas Bräu via gsoc-students-2019 <gsoc-students-2019(a)freifunk.net>
Reply-To: Andreas Bräu <ab(a)andi95.de>
To: gsoc-students-2019(a)freifunk.net
Hi there,
as we had a break this year in participating on GSoC, a new iteration
got announces now. So we can apply again and take an new chance :)
There are some important changes for next year, for details see the
forwarded mail. Management summary:
* half workload for projects
* project duration 10 weeks instead of 12 weeks
* 10 weeks can be distributed more flexible, so exams and other breaks
are possible
* less evaluation overhead
The most important impact for us is that we have to adopt our project
ideas to be smaller. I think that will also make it easier to find students.
So please take a look at https://projects.freifunk.net/#/projects and
add or edit your ideas at
https://github.com/freifunk/projects.freifunk.net-contents
If you have any questions, please ask :)
Best,
Andi
-------- Forwarded Message --------
Subject: [GSoC Mentors Announce] GSoC 2021 is on with a few chages
Date: Mon, 26 Oct 2020 14:30:19 -0700 (PDT)
From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce
List <gsoc-mentors-announce(a)googlegroups.com>
Reply-To: gsoc-mentors-announce+owners(a)googlegroups.com
To: Google Summer of Code Mentors Announce List
<gsoc-mentors-announce(a)googlegroups.com>
Hello GSoC Mentors and Org Admins,
We are pleased to announce Google Summer of Code 2021
<http://g.co/gsoc>, the 17th consecutive year of the program!
As many of you might have heard if you attended the Mentor Summit a
couple of weeks ago (or chatted with someone who did) we are making a
few changes for the 2021 program. We’ve spent a lot of time evaluating
the GSoC program and have been looking at where we can make some changes
to help meet the #1 goal of GSoC - bring new, diverse contributors into
your communities that stay in your communities after their GSoC program
ends. And with the challenges of the pandemic and the strains it has put
on everyone’s time (students, mentors and org admins alike) we are
looking to provide more flexibility in 2021.
What are the changes for 2021 from 2020?
1. *Smaller project size** - *all students participating in the 2021
program will be working on a 175 hour project (instead of a 350 hr
project). This change will also result in a few other changes
including the student stipend being cut in half.
* Currently we are missing out on many wonderful students who could
never commit to such a huge project and time commitment but would be
great contributors to your community. This is a significant change
as we now are no longer strongly encouraging students to focus only
on GSoC over their summer. Students have many other responsibilities
especially during the pandemic that make it hard for them to spend
30 hours a week on a project.
* We realize this is going to require all of you to think about
smaller projects and update your project ideas which is why we
wanted to give you 3+ months to start talking it through with your
communities.
* The mentor stipends will be adjusted to $400 per student mentored.
In feedback from the mentor summit it was pointed out that the
effort from mentors will not be half as much even though the project
size is cut in half so we adjusted from $250 to $400.
1. *Shortened coding period* - the /coding period will be 10
weeks/ with a lot more flexibility for the mentor and student to
decide together how they want to spread the work out over the
summer. Some folks may choose to stick to a 17-18 hour a week
schedule with their students, others may factor in a couple of
breaks during the program (for student and mentor) and some may have
students focus 30 hours a week on their project so they wrap up in 6
weeks. This also makes it a lot easier for students with finals or
other commitments (weddings, etc.) to adjust their schedules.
2.
*2 evaluations (instead of 3)* - There will be an evaluation after
5 weeks and the final evaluation will take place after the 10th
week. We are also no longer requiring students complete their first
evaluation (though we encourage them to do so), so if a student
doesn’t complete the first evaluation they will not automatically be
removed from the program. They are still required to complete the
final evaluation.
3.
*Eligibility requirements* - In 2020 there are many ways students
are learning and we want to acknowledge that so we will be allowing
students who are 18 years old AND currently enrolled (or accepted
into) a post-secondary academic program as of May 17, 2021 or have
graduated from a post-secondary academic program between December 1,
2020 and May 17, 2021 to apply to the GSoC program.
* What this means is that now the program will be open to folks
participating in a variety of different academic programs, not just
accredited university programs. This includes licensed coding camps,
community colleges, and many other programs that may not be
accredited yet but are post-secondary academic programs.
These changes were made to help find more diverse students who we hope
will stay involved in your communities after their GSoC ends. We look
forward to these changes and will definitely be getting feedback from
all of you as the 2021 program goes on to see what is working and what
we should consider adjusting for any possible future program.
The program announcement
<https://opensource.googleblog.com/2020/10/google-summer-of-code-2021-is-bri…>, timeline
<https://developers.google.com/open-source/gsoc/timeline>, marketing
materials
<https://developers.google.com/open-source/gsoc/resources/marketing> (slide
deck, flyers), FAQs
<https://developers.google.com/open-source/gsoc/faq>, and short videos
<https://developers.google.com/open-source/gsoc/videos> with tips for
mentors and students are all available. You'll also notice the 2020
program has now been archived
<https://summerofcode.withgoogle.com/archive/2020/organizations/>.
*Organizations* -- If you would like to apply for the 2021 program
please start thinking about the ~175 hr projects you would like students
to work on and also reach out to your community members to ask if they
would like to be mentors for the program. Having a thorough and well
thought out list of Project Ideas is the most important part of your
application.
Encourage other open source orgs to apply -- Please also consider
encouraging other open source projects to apply and be a first time GSoC
org - we’re hoping to accept more orgs in 2021 than ever before with a
good number of them being first time orgs. When orgs apply they can put
your org down as a reference.
*Please note that Org applications will open on January 29th. *
We are looking forward to another exciting year of GSoC!
For any questions about the programs please email us at
gsoc-s...(a)google.com <https://groups.google.com/>
Best,
Stephanie Taylor
GSoC Program Lead
--
You received this message because you are subscribed to the Google
Groups "Google Summer of Code Mentors Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to gsoc-mentors-announce+unsubscribe(a)googlegroups.com
<mailto:gsoc-mentors-announce+unsubscribe@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/gsoc-mentors-announce/81a3ac0c-8ab5-44f3-…
<https://groups.google.com/d/msgid/gsoc-mentors-announce/81a3ac0c-8ab5-44f3-…>.
--
gsoc-students-2019 mailing list
gsoc-students-2019(a)freifunk.net
https://lists.freifunk.net/mailman/listinfo/gsoc-students-2019-freifunk.net
