- Ibr-dtn - lists.ibr.cs.tu-bs.de

Fwd: Error while bindin IBRDTN to my ethernet interface
by Francisco Cuesta 21 Feb '14

21 Feb '14

---------- Forwarded message ---------- From: Francisco Cuesta <ndarkness(a)gmail.com> Date: 2014-02-18 14:20 GMT+01:00 Subject: Re: [ibr-dtn] Error while bindin IBRDTN to my ethernet interface To: Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de> Hello Johannes, The daemon seems to be running, as it can be seen below root@OpenWrt:~# ps 13811 root 52368 S /usr/sbin/dtnd -c /tmp/ibrdtn.config The error persists, but as you said I will ignore it root@OpenWrt:~# cat /tmp/ibrdtn.err Sat Sep 10 21:46:54 2011 ERROR IPNDAgent: join failed on wlan0; 22: setsockopt() the list of packages that I have installed of IP root@OpenWrt:~# opkg list | grep ip ip - 3.3.0-1 iptables - 1.4.10-5 kmod-ipip - 3.3.8-1 kmod-ipt-conntrack - 3.3.8-1 kmod-ipt-core - 3.3.8-1 kmod-ipt-nat - 3.3.8-1 kmod-ipt-nathelper - 3.3.8-1 kmod-iptunnel4 - 3.3.8-1 libip4tc - 1.4.10-5 libip6tc - 1.4.10-5 luci-lib-ipkg - 0.11+svn9934-1 2014-02-17 15:09 GMT+01:00 Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de>: Am 17.02.2014 15:03, schrieb Francisco Cuesta: > > > > Reading the mailing-list I found this post of yours > > https://mail.ibr.cs.tu-bs.de/pipermail/ibr-dtn/2014-February/000594.html > > , there you were telling the fact that OpenWRT has some flaw with the > > IPv6 get() function, how did you check this out? And what's more, is > > there any available solution or patch to be applicable? I ask it since I > > am suffering the same kind of error I was trying to figure it out; just > > mention that I don't have IPv6 package installed on my device and I do > > have the libnl-2.0 one. > > If the IPv6 module is not loaded, you can just ignore this error. Please > test if the daemon is working even with the error. > > Kind regards, > Johannes > > -- > Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund > Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23 > Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig >

1 1

Interface failed to start (IBR-DTN v.0.10.2)
by Shyam B 17 Feb '14

17 Feb '14

Hi Sebastian, Thanks for coming to the rescue yet again. I already owe you some for the couple previous rescues;) I have two systems (One is RPi and the other is a TP-Link router). Both have the following IPs: 192.168.10.53 and 192.168.10.207 and both are able to ping each other on the network level. Therefore, I assume the problem to be on the IBR-DTN level since ad-hoc communication is set properly. When I use two RPi's or an RPi and an x64-based laptop running Ubuntu, DTN-pings like a charm. There seems to be a problem communicating between the two (Rpi and TP-Link). The DTN is running on an external pen drive on TP-Link (since, there is no space for it on the flash memory) Apparently not just one but these two errors, aka warnings (over TP-Link): ERROR TCPConvergenceLayer: bind failed (cannot bind socket with address [192.168.10.207]:4556) ERROR IPNDAgent: join failed on wlan0; 99: setsockopt() PS: Attached is the ibrdtn.conf file as seen on the TP-Link router and RPi. In my personal experience, the Rpi Ibrdtn file is unchanged for a long time and the settings work with other neighboring nodes without a problem. The problem can be/should be with TP-Link part, I believe. If I solve this, I am sure to throw a party ;) Any help is greatly appreciated. -- Best Regards, Shyam

1 0

Interface failed to start (IBR-DTN v.0.10.2)
by Shyam B 17 Feb '14

17 Feb '14

Hi, I started the DTN directly via the following command on Attitude Adjustment, OpenWRT router: *dtnd --badclock -i wlan0* The following is the message I get: Sat Feb 17 09:47:07 2014 ERROR IPNDAgent: join failed on wlan0; 99: setsockopt() Any help is appreciated on how to resolve this. I think one of my colleagues, Francesco Cuesta also posted this but we are still unable to get it to work. -- Thanks and regards, Shyam

2 1

Error while bindin IBRDTN to my ethernet interface
by Francisco Cuesta 17 Feb '14

17 Feb '14

