picolab in ecs360

pan · Post by **pan** » Tue Sep 07, 2021 9:57 am

Namely, in the lab:
Start PicoLab container.
(from the dock on the desktop, or command line terminal)
Code: Select all
myname@n-lab-machine:~$ picolab
The PicoLab window will open and looks the same as in your VM.

Stop the container (typically not needed, you simply close the window)
Close PicoLab window.
Code: Select all
myname@n-lab-machine:~$ picolab stop
Restart the container
Close PicoLab window.
Code: Select all
myname@n-lab-machine:~$ picolab stop
myname@n-lab-machine:~$ picolab

pan · Post by **pan** » Thu Sep 09, 2021 7:00 am

from tomas too: [quote]Re: Different hypervisor/virtualization software is used for at home use and in ECS 360 lab implementation of PicoLab - why?

KVM is native to Ubuntu, where MacOS doesn't support it and has its own hypervisor implementation.

Multipass was used for the at-home PicoLab setup because it abstracts from a specific hypervisor across platforms (mac/linux, but windows with compications).
This is not necessary on the lab machines as we know exactly what OS they are running and multipass would be an unnecessary added layer of abstraction.
So, there is no need to mention Multipass in the context of the ECS 360 lab implementation of PicoLab.
In both cases, there are two layers of virtualization where the first one is a fully fledged (KVM or other) virtual machine running Ubuntu with Docker installed in it.
Inside that VM, Docker container (lightweight virtualization for isolation and speed of startup) has the four PicoNet namespaces ...
custom namespaces h1, h2, r and the default (unnamed) namespace.
(run 'ip netns list' and 'ip netns id' in each terminal - perhaps use sudo with the commands in terminal 4)
Most significantly, in each of the four namespaces, any programs/processes running there, 'see' the different network devices and configuration as
configured by the PicoNet scripts.
(e.g. run 'ip a' in each terminal).

Re: Is terminal 4 “jovyan” inside the container running by docker or outside, but still inside VM?

As explained above, the 4th terminal shell is not configured for any custom namespace and is the PicoNet Docker container's default namespace with the network interface directly assigned to the container by Docker. In contrast, h1, h2 and r namespaces and their interfaces were created solely by the PicoNet scripts. So, that terminal provides access to the 'machine' (container) that 'hosts' the three custom namespaces. In that sense, we have a third layer of virtualization (or abstraction, at least) for network only. And h1, h2, r are the individual custom 'machines' and terminal 4 shows the 'hosting' machine for them.
For example, iptables is set up for NAT in the default network namespace, and not in the other namespaces. (try 'iptables-save' in each terminal, use sudo in 4)

Re: At terminal 4 “jovyan”, it read and write to picolab file server. How about the three namespaces (h1, h2 and r)? By default, where does it write to?

The namespaces are configured only for networking and all of the four containers are using the same storage (namespace).
(run 'df -h' in all terminals with the same result)
One significant difference in terminal 4 is that the shell is run as a regular (unprivileged) user named jovyan, while h1, h2 and r are run as the all-privileged 'root' user. So, files created in the 'root' shells will be owned by 'root', while files created by 'jovyan' in terminal 4 will be owned by that user. The 'sudo' mechanism is used here to allow 'jovyan' to run commands as root in the default namespace of the container.

File ownership - differs in terminal 4, because runs as a different user:
files created as 'root' in h1,h2,r terminals may not be readable or deletable by 'jovyan' in terminal 4 because they are owned by 'root'.
Either change the ownership to match with jovyan's files in one of the root terminals, or use one of the root shells to manipulate the 'root' owned files directly.

Permanent/ephemeral storage:
The /home/jovyan directory is owned by 'jovyan' and (on the lab machine implementation) is backed by a Docker volume, which in turn points at a directory on our department NAS (network attached storage) , (run 'df -h' in in any terminal) Thus, anything stored there is permanent and will be there next PicoLab run on any machine in the lab. For security reasons (we give root access in PicoLab!) that storage is independent of the regular department home directory mounted on the lab workstation.

Anything stored outside of that directory is saved in the container and is not permanent between sessions - fresh container is used every time you start PicoLab.

Downloads from PicoLab on the lab workstations:
Temporary files, such as captures, can be created in the /tmp directory and then copied in terminal 4 to /home/jovyan for download to the lab workstation to be examined by Wireshark. On the lab machines, such a download typically ends up in the ~/Downloads directory in your department home directory (aka H:\ drive in the Windows labs).[/quote]

pan · Post by **pan** » Thu Sep 09, 2021 9:26 am

picolab = piconet in ecs360 http://tinyurl.com/ecs360

pan · Post by **pan** » Mon Jun 06, 2022 12:03 pm

now ecs switched to uvicnet but it seems that uvicnet does not like traceroute at all ;-) so we need to check the impact on piconet in ecs360 too

$ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 142.104.68.1 0.415 ms 0.401 ms 0.391 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *

picolab · Post by **picolab** » Sun Oct 02, 2022 1:54 pm

deadwood changed to named for recursive dns lookup with dnssec: h1

Code: Select all

root@h1:/home/jovyan# nslookup
www.csc.uvic.ca.
Server:         172.16.1.1
Address:        172.16.1.1#53

Non-authoritative answer:
Name:   www.csc.uvic.ca
Address: 142.104.71.42

www.ibm.com.
Server:         172.16.1.1
Address:        172.16.1.1#53

Non-authoritative answer:
www.ibm.com     canonical name = www.ibm.com.cs186.net.
www.ibm.com.cs186.net   canonical name = outer-global-dual.ibmcom-tls12.edgekey.net.
outer-global-dual.ibmcom-tls12.edgekey.net      canonical name = e7817.dscx.akamaiedge.net.
Name:   e7817.dscx.akamaiedge.net
Address: 23.6.255.198
Name:   e7817.dscx.akamaiedge.net
Address: 2001:569:139:18c::1e89
Name:   e7817.dscx.akamaiedge.net
Address: 2001:569:139:19e::1e89

r

Code: Select all

root@r:/home/jovyan# tcpdump -n -l -i r-eth0 udp port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on r-eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
13:49:28.708598 IP 192.168.1.100.33199 > 172.16.1.1.53: 42509+ A? www.csc.uvic.ca. (33)
13:49:29.338055 IP 172.16.1.1.53 > 192.168.1.100.33199: 42509 1/0/0 A 142.104.71.42 (49)
13:49:29.338784 IP 192.168.1.100.35065 > 172.16.1.1.53: 3829+ AAAA? www.csc.uvic.ca. (33)
13:49:29.350637 IP 172.16.1.1.53 > 192.168.1.100.35065: 3829 0/1/0 (100)

13:49:45.863579 IP 192.168.1.100.44612 > 172.16.1.1.53: 9710+ A? www.ibm.com. (29)
13:49:48.122992 IP 172.16.1.1.53 > 192.168.1.100.44612: 9710 4/0/0 CNAME www.ibm.com.cs186.net., CNAME outer-global-dual.ibmcom-tls12.edgekey.net., CNAME e7817.dscx.akamaiedge.net., A 23.6.255.198 (175)
13:49:48.123687 IP 192.168.1.100.53844 > 172.16.1.1.53: 53058+ AAAA? e7817.dscx.akamaiedge.net. (43)
13:49:48.129472 IP 172.16.1.1.53 > 192.168.1.100.53844: 53058 2/0/0 AAAA 2001:569:139:18c::1e89, AAAA 2001:569:139:19e::1e89 (99)

