[Mini-NDN] Connect mini-ndn nodes to an outside network
Ashlesh Gawande (agawande)
agawande at memphis.edu
Fri Nov 18 05:13:10 PST 2016
Yes that means it is working.
a-eth2 is connected to root-eth0 (your machine).
You can ping 1.0.0.9 from your machine and see that it works.
Now you can run NFD on your machine and register routes to nodes running in Mini-NDN and to the outside world.
Ashlesh
________________________________
From: Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Friday, November 18, 2016 3:21:53 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Connect mini-ndn nodes to an outside network
Dear Ashlesh,
No Errors at the beginning of MiniNDN, and no errors in general.
However, doing "switch off and reboot" I've some improvements. The
root-eth0 is present just running ifconfig in the machine. Is it enough?
My output are:
1) MININDN
mininet> a ifconfig
a-eth0 Link encap:Ethernet HWaddr 12:b7:c7:b0:99:c7
inet addr:1.0.0.1 Bcast:1.0.0.3 Mask:255.255.255.252
inet6 addr: fe80::10b7:c7ff:feb0:99c7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1404 (1.4 KB) TX bytes:1404 (1.4 KB)
a-eth1 Link encap:Ethernet HWaddr fe:2c:28:35:26:dc
inet addr:1.0.0.5 Bcast:1.0.0.7 Mask:255.255.255.252
inet6 addr: fe80::fc2c:28ff:fe35:26dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1404 (1.4 KB) TX bytes:1404 (1.4 KB)
a-eth2 Link encap:Ethernet HWaddr 26:8e:b9:9a:ec:8a
inet addr:1.0.0.10 Bcast:1.0.0.11 Mask:255.255.255.252
inet6 addr: fe80::248e:b9ff:fe9a:ec8a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:851 (851.0 B) TX bytes:931 (931.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
------------------------------------------------------------------
------------------------------------------------------------------
2) IN THE MACHINE
ndn at ndn:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:35:af:94:4b
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:35ff:feaf:944b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25315 errors:0 dropped:0 overruns:0 frame:0
TX packets:13892 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9648263 (9.6 MB) TX bytes:1989463 (1.9 MB)
eth1 Link encap:Ethernet HWaddr 52:54:00:12:34:56
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::5054:ff:fe12:3456/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5365 errors:0 dropped:0 overruns:0 frame:0
TX packets:5399 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:769454 (769.4 KB) TX bytes:781753 (781.7 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:2278 (2.2 KB) TX bytes:2278 (2.2 KB)
root-eth0 Link encap:Ethernet HWaddr b2:6e:70:b5:4d:60
inet addr:1.0.0.9 Bcast:1.0.0.11 Mask:255.255.255.252
inet6 addr: fe80::b06e:70ff:feb5:4d60/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1190 (1.1 KB) TX bytes:1138 (1.1 KB)
Bests,
Matteo
Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:
> Are there any errors when Mini-NDN starts?
>
>
> What is the output of "a ifconfig" in Mini-NDN?
>
>
> And the output of ifconfig on the machine (not in Mini-NDN)?
>
>
> Ashlesh
>
> ________________________________
> From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
> Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
> Sent: Thursday, November 17, 2016 11:47:54 AM
> To: mini-ndn at lists.cs.ucla.edu
> Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
>
> Hello,
> I followed this doc:
> https://github.com/named-data/mini-ndn/blob/master/docs/CONNECT-TO-OUTSIDE.md
>
> Unfortunately, at this point:
>
> "Run Mini-NDN with the simple topology and issue ifconfig on the local
> machine to confirm the addition of the interface. You should be able
> to locate "root-eth0" "
>
> I am not able to see the node root neither root-eth0.
>
> Do you manage to run this scenario?
> Thanks,
> Matteo
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/d1e9c6ba/attachment.html>
More information about the Mini-NDN
mailing list