5 Oct
2016
5 Oct
'16
6:06 p.m.
Most users expect to connect to 192.168.1.1 for the first login, as
defaults in OpenWrt and LEDE.
This should be the default also for LibreMesh in my opinion.
Can be done setting the main_ipv4_address parameter in lime-defaults
[1] to 192.168.1.1/24 instead of what we have now (10.%N1.0.0/16 where
%N1 depends on the chosen name of the AP interface and the last two
fields are chosen depending on the device mac address [2]).
Are there other ways?
Do you think that keeping the auto IPv4 assignment enabled by default
is worth the trouble?
Bye!
Ilario
[1]
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
[2] /16 seems good enough for avoiding collisions, checking the
birthday paradox [3] against a /16 range results that 300 hosts are
needed for having a 50 % probability of a collision. Neither the
possible collisions coming from the fallback mechanism for invalid
addresses [4] seem to be a problem.
[3] https://en.wikipedia.org/wiki/Birthday_problem
[4]
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
12 Oct
12 Oct
4:40 p.m.
2016-10-05 20:06 GMT+02:00 Ilario <iochesonome(a)gmail.com>om>:
Most users expect to connect to 192.168.1.1 for the
first login, as
defaults in OpenWrt and LEDE.
This should be the default also for LibreMesh in my opinion.
Are there other ways?
If 192.168.1.1 is a bad default in your opinion (I guess...?), here's
another way: suggesting the users to connect to anygw address.
But neither anygw address is easy to guess, as by default is
10.%N1.0.1 (%N1 depends on ESSID).
An user-friendly and easy to document IP would be anygw 10.0.0.1 and
we can have it replacing 10.%N1.0.0/16 with 10.%N1.0.0/8/16 in the
default configuration.
/8/16 in main_ipv4_address results in a /8 broadcast with IPv4
auto-configuration in a /16 range [1].
Would be a bad default to have a /8 routing mask?
[1]
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
13 Oct
13 Oct
12:39 a.m.
New subject: Default anygw DNS-Names (better than IPv4 192.168.1.1)
Am 12.10.16 um 18:40 schrieb Ilario:
2016-10-05 20:06 GMT+02:00 Ilario
<iochesonome(a)gmail.com>om>:
If 192.168.1.1 is a bad default in your opinion (I guess...?)
yes
An user-friendly and easy to document IP would be
anygw 10.0.0.1 and
..
Would be a bad default to have a /8 routing mask?
yes, would be bad to have /8.
a normal libremesh-mesh should be in one /16, thats needed to seperate
it to other 10.y/16 netzworks
it would be better to set nice dns hostnames! it should be easy to
program because every libremsh node has dns-server
when i look at my tplink-850RE there is written down
http://tplinkrepeater.net to acess that device. So for tplink devices a
update.path is already existing. nice specail: when your
firmware-upgrade fails and your network-settings are wrong about access
to your wifi-router you are getting "the real website" warning that your
are wrong!
within the "lime field tool" smartphone app
https://github.com/libremesh/lime-field-tools/blob/master/main.py (seems
just a testcase, but nice to HEAR the wifi-strength in db via
loudspeaker).. there is for anygw
minodo.info
so there already might be a configuration for that!? but it isnt set in
the new "stable" default libremesh version.
as i looked into different mesh firmwares (f.i. some of freifunk) many
communities have different "easy to lern" first-contact dns names. So we
should have several dns-names in libremesh to make that "first contact"
most easy!
is it possible to re-configure libremesh-dns to use several dns aliases
for its own anygw-host-IP? afterwards all communities could add their
most likely, intuitive dns-names
f.i.
http://libremesh (nice, but inside browser searching maschines may conquer)
http://libremesh.info (might be better?)
http://minodo.info (at least for backwards compatibility!)
http://tplinkrepeater.net (its written down on tplink housings!)
http://freifunk
ufo
p.s.
somewhere in the firmware there is still a /8 route, but i think thats a
mistake and of course another thread!?
root@LiMe-41cc18:/etc/config# bmx6 -cd8 | grep /8
clouds 10.0.0.0/8 8 128 20 100 960 bmxOut_LiMe-e6
10.13.0.0/16 LiMe-e6386e 10.13.0.0/16 128G 51700
62668
its on default new libremesh-firmware (stable-version)
root@LiMe-41cc18:/etc/config# cat /etc/openwrt_*
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='Chaos Calmer'
DISTRIB_REVISION='r49403'
DISTRIB_CODENAME='chaos_calmer'
DISTRIB_TARGET='ar71xx/generic'
DISTRIB_DESCRIPTION='OpenWrt Chaos Calmer 15.05.1'
DISTRIB_TAINTS='no-all mklibs busybox'
15.05.1
--
---
Freifunk Leipzig http://leipzig.freifunk.net
11:20 a.m.
New subject: Default anygw DNS-Names (better than IPv4 192.168.1.1)
2016-10-13 2:39 GMT+02:00 Ufo <ufo(a)rund.freifunk.net>et>:
Ok.
Is it a too ugly workaround to catch all packets to 10.0.0.1 via the firewall?
Is there a clean way to have an unique local management IPv4 for LiMe?
Am 12.10.16 um 18:40 schrieb Ilario:
Ok :)
2016-10-05 20:06 GMT+02:00 Ilario
<iochesonome(a)gmail.com>om>:
If 192.168.1.1 is a bad default in your opinion (I guess...?)
yes An
user-friendly and easy to document IP would be anygw 10.0.0.1 and
..
Would be a bad default to have a /8 routing mask?
yes, would be bad to have /8.
a normal libremesh-mesh should be in one /16, thats needed to seperate
it to other 10.y/16 netzworks it would be better to set nice dns hostnames! it
should be easy to
program because every libremsh node has dns-server
We already have one!
thisnode.info
It has been added some time ago [1] and documented [2].
somewhere in the firmware there is still a /8 route,
but i think thats a
mistake and of course another thread!?
root@LiMe-41cc18:/etc/config# bmx6 -cd8 | grep /8
clouds 10.0.0.0/8 8 128 20 100 960 bmxOut_LiMe-e6
10.13.0.0/16 LiMe-e6386e 10.13.0.0/16 128G 51700
62668
Ehm no idea...
Bye!
Ilario
[1]
https://github.com/libremesh/lime-packages/commit/8bcf0f2f060c16c765e8a24b2…
[2] http://libremesh.org/docs/connecting_nodes.html
3:29 p.m.
On 12/10/16 18:40, Ilario wrote:
2016-10-05 20:06 GMT+02:00 Ilario
<iochesonome(a)gmail.com>om>:
personally NAK to all of this thread :(
the %N1 is there for a reason: you need only to customize ap_name and
you'll get a reasonable random ipv4/v6 network.
we definitely want to minimize the chance of ending up with two
different ap_name having the same IP addres (10.0.0.1 or whatever)
and besides that...
there's a DNS already in place (as Ufo was asking) that is
http://thisnode.info/
so you can write thisnode.info on any browser and it will not get
confused, search engine will not conquer, and you'll get to LuCI
we even have that real domain registered to put up some content on the
internet that makes sense, like "You're trying to reach a local
libremesh node but something is wrong with your setup. Either the DNS
settings in your mobile or computer are manually configured, or you're
not actually connected to a libremesh network. Get more info about
libremesh [here]..."
The commented aliases you saw on the chef, Ufo (like minodo.info) are
just example translations if someone wants to customize additional names
for that (so that both thisnode.info and minodo.info work)
we should really document what i just wrote somewhere. probably a "quick
start guide" or something. We had that for AlterMesh at
docs.altermundi.net (spanish only). Ilario, any suggestions? :)
cheers!!
gui
Most users expect to connect to 192.168.1.1 for
the first login, as
defaults in OpenWrt and LEDE.
This should be the default also for LibreMesh in my opinion.
Are there other ways?
If 192.168.1.1 is a bad default in your opinion (I guess...?), here's
another way: suggesting the users to connect to anygw address.
But neither anygw address is easy to guess, as by default is
10.%N1.0.1 (%N1 depends on ESSID).
An user-friendly and easy to document IP would be anygw 10.0.0.1 and
we can have it replacing 10.%N1.0.0/16 with 10.%N1.0.0/8/16 in the
default configuration. /8/16 in main_ipv4_address results in a /8 broadcast
with IPv4
auto-configuration in a /16 range [1].
Would be a bad default to have a /8 routing mask?
[1]
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
17 Oct
17 Oct
11:02 a.m.
2016-10-13 17:29 GMT+02:00 Gui Iribarren <gui(a)altermundi.net>et>:
there's a DNS already in place (as Ufo was
asking) that is
http://thisnode.info/
Yep, it's also documented on the website.
See also the "Default anygw DNS-Names (better than IPv4 192.168.1.1)"
topic on this list.
Still I suggest to have a fixed management IP.
so you can write thisnode.info on any browser and it
will not get
confused, search engine will not conquer, and you'll get to LuCI
we even have that real domain registered to put up some content on the
internet that makes sense, like "You're trying to reach a local
libremesh node but something is wrong with your setup. Either the DNS
settings in your mobile or computer are manually configured, or you're
not actually connected to a libremesh network. Get more info about
libremesh [here]..."
That's great!
we should really document what i just wrote somewhere.
probably a "quick
start guide" or something. We had that for AlterMesh at
docs.altermundi.net (spanish only). Ilario, any suggestions? :)
A "quick start guide" is a good idea!!! :D (maybe even multilingual?)
It could replace the "Overview" of the "Documentation" section in the
web (which now contains just a duplicated "The Web Presence" (to be
merged in the equivalent subsection of Development section) and
"Presentations and Documents" which can be moved in "How it works").
So, let's create it on:
https://github.com/libremesh/lime-web/blob/master/docs/quick_starting_guide…
which will appear on:
http://libremesh.org/docs/quick_starting_guide.html
contributions on this list or via github pull requests are welcome!
18 Oct
18 Oct
2:06 a.m.
Is this thread related to my continued difficulty connecting to stable
builds (http://downloads.libremesh.org/community_chaos/)? I just
reflashed and I'm still not able to connect over wifi or ethernet unless
I use the failsafe or custom network connection profile method.
Until a long term solution/IP is agreed on, what is the short term fix
so that any device can connect without those hacks?
On 10/17/2016 06:02 AM, Ilario wrote:
2016-10-13 17:29 GMT+02:00 Gui Iribarren
<gui(a)altermundi.net>et>:
there's a DNS already in place (as Ufo was
asking) that is
http://thisnode.info/
Yep, it's also documented on the website.
See also the "Default anygw DNS-Names (better than IPv4 192.168.1.1)"
topic on this list.
Still I suggest to have a fixed management IP.
so you can write thisnode.info on any browser and
it will not get
confused, search engine will not conquer, and you'll get to LuCI
we even have that real domain registered to put up some content on the
internet that makes sense, like "You're trying to reach a local
libremesh node but something is wrong with your setup. Either the DNS
settings in your mobile or computer are manually configured, or you're
not actually connected to a libremesh network. Get more info about
libremesh [here]..."
That's great!
we should really document what i just wrote
somewhere. probably a "quick
start guide" or something. We had that for AlterMesh at
docs.altermundi.net (spanish only). Ilario, any suggestions? :)
A "quick
start guide" is a good idea!!! :D (maybe even multilingual?)
It could replace the "Overview" of the "Documentation" section in
the
web (which now contains just a duplicated "The Web Presence" (to be
merged in the equivalent subsection of Development section) and
"Presentations and Documents" which can be moved in "How it works").
So, let's create it on:
https://github.com/libremesh/lime-web/blob/master/docs/quick_starting_guide…
which will appear on:
http://libremesh.org/docs/quick_starting_guide.html
contributions on this list or via github pull requests are welcome!
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
2986
days inactive
2999
days old
6 comments
4 participants
participants (4)
-
Gui Iribarren -
Ilario -
Marvin Arnold -
Ufo