Hello IBRDTN community, I have found a very weird behaviour when using ibrdtn-0,10.2 with OpenWRT ATTITUDE ADJUSTMENT (12.09, r36088), the behaviour is the following, each time that I wan to start the dtnd daemon I get an error when binding it to my ethernet interface. I have looked into /tmp/ibrdtn.err and I get always the error *ERROR IPNDAgent: join failed on eth0; 22: setsockopt() *independently of the interface that I use root@OpenWrt:~# tail -f /tmp/ibrdtn.err Thu Sep 8 15:49:37 2011 ERROR IPNDAgent: join failed on br-lan; 22: setsockopt() .1]:4550 Thu Sep 8 15:50:07 2011 ERROR TCPConvergenceLayer: bind failed (cannot bind socket with address [192.168.20.2]:4556) Thu Sep 8 15:50:07 2011 ERROR IPNDAgent: join failed on br-lan; 22: setsockopt() Thu Sep 8 15:52:09 2011 ERROR IPNDAgent: join failed on eth0; 22: setsockopt() .0.1]:4550 Thu Sep 8 15:53:54 2011 ERROR IPNDAgent: join failed on eth0; 22: setsockopt() Has anyone experience the same? Thanks in advance, regards My settings are > My interfaces are the following ones br-lan Link encap:Ethernet HWaddr 64:70:02:3E:A7:80 inet addr:192.168.20.2 Bcast:192.168.20.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7818 errors:0 dropped:385 overruns:0 frame:0 TX packets:6473 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:662620 (647.0 KiB) TX bytes:831077 (811.5 KiB) eth0 Link encap:Ethernet HWaddr 64:70:02:3E:A7:80 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8142 errors:0 dropped:30 overruns:0 frame:0 TX packets:6840 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:869850 (849.4 KiB) TX bytes:999198 (975.7 KiB) Interrupt:4 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8560 errors:0 dropped:0 overruns:0 frame:0 TX packets:8560 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:583341 (569.6 KiB) TX bytes:583341 (569.6 KiB) wlan0 Link encap:Ethernet HWaddr 64:70:02:3E:A7:81 inet addr:192.168.20.207 Bcast:192.168.255.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1978 errors:0 dropped:0 overruns:0 frame:0 TX packets:597 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:169824 (165.8 KiB) TX bytes:69530 (67.9 KiB) wlan1 Link encap:Ethernet HWaddr 64:70:02:3E:A7:82 inet addr:192.168.20.208 Bcast:192.168.255.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:591 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:68868 (67.2 KiB) Current ibrdtn configuration root@OpenWrt:~# cat /etc/config/ibrdtn ##################################### # IBR-DTN daemon # ##################################### config 'daemon' 'main' # The local eid of the dtn node. Default is the hostname. # option uri dtn://node.dtn # timezone offset in hours # option timezone +1 # logfile for standard output option logfile /tmp/ibrdtn.log option errfile /tmp/ibrdtn.err # debug level option debug 20 # block size limit # option blocksize 512M # option foreign_blocksize 128M # # If something bad happened, the safe mode will be activated. # These are the restrictions for safe mode only. # config 'daemon' 'safemode' option forwarding no option storage 64M option maxblock 16M # option wait_mount /dev/sda1 ##################################### # storage configuration # ##################################### config 'daemon' 'storage' # possible engines are: simple, sqlite option engine simple option blobs /tmp/ibrdtn/blobs option bundles /tmp/ibrdtn/bundles # option container /tmp/ibrdtn/container.img # option path /tmp/ibrdtn/container # option limit 1G ##################################### # routing configuration # ##################################### # # In the "default" the daemon only delivers bundles to neighbors and static # available nodes. The alternative module "epidemic" spread all bundles to # all available neighbors. # config 'daemon' 'main' # values: none | default | epidemic | flooding | prophet option routing epidemic#default option forwarding yes # option fragmentation yes # # static routing rules # - a rule is a regex pattern # - format is <target-scheme> <routing-node> # #config 'static-route' # list pattern ^dtn://[[:alpha:]].moon.dtn/[[:alpha:]] # option destination dtn://router.dtn ##################################### # static connections ##################################### #config 'static-connection' # option uri dtn://node-five.dtn # option address 10.0.0.5 # option port 4556 # option protocol tcp # option immediately yes #config 'static-connection' # option uri dtn://node-ten # option address 10.0.0.10 # option port 4556 # option protocol udp # option immediately no ##################################### # convergence layer configuration # ##################################### # # You can specify an multicast address to listen to for discovery announcements. # If no address is specified the multicast equivalent of broadcast is used. # config 'daemon' 'discovery' option address 192.168.20.255 # option timeout 5 option crosslayer yes config 'daemon' 'tcptuning' # option 'idle_timeout' 120 # option 'nodelay' yes # option 'chunksize' 4096 config 'network' option type tcp option interface eth0 option port 4556 #config 'network' # option type tcp # option interface wlan0 # option port 4556 ##################################### # bundle security protocol # ##################################### # # the level specifies the security constains # # 0 = no constrains (default) # 1 = accept only BAB authenticated bundles # 2 = accept only encrypted bundles # 3 = accept only BAB authenticated and encrypted bundles # #config 'daemon' 'security' # option level 0 # option bab_key /path/to/default-bab-key.mac # option key_path /path/to/security-keys #config 'daemon' 'tls' # option certificate /path/to/tls-cert.crt # option key /path/to/tls-key.key # option trustedpath /path/to/tls-ca # option required no # option noencryption no ##################################### # time synchronization # ##################################### #config 'daemon' 'timesync' # option reference yes # option synchronize yes # option discovery_announcement yes # option sigma 1.001 # option psi 0.9 # option sync_level 0.1 ##################################### # DHT # ##################################### config 'daemon' 'dht' option 'enabled' 'no' # option 'id' '<enter your unique id here>' option 'bootstrap' 'yes' # option 'nodesfile' '/tmp/dht_nodes.dat' option 'port' '9999' option 'enable_ipv6' 'no' # option 'enable_ipv4' 'no' # option 'bind_ipv4' '127.0.0.1' # option 'bind_ipv6' '::1' option 'ignore_neighbour_informations' 'yes' option 'allow_neighbours_to_announce_me' 'no' option 'allow_neighbour_announcement' 'no'

