Hi,
I tested it taking into account Bruno's guide for old Nodogsplash on LiMe
[0] and the new official documentation of new Nodogsplash [1] [2]. But
could not make it work, I could access http pages without being captured by
Nodogsplash.
Perhaps it is related to a note in the documentation [3] reading "*At
the time of writing, Nodogsplash has been tested with OpenWrt 18.06.0; it
may or may not work on older versions of OpenWrt or on other kinds of
Linux-based router firmware.*"
[0]
On 17/08/18 16:12, bruno vianna wrote:
yes! let us know if it will work on lime
On Fri, Aug 17, 2018 at 6:37 AM amuza <amuza(a)riseup.net> wrote:
Hi!
Nodogsplash 3.0.0 is out.
I have not tested it yet, but I will, as it seems to do by default what
I need.
https://github.com/nodogsplash/nodogsplash/releases/tag/v3.0.0
Cheers!
On 04/04/18 19:29, bruno vianna wrote:
Https requests give an error instead of the splash page, and there is
also the problems people will face when using the
connection for apps
different than a browser.
Yes, it is annoying. But most of our users have android, which is smart
enough to detect the portal and redirect users to the login page. Even
firefox on desktops will also detect that.
I like a solution Pau mentioned on that thread:
capturing only port 80
traffic and letting everything else flow. He mentioned a modified version
of tinyproxy to do that. However I see (at least in the current Nodogsplash
version) it seems possible to do it just by editing the configuration file.
There are a few issues there- first, most of the web traffic is now on
port https (443). So someone who just uses facebook (mercy!) would never
end up in the portal.
Besides, there are apps out there built to circunvent portals by
creating VPN connections on other ports. So I don't think this is the best
solution. I don't know if there is one.
In the Nodogsplash configuration file I see
things like:
FirewallRule allow tcp port 53
Do you know what I should write in order to "Allow everything but port
80"?
I don't know the correct syntax, but I think the way to do that
something like
FirewallRule block tcp all ports
FirewallRule allow tcp port 80
As the rules are followed in the order of the file.
Let us know how it works for you!
Best
Bruno
In the meantime... here is the tutorial for the
nodogsplash hack.
Please test and let us now any problems, typos, etc.
http://wiki.coolab.org/index.php?title=How_to_create_a_captive_portal
Have fun!
On Sun, Mar 25, 2018 at 8:38 PM, <modante(a)disroot.org> wrote:
> Absolutely agree. I am not developer but could be a tester :-)
>
>
> 24 de marzo de 2018 11:08, "Patricio Gibbs"
<patricio(a)altermundi.net>
> escribió:
>
> > El 23 de marzo de 2018 7:42:17 GMT-05:00, bruno vianna <
> bruno(a)pobox.com> escribió:
>
> >
> >> Pitbull is not useful yet according to Nico Pace. We started to
> >> collaborate
> >> to develop to get it finished but it doesn't seem like it will
> happen
> >> in
> >> less than 6 months or so.
> >
> > If we write a brief description of the skills and work needed to
> create Pitbull, maybe we can
> > attract more developers. And even if we don't attract more people to
> participate, we will have a
> > clearer understanding of the work. Who can improve this first draft?:
> >
> > *The LibreMesh community will soon start working on a captive portal
> software to enable community
> > functions such as local bulletin boards and network access control.
> We call on people with Lua
> > programming experience to look at our GitHub repo at
>
https://GitHub.com/libremesh/pitbull and post
> > questions and comments there. For more read communication, visit our
> matrix chat room at -insert
> > address here-. We also call on people interested in testing the
> captive portal software as we
> > develop it.*
> >
> > Improving this call to action and distributing it among our networks
> at least opens the chance of
> > other people joining the effort... Nothing to lose.
> >
> > (I'm willing to learn more programming, but I don't I can contribute
> much in that task. Testing I
> > think I can do.)
> >
> > I think these creations, such as the captive portal, add a lot of
> value to our networks and make
> > them more attractive and more viable as real alternatives to
> non-community networks, offering tools
> > and social dynamics that non-community networks cannot offer.
> >
> >> I'll work on an English documentation of the hack this weekend and
> send
> >> it
> >> to the list, it would be great if you could test.
> >
> > Great! Our community in Caimito has wanted a captive portal since we
> started over a year ago. I
> > look forward to testing (and upgrading or nodes to libremesh 17).
> >
> > Patrick
> >
> >> Bruno
> >>
> >> On Fri, Mar 23, 2018 at 8:44 AM, Paul Harmor <psharmor(a)gmail.com>
> >> wrote:
> >>
> >>> Not that I can provide any useful information to answer the
> question
> >>> posed, but I'd sure like to see this become a reality as well!
> Think
> >>
> >> of
> >>> this as a +1!
> >>>
> >>> On Fri, Mar 23, 2018, 05:12 Amuza <amuza(a)riseup.net> wrote:
> >>
> >> Hello,
> >>
> >> Here we are considering again the captive portal thing. It would be
> >> a
> >> welcome page with some community news, not real authentication. I
> >> guess
> >> we would like a system where MAC addresses of users who just clicked
> >> an
> >> "Ok" button of the splash page would be validated for a month. So
> >> they
> >> would have to go through this News page once a month.
> >>
> >> I've seen Nodogsplash seems to be maintained again, so I can try to
> >> make
> >> it work for LiMe. But first I wanted to ask about Pitbull, as I
> >> think
> >> that was something similar but specially made for LiMe.
> >>
> >> What is the status of Pitbull?
> >>
> >> Would it work for the described need?
> >>
> >> Thank you!
> >>
> >> _______________________________________________
> >> 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
> >
> > _______________________________________________
> > 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
>
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico
▀─█▄██▄▀█▀█▄▌██─█▌█▌
_______________________________________________
lime-users mailing
listlime-users@lists.libremesh.orghttps://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
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
_______________________________________________
lime-users mailing
listlime-users@lists.libremesh.orghttps://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 ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
_______________________________________________
lime-users mailing
listlime-users@lists.libremesh.orghttps://lists.libremesh.org/mailman/listinfo/lime-users
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org