On 10/31/18 1:13 PM, Fernando Castro wrote:
Amazing :D
I would like each of the nodes to have ip 10.x.x.1 /
16 is it possible?
I did a test with the configuration:
option main_ipv4_address '10.% N1.0.1 / 16 '
This is already the case...
Additionally to the specific node IPv4, each node also have the anygw
address which is exactly 10.%N1.0.1
So for example your node will have both 10.13.123.123 and 10.13.0.1 (the
second one being present in all nodes).
But compiling and installing the firmware does not
start the interface
with the defined ipv4.
That's because you're defining an IPv4 which is reserved for anygw and
it gets identified as invalid in this line:
https://github.com/libremesh/lime-packages/blob/master/packages/lime-system…
We will have to add a warning in lime-config output...
Although really what I would like to do is the
following:
That all the nodes remain in a network / 24 and that each node tries the
ip 10.x.x.1 / 24 to have a better form of control, looking at the
documentation I think it can be something like:
option main_ipv4_address '10.% N1.% M5.1 / 16/24 '
I'm not sure I got what you mean, maybe something like:
option main_ipv4_address '10.%N1.%M5.1/24'
would do? Each node will be in a different subnet, but this is ok.
Please note that the autoconfiguration will happen just between 256
possible IPs, so it's quite likely to have a collision with two nodes
having the same IPv4 (probability of 50 % with 19 nodes), see
https://en.wikipedia.org/wiki/Birthday_problem
You will have to set manually the IP for each antenna in order to avoid
collisions :)
The notation that you suggested (/16/24) is not what you're looking for,
that notation means that:
1) the broadcast domain is /16, so 255.255.0.0
2) the autoconfiguration of IPv4 is restricted in the /24 network
identifier (x.y.z.0) provided.
For example:
10.13.0.0/16 (the default)
router's IPs autoconfigured in the 10.13.0.2-10.13.255.254 range
(and also anygw at 10.13.0.1)
broadcast domain /16 or 255.255.0.0
10.13.123.0/24
router's IPs autoconfigured in the 10.13.123.2-10.13.123.254 range
(and also anygw at 10.13.123.1)
broadcast domain /24 or 255.255.255.0
10.13.123.0/16/24
router's IPs autoconfigured in the 10.13.123.2-10.13.123.254 range
(and also anygw at 10.13.0.1)
broadcast domain /16 or 255.255.0.0
10.13.123.1/16
router's IPs 10.13.123.1
(and also anygw at 10.13.0.1)
broadcast domain /16 or 255.255.0.0
10.13.123.1/16/24 does not make much sense, 'cause the given address is
not a network identifier but a specific IP, and /24 gets ignored
router's IPs 10.13.123.1
(and also anygw at 10.13.0.1)
broadcast domain /16 or 255.255.0.0
10.13.0.0/16 invalid IP (network identifier), using fallback address
router's IPs 10.13.255.254
broadcast domain /16 or 255.255.0.0
(in LibreMesh 17.06 there's a bug which sets the broadcast domain to
/32 or 255.255.255.255, fixed in #301)
10.13.0.1/16 invalid IP (reserved to anygw), using fallback address
router's IPs 10.13.255.254
broadcast domain /16 or 255.255.0.0
(in LibreMesh 17.06 there's a bug which sets the broadcast domain to
/32 or 255.255.255.255, fixed in #301)
10.13.255.255/16 invalid IP (broadcast), using fallback address
router's IPs 10.13.255.254
broadcast domain /16 or 255.255.0.0
(in LibreMesh 17.06 there's a bug which sets the broadcast domain to
/32 or 255.255.255.255, fixed in #301)
Ciao!
Ilario