2 8

Re: [ibr-dtn] Problems compiling source code - please send make files
by Johannes Morgenroth 14 Feb '14

14 Feb '14

Hello Romeu. Am 12.02.2014 22:28, schrieb Romeu Monteiro: > I tried the recipes from the repository and now the code is compiling > for all the packages except ibrdtnd. > For ibrdtnd it is necessary the dependency dtndht. I got the code from > here, although I'm not sure this should be > it: https://github.com/soneyworld/dtndht/ . But we are still getting > errors: dtndht is included in the recipes for OpenWrt too: https://github.com/ibrdtn/ibrdtn/tree/release/0.10.2/recipes/openwrt Please use that one instead and start over again. But first clean your packages (make clean), because the error messages looks as the packages are compiled diffently. ibrdtnd is compile with OpenSSL and ibrdtn without. Kind regards, Johannes -- Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23 Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig

2 1

Fragmentation issue
by Theodoros Bourchas 14 Feb '14

14 Feb '14

Hi, I would like to test the fragmentation in ibr-dtn. For two nodes I did the following: I have set in /etc/config/ibrdtn # block size limit option blocksize 100K option foreign_blocksize 100K and uncommented this option config 'daemon' 'main' # values: none | default | epidemic | flooding | prophet option routing epidemic # option forwarding no option fragmentation yes I generated 1MB file and tried to send it. In the sender-daemon I received these messages Fri Feb 14 13:19:54 2014 NOTICE BundleReceivedEvent: Bundle received [0.1] dtn://host1/xYTmYAXcGdEFUpqg (local) Fri Feb 14 13:19:55 2014 NOTICE QueueBundleEvent: New bundle queued [0.1] dtn://host1/xYTmYAXcGdEFUpqg Fri Feb 14 13:19:55 2014 NOTICE BundleEvent: bundle [0.1] dtn://host1/xYTmYAXcGdEFUpqg received Fri Feb 14 13:19:55 2014 NOTICE ConnectionEvent: connection setup dtn://host3 Fri Feb 14 13:19:55 2014 NOTICE ConnectionEvent: connection up dtn://host3 Fri Feb 14 13:20:05 2014 NOTICE TransferAbortedEvent: transfer of bundle [0.1] dtn://host1/xYTmYAXcGdEFUpqg to dtn://host3 aborted. (bundle has been refused) I expected the original message to be fragmented in 10 bundles of 100K but this is not the case. Do I miss sth? Theodoros

2 1

Log daemon messages
by Theodoros Bourchas 13 Feb '14

