enoch/n2n
1
0
Fork 0
mirror of https://github.com/ntop/n2n.git synced 2024-09-19 16:41:11 +02:00
Code Issues Actions Packages Projects Releases 1 Wiki Activity

let auto ip feature handle several sub-networks

Browse Source
This commit is contained in:
Logan007 2020-08-18 23:27:03 +05:45
parent 78409df1c8
commit f57bb94fa5
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
community.list
View File

@ -38,28 +38,28 @@ ntop[0-1][0-9]
# fixed-name communities can optionally be followed by a network using the
# network/bitlen syntax such as the following line
#
home 192.168.1.0/24
home 192.168.168.0/24
#
# the supernode draws ip addresses to assign to the edges (if they omit the `-a`
# parameter) from this network. note that the network is delimited by [SPACE] so
# community names cannot contain a [SPACE] either.
# community names cannot contain [SPACE] either.
#
# if no network is provided here, the supernode assigns some other network to each
# community. networks are taken from the default range 10.128.0.0 - 10.255.255.0/24
# as long as no other network rane is provided through the supernode's command line
# as long as no other network range is provided through the supernode's command line
# option `-d`. those sub-networks are distinct so several edges with different
# communities can be used at the same computer (being served ip addresses from the
# same supernode). also, the networks described in this file are avoided.
# same supernode). also, the sub-networks described in this file are avoided.
#
# however, all networks assigned in this file are not checked for colliding ranges
# so different communities can use same or overlapping sub-networks. that does not
# impose a problem if the communities do not share edge nodes.
# however, all networks assigned in this file are not mutually checked for colliding
# ranges so different communities can use same or overlapping sub-networks. that does
# not impose a problem if the communities do not share edge nodes.
#
# there seems to be no sense in pre-assigning sub-networks to communities whose
# names are defined by regular expressions. those will be assigned a sub-network
# from the default range or the `-d` range.
# names are defined by regular expressions. those will be assigned distinct
# sub-networks from the default range or the `-d` range.
#
# if `-a` is used with the edge, the edge uses the ip address specified with the
# `-a xxx.xxx.xxx.xxx` option. also, the enhanced syntax `-r -a dhcp:0.0.0.0` is
# still available to serve more professional needs by a dhcp server.
# still available to have more professional needs served by a full dhcp server.
#