piconet code jovyan@piconet:~$ sudo tcpdump -n -l -i host-nat udp port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on host-nat, link-type EN10MB (Ethernet), capture size 262144 bytes
13:49:28.710723 IP 172.16.1.1.52233 > 192.5.5.241.53: 40889 [1au] A? _.ca. (45)
13:49:28.714645 IP 192.5.5.241.53 > 172.16.1.1.52233: 40889-| 0/6/4 (505)
13:49:28.722271 IP 172.16.1.1.56741 > 199.4.144.2.53: 20899 [1au] A? _.uvic.ca. (50)
13:49:28.754229 IP 199.4.144.2.53 > 172.16.1.1.56741: 20899-| 0/5/1 (253)
13:49:28.819434 IP 172.16.1.1.58493 > 142.104.6.1.53: 22485 [1au] A? _.csc.uvic.ca. (54)
13:49:28.820293 IP 142.104.6.1.53 > 172.16.1.1.58493: 22485 NXDomain* 0/1/1 (123)
13:49:28.821459 IP 172.16.1.1.58044 > 199.253.250.68.53: 64910 [1au] DS? uvic.ca. (48)
13:49:28.986576 IP 199.253.250.68.53 > 172.16.1.1.58044: 64910-| 0/4/1 (424)
13:49:29.313928 IP 172.16.1.1.43625 > 198.182.167.1.53: 45730 [1au] DNSKEY? ca. (43)
13:49:29.320320 IP 198.182.167.1.53 > 172.16.1.1.43625: 45730-|$ 0/0/1 (31)
13:49:29.336082 IP 172.16.1.1.49736 > 199.7.91.13.53: 2454% [1au] AAAA? dns1.uvic.ca. (53)
13:49:29.336294 IP 172.16.1.1.35595 > 142.104.6.1.53: 59425 [1au] A? www.csc.uvic.ca. (72)
13:49:29.336689 IP 172.16.1.1.59118 > 199.7.91.13.53: 14511% [1au] AAAA? ns3.uvic.ca. (52)
13:49:29.336944 IP 172.16.1.1.52293 > 199.7.91.13.53: 35172% [1au] AAAA? dns2.uvic.ca. (53)
13:49:29.337232 IP 142.104.6.1.53 > 172.16.1.1.35595: 59425* 1/5/6 A 142.104.71.42 (265)
13:49:29.339767 IP 172.16.1.1.56175 > 142.104.6.1.53: 34321 [1au] A? _.csc.uvic.ca. (70)
13:49:29.340612 IP 142.104.6.1.53 > 172.16.1.1.56175: 34321 NXDomain* 0/1/1 (123)
13:49:29.341192 IP 172.16.1.1.43692 > 142.104.6.1.53: 65321 [1au] AAAA? www.csc.uvic.ca. (72)
13:49:29.341778 IP 142.104.6.1.53 > 172.16.1.1.43692: 65321* 0/1/1 (125)
13:49:29.357468 IP 199.7.91.13.53 > 172.16.1.1.49736: 2454- 0/6/4 (501)
13:49:29.357494 IP 199.7.91.13.53 > 172.16.1.1.52293: 35172- 0/6/4 (501)
13:49:29.358097 IP 172.16.1.1.48822 > 185.159.196.2.53: 15969% [1au] AAAA? dns2.uvic.ca. (53)
13:49:29.358097 IP 172.16.1.1.38368 > 185.159.196.2.53: 43633% [1au] AAAA? dns1.uvic.ca. (53)
13:49:29.358243 IP 199.7.91.13.53 > 172.16.1.1.59118: 14511- 0/6/4 (500)
13:49:29.358591 IP 172.16.1.1.38891 > 185.159.196.2.53: 63548% [1au] AAAA? ns3.uvic.ca. (52)
13:49:29.362995 IP 185.159.196.2.53 > 172.16.1.1.38368: 43633-| 0/5/1 (256)
13:49:29.363591 IP 185.159.196.2.53 > 172.16.1.1.48822: 15969-| 0/5/1 (256)
13:49:29.363598 IP 185.159.196.2.53 > 172.16.1.1.38891: 63548-| 0/0/1 (40)
13:49:29.371964 IP 172.16.1.1.36620 > 142.104.6.1.53: 28142% [1au] AAAA? dns1.uvic.ca. (69)
13:49:29.372602 IP 142.104.6.1.53 > 172.16.1.1.36620: 28142* 0/1/1 (114)
13:49:29.372728 IP 172.16.1.1.49288 > 142.104.6.1.53: 48433% [1au] AAAA? dns2.uvic.ca. (69)
13:49:29.373273 IP 142.104.6.1.53 > 172.16.1.1.49288: 48433* 0/1/1 (119)
13:49:29.373547 IP 172.16.1.1.53790 > 142.104.6.1.53: 23798% [1au] AAAA? ns3.uvic.ca. (68)
13:49:29.374138 IP 142.104.6.1.53 > 172.16.1.1.53790: 23798* 0/1/1 (118)