13 Feb '14

Hi, I would like to store log messages of the ibrdtn daemon. In the configuration file (/etc/config/ibrdtn) there is the /tmp/ibrdtn.log, but only INFO type of log messages appear there. I would like to store NOTICE type of log messages as they appear , when I execute "dtnd -v" command. Is there any way to do this? Or how can I have the sequence of bundle events stored in a file? Thanks, Theodoros

2 2

Problems compiling source code - please send make files
by Romeu Monteiro 12 Feb '14

12 Feb '14

Hi, We have been trying to compile the 4 packages for IBR-DTN for OpenWrt but we have been having some problems. At this point, we managed to compile ibrcommon and ibrdtn but we are having troubles compiling ibrdtnd as the compiler fails to find the libraries (ibrcommon and ibrdtn). We get the error: "checking for ibrdtn... no configure: error: ibrdtn library not found!" We would greatly appreciate if someone who has already compiled the code in the past could send us the makefiles they used for openwrt. Perhaps that might help us. Other ideas are also welcome Thank you, Romeu

3 2

Sending big data packets with ibr-dtn
by Theodoros Bourchas 11 Feb '14

11 Feb '14

Hi all, I am trying to identify the main features of IBR-DTN overlay and what is going on beyond the basic tutorial in the website. I have initialized two nodes running in epidemic mode (change corresponding parameter in configuration file /etc/config/ibrdtn) and i tried to send a 5M file from one to another using dtninbox/dtnoutbox. So, @sender_node : 1) root@OpenWrt:~/outboxFolder# dd if=/dev/zero of=output5M bs=5M count=1 1+0 records in 1+0 records out 2) root@OpenWrt:~# dtnoutbox outboxSender outboxFolder/ dtn://host1/inboxReceiver files: output5M Killed @Receiver_node : Tue Feb 11 10:33:49 2014 WARNING BundleCore: bundle rejected: bundle has expired ([0.66] dtn://host2/outboxSender) Tue Feb 11 10:33:49 2014 WARNING TCPConnection: bundle has been rejected: bundle is expired and of course there was nothing at the inboxFolder when I typed: root@OpenWrt:/overlay# dtninbox inboxReceiver inboxFolder/ Moreover, in order to extend router's capabilities I have performed an external root and I changed the storage option in the configuration file: ##################################### # storage configuration # ##################################### config 'daemon' 'storage' # possible engines are: simple, sqlite option engine simple option blobs /tmp/ibrdtn/blobs # option bundles /tmp/ibrdtn/bundles option bundles /overlay/inboxFolder # option container /tmp/ibrdtn/container.img # option path /tmp/ibrdtn/container # option limit 1G Is there a limit in how big are the data packets? Furthermore, is there any more extended tutorial where the parameters of the configuration file and how to change them according to our needs, are explained in more detail? Thanks, Theodoros

2 7

Help with ERROR TCPConvergenceLayer: bind failed
by Romeu Monteiro 05 Feb '14

05 Feb '14

