From: Germano Massullo <germano.massullo@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] Questions arised while iplementing NetJSON
Date: Thu, 8 Oct 2015 09:25:55 +0200 [thread overview]
Message-ID: <56161A83.9060904@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
I have some questions about JSONDoc created by command <<batadv-vis
--format=jsondoc>>
In jsondoc_commented file there are a few addresses that are not shown
in ip_addr file. I commented them using
# non existing in file ip_addr
What are exactly the addresses in "clients"? What do they represent?
The procedure I followed to create the interfaces is available at [1]
Thank you for your time
[1]
https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-September/013700.html
[-- Attachment #2: ip_addr --]
[-- Type: text/plain, Size: 3306 bytes --]
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532 qdisc fq_codel master bat0 state UP group default qlen 1000
link/ether 08:00:27:83:e5:59 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.119/24 brd 192.168.1.255 scope global dynamic enp0s3
valid_lft 42000sec preferred_lft 42000sec
inet6 fdd7:4778:df22::d99/128 scope global dynamic
valid_lft 85202sec preferred_lft 85202sec
inet6 fdd7:4778:df22:0:a00:27ff:fe83:e559/64 scope global noprefixroute dynamic
valid_lft 7108sec preferred_lft 1708sec
inet6 fe80::a00:27ff:fe83:e559/64 scope link
valid_lft forever preferred_lft forever
3: bat0@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
link/ether 2a:d7:37:c6:84:fa brd ff:ff:ff:ff:ff:ff
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532 qdisc fq_codel master bat0 state UP group default qlen 1000
link/ether 08:00:27:8f:b1:c2 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.237/24 brd 192.168.1.255 scope global dynamic enp0s3
valid_lft 41678sec preferred_lft 41678sec
inet6 fdd7:4778:df22::a3d/128 scope global dynamic
valid_lft 84879sec preferred_lft 84879sec
inet6 fdd7:4778:df22:0:a00:27ff:fe8f:b1c2/64 scope global noprefixroute dynamic
valid_lft 6966sec preferred_lft 1566sec
inet6 fe80::a00:27ff:fe8f:b1c2/64 scope link
valid_lft forever preferred_lft forever
3: bat0@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
link/ether c6:84:ae:77:3e:f1 brd ff:ff:ff:ff:ff:ff
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532 qdisc fq_codel master bat0 state UP group default qlen 1000
link/ether 08:00:27:a9:8d:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.182/24 brd 192.168.1.255 scope global dynamic enp0s3
valid_lft 39217sec preferred_lft 39217sec
inet6 fdd7:4778:df22::1dd/128 scope global dynamic
valid_lft 86019sec preferred_lft 86019sec
inet6 fdd7:4778:df22:0:a00:27ff:fea9:8daf/64 scope global noprefixroute dynamic
valid_lft 6883sec preferred_lft 1483sec
inet6 fe80::a00:27ff:fea9:8daf/64 scope link
valid_lft forever preferred_lft forever
3: bat0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether a2:7f:aa:75:15:f2 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a07f:aaff:fe75:15f2/64 scope link
valid_lft forever preferred_lft forever
[-- Attachment #3: jsondoc_commented --]
[-- Type: text/plain, Size: 2162 bytes --]
{
"source_version" : "2015.1-2-g4384c2b-dirty",
"algorithm" : 4,
"vis" : [
{ "primary" : "08:00:27:8f:b1:c2", # enp0s3 2nd virtual machine
"neighbors" : [
{ "router" : "08:00:27:8f:b1:c2", # enp0s3 2nd virtual machine
"neighbor" : "08:00:27:a9:8d:af", # enp0s3 3rd virtual machine
"metric" : "1.000" },
{ "router" : "08:00:27:8f:b1:c2", # enp0s3 2nd virtual machine
"neighbor" : "08:00:27:83:e5:59", # enp0s3 1st virtual machine
"metric" : "1.000" }
],
"clients" : [
"33:33:00:00:00:01", # non existing in file ip_addr
"c6:84:ae:77:3e:f1" # bat0 2nd virtual machine
]
},
{ "primary" : "08:00:27:83:e5:59", # enp0s3 1st virtual machine
"neighbors" : [
{ "router" : "08:00:27:83:e5:59", # enp0s3 1st virtual machine
"neighbor" : "08:00:27:a9:8d:af", # enp0s3 3rd virtual machine
"metric" : "1.000" },
{ "router" : "08:00:27:83:e5:59", # enp0s3 1st virtual machine
"neighbor" : "08:00:27:8f:b1:c2", # enp0s3 2nd virtual machine
"metric" : "1.000" }
],
"clients" : [
"33:33:00:00:00:01",
"2nd:d7:37:c6:84:fa" # bat0 1st virtual machine
]
},
{ "primary" : "08:00:27:a9:8d:af", # enp0s3 3rd virtual machine
"neighbors" : [
{ "router" : "08:00:27:a9:8d:af", # enp0s3 3rd virtual machine
"neighbor" : "08:00:27:8f:b1:c2", # enp0s3 2nd virtual machine
"metric" : "1.000" },
{ "router" : "08:00:27:a9:8d:af", # enp0s3 3rd virtual machine
"neighbor" : "08:00:27:83:e5:59", # enp0s3 1st virtual machine
"metric" : "1.016" }
],
"clients" : [
"33:33:ff:75:15:f2", # non existing in file ip_addr
"33:33:00:00:00:01", # non existing in file ip_addr
"a2:7f:aa:75:15:f2", # bat0 3rd virtual machine
"01:00:5e:00:00:01" # non existing in file ip_addr
]
}
]
}
next reply other threads:[~2015-10-08 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 7:25 Germano Massullo [this message]
2015-10-08 9:07 ` [B.A.T.M.A.N.] Questions arised while iplementing NetJSON Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2015-10-05 16:39 Germano Massullo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56161A83.9060904@gmail.com \
--to=germano.massullo@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.