13:49:45.864936 IP 172.16.1.1.59606 > 202.12.27.33.53: 26598 [1au] A? _.com. (46)
13:49:46.011109 IP 202.12.27.33.53 > 172.16.1.1.59606: 26598-| 0/0/1 (34)
13:49:46.309319 IP 172.16.1.1.60702 > 192.48.79.30.53: 44378 [1au] A? _.ibm.com. (50)
13:49:46.367531 IP 192.48.79.30.53 > 172.16.1.1.60702: 44378-| 0/10/1 (479)
13:49:46.471893 IP 172.16.1.1.51569 > 198.41.0.4.53: 35274% [1au] A? eur5.akam.net. (54)
13:49:46.472193 IP 172.16.1.1.59202 > 198.41.0.4.53: 3947% [1au] AAAA? eur5.akam.net. (54)
13:49:46.472991 IP 172.16.1.1.37456 > 198.41.0.4.53: 44219% [1au] A? eur2.akam.net. (54)
13:49:46.473166 IP 172.16.1.1.59926 > 198.41.0.4.53: 29687% [1au] AAAA? eur2.akam.net. (54)
13:49:46.473311 IP 172.16.1.1.49196 > 198.41.0.4.53: 62589% [1au] A? usc2.akam.net. (54)
13:49:46.473454 IP 172.16.1.1.55810 > 198.41.0.4.53: 578% [1au] AAAA? usc2.akam.net. (54)
13:49:46.473611 IP 172.16.1.1.39491 > 198.41.0.4.53: 21702% [1au] A? usc3.akam.net. (54)
13:49:46.473895 IP 172.16.1.1.46391 > 198.41.0.4.53: 30548% [1au] AAAA? usc3.akam.net. (54)
13:49:46.474164 IP 172.16.1.1.60178 > 198.41.0.4.53: 523% [1au] A? usw2.akam.net. (54)
13:49:46.474433 IP 172.16.1.1.54609 > 198.41.0.4.53: 4935% [1au] AAAA? usw2.akam.net. (54)
13:49:46.478216 IP 198.41.0.4.53 > 172.16.1.1.59202: 3947-| 0/14/2 (327)
13:49:46.478434 IP 198.41.0.4.53 > 172.16.1.1.51569: 35274-| 0/14/2 (327)
13:49:46.478879 IP 198.41.0.4.53 > 172.16.1.1.59926: 29687-| 0/14/2 (327)
13:49:46.478910 IP 198.41.0.4.53 > 172.16.1.1.39491: 21702-| 0/14/2 (327)
13:49:46.479048 IP 198.41.0.4.53 > 172.16.1.1.49196: 62589-| 0/14/2 (327)
13:49:46.479621 IP 198.41.0.4.53 > 172.16.1.1.37456: 44219-| 0/14/2 (327)
13:49:46.479636 IP 198.41.0.4.53 > 172.16.1.1.55810: 578-| 0/14/2 (327)
13:49:46.480155 IP 198.41.0.4.53 > 172.16.1.1.54609: 4935-| 0/14/2 (327)
13:49:46.480285 IP 198.41.0.4.53 > 172.16.1.1.46391: 30548-| 0/14/2 (327)
13:49:46.480300 IP 198.41.0.4.53 > 172.16.1.1.60178: 523-| 0/14/2 (327)
13:49:46.492891 IP 172.16.1.1.48177 > 192.35.51.30.53: 52812% [1au] A? eur5.akam.net. (54)
13:49:46.493311 IP 172.16.1.1.57459 > 192.35.51.30.53: 21222% [1au] AAAA? eur5.akam.net. (54)
13:49:46.493518 IP 172.16.1.1.53763 > 192.35.51.30.53: 18621% [1au] A? eur2.akam.net. (54)
13:49:46.494012 IP 172.16.1.1.43993 > 192.35.51.30.53: 59616% [1au] A? usc2.akam.net. (54)
13:49:46.494327 IP 172.16.1.1.44390 > 192.35.51.30.53: 49464% [1au] A? usw2.akam.net. (54)
13:49:46.494409 IP 172.16.1.1.55548 > 192.35.51.30.53: 49629% [1au] AAAA? usc2.akam.net. (54)
13:49:46.495083 IP 172.16.1.1.57350 > 192.35.51.30.53: 62050% [1au] AAAA? eur2.akam.net. (54)
13:49:46.495662 IP 172.16.1.1.50223 > 192.35.51.30.53: 53892% [1au] A? usc3.akam.net. (54)
13:49:46.496249 IP 172.16.1.1.59688 > 192.35.51.30.53: 13476% [1au] AAAA? usc3.akam.net. (54)
13:49:46.496795 IP 172.16.1.1.34424 > 192.35.51.30.53: 35919% [1au] AAAA? usw2.akam.net. (54)
13:49:46.523517 IP 192.35.51.30.53 > 172.16.1.1.53763: 18621-| 0/15/2 (483)
13:49:46.526752 IP 192.35.51.30.53 > 172.16.1.1.44390: 49464-| 0/15/2 (483)
13:49:46.526816 IP 192.35.51.30.53 > 172.16.1.1.57350: 62050-| 0/15/2 (483)
13:49:46.527085 IP 192.35.51.30.53 > 172.16.1.1.55548: 49629-| 0/15/2 (483)
13:49:46.527339 IP 192.35.51.30.53 > 172.16.1.1.57459: 21222-| 0/15/2 (483)
13:49:46.527393 IP 192.35.51.30.53 > 172.16.1.1.48177: 52812-| 0/15/2 (483)
13:49:46.528304 IP 192.35.51.30.53 > 172.16.1.1.43993: 59616-| 0/15/2 (483)
13:49:46.528971 IP 192.35.51.30.53 > 172.16.1.1.50223: 53892-| 0/15/2 (483)
13:49:46.529045 IP 192.35.51.30.53 > 172.16.1.1.34424: 35919-| 0/15/2 (483)
13:49:46.529263 IP 192.35.51.30.53 > 172.16.1.1.59688: 13476-| 0/15/2 (483)
13:49:46.589248 IP 172.16.1.1.49802 > 184.85.248.67.53: 20186% [1au] A? eur2.akam.net. (54)
13:49:46.589469 IP 172.16.1.1.36597 > 184.85.248.67.53: 1380% [1au] A? eur5.akam.net. (54)
13:49:46.590424 IP 172.16.1.1.32785 > 23.211.133.67.53: 20300% [1au] AAAA? usc3.akam.net. (54)
13:49:46.591042 IP 172.16.1.1.55879 > 23.211.133.67.53: 8516% [1au] AAAA? eur2.akam.net. (54)
13:49:46.592449 IP 172.16.1.1.37812 > 23.211.133.67.53: 58213% [1au] AAAA? eur5.akam.net. (54)
13:49:46.593426 IP 172.16.1.1.40386 > 23.211.133.67.53: 61543% [1au] A? usc2.akam.net. (54)
13:49:46.593976 IP 172.16.1.1.38565 > 23.211.133.67.53: 53513% [1au] A? usc3.akam.net. (54)
13:49:46.594620 IP 172.16.1.1.59774 > 23.211.133.67.53: 36052% [1au] AAAA? usw2.akam.net. (54)
13:49:46.596101 IP 172.16.1.1.43514 > 23.211.133.67.53: 39010% [1au] AAAA? usc2.akam.net. (54)
13:49:46.596513 IP 172.16.1.1.56285 > 23.211.133.67.53: 59944% [1au] A? usw2.akam.net. (54)
13:49:46.740568 IP 23.211.133.67.53 > 172.16.1.1.32785: 20300- 0/1/1 (108)
13:49:46.741633 IP 23.211.133.67.53 > 172.16.1.1.55879: 8516- 0/1/1 (108)
13:49:46.742102 IP 23.211.133.67.53 > 172.16.1.1.37812: 58213- 0/1/1 (108)
13:49:46.744665 IP 23.211.133.67.53 > 172.16.1.1.59774: 36052- 0/1/1 (108)
13:49:46.747427 IP 23.211.133.67.53 > 172.16.1.1.40386: 61543- 1/0/1 A 184.26.160.64 (58)
13:49:46.748581 IP 172.16.1.1.60994 > 184.26.160.64.53: 18236 [1au] A? www.ibm.com. (52)
13:49:46.748840 IP 172.16.1.1.36620 > 184.85.248.67.53: 61207% [1au] A? asia3.akam.net. (55)
13:49:46.749011 IP 172.16.1.1.39319 > 184.85.248.67.53: 40871% [1au] AAAA? asia3.akam.net. (55)
13:49:46.752957 IP 23.211.133.67.53 > 172.16.1.1.38565: 53513- 1/0/1 A 96.7.50.64 (58)
13:49:46.756085 IP 23.211.133.67.53 > 172.16.1.1.56285: 59944- 1/0/1 A 184.26.161.64 (58)
13:49:46.759390 IP 184.85.248.67.53 > 172.16.1.1.49802: 20186- 1/0/1 A 95.100.173.64 (58)
13:49:46.791069 IP 184.85.248.67.53 > 172.16.1.1.36597: 1380- 1/0/1 A 23.74.25.64 (58)
13:49:46.793115 IP 184.26.160.64.53 > 172.16.1.1.60994: 18236- 1/0/1 CNAME www.ibm.com.cs186.net. (75)
13:49:46.793785 IP 172.16.1.1.60397 > 192.12.94.30.53: 33325 [1au] DS? ibm.com. (48)
13:49:46.799182 IP 192.12.94.30.53 > 172.16.1.1.60397: 33325-| 0/4/1 (463)
13:49:46.808412 IP 23.211.133.67.53 > 172.16.1.1.43514: 39010- 0/1/1 (108)
13:49:46.812500 IP 172.16.1.1.51356 > 192.42.93.30.53: 39130 [1au] DNSKEY? com. (44)
13:49:46.846299 IP 192.42.93.30.53 > 172.16.1.1.51356: 39130-| 2/0/1 DNSKEY, DNSKEY (486)
13:49:46.899391 IP 184.85.248.67.53 > 172.16.1.1.36620: 61207- 1/0/1 A 23.211.61.64 (59)
13:49:46.899911 IP 184.85.248.67.53 > 172.16.1.1.39319: 40871- 0/1/1 (109)
13:49:46.912099 IP 172.16.1.1.60953 > 192.55.83.30.53: 53709 [1au] A? _.cs186.net. (52)
13:49:46.964029 IP 192.55.83.30.53 > 172.16.1.1.60953: 53709-| 0/6/1 (463)
13:49:47.056781 IP 172.16.1.1.59522 > 192.52.178.30.53: 45081% [1au] A? ns.events.ihost.com. (60)
13:49:47.056968 IP 172.16.1.1.33725 > 192.52.178.30.53: 27039% [1au] AAAA? ns.events.ihost.com. (60)
13:49:47.057103 IP 172.16.1.1.44718 > 192.52.178.30.53: 27216% [1au] A? ns1.events.ihost.com. (61)
13:49:47.057212 IP 172.16.1.1.59608 > 192.52.178.30.53: 40713% [1au] AAAA? ns1.events.ihost.com. (61)
13:49:47.057359 IP 172.16.1.1.47611 > 192.52.178.30.53: 22956% [1au] A? ns2.events.ihost.com. (61)
13:49:47.057477 IP 172.16.1.1.44003 > 192.52.178.30.53: 62563% [1au] AAAA? ns2.events.ihost.com. (61)
13:49:47.103614 IP 192.52.178.30.53 > 172.16.1.1.59522: 45081-| 0/10/1 (489)
13:49:47.110061 IP 192.52.178.30.53 > 172.16.1.1.59608: 40713-| 0/10/1 (490)
13:49:47.115169 IP 192.52.178.30.53 > 172.16.1.1.47611: 22956-| 0/10/1 (490)
13:49:47.115555 IP 192.52.178.30.53 > 172.16.1.1.44718: 27216-| 0/10/1 (490)
13:49:47.115566 IP 192.52.178.30.53 > 172.16.1.1.44003: 62563-| 0/10/1 (490)
13:49:47.115569 IP 192.52.178.30.53 > 172.16.1.1.33725: 27039-| 0/10/1 (489)
13:49:47.196444 IP 172.16.1.1.57427 > 23.61.199.67.53: 41369% [1au] A? ns1-99.akam.net. (56)
13:49:47.196522 IP 172.16.1.1.46286 > 96.7.50.64.53: 41770% [1au] A? ns.events.ihost.com. (60)
13:49:47.196666 IP 172.16.1.1.45096 > 23.61.199.67.53: 28007% [1au] AAAA? ns1-99.akam.net. (56)
13:49:47.196780 IP 172.16.1.1.50645 > 23.61.199.67.53: 17760% [1au] A? ns1-206.akam.net. (57)
13:49:47.196957 IP 172.16.1.1.38197 > 23.61.199.67.53: 50247% [1au] AAAA? ns1-206.akam.net. (57)
13:49:47.207304 IP 172.16.1.1.41150 > 96.7.50.64.53: 7167% [1au] AAAA? ns.events.ihost.com. (60)
13:49:47.214521 IP 172.16.1.1.46473 > 96.7.50.64.53: 61723% [1au] AAAA? ns1.events.ihost.com. (61)
13:49:47.218857 IP 172.16.1.1.59580 > 96.7.50.64.53: 15254% [1au] A? ns2.events.ihost.com. (61)
13:49:47.219149 IP 172.16.1.1.33954 > 96.7.50.64.53: 5487% [1au] A? ns1.events.ihost.com. (61)
13:49:47.219791 IP 172.16.1.1.48104 > 96.7.50.64.53: 1997% [1au] AAAA? ns2.events.ihost.com. (61)
13:49:47.226784 IP 23.61.199.67.53 > 172.16.1.1.50645: 17760- 1/0/1 A 193.108.91.206 (61)
13:49:47.227634 IP 23.61.199.67.53 > 172.16.1.1.38197: 50247- 1/0/1 AAAA 26002::ce (73)
13:49:47.227646 IP 23.61.199.67.53 > 172.16.1.1.57427: 41369- 1/0/1 A 193.108.91.99 (60)
13:49:47.231167 IP 23.61.199.67.53 > 172.16.1.1.45096: 28007- 1/0/1 AAAA 26002::63 (72)
13:49:47.258231 IP 96.7.50.64.53 > 172.16.1.1.46286: 41770- 0/3/4 (146)
13:49:47.258743 IP 172.16.1.1.46731 > 129.42.10.200.53: 32801% [1au] A? ns.events.ihost.com. (60)
13:49:47.269423 IP 96.7.50.64.53 > 172.16.1.1.41150: 7167- 0/3/4 (146)
13:49:47.270090 IP 172.16.1.1.57837 > 129.42.10.200.53: 48759% [1au] AAAA? ns.events.ihost.com. (60)
13:49:47.276101 IP 96.7.50.64.53 > 172.16.1.1.46473: 61723- 0/3/4 (146)
13:49:47.276603 IP 172.16.1.1.45440 > 129.42.10.200.53: 1943% [1au] AAAA? ns1.events.ihost.com. (61)
13:49:47.280527 IP 96.7.50.64.53 > 172.16.1.1.59580: 15254- 0/3/4 (146)
13:49:47.280876 IP 172.16.1.1.52077 > 129.42.10.200.53: 60344% [1au] A? ns2.events.ihost.com. (61)
13:49:47.281109 IP 96.7.50.64.53 > 172.16.1.1.33954: 5487- 0/3/4 (146)
13:49:47.281283 IP 96.7.50.64.53 > 172.16.1.1.48104: 1997- 0/3/4 (146)
13:49:47.281468 IP 172.16.1.1.48582 > 129.42.10.200.53: 15722% [1au] A? ns1.events.ihost.com. (61)
13:49:47.281795 IP 172.16.1.1.49934 > 129.42.10.200.53: 40842% [1au] AAAA? ns2.events.ihost.com. (61)
13:49:47.406223 IP 129.42.10.200.53 > 172.16.1.1.46731: 32801- 1/0/1 A 129.42.3.200 (92)
13:49:47.406847 IP 172.16.1.1.33935 > 129.42.1.200.53: 32979 [1au] A? _.com.cs186.net. (56)
13:49:47.417752 IP 129.42.10.200.53 > 172.16.1.1.57837: 48759- 0/1/1 (127)
13:49:47.423690 IP 129.42.10.200.53 > 172.16.1.1.45440: 1943- 0/1/1 (124)
13:49:47.427916 IP 129.42.10.200.53 > 172.16.1.1.52077: 60344- 1/0/1 A 129.42.10.200 (93)
13:49:47.429171 IP 129.42.10.200.53 > 172.16.1.1.49934: 40842- 0/1/1 (128)
13:49:47.429185 IP 129.42.10.200.53 > 172.16.1.1.48582: 15722- 1/0/1 A 129.42.1.200 (93)
13:49:47.482212 IP 129.42.1.200.53 > 172.16.1.1.33935: 32979 NXDomain- 0/1/1 (134)
13:49:47.483008 IP 172.16.1.1.52864 > 192.31.80.30.53: 32028 [1au] DS? cs186.net. (50)
13:49:47.503799 IP 192.31.80.30.53 > 172.16.1.1.52864: 32028-| 0/4/1 (465)
13:49:47.515788 IP 172.16.1.1.47494 > 192.41.162.30.53: 22803 [1au] DNSKEY? net. (44)
13:49:47.575507 IP 192.41.162.30.53 > 172.16.1.1.47494: 22803-| 2/0/1 DNSKEY, DNSKEY (484)
13:49:47.679572 IP 172.16.1.1.37600 > 129.42.3.200.53: 61353 [1au] A? _.ibm.com.cs186.net. (60)
13:49:47.716047 IP 129.42.3.200.53 > 172.16.1.1.37600: 61353 NXDomain- 0/1/1 (138)
13:49:47.716719 IP 172.16.1.1.52698 > 129.42.3.200.53: 20404 [1au] A? www.ibm.com.cs186.net. (78)
13:49:47.752804 IP 129.42.3.200.53 > 172.16.1.1.52698: 20404- 1/0/1 CNAME outer-global-dual.ibmcom-tls12.edgekey.net. (131)
13:49:47.754478 IP 172.16.1.1.57429 > 192.43.172.30.53: 36944 [1au] A? _.edgekey.net. (54)
13:49:47.788662 IP 192.43.172.30.53 > 172.16.1.1.57429: 36944-| 0/15/2 (490)
13:49:47.858927 IP 172.16.1.1.40950 > 95.100.168.65.53: 62526 [1au] A? _.ibmcom-tls12.edgekey.net. (67)
13:49:47.884879 IP 95.100.168.65.53 > 172.16.1.1.40950: 62526 NXDomain- 0/1/1 (118)
13:49:47.886573 IP 172.16.1.1.54182 > 192.26.92.30.53: 49038 [1au] DS? edgekey.net. (52)
13:49:47.892419 IP 192.26.92.30.53 > 172.16.1.1.54182: 49038-| 0/4/1 (467)
13:49:47.906225 IP 172.16.1.1.60749 > 95.101.36.67.53: 19918% [1au] AAAA? a12-65.akam.net. (56)
13:49:47.906658 IP 172.16.1.1.43106 > 95.101.36.67.53: 5888% [1au] AAAA? a18-65.akam.net. (56)
13:49:47.906982 IP 172.16.1.1.55064 > 95.101.36.67.53: 3456% [1au] AAAA? ns4-66.akam.net. (56)
13:49:47.907151 IP 172.16.1.1.58317 > 184.26.160.65.53: 17536 [1au] A? outer-global-dual.ibmcom-tls12.edgekey.net. (83)
13:49:47.907326 IP 172.16.1.1.41731 > 95.101.36.67.53: 46967% [1au] AAAA? ns5-66.akam.net. (56)
13:49:47.907657 IP 172.16.1.1.60620 > 95.101.36.67.53: 43829% [1au] AAAA? ns7-65.akam.net. (56)
13:49:47.907913 IP 172.16.1.1.49931 > 95.101.36.67.53: 18149% [1au] AAAA? usw6.akam.net. (54)
13:49:47.908175 IP 172.16.1.1.40802 > 95.101.36.67.53: 57714% [1au] AAAA? a5-65.akam.net. (55)
13:49:47.908414 IP 172.16.1.1.50745 > 95.101.36.67.53: 4239% [1au] AAAA? a13-65.akam.net. (56)
13:49:47.908666 IP 172.16.1.1.43268 > 95.101.36.67.53: 15928% [1au] AAAA? adns1.akam.net. (55)
13:49:47.908955 IP 172.16.1.1.33999 > 95.101.36.67.53: 3476% [1au] AAAA? a28-65.akam.net. (56)
13:49:47.952047 IP 184.26.160.65.53 > 172.16.1.1.58317: 17536- 1/0/1 CNAME e7817.dscx.akamaiedge.net. (107)
13:49:47.953553 IP 172.16.1.1.48986 > 192.54.112.30.53: 31280 [1au] A? _.akamaiedge.net. (57)
13:49:47.982208 IP 95.101.36.67.53 > 172.16.1.1.55064: 3456- 0/1/1 (110)
13:49:47.982606 IP 95.101.36.67.53 > 172.16.1.1.60749: 19918- 0/1/1 (110)
13:49:47.982858 IP 95.101.36.67.53 > 172.16.1.1.43106: 5888- 0/1/1 (110)
13:49:47.983049 IP 95.101.36.67.53 > 172.16.1.1.50745: 4239- 1/0/1 AAAA 2600800::41 (72)
13:49:47.983862 IP 95.101.36.67.53 > 172.16.1.1.40802: 57714- 1/0/1 AAAA 2600b000::41 (71)
13:49:47.984087 IP 95.101.36.67.53 > 172.16.1.1.43268: 15928- 0/1/1 (109)
13:49:47.984407 IP 95.101.36.67.53 > 172.16.1.1.41731: 46967- 0/1/1 (110)
13:49:47.984458 IP 95.101.36.67.53 > 172.16.1.1.60620: 43829- 0/1/1 (110)
13:49:47.984592 IP 95.101.36.67.53 > 172.16.1.1.49931: 18149- 0/1/1 (108)
13:49:47.985483 IP 192.54.112.30.53 > 172.16.1.1.48986: 31280-| 0/15/2 (493)
13:49:47.986000 IP 95.101.36.67.53 > 172.16.1.1.33999: 3476- 0/1/1 (110)
13:49:48.052114 IP 172.16.1.1.43666 > 184.26.161.192.53: 48370 [1au] A? _.dscx.akamaiedge.net. (62)
13:49:48.088786 IP 184.26.161.192.53 > 172.16.1.1.43666: 48370- 0/8/10 (374)
13:49:48.090171 IP 172.16.1.1.47366 > 84.53.139.192.53: 12882% [1au] AAAA? n3dscx.akamaiedge.net. (62)
13:49:48.091208 IP 172.16.1.1.42024 > 84.53.139.192.53: 59841% [1au] AAAA? n7dscx.akamaiedge.net. (62)
13:49:48.091370 IP 172.16.1.1.40832 > 23.0.163.21.53: 34864 [1au] A? e7817.dscx.akamaiedge.net. (66)
13:49:48.091681 IP 172.16.1.1.36145 > 84.53.139.192.53: 52102% [1au] AAAA? n1dscx.akamaiedge.net. (62)
13:49:48.092030 IP 172.16.1.1.59383 > 84.53.139.192.53: 2180% [1au] AAAA? n2dscx.akamaiedge.net. (62)
13:49:48.092332 IP 172.16.1.1.33658 > 84.53.139.192.53: 48878% [1au] AAAA? n4dscx.akamaiedge.net. (62)
13:49:48.092607 IP 172.16.1.1.34981 > 84.53.139.192.53: 54438% [1au] AAAA? n5dscx.akamaiedge.net. (62)
13:49:48.092927 IP 172.16.1.1.36046 > 84.53.139.192.53: 55948% [1au] AAAA? n6dscx.akamaiedge.net. (62)
13:49:48.094761 IP 23.0.163.21.53 > 172.16.1.1.40832: 34864- 1/0/1 A 23.6.255.198 (70)
13:49:48.095656 IP 172.16.1.1.42455 > 192.33.14.30.53: 24788 [1au] DS? akamaiedge.net. (55)
13:49:48.109004 IP 192.33.14.30.53 > 172.16.1.1.42455: 24788-| 0/4/1 (470)
13:49:48.122701 IP 84.53.139.192.53 > 172.16.1.1.47366: 12882- 0/1/1 (116)
13:49:48.124043 IP 172.16.1.1.37790 > 184.30.149.155.53: 27230 [1au] AAAA? e7817.dscx.akamaiedge.net. (66)
13:49:48.124666 IP 84.53.139.192.53 > 172.16.1.1.42024: 59841- 0/1/1 (116)
13:49:48.124922 IP 84.53.139.192.53 > 172.16.1.1.33658: 48878- 0/1/1 (116)
13:49:48.125634 IP 84.53.139.192.53 > 172.16.1.1.36046: 55948- 0/1/1 (116)
13:49:48.125683 IP 84.53.139.192.53 > 172.16.1.1.36145: 52102- 0/1/1 (116)
13:49:48.126498 IP 84.53.139.192.53 > 172.16.1.1.59383: 2180- 0/1/1 (116)
13:49:48.127561 IP 84.53.139.192.53 > 172.16.1.1.34981: 54438- 0/1/1 (116)
13:49:48.129087 IP 184.30.149.155.53 > 172.16.1.1.37790: 27230*- 2/0/1 AAAA 2001:569:139:18c::1e89, AAAA 2001:569:139:19e::1e89 (110)[/code]

Panlab: Brewing IDEAS