Hi, We are testing IBR-DTN for OpenWrt with 2 wireless devices, but we are getting an error we do not know how to solve. First, we did not get any errors while installing IBR-DTN. Then, we created the wi-fi channel on both devices and pinged (normal ping command) the wireless interfaces and this worked, they were communicating both ways. We then launched the daemon on these wireless interfaces (following the tutorial: https://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/ibr-dtn-tut) but we got the same error on both devices: root@VeniamWorks666:~# dtnd -i wlan2 Thu Jan 1 01:27:36 1970 INFO Configuration: Using default settings. Call with --help for options. Thu Jan 1 01:27:36 1970 INFO NativeDaemon: IBR-DTN daemon 0.10.2 (build 1d89427) Thu Jan 1 01:27:36 1970 INFO Configuration: Using default settings. Call with --help for options. Thu Jan 1 01:27:36 1970 INFO BundleCore: Local node name: dtn://VeniamWorks666 Thu Jan 1 01:27:36 1970 INFO BundleCore: Forwarding of bundles enabled. Thu Jan 1 01:27:36 1970 INFO NativeDaemon: using bundle storage in memory-only mode Thu Jan 1 01:27:36 1970 WARNING DTNTPWorker: The local clock seems to be wrong. Expiration disabled. Thu Jan 1 01:27:36 1970 INFO NativeDaemon: API initialized using tcp socket: loopback:4550 Thu Jan 1 01:27:36 1970 INFO NativeDaemon: TCP ConvergenceLayer added on wlan2:4556 Thu Jan 1 01:27:36 1970 INFO DiscoveryAgent: listen to [ff02::142]:4551 Thu Jan 1 01:27:36 1970 INFO DiscoveryAgent: listen to [224.0.0.142]:4551 Thu Jan 1 01:27:36 1970 INFO DiscoveryAgent: add interface wlan2 Thu Jan 1 01:27:36 1970 ERROR TCPConvergenceLayer: bind failed (Die addr_len war falsch oder der Socket gehrte nicht zur AF_UNIX Familie.) Thu Jan 1 01:27:36 1970 ERROR IPNDAgent: Die addr_len war falsch oder der Socket gehrte nicht zur AF_UNIX Familie. Thu Jan 1 01:27:36 1970 INFO NativeDaemon: Using default routing extens When we tried running the daemon with no interface specified we did not get this error (although we did not succeed in "dtnpinging" either). With interface eth0 there was no error, and with interface br-lan we get got the same error as above. But we must use interface wlan2 for our work, since it is connected to the wireless techonology we want to use. We are including some more details bellow about the interfaces. Can you help us please? Thank you, Romeu Monteiro and Luís Guedes, University of Aveiro, Portugal ************************** root@VeniamWorks666:~# ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br-lan state UP qlen 1000 link/ether d4:ca:6d:ae:c7:10 brd ff:ff:ff:ff:ff:ff 3: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether d4:ca:6d:ae:c7:10 brd ff:ff:ff:ff:ff:ff inet 192.168.6.66/24 brd 192.168.6.255 scope global br-lan inet6 2001:690:2380:7770:d6ca:6dff:feae:c710/64 scope global dynamic valid_lft 2584321sec preferred_lft 597121sec inet6 fdce:a4d:96d9::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::d6ca:6dff:feae:c710/64 scope link valid_lft forever preferred_lft forever 8: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000 link/ether 30:14:4a:e9:fb:8b brd ff:ff:ff:ff:ff:ff inet6 fe80::3214:4aff:fee9:fb8b/64 scope link valid_lft forever preferred_lft forever 9: wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000 link/ether 30:14:4a:e9:fb:8b brd ff:ff:ff:ff:ff:ff inet 20.0.6.66/24 brd 20.0.255.255 scope global wlan2 inet6 fe80::3214:4aff:fee9:fb8b/64 scope link valid_lft forever preferred_lft forever 10: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 32 link/ether d4:ca:6d:ae:c7:11 brd ff:ff:ff:ff:ff:ff inet 40.0.6.66/24 brd 40.0.255.255 scope global wlan0 100: 3g-3G: <POINTOPOINT,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 3 link/ppp root@VeniamWorks666:~# ifconfig br-lan Link encap:Ethernet HWaddr D4:CA:6D:AE:C7:10 inet addr:192.168.6.66 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::d6ca:6dff:feae:c710/64 Scope:Link inet6 addr: 2001:690:2380:7770:d6ca:6dff:feae:c710/64 Scope:Global inet6 addr: fdce:a4d:96d9::1/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:307359 errors:0 dropped:789 overruns:0 frame:0 TX packets:1447 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41996927 (40.0 MiB) TX bytes:197944 (193.3 KiB) eth0 Link encap:Ethernet HWaddr D4:CA:6D:AE:C7:10 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:308310 errors:0 dropped:271 overruns:9 frame:0 TX packets:1458 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:46390072 (44.2 MiB) TX bytes:198538 (193.8 KiB) Interrupt:4 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:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:448 (448.0 B) TX bytes:448 (448.0 B) wlan0 Link encap:Ethernet HWaddr D4:CA:6D:AE:C7:11 inet addr:40.0.6.66 Bcast:40.0.255.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 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:32 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan1 Link encap:Ethernet HWaddr 30:14:4A:E9:FB:8B inet6 addr: fe80::3214:4aff:fee9:fb8b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:832 (832.0 B) wlan2 Link encap:Ethernet HWaddr 30:14:4A:E9:FB:8B inet addr:20.0.6.66 Bcast:20.0.255.255 Mask:255.255.255.0 inet6 addr: fe80::3214:4aff:fee9:fb8b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:45 errors:0 dropped:0 overruns:0 frame:0 TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3642 (3.5 KiB) TX bytes:7168 (7.0 KiB)

2 6