-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Maybe this can be of some use to us... it would also be an excuse to
interact with the Commotion guys.
cheers,
Nico
- -------- Original Message --------
Date: Wed, 29 May 2013 10:03:56 -0400
From: Dan Staples <danstaples(a)opentechinstitute.org>
To: nodogsplash(a)ml.ninux.org
Subject: [Nodogsplash] LuCI page for configuring Nodogsplash
Hi all,
As part of another project, I created an OpenWRT LuCI page for
configuring Nodogsplash (similar to luci-app-splash). It lets the
administrator set leasetime, which interfaces/zones to captive portal,
whitelist and blacklist MACs, whitelist IP ranges, and set the splash
page text. It's certainly not all the Nodogsplash options, but enough
for a simple setup.
The Nodogsplash default splash page I include also uses a simple
javascript redirect to point to a LuCI-created splash page, which allows
you to use your router's web interface theme and include LuCI
headers/footers and whatnot on the splash page.
Just wanted to throw it out there in case it would be of use to anyone.
The source is here: https://github.com/opentechinstitute/commotion-splash
I would love feedback on it if anyone has any. I also haven't tried it
on vanilla Attitude Adjustment, I've only used it as part of the
Commotion OpenWRT-based firmware. So the one caveat is that it depends
on a small lua file being present in /usr/lib/lua/, which can be found
here:
https://github.com/opentechinstitute/luci-commotion/blob/master/luasrc/comm…
cheers,
Dan
- --
Dan Staples
Open Technology Institute
https://commotionwireless.net
_______________________________________________
Nodogsplash mailing list
Nodogsplash(a)ml.ninux.org
http://ml.ninux.org/mailman/listinfo/nodogsplash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRpi7dAAoJEPHORz17N0TFOKYIANRQuLr74RU+H0rtXa26KInh
cWOLlrYLi6sjB02NFL1kID7C2pVaWV+F/oYghTs//Z9PZM1EwmqP3OZwm4mB4Vni
EWxN8Ol+Mlf2XVJkntAlSNEShzNFrt9VDt6dz1+eJ43Pwy21IYFdJ1wfXpKvkRQ5
/UkajGkAKk5Pl2jAy7r3WBwIUh74KlpyklEQvQlkbWdTZk1SezErci2HbTGo5VLz
MI69cYtoHNLcDH8ChHQAooTCnTH3OgWEte2t6ZMZBcz03hFpV91PIb+HlKBBtLpS
zrZWDctHal5hoKP37wv582nLPWClr9onc+AtAHs7UTESNI5798xf+5B/S3qjOR4=
=qqdW
-----END PGP SIGNATURE-----
In eigennet firmware we really didn't have a build system, so have an autconfig
script inside the device make a lot of sense, but in libre-mesh we have lime-
build and chef, so were we put the limit between autobuild and autoconfig ?
Autoconfig works well on simple devices like picostation or nanostation, but on
more complex setup like the black tplink is not the good approach, so i was
thinking about completely moving to a build + profile system without or with
minimal autoconfig script on the device
what do you think about that ?
Hi Pau and SAn,
during the brainstorming sessions that gave birth to libre-mesh we
talked about integrating qmpfw and the firmware Chef.
Pau and SAn are the guys behind the development of these tools, maybe it
would be interesting to start coordinating how this can be actually
implemented?
Cheers,
Nico.
I saw that it depends on libpcap, it is the only way to listen for icmp
messages?
In this case i think it is not the case to use icmp protocol and instad would
be simpler and more performant just a simple udp multicast socket like bmx6 do
I have talked today with antonio (ordex) and really what they call backbon is
not the common sense of backbone, so we should add a vlan on top of ethernet
interfaces where client are accepted too if we want batman-adv to route traffic
accross ethernet too
Is p4u receiving mail from the mailing list or there is some problem ?
---------- Forwarded Message ----------
Subject: News in libremesh
Date: Wednesday 15 May 2013, 00:06:01
From: Pau <hakais(a)gmail.com>
To: NicoEchániz <nicoechaniz(a)altermundi.net>, Gioacchino Mazzurco
<gio(a)eigenlab.org>, Gui Iribarren <gui(a)altermundi.net>
Hi.
We are currently using the the repositories created in github. I see
Gio added the package for cracking the ath9k regdomain.
I added a dummy package named lime-system with some basic dependences.
If you clone the repository lime-build and type "make T=tl-703n J=2",
it should compile the system with the lime-system enabled and the
dependences.
For the moment only the targets tl-703n and tl-wdr4300 are supported,
but it is just a mather of adding the config files in the
configs/directory
To create them execute
- make T=NEW_TARGET menuconfig
- find the resulting config file in build/configs/NEW_TARGET
- diffconfig it with build/ar71xx/scripts/diffconfig (yes, it should
be added to the Makefile to do it automatically, please volunteeers!!)
- save it to configs/NEW_TARGET
Following this approach we can have kind of useful diferent profiles
for each target. So, some software can fit in devices such as wdr4300
and not in 703n.
I also have been thinking about the network architecture modes (NAM).
I think we should implement some of them and let the administrator
choose (can be different for each community).
- bmx6 + bat-adv in all nodes
- bat-adv in all nodes and bmx6 in the borders (autoloaded)
- bat-adv in all nodes and bmx6 only in the nodes designed by the
administrator
[1] https://github.com/libre-mesh
PS: Do we have mailing list?
--
./p4u
-----------------------------------------
