Setting Up AdGuard: DNS Redirect doesn’t work Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

I installed AdGuard Home on DietPi v7.3, Rpi 4b from the Dietpi repository. I walked through the configuration & Unbound setup. Dietpi Internet connection test works. Successfully logged into my web AdGuard setup & Dashboard from my PC.

However, redirecting to the Rpi’s address doesn’t work through the router. I.e no internet connection. Admittedly my SmartRG modem router has a confusing interface so I may not have clicked the correct options. So, I returned it to its original settings and instead changed my Win 10 pc’s ipv4 DNS to the Rpi’s address. Still no internet connection, however,

This makes me think that the configuration of the Rpi is faulty. Can someone suggest what to try next or which settings to check & how?
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

Hi,

ok let's have a look to your system and check all running services

Code: Select all

dietpi-services status
as well let's check open ports

Code: Select all

ss -tulpn | grep LISTEN
and finally let's check DNS resolution for AGH and Unbound. Replace 192.168.x.x with the IP address of your device

Code: Select all

dig 192.168.x.x -p 53 google.com
dig 127.0.0.1 -p 5335 google.com
It might be dig command did not exist. If this is the case, simply install it apt install dnsutils
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Hi, Joulinar, here's the output:

Code: Select all

DietPi-Services
─────────────────────────────────────────────────────
 Mode: status 

[  OK  ] DietPi-Services | avahi-daemon		active (running) since Thu 2021-07-01 21:03:26 BST; 1min 59s ago
[  OK  ] DietPi-Services | shairport-sync	active (running) since Thu 2021-07-01 21:03:26 BST; 1min 59s ago
[  OK  ] DietPi-Services | cron			active (running) since Thu 2021-07-01 21:03:26 BST; 1min 59s ago
[  OK  ] DietPi-Services | dropbear		active (running) since Thu 2021-07-01 21:03:25 BST; 1min 59s ago
Warning: The unit file, source configuration file or drop-ins of unbound.service changed on disk. Run 'systemctl daemon-reload' to reload units.
[  OK  ] DietPi-Services | unbound		active (running) since Thu 2021-07-01 21:03:20 BST; 2min 5s ago
[  OK  ] DietPi-Services | adguardhome		active (running) since Thu 2021-07-01 21:03:25 BST; 1min 59s ago
[ INFO ] DietPi-Services | dietpi-vpn		inactive (dead)
[  OK  ] DietPi-Services | dietpi-ramlog	active (exited) since Thu 2021-07-01 21:02:22 BST; 3min 3s ago
[  OK  ] DietPi-Services | dietpi-preboot	active (exited) since Thu 2021-07-01 21:02:22 BST; 3min 2s ago
[  OK  ] DietPi-Services | dietpi-boot		active (exited) since Thu 2021-07-01 21:03:25 BST; 1min 59s ago
[  OK  ] DietPi-Services | dietpi-postboot	active (exited) since Thu 2021-07-01 21:03:25 BST; 1min 59s ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor	inactive (dead)
====

Code: Select all

tcp     LISTEN   0        1000             0.0.0.0:22             0.0.0.0:*      users:(("dropbear",pid=970,fd=3))                                              
tcp     LISTEN   0        256            127.0.0.1:5335           0.0.0.0:*      users:(("unbound",pid=936,fd=4))                                               
tcp     LISTEN   0        5                0.0.0.0:5000           0.0.0.0:*      users:(("shairport-sync",pid=996,fd=5))                                        
tcp     LISTEN   0        4096                   *:53                   *:*      users:(("AdGuardHome",pid=964,fd=18))                                          
tcp     LISTEN   0        1000                [::]:22                [::]:*      users:(("dropbear",pid=970,fd=4))                                              
tcp     LISTEN   0        5                   [::]:5000              [::]:*      users:(("shairport-sync",pid=996,fd=7))                                        
tcp     LISTEN   0        4096                   *:8083                 *:*      users:(("AdGuardHome",pid=964,fd=16))      
====

Code: Select all

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> 192.168.1.100 -p 53 google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21922
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;192.168.1.100.			IN	A

;; AUTHORITY SECTION:
.			730	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2021070103 1800 900 604800 86400

;; Query time: 18 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jul 02 00:23:43 BST 2021
;; MSG SIZE  rcvd: 117

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58683
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		102	IN	A	172.217.164.206

;; Query time: 18 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jul 02 00:23:43 BST 2021
;; MSG SIZE  rcvd: 55
====

Code: Select all

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> 127.0.0.1 -p 5335 google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

hmm the DNS request sent to AGH (192.168.1.100) was answered by a different server (192.168.1.1). I guess this is your router. Correct?

Code: Select all

;; SERVER: 192.168.1.1#53(192.168.1.1)
Furthermore there seems to be an issue with Unbound not able to answer your DNS request at all

Code: Select all

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> 127.0.0.1 -p 5335 google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
Did you use default configuration on Unbound or was there something changed? Can you have a look to the log pls

Code: Select all

journalctl -u unbound.service
Did you restart your system after installation?

As a workaround we could deactivate Unbound within AGH settings to see if AGH would be working on it's own.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Hi Joulinar,

Yes, 192.168.1.1 is my router/modem.
Re: Unbound configuration, I think I just used the default. Log is below.
Re reboot: yes I believe I did after Unbound was installed. Also after Dig was installed. I reran the dig commands (see below Unbound Log.)

How does one deactivate Unbound?

====

Code: Select all

-- Logs begin at Thu 2019-02-14 10:11:58 GMT, end at Fri 2021-07-02 16:25:16 BST
. --
Jul 02 16:05:33 DietPi systemd[1]: Starting Unbound DNS server...
Jul 02 16:05:33 DietPi package-helper[631]: /var/lib/unbound/root.key has content
Jul 02 16:05:33 DietPi package-helper[631]: success: the anchor is ok
Jul 02 16:05:34 DietPi unbound[648]: [648:0] info: start of service (unbound 1.9.0).
Jul 02 16:05:34 DietPi systemd[1]: Started Unbound DNS server.
====

Code: Select all

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> 192.168.1.100 -p 53 google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2016
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;192.168.1.100.			IN	A

;; AUTHORITY SECTION:
.			512	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2021070200 1800 900 604800 86400

;; Query time: 17 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jul 02 16:11:39 BST 2021
;; MSG SIZE  rcvd: 117

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22190
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		106	IN	A	172.217.164.206

;; Query time: 17 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jul 02 16:11:39 BST 2021
;; MSG SIZE  rcvd: 55
====

Code: Select all

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> 127.0.0.1 -p 5335 google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

ok to remove Unbound from AGH configuration

Code: Select all

G_CONFIG_INJECT 'upstream_dns_file:[[:blank:]]' '  upstream_dns_file: ""' /mnt/dietpi_userdata/adguardhome/AdGuardHome.yaml
systemctl restart adguardhome
Now, AGH should use preconfigured global upstream DNS server. You should be ok to change a computer to use AGH as DNS and in AGH have a look to the dashboard if you see DNS queries. If this is working fine, we could have a look to Unbound afterwards.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Thanks Joulinard,
Here's the output from the Unbound removal:
OK ] G_CONFIG_INJECT | Setting in /mnt/dietpi_userdata/adguardhome/AdGuardHome.yaml adjusted: upstream_dns_file: ""

Next, I disabled DHCP on my router and pointed to the Adguard Rpi fixed address. Didn't include a secondary DNS server. But I couldn't get on the internet.

Then Reloaded saved router settings with DHCP enabled. Changed PC ipv4 DNS to point to Adguard on the Rpi. I still have PC internet access but AdGuard Home dashboard shows no activity. Rpi doesn't show up in the DHCP router list, but it has an internet connection.

Not sure what the issue is. Perhaps the Adguard Home dashboard settings need changing.
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

I notice in the AdGuardHome.yaml file that under "bind hosts:" it shows 0.0.0.0 rather than 192.168.1.100. (Rpi Adguard.) Is that correct?
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

let me try to answer some of your points
I disabled DHCP on my router
There is no need to disable DHCP directly on your router.
"bind hosts:" it shows 0.0.0.0 rather than 192.168.1.100
This is perfect setting. 0.0.0.0 are seen as wildcards, means AGH will LISTEN on all interfaces.
Rpi doesn't show up in the DHCP router list...
Maybe your RPi is using STATIC IP instead of DHCP?
...but it has an internet connection.
The RPi is not using AGH as DNS server. Usually it should connect directly to Quad9 global upstream DNS. This is totally fine.



OK let's see if we could do some more tracing for your issue

First let's install tcpdump on your RPi

Code: Select all

dietpi-software install 15
Now change DNS server on your Windows network settings. You can leave IP address set to DHCP. I guess you know what I mean, even if it is German language

picture.png
picture.png (13.45 KiB) Viewed 262 times

Now we are ready to trace. Pls run following command on your RPi. It captures whole DNS traffic and will stop after 500 lines or once cancelled

Code: Select all

tcpdump -i any -c500 -nn port 853 or port 53 or port 443
on Windows open a cmd and run following

Code: Select all

nslookup google.com
Hopefully you will see something captured by tcpdump now. If possible post the output from both, tcpdump as well as nslookup
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Here's the nslookup:

Code: Select all

DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.100

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out
====

Here's the tcp dump:

Code: Select all

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
13:51:19.761934 IP 192.168.1.2.57804 > 192.168.1.100.53: 15523+ A? example.org. (29)
13:51:19.762014 IP 192.168.1.2.55772 > 192.168.1.100.53: 25103+ A? ipv4only.arpa. (31)
13:51:19.762016 IP 192.168.1.2.57967 > 192.168.1.100.53: 37015+ A? detectportal.firefox.com. (42)
13:51:19.929957 IP 192.168.1.2.53539 > 192.168.1.100.53: 24535+ A? wpad.Home. (27)
13:51:19.932211 IP 192.168.1.2.57584 > 192.168.1.100.53: 60039+ A? example.org. (29)
13:51:20.392512 IP 192.168.1.2.50988 > 192.168.1.100.53: 24013+ A? secure10.sync.com. (35)
13:51:20.935197 IP 192.168.1.2.57584 > 192.168.1.100.53: 60039+ A? example.org. (29)
13:51:21.939204 IP 192.168.1.2.53539 > 192.168.1.100.53: 24535+ A? wpad.Home. (27)
13:51:21.939218 IP 192.168.1.2.57584 > 192.168.1.100.53: 60039+ A? example.org. (29)
13:51:22.225144 IP 192.168.1.2.59669 > 192.168.1.100.53: 39228+ A? secure1.sync.com. (34)
13:51:22.403032 IP 192.168.1.2.50988 > 192.168.1.100.53: 24013+ A? secure10.sync.com. (35)
13:51:23.230225 IP 192.168.1.2.59669 > 192.168.1.100.53: 39228+ A? secure1.sync.com. (34)
13:51:23.245520 IP 192.168.1.2.63584 > 192.168.1.100.53: 14417+ A? dns.msftncsi.com. (34)
13:51:23.245908 IP 192.168.1.2.59874 > 192.168.1.100.53: 7969+ A? ipv6.msftconnecttest.com. (42)
13:51:23.776965 IP 192.168.1.2.57967 > 192.168.1.100.53: 37015+ A? detectportal.firefox.com. (42)
13:51:23.777282 IP 192.168.1.2.57804 > 192.168.1.100.53: 15523+ A? example.org. (29)
13:51:23.777296 IP 192.168.1.2.55772 > 192.168.1.100.53: 25103+ A? ipv4only.arpa. (31)
13:51:23.950539 IP 192.168.1.2.57584 > 192.168.1.100.53: 60039+ A? example.org. (29)
13:51:24.235934 IP 192.168.1.2.59669 > 192.168.1.100.53: 39228+ A? secure1.sync.com. (34)
13:51:25.945851 IP 192.168.1.2.55241 > 192.168.1.100.53: 58624+ A? Home.Home. (27)
13:51:26.245498 IP 192.168.1.2.59669 > 192.168.1.100.53: 39228+ A? secure1.sync.com. (34)
13:51:26.408653 IP 192.168.1.2.50988 > 192.168.1.100.53: 24013+ A? secure10.sync.com. (35)
13:51:26.950686 IP 192.168.1.2.55241 > 192.168.1.100.53: 58624+ A? Home.Home. (27)
13:51:27.248401 IP 192.168.1.2.60457 > 192.168.1.100.53: 221+ A? dns.msftncsi.com. (34)
13:51:27.248421 IP 192.168.1.2.53794 > 192.168.1.100.53: Flags [S], seq 522051813, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:27.248428 IP 192.168.1.2.51106 > 192.168.1.100.53: 63114+ AAAA? dns.msftncsi.com. (34)
13:51:27.791376 IP 192.168.1.2.64473 > 192.168.1.100.53: 8268+ A? ipv4only.arpa. (31)
13:51:27.791660 IP 192.168.1.2.49893 > 192.168.1.100.53: 7378+ A? detectportal.firefox.com. (42)
13:51:27.951030 IP 192.168.1.2.57584 > 192.168.1.100.53: 60039+ A? example.org. (29)
13:51:28.248089 IP 192.168.1.2.53794 > 192.168.1.100.53: Flags [S], seq 522051813, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:28.248422 IP 192.168.1.2.51106 > 192.168.1.100.53: 63114+ AAAA? dns.msftncsi.com. (34)
13:51:28.248437 IP 192.168.1.2.60457 > 192.168.1.100.53: 221+ A? dns.msftncsi.com. (34)
13:51:28.805437 IP 192.168.1.2.49893 > 192.168.1.100.53: 7378+ A? detectportal.firefox.com. (42)
13:51:28.805454 IP 192.168.1.2.64473 > 192.168.1.100.53: 8268+ A? ipv4only.arpa. (31)
13:51:28.959071 IP 192.168.1.2.55241 > 192.168.1.100.53: 58624+ A? Home.Home. (27)
13:51:29.258253 IP 192.168.1.2.60457 > 192.168.1.100.53: 221+ A? dns.msftncsi.com. (34)
13:51:29.258606 IP 192.168.1.2.51106 > 192.168.1.100.53: 63114+ AAAA? dns.msftncsi.com. (34)
13:51:29.807837 IP 192.168.1.2.64473 > 192.168.1.100.53: 8268+ A? ipv4only.arpa. (31)
13:51:29.807856 IP 192.168.1.2.49893 > 192.168.1.100.53: 7378+ A? detectportal.firefox.com. (42)
13:51:30.249100 IP 192.168.1.2.53794 > 192.168.1.100.53: Flags [S], seq 522051813, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:30.249429 IP 192.168.1.2.59669 > 192.168.1.100.53: 39228+ A? secure1.sync.com. (34)
13:51:30.462868 IP 192.168.1.2.60346 > 192.168.1.100.53: 5020+ A? secure20.sync.com. (35)
13:51:31.269597 IP 192.168.1.2.51106 > 192.168.1.100.53: 63114+ AAAA? dns.msftncsi.com. (34)
13:51:31.269618 IP 192.168.1.2.60457 > 192.168.1.100.53: 221+ A? dns.msftncsi.com. (34)
13:51:31.475427 IP 192.168.1.2.60346 > 192.168.1.100.53: 5020+ A? secure20.sync.com. (35)
13:51:31.809209 IP 192.168.1.2.49893 > 192.168.1.100.53: 7378+ A? detectportal.firefox.com. (42)
13:51:31.809369 IP 192.168.1.2.64473 > 192.168.1.100.53: 8268+ A? ipv4only.arpa. (31)
13:51:31.965235 IP 192.168.1.2.54779 > 192.168.1.100.53: 21108+ A? example.org. (29)
13:51:32.484173 IP 192.168.1.2.60346 > 192.168.1.100.53: 5020+ A? secure20.sync.com. (35)
13:51:32.967949 IP 192.168.1.2.54779 > 192.168.1.100.53: 21108+ A? example.org. (29)
13:51:32.969007 IP 192.168.1.2.64589 > 192.168.1.100.53: 37328+ A? Home.Home. (27)
13:51:33.984212 IP 192.168.1.2.54779 > 192.168.1.100.53: 21108+ A? example.org. (29)
13:51:33.984230 IP 192.168.1.2.64589 > 192.168.1.100.53: 37328+ A? Home.Home. (27)
13:51:34.254278 IP 192.168.1.2.53794 > 192.168.1.100.53: Flags [S], seq 522051813, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:34.490540 IP 192.168.1.2.60346 > 192.168.1.100.53: 5020+ A? secure20.sync.com. (35)
13:51:35.271120 IP 192.168.1.2.60457 > 192.168.1.100.53: 221+ A? dns.msftncsi.com. (34)
13:51:35.271139 IP 192.168.1.2.51106 > 192.168.1.100.53: 63114+ AAAA? dns.msftncsi.com. (34)
13:51:35.817386 IP 192.168.1.2.64473 > 192.168.1.100.53: 8268+ A? ipv4only.arpa. (31)
13:51:35.817404 IP 192.168.1.2.49893 > 192.168.1.100.53: 7378+ A? detectportal.firefox.com. (42)
13:51:35.985123 IP 192.168.1.2.64589 > 192.168.1.100.53: 37328+ A? Home.Home. (27)
13:51:35.985476 IP 192.168.1.2.54779 > 192.168.1.100.53: 21108+ A? example.org. (29)
13:51:38.501972 IP 192.168.1.2.60346 > 192.168.1.100.53: 5020+ A? secure20.sync.com. (35)
13:51:39.280011 IP 192.168.1.2.61700 > 192.168.1.100.53: 44064+ AAAA? Home. (22)
13:51:39.280310 IP 192.168.1.2.61641 > 192.168.1.100.53: Flags [S], seq 1418498172, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:39.280420 IP 192.168.1.2.53070 > 192.168.1.100.53: 3916+ A? Home. (22)
13:51:39.280958 IP 192.168.1.2.50409 > 192.168.1.100.53: Flags [S], seq 3909286532, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:39.828546 IP 192.168.1.2.49650 > 192.168.1.100.53: 42683+ A? detectportal.firefox.com. (42)
13:51:39.998885 IP 192.168.1.2.54779 > 192.168.1.100.53: 21108+ A? example.org. (29)
13:51:40.280180 IP 192.168.1.2.61700 > 192.168.1.100.53: 44064+ AAAA? Home. (22)
13:51:40.280200 IP 192.168.1.2.53070 > 192.168.1.100.53: 3916+ A? Home. (22)
13:51:40.295141 IP 192.168.1.2.61641 > 192.168.1.100.53: Flags [S], seq 1418498172, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:40.295162 IP 192.168.1.2.50409 > 192.168.1.100.53: Flags [S], seq 3909286532, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:40.841803 IP 192.168.1.2.49650 > 192.168.1.100.53: 42683+ A? detectportal.firefox.com. (42)
13:51:41.289300 IP 192.168.1.2.53070 > 192.168.1.100.53: 3916+ A? Home. (22)
13:51:41.289656 IP 192.168.1.2.61700 > 192.168.1.100.53: 44064+ AAAA? Home. (22)
13:51:41.855219 IP 192.168.1.2.49650 > 192.168.1.100.53: 42683+ A? detectportal.firefox.com. (42)
13:51:42.254489 IP 192.168.1.2.53794 > 192.168.1.100.53: Flags [S], seq 522051813, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:42.301187 IP 192.168.1.2.50409 > 192.168.1.100.53: Flags [S], seq 3909286532, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:42.301205 IP 192.168.1.2.61641 > 192.168.1.100.53: Flags [S], seq 1418498172, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:43.295647 IP 192.168.1.2.61700 > 192.168.1.100.53: 44064+ AAAA? Home. (22)
13:51:43.295669 IP 192.168.1.2.53070 > 192.168.1.100.53: 3916+ A? Home. (22)
13:51:43.659081 IP 192.168.1.5.53735 > 192.168.1.100.53: Flags [S], seq 3792271665, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:43.859247 IP 192.168.1.2.49650 > 192.168.1.100.53: 42683+ A? detectportal.firefox.com. (42)
13:51:44.670590 IP 192.168.1.5.53735 > 192.168.1.100.53: Flags [S], seq 3792271665, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:46.307138 IP 192.168.1.2.50409 > 192.168.1.100.53: Flags [S], seq 3909286532, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:46.307157 IP 192.168.1.2.61641 > 192.168.1.100.53: Flags [S], seq 1418498172, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:46.674109 IP 192.168.1.5.53735 > 192.168.1.100.53: Flags [S], seq 3792271665, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:47.298972 IP 192.168.1.2.53070 > 192.168.1.100.53: 3916+ A? Home. (22)
13:51:47.299153 IP 192.168.1.2.61700 > 192.168.1.100.53: 44064+ AAAA? Home. (22)
13:51:47.861026 IP 192.168.1.2.49650 > 192.168.1.100.53: 42683+ A? detectportal.firefox.com. (42)
13:51:49.733603 IP 192.168.1.2.56369 > 192.168.1.100.53: 55377+ A? secure10.sync.com. (35)
13:51:50.684883 IP 192.168.1.5.53735 > 192.168.1.100.53: Flags [S], seq 3792271665, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:50.746971 IP 192.168.1.2.56369 > 192.168.1.100.53: 55377+ A? secure10.sync.com. (35)
13:51:51.758948 IP 192.168.1.2.56369 > 192.168.1.100.53: 55377+ A? secure10.sync.com. (35)
13:51:53.451026 IP 192.168.1.2.64018 > 192.168.1.100.53: 3143+ A? dns.msftncsi.com. (34)
13:51:53.766093 IP 192.168.1.2.56369 > 192.168.1.100.53: 55377+ A? secure10.sync.com. (35)
13:51:54.314061 IP 192.168.1.2.61641 > 192.168.1.100.53: Flags [S], seq 1418498172, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:54.314070 IP 192.168.1.2.50409 > 192.168.1.100.53: Flags [S], seq 3909286532, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:51:54.455688 IP 192.168.1.2.64018 > 192.168.1.100.53: 3143+ A? dns.msftncsi.com. (34)
13:51:55.465642 IP 192.168.1.2.64018 > 192.168.1.100.53: 3143+ A? dns.msftncsi.com. (34)
13:51:57.472805 IP 192.168.1.2.64018 > 192.168.1.100.53: 3143+ A? dns.msftncsi.com. (34)
13:51:57.772076 IP 192.168.1.2.56369 > 192.168.1.100.53: 55377+ A? secure10.sync.com. (35)
13:51:58.693543 IP 192.168.1.5.53735 > 192.168.1.100.53: Flags [S], seq 3792271665, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:01.484007 IP 192.168.1.2.64018 > 192.168.1.100.53: 3143+ A? dns.msftncsi.com. (34)
13:52:01.814798 IP 192.168.1.2.51245 > 192.168.1.100.53: 50497+ A? secure20.sync.com. (35)
13:52:02.828169 IP 192.168.1.2.51245 > 192.168.1.100.53: 50497+ A? secure20.sync.com. (35)
13:52:03.839873 IP 192.168.1.2.51245 > 192.168.1.100.53: 50497+ A? secure20.sync.com. (35)
13:52:05.487784 IP 192.168.1.2.53434 > 192.168.1.100.53: Flags [S], seq 215937533, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:05.843205 IP 192.168.1.2.51245 > 192.168.1.100.53: 50497+ A? secure20.sync.com. (35)
13:52:06.499312 IP 192.168.1.2.53434 > 192.168.1.100.53: Flags [S], seq 215937533, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:08.512962 IP 192.168.1.2.53434 > 192.168.1.100.53: Flags [S], seq 215937533, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:09.822461 IP 192.168.1.2.63093 > 192.168.1.100.53: 53714+ A? secure10.sync.com. (35)
13:52:09.847785 IP 192.168.1.2.51245 > 192.168.1.100.53: 50497+ A? secure20.sync.com. (35)
13:52:10.834452 IP 192.168.1.2.63093 > 192.168.1.100.53: 53714+ A? secure10.sync.com. (35)
13:52:11.849137 IP 192.168.1.2.63093 > 192.168.1.100.53: 53714+ A? secure10.sync.com. (35)
13:52:12.524915 IP 192.168.1.2.53434 > 192.168.1.100.53: Flags [S], seq 215937533, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:13.851203 IP 192.168.1.2.63093 > 192.168.1.100.53: 53714+ A? secure10.sync.com. (35)
13:52:17.855565 IP 192.168.1.2.63093 > 192.168.1.100.53: 53714+ A? secure10.sync.com. (35)
13:52:18.666595 IP 192.168.1.2.52668 > 192.168.1.100.53: 19841+ A? checkappexec.microsoft.com. (44)
13:52:19.678167 IP 192.168.1.2.52668 > 192.168.1.100.53: 19841+ A? checkappexec.microsoft.com. (44)
13:52:20.527160 IP 192.168.1.2.53434 > 192.168.1.100.53: Flags [S], seq 215937533, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:20.683460 IP 192.168.1.2.52668 > 192.168.1.100.53: 19841+ A? checkappexec.microsoft.com. (44)
13:52:22.685584 IP 192.168.1.2.52668 > 192.168.1.100.53: 19841+ A? checkappexec.microsoft.com. (44)
13:52:23.170239 IP 192.168.1.2.51322 > 192.168.1.100.53: 29836+ A? wpad.Home. (27)
13:52:23.395417 IP 192.168.1.2.65359 > 192.168.1.100.53: 48156+ A? dns.msftncsi.com. (34)
13:52:23.414381 IP 192.168.1.2.51799 > 192.168.1.100.53: 7115+ A? ipv6.msftconnecttest.com. (42)
13:52:24.172337 IP 192.168.1.2.51322 > 192.168.1.100.53: 29836+ A? wpad.Home. (27)
13:52:24.201300 IP 192.168.1.2.50189 > 192.168.1.100.53: 23888+ A? example.org. (29)
13:52:24.201657 IP 192.168.1.2.62927 > 192.168.1.100.53: 7465+ A? ipv4only.arpa. (31)
13:52:24.201671 IP 192.168.1.2.57875 > 192.168.1.100.53: 15395+ A? detectportal.firefox.com. (42)
13:52:24.406385 IP 192.168.1.2.65359 > 192.168.1.100.53: 48156+ A? dns.msftncsi.com. (34)
13:52:24.421388 IP 192.168.1.2.51799 > 192.168.1.100.53: 7115+ A? ipv6.msftconnecttest.com. (42)
13:52:25.209955 IP 192.168.1.2.57875 > 192.168.1.100.53: 15395+ A? detectportal.firefox.com. (42)
13:52:25.209965 IP 192.168.1.2.50189 > 192.168.1.100.53: 23888+ A? example.org. (29)
13:52:25.209968 IP 192.168.1.2.62927 > 192.168.1.100.53: 7465+ A? ipv4only.arpa. (31)
13:52:25.411252 IP 192.168.1.2.65359 > 192.168.1.100.53: 48156+ A? dns.msftncsi.com. (34)
13:52:25.426728 IP 192.168.1.2.51799 > 192.168.1.100.53: 7115+ A? ipv6.msftconnecttest.com. (42)
13:52:26.174524 IP 192.168.1.2.51322 > 192.168.1.100.53: 29836+ A? wpad.Home. (27)
13:52:26.219439 IP 192.168.1.2.62927 > 192.168.1.100.53: 7465+ A? ipv4only.arpa. (31)
13:52:26.219458 IP 192.168.1.2.57875 > 192.168.1.100.53: 15395+ A? detectportal.firefox.com. (42)
13:52:26.219464 IP 192.168.1.2.50189 > 192.168.1.100.53: 23888+ A? example.org. (29)
13:52:27.419455 IP 192.168.1.2.65359 > 192.168.1.100.53: 48156+ A? dns.msftncsi.com. (34)
13:52:27.434851 IP 192.168.1.2.51799 > 192.168.1.100.53: 7115+ A? ipv6.msftconnecttest.com. (42)
13:52:28.220367 IP 192.168.1.2.50189 > 192.168.1.100.53: 23888+ A? example.org. (29)
13:52:28.220387 IP 192.168.1.2.62927 > 192.168.1.100.53: 7465+ A? ipv4only.arpa. (31)
13:52:28.220542 IP 192.168.1.2.57875 > 192.168.1.100.53: 15395+ A? detectportal.firefox.com. (42)
13:52:28.687501 IP 192.168.1.2.63179 > 192.168.1.100.53: 15784+ A? licensing.mp.microsoft.com. (44)
13:52:29.017003 IP 192.168.1.2.63451 > 192.168.1.100.53: 31721+ A? wpad.Home. (27)
13:52:29.694386 IP 192.168.1.2.63179 > 192.168.1.100.53: 15784+ A? licensing.mp.microsoft.com. (44)
13:52:30.019237 IP 192.168.1.2.63451 > 192.168.1.100.53: 31721+ A? wpad.Home. (27)
13:52:30.175864 IP 192.168.1.2.54571 > 192.168.1.100.53: 27035+ A? Home.Home. (27)
13:52:30.699312 IP 192.168.1.2.63179 > 192.168.1.100.53: 15784+ A? licensing.mp.microsoft.com. (44)
13:52:30.909077 IP 192.168.1.2.64771 > 192.168.1.100.53: 46927+ A? secure10.sync.com. (35)
13:52:31.182026 IP 192.168.1.2.54571 > 192.168.1.100.53: 27035+ A? Home.Home. (27)
13:52:31.431222 IP 192.168.1.2.65359 > 192.168.1.100.53: 48156+ A? dns.msftncsi.com. (34)
13:52:31.446666 IP 192.168.1.2.51799 > 192.168.1.100.53: 7115+ A? ipv6.msftconnecttest.com. (42)
13:52:31.915974 IP 192.168.1.2.64771 > 192.168.1.100.53: 46927+ A? secure10.sync.com. (35)
13:52:32.023497 IP 192.168.1.2.63451 > 192.168.1.100.53: 31721+ A? wpad.Home. (27)
13:52:32.226477 IP 192.168.1.2.50189 > 192.168.1.100.53: 23888+ A? example.org. (29)
13:52:32.226496 IP 192.168.1.2.62927 > 192.168.1.100.53: 7465+ A? ipv4only.arpa. (31)
13:52:32.226502 IP 192.168.1.2.57875 > 192.168.1.100.53: 15395+ A? detectportal.firefox.com. (42)
13:52:32.718200 IP 192.168.1.2.63179 > 192.168.1.100.53: 15784+ A? licensing.mp.microsoft.com. (44)
13:52:32.916413 IP 192.168.1.2.64771 > 192.168.1.100.53: 46927+ A? secure10.sync.com. (35)
13:52:33.196579 IP 192.168.1.2.54571 > 192.168.1.100.53: 27035+ A? Home.Home. (27)
13:52:34.922449 IP 192.168.1.2.64771 > 192.168.1.100.53: 46927+ A? secure10.sync.com. (35)
13:52:35.446141 IP 192.168.1.2.62004 > 192.168.1.100.53: 52300+ A? Home. (22)
13:52:35.446494 IP 192.168.1.2.58697 > 192.168.1.100.53: Flags [S], seq 2903736834, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:35.446731 IP 192.168.1.2.56765 > 192.168.1.100.53: 21125+ A? dns.msftncsi.com. (34)
13:52:35.462559 IP 192.168.1.2.53904 > 192.168.1.100.53: 18182+ AAAA? dns.msftncsi.com. (34)
13:52:36.232268 IP 192.168.1.2.60587 > 192.168.1.100.53: 40136+ A? example.org. (29)
13:52:36.233247 IP 192.168.1.2.61477 > 192.168.1.100.53: 35550+ A? ipv4only.arpa. (31)
13:52:36.233263 IP 192.168.1.2.57953 > 192.168.1.100.53: 63826+ A? detectportal.firefox.com. (42)
13:52:36.446744 IP 192.168.1.2.58697 > 192.168.1.100.53: Flags [S], seq 2903736834, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:36.446921 IP 192.168.1.2.56765 > 192.168.1.100.53: 21125+ A? dns.msftncsi.com. (34)
13:52:36.446929 IP 192.168.1.2.62004 > 192.168.1.100.53: 52300+ A? Home. (22)
13:52:36.476955 IP 192.168.1.2.53904 > 192.168.1.100.53: 18182+ AAAA? dns.msftncsi.com. (34)
13:52:36.729194 IP 192.168.1.2.63179 > 192.168.1.100.53: 15784+ A? licensing.mp.microsoft.com. (44)
13:52:37.197897 IP 192.168.1.2.55663 > 192.168.1.100.53: 57560+ A? Home.Home. (27)
13:52:37.243615 IP 192.168.1.2.57953 > 192.168.1.100.53: 63826+ A? detectportal.firefox.com. (42)
13:52:37.243776 IP 192.168.1.2.60587 > 192.168.1.100.53: 40136+ A? example.org. (29)
13:52:37.243783 IP 192.168.1.2.61477 > 192.168.1.100.53: 35550+ A? ipv4only.arpa. (31)
13:52:37.459966 IP 192.168.1.2.62004 > 192.168.1.100.53: 52300+ A? Home. (22)
13:52:37.460134 IP 192.168.1.2.56765 > 192.168.1.100.53: 21125+ A? dns.msftncsi.com. (34)
13:52:37.492472 IP 192.168.1.2.53904 > 192.168.1.100.53: 18182+ AAAA? dns.msftncsi.com. (34)
13:52:38.209543 IP 192.168.1.2.55663 > 192.168.1.100.53: 57560+ A? Home.Home. (27)
13:52:38.255696 IP 192.168.1.2.57953 > 192.168.1.100.53: 63826+ A? detectportal.firefox.com. (42)
13:52:38.255852 IP 192.168.1.2.60587 > 192.168.1.100.53: 40136+ A? example.org. (29)
13:52:38.255859 IP 192.168.1.2.61477 > 192.168.1.100.53: 35550+ A? ipv4only.arpa. (31)
13:52:38.457896 IP 192.168.1.2.58697 > 192.168.1.100.53: Flags [S], seq 2903736834, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:38.934690 IP 192.168.1.2.64771 > 192.168.1.100.53: 46927+ A? secure10.sync.com. (35)
13:52:39.468619 IP 192.168.1.2.56765 > 192.168.1.100.53: 21125+ A? dns.msftncsi.com. (34)
13:52:39.468778 IP 192.168.1.2.62004 > 192.168.1.100.53: 52300+ A? Home. (22)
13:52:39.499254 IP 192.168.1.2.53904 > 192.168.1.100.53: 18182+ AAAA? dns.msftncsi.com. (34)
13:52:40.213848 IP 192.168.1.2.55663 > 192.168.1.100.53: 57560+ A? Home.Home. (27)
13:52:40.259984 IP 192.168.1.2.57953 > 192.168.1.100.53: 63826+ A? detectportal.firefox.com. (42)
13:52:40.260158 IP 192.168.1.2.60587 > 192.168.1.100.53: 40136+ A? example.org. (29)
13:52:40.260164 IP 192.168.1.2.61477 > 192.168.1.100.53: 35550+ A? ipv4only.arpa. (31)
13:52:42.472424 IP 192.168.1.2.58697 > 192.168.1.100.53: Flags [S], seq 2903736834, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:43.481324 IP 192.168.1.2.62004 > 192.168.1.100.53: 52300+ A? Home. (22)
13:52:43.481342 IP 192.168.1.2.56765 > 192.168.1.100.53: 21125+ A? dns.msftncsi.com. (34)
13:52:43.512494 IP 192.168.1.2.53904 > 192.168.1.100.53: 18182+ AAAA? dns.msftncsi.com. (34)
13:52:44.265346 IP 192.168.1.2.57953 > 192.168.1.100.53: 63826+ A? detectportal.firefox.com. (42)
13:52:44.265365 IP 192.168.1.2.61477 > 192.168.1.100.53: 35550+ A? ipv4only.arpa. (31)
13:52:44.265764 IP 192.168.1.2.60587 > 192.168.1.100.53: 40136+ A? example.org. (29)
13:52:47.486279 IP 192.168.1.2.58418 > 192.168.1.100.53: Flags [S], seq 896120150, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:47.516719 IP 192.168.1.2.57883 > 192.168.1.100.53: 35003+ AAAA? Home. (22)
13:52:47.516927 IP 192.168.1.2.63864 > 192.168.1.100.53: Flags [S], seq 3365043248, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:48.275270 IP 192.168.1.2.65436 > 192.168.1.100.53: 62312+ A? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:48.295370 IP 192.168.1.2.60068 > 192.168.1.100.53: 47699+ AAAA? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:48.488722 IP 192.168.1.2.58418 > 192.168.1.100.53: Flags [S], seq 896120150, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:48.519659 IP 192.168.1.2.63864 > 192.168.1.100.53: Flags [S], seq 3365043248, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:48.519677 IP 192.168.1.2.57883 > 192.168.1.100.53: 35003+ AAAA? Home. (22)
13:52:49.283583 IP 192.168.1.2.65436 > 192.168.1.100.53: 62312+ A? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:49.299243 IP 192.168.1.2.60068 > 192.168.1.100.53: 47699+ AAAA? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:49.531867 IP 192.168.1.2.57883 > 192.168.1.100.53: 35003+ AAAA? Home. (22)
13:52:49.815887 IP 192.168.1.2.55735 > 192.168.1.100.53: 1+ PTR? 100.1.168.192.in-addr.arpa. (44)
13:52:50.286458 IP 192.168.1.2.65436 > 192.168.1.100.53: 62312+ A? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:50.301551 IP 192.168.1.2.60068 > 192.168.1.100.53: 47699+ AAAA? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:50.478806 IP 192.168.1.2.58697 > 192.168.1.100.53: Flags [S], seq 2903736834, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:50.493994 IP 192.168.1.2.58418 > 192.168.1.100.53: Flags [S], seq 896120150, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:50.524623 IP 192.168.1.2.63864 > 192.168.1.100.53: Flags [S], seq 3365043248, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:51.535125 IP 192.168.1.2.57883 > 192.168.1.100.53: 35003+ AAAA? Home. (22)
13:52:51.825520 IP 192.168.1.2.58911 > 192.168.1.100.53: 2+ A? google.com.Home. (33)
13:52:52.300645 IP 192.168.1.2.65436 > 192.168.1.100.53: 62312+ A? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:52.315967 IP 192.168.1.2.60068 > 192.168.1.100.53: 47699+ AAAA? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:53.443372 IP 192.168.1.2.62839 > 192.168.1.100.53: 7142+ A? dns.msftncsi.com. (34)
13:52:53.833865 IP 192.168.1.2.62840 > 192.168.1.100.53: 3+ AAAA? google.com.Home. (33)
13:52:54.447470 IP 192.168.1.2.62839 > 192.168.1.100.53: 7142+ A? dns.msftncsi.com. (34)
13:52:54.495832 IP 192.168.1.2.58418 > 192.168.1.100.53: Flags [S], seq 896120150, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:54.526095 IP 192.168.1.2.63864 > 192.168.1.100.53: Flags [S], seq 3365043248, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:52:55.454853 IP 192.168.1.2.62839 > 192.168.1.100.53: 7142+ A? dns.msftncsi.com. (34)
13:52:55.547205 IP 192.168.1.2.57883 > 192.168.1.100.53: 35003+ AAAA? Home. (22)
13:52:55.840803 IP 192.168.1.2.62841 > 192.168.1.100.53: 4+ A? google.com. (28)
13:52:56.307301 IP 192.168.1.2.65436 > 192.168.1.100.53: 62312+ A? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:56.322541 IP 192.168.1.2.60068 > 192.168.1.100.53: 47699+ AAAA? prod.detectportal.prod.cloudops.mozgcp.net. (60)
13:52:57.468960 IP 192.168.1.2.62839 > 192.168.1.100.53: 7142+ A? dns.msftncsi.com. (34)
13:52:57.855032 IP 192.168.1.2.62842 > 192.168.1.100.53: 5+ AAAA? google.com. (28)
13:53:00.322376 IP 192.168.1.2.53825 > 192.168.1.100.53: 2729+ A? Home.Home. (27)
13:53:00.337393 IP 192.168.1.2.62070 > 192.168.1.100.53: 25377+ AAAA? Home.Home. (27)
13:53:01.325515 IP 192.168.1.2.53825 > 192.168.1.100.53: 2729+ A? Home.Home. (27)
13:53:01.339965 IP 192.168.1.2.62070 > 192.168.1.100.53: 25377+ AAAA? Home.Home. (27)
13:53:01.478867 IP 192.168.1.2.62839 > 192.168.1.100.53: 7142+ A? dns.msftncsi.com. (34)
13:53:02.503723 IP 192.168.1.2.58418 > 192.168.1.100.53: Flags [S], seq 896120150, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:02.534296 IP 192.168.1.2.63864 > 192.168.1.100.53: Flags [S], seq 3365043248, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:03.330107 IP 192.168.1.2.53825 > 192.168.1.100.53: 2729+ A? Home.Home. (27)
13:53:03.345240 IP 192.168.1.2.62070 > 192.168.1.100.53: 25377+ AAAA? Home.Home. (27)
13:53:05.485082 IP 192.168.1.2.56988 > 192.168.1.100.53: Flags [S], seq 1033632831, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:06.499730 IP 192.168.1.2.56988 > 192.168.1.100.53: Flags [S], seq 1033632831, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:07.352334 IP 192.168.1.2.58805 > 192.168.1.100.53: 955+ AAAA? Home.Home. (27)
13:53:08.357221 IP 192.168.1.2.58805 > 192.168.1.100.53: 955+ AAAA? Home.Home. (27)
13:53:08.511607 IP 192.168.1.2.56988 > 192.168.1.100.53: Flags [S], seq 1033632831, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:10.369690 IP 192.168.1.2.58805 > 192.168.1.100.53: 955+ AAAA? Home.Home. (27)
13:53:12.513222 IP 192.168.1.2.56988 > 192.168.1.100.53: Flags [S], seq 1033632831, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:20.525370 IP 192.168.1.2.56988 > 192.168.1.100.53: Flags [S], seq 1033632831, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:23.450441 IP 192.168.1.2.64071 > 192.168.1.100.53: 12230+ A? dns.msftncsi.com. (34)
13:53:24.462108 IP 192.168.1.2.64071 > 192.168.1.100.53: 12230+ A? dns.msftncsi.com. (34)
13:53:25.465117 IP 192.168.1.2.64071 > 192.168.1.100.53: 12230+ A? dns.msftncsi.com. (34)
13:53:27.476681 IP 192.168.1.2.64071 > 192.168.1.100.53: 12230+ A? dns.msftncsi.com. (34)
13:53:31.484164 IP 192.168.1.2.64071 > 192.168.1.100.53: 12230+ A? dns.msftncsi.com. (34)
13:53:35.491782 IP 192.168.1.2.54414 > 192.168.1.100.53: Flags [S], seq 3313508324, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:36.503386 IP 192.168.1.2.54414 > 192.168.1.100.53: Flags [S], seq 3313508324, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:38.517179 IP 192.168.1.2.54414 > 192.168.1.100.53: Flags [S], seq 3313508324, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:42.521539 IP 192.168.1.2.54414 > 192.168.1.100.53: Flags [S], seq 3313508324, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:45.825455 IP 192.168.1.2.57150 > 192.168.1.100.53: 29023+ A? secure10.sync.com. (35)
13:53:46.835459 IP 192.168.1.2.57150 > 192.168.1.100.53: 29023+ A? secure10.sync.com. (35)
13:53:47.839068 IP 192.168.1.2.57150 > 192.168.1.100.53: 29023+ A? secure10.sync.com. (35)
13:53:49.849852 IP 192.168.1.2.57150 > 192.168.1.100.53: 29023+ A? secure10.sync.com. (35)
13:53:50.522544 IP 192.168.1.2.54414 > 192.168.1.100.53: Flags [S], seq 3313508324, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:53:51.095217 IP 192.168.1.2.54107 > 192.168.1.100.53: 29178+ A? wpad.Home. (27)
13:53:52.108959 IP 192.168.1.2.54107 > 192.168.1.100.53: 29178+ A? wpad.Home. (27)
13:53:53.447436 IP 192.168.1.2.59146 > 192.168.1.100.53: 30477+ A? dns.msftncsi.com. (34)
13:53:53.855948 IP 192.168.1.2.57150 > 192.168.1.100.53: 29023+ A? secure10.sync.com. (35)
13:53:54.112619 IP 192.168.1.2.54107 > 192.168.1.100.53: 29178+ A? wpad.Home. (27)
13:53:54.460078 IP 192.168.1.2.59146 > 192.168.1.100.53: 30477+ A? dns.msftncsi.com. (34)
13:53:55.460267 IP 192.168.1.2.59146 > 192.168.1.100.53: 30477+ A? dns.msftncsi.com. (34)
13:53:57.500442 IP 192.168.1.2.59146 > 192.168.1.100.53: 30477+ A? dns.msftncsi.com. (34)
13:54:01.516018 IP 192.168.1.2.59146 > 192.168.1.100.53: 30477+ A? dns.msftncsi.com. (34)
13:54:05.532487 IP 192.168.1.2.60041 > 192.168.1.100.53: Flags [S], seq 2349825664, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:06.537957 IP 192.168.1.2.60041 > 192.168.1.100.53: Flags [S], seq 2349825664, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:08.543081 IP 192.168.1.2.60041 > 192.168.1.100.53: Flags [S], seq 2349825664, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:12.552384 IP 192.168.1.2.60041 > 192.168.1.100.53: Flags [S], seq 2349825664, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:20.558591 IP 192.168.1.2.60041 > 192.168.1.100.53: Flags [S], seq 2349825664, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:23.453662 IP 192.168.1.2.60836 > 192.168.1.100.53: 5425+ A? dns.msftncsi.com. (34)
13:54:24.461264 IP 192.168.1.2.60836 > 192.168.1.100.53: 5425+ A? dns.msftncsi.com. (34)
13:54:25.473287 IP 192.168.1.2.60836 > 192.168.1.100.53: 5425+ A? dns.msftncsi.com. (34)
13:54:27.478928 IP 192.168.1.2.60836 > 192.168.1.100.53: 5425+ A? dns.msftncsi.com. (34)
13:54:31.487609 IP 192.168.1.2.60836 > 192.168.1.100.53: 5425+ A? dns.msftncsi.com. (34)
13:54:32.040226 IP 192.168.1.2.51013 > 192.168.1.100.53: 8788+ A? d.dropbox.com. (31)
13:54:33.040276 IP 192.168.1.2.51013 > 192.168.1.100.53: 8788+ A? d.dropbox.com. (31)
13:54:34.052614 IP 192.168.1.2.51013 > 192.168.1.100.53: 8788+ A? d.dropbox.com. (31)
13:54:35.501465 IP 192.168.1.2.51349 > 192.168.1.100.53: Flags [S], seq 3458210356, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:36.064281 IP 192.168.1.2.51013 > 192.168.1.100.53: 8788+ A? d.dropbox.com. (31)
13:54:36.504574 IP 192.168.1.2.51349 > 192.168.1.100.53: Flags [S], seq 3458210356, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:38.509401 IP 192.168.1.2.51349 > 192.168.1.100.53: Flags [S], seq 3458210356, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:40.069905 IP 192.168.1.2.51013 > 192.168.1.100.53: 8788+ A? d.dropbox.com. (31)
13:54:42.512511 IP 192.168.1.2.51349 > 192.168.1.100.53: Flags [S], seq 3458210356, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:54:50.518875 IP 192.168.1.2.51349 > 192.168.1.100.53: Flags [S], seq 3458210356, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:55:08.448401 IP 192.168.1.2.59052 > 192.168.1.100.53: 57091+ A? dns.msftncsi.com. (34)
13:55:09.449898 IP 192.168.1.2.59052 > 192.168.1.100.53: 57091+ A? dns.msftncsi.com. (34)
13:55:10.454968 IP 192.168.1.2.59052 > 192.168.1.100.53: 57091+ A? dns.msftncsi.com. (34)
13:55:12.461156 IP 192.168.1.2.59052 > 192.168.1.100.53: 57091+ A? dns.msftncsi.com. (34)
13:55:16.473075 IP 192.168.1.2.59052 > 192.168.1.100.53: 57091+ A? dns.msftncsi.com. (34)
13:55:20.486150 IP 192.168.1.2.49317 > 192.168.1.100.53: 31305+ A? dns.msftncsi.com. (34)
13:55:20.486423 IP 192.168.1.2.61999 > 192.168.1.100.53: Flags [S], seq 2129389233, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:55:21.495167 IP 192.168.1.2.61999 > 192.168.1.100.53: Flags [S], seq 2129389233, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:55:21.495508 IP 192.168.1.2.49317 > 192.168.1.100.53: 31305+ A? dns.msftncsi.com. (34)
13:55:22.496195 IP 192.168.1.2.49317 > 192.168.1.100.53: 31305+ A? dns.msftncsi.com. (34)
13:55:23.501432 IP 192.168.1.2.61999 > 192.168.1.100.53: Flags [S], seq 2129389233, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:55:24.501571 IP 192.168.1.2.49317 > 192.168.1.100.53: 31305+ A? dns.msftncsi.com. (34)
13:55:27.514205 IP 192.168.1.2.61999 > 192.168.1.100.53: Flags [S], seq 2129389233, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:55:28.505620 IP 192.168.1.2.49317 > 192.168.1.100.53: 31305+ A? dns.msftncsi.com. (34)
13:55:35.519511 IP 192.168.1.2.61999 > 192.168.1.100.53: Flags [S], seq 2129389233, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:55:53.450248 IP 192.168.1.2.57836 > 192.168.1.100.53: 26854+ A? dns.msftncsi.com. (34)
13:55:54.458293 IP 192.168.1.2.57836 > 192.168.1.100.53: 26854+ A? dns.msftncsi.com. (34)
13:55:55.469518 IP 192.168.1.2.57836 > 192.168.1.100.53: 26854+ A? dns.msftncsi.com. (34)
13:55:56.156706 IP 192.168.1.2.60149 > 192.168.1.100.53: 32237+ AAAA? www.dropbox.com. (33)
13:55:57.160963 IP 192.168.1.2.60149 > 192.168.1.100.53: 32237+ AAAA? www.dropbox.com. (33)
13:55:57.472918 IP 192.168.1.2.57836 > 192.168.1.100.53: 26854+ A? dns.msftncsi.com. (34)
13:55:58.173830 IP 192.168.1.2.60149 > 192.168.1.100.53: 32237+ AAAA? www.dropbox.com. (33)
13:55:59.534638 IP 192.168.1.2.65152 > 192.168.1.100.53: 55206+ A? secure10.sync.com. (35)
13:56:00.188675 IP 192.168.1.2.60149 > 192.168.1.100.53: 32237+ AAAA? www.dropbox.com. (33)
13:56:00.538763 IP 192.168.1.2.65152 > 192.168.1.100.53: 55206+ A? secure10.sync.com. (35)
13:56:01.488592 IP 192.168.1.2.57836 > 192.168.1.100.53: 26854+ A? dns.msftncsi.com. (34)
13:56:01.551376 IP 192.168.1.2.65152 > 192.168.1.100.53: 55206+ A? secure10.sync.com. (35)
13:56:03.566488 IP 192.168.1.2.65152 > 192.168.1.100.53: 55206+ A? secure10.sync.com. (35)
13:56:04.200498 IP 192.168.1.2.60149 > 192.168.1.100.53: 32237+ AAAA? www.dropbox.com. (33)
13:56:05.494673 IP 192.168.1.2.50313 > 192.168.1.100.53: 63264+ A? dns.msftncsi.com. (34)
13:56:05.494821 IP 192.168.1.2.63716 > 192.168.1.100.53: Flags [S], seq 829029125, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:06.502297 IP 192.168.1.2.63716 > 192.168.1.100.53: Flags [S], seq 829029125, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:06.502468 IP 192.168.1.2.50313 > 192.168.1.100.53: 63264+ A? dns.msftncsi.com. (34)
13:56:07.502659 IP 192.168.1.2.50313 > 192.168.1.100.53: 63264+ A? dns.msftncsi.com. (34)
13:56:07.579154 IP 192.168.1.2.65152 > 192.168.1.100.53: 55206+ A? secure10.sync.com. (35)
13:56:08.211803 IP 192.168.1.2.64149 > 192.168.1.100.53: 54254+ A? netmon-control.dropbox.com. (44)
13:56:08.510215 IP 192.168.1.2.63716 > 192.168.1.100.53: Flags [S], seq 829029125, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:09.220689 IP 192.168.1.2.64149 > 192.168.1.100.53: 54254+ A? netmon-control.dropbox.com. (44)
13:56:09.504664 IP 192.168.1.2.50313 > 192.168.1.100.53: 63264+ A? dns.msftncsi.com. (34)
13:56:10.222828 IP 192.168.1.2.64149 > 192.168.1.100.53: 54254+ A? netmon-control.dropbox.com. (44)
13:56:12.238228 IP 192.168.1.2.64149 > 192.168.1.100.53: 54254+ A? netmon-control.dropbox.com. (44)
13:56:12.523879 IP 192.168.1.2.63716 > 192.168.1.100.53: Flags [S], seq 829029125, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:13.508760 IP 192.168.1.2.50313 > 192.168.1.100.53: 63264+ A? dns.msftncsi.com. (34)
13:56:16.245487 IP 192.168.1.2.64149 > 192.168.1.100.53: 54254+ A? netmon-control.dropbox.com. (44)
13:56:20.529599 IP 192.168.1.2.63716 > 192.168.1.100.53: Flags [S], seq 829029125, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:23.447730 IP 192.168.1.2.62679 > 192.168.1.100.53: 46872+ A? dns.msftncsi.com. (34)
13:56:24.449976 IP 192.168.1.2.62679 > 192.168.1.100.53: 46872+ A? dns.msftncsi.com. (34)
13:56:25.453631 IP 192.168.1.2.62679 > 192.168.1.100.53: 46872+ A? dns.msftncsi.com. (34)
13:56:27.461986 IP 192.168.1.2.62679 > 192.168.1.100.53: 46872+ A? dns.msftncsi.com. (34)
13:56:31.468500 IP 192.168.1.2.62679 > 192.168.1.100.53: 46872+ A? dns.msftncsi.com. (34)
13:56:35.471250 IP 192.168.1.2.63325 > 192.168.1.100.53: Flags [S], seq 42195071, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:36.478724 IP 192.168.1.2.63325 > 192.168.1.100.53: Flags [S], seq 42195071, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:38.488703 IP 192.168.1.2.63325 > 192.168.1.100.53: Flags [S], seq 42195071, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:42.489073 IP 192.168.1.2.63325 > 192.168.1.100.53: Flags [S], seq 42195071, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:42.506936 IP 192.168.1.2.53963 > 192.168.1.100.53: 45148+ A? secure20.sync.com. (35)
13:56:43.517178 IP 192.168.1.2.53963 > 192.168.1.100.53: 45148+ A? secure20.sync.com. (35)
13:56:44.528806 IP 192.168.1.2.53963 > 192.168.1.100.53: 45148+ A? secure20.sync.com. (35)
13:56:46.536652 IP 192.168.1.2.53963 > 192.168.1.100.53: 45148+ A? secure20.sync.com. (35)
13:56:50.498523 IP 192.168.1.2.63325 > 192.168.1.100.53: Flags [S], seq 42195071, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
13:56:50.544202 IP 192.168.1.2.53963 > 192.168.1.100.53: 45148+ A? secure20.sync.com. (35)
13:57:07.973751 IP 192.168.1.2.57505 > 192.168.1.100.53: 2600+ A? bolt.dropbox.com. (34)
13:57:08.986074 IP 192.168.1.2.57505 > 192.168.1.100.53: 2600+ A? bolt.dropbox.com. (34)
13:57:09.989598 IP 192.168.1.2.57505 > 192.168.1.100.53: 2600+ A? bolt.dropbox.com. (34)
13:57:11.999591 IP 192.168.1.2.57505 > 192.168.1.100.53: 2600+ A? bolt.dropbox.com. (34)
13:57:16.014644 IP 192.168.1.2.57505 > 192.168.1.100.53: 2600+ A? bolt.dropbox.com. (34)
13:57:20.175570 IP 192.168.1.2.61693 > 192.168.1.100.53: 4355+ A? client.dropbox.com. (36)
13:57:21.187027 IP 192.168.1.2.61693 > 192.168.1.100.53: 4355+ A? client.dropbox.com. (36)
13:57:22.197641 IP 192.168.1.2.61693 > 192.168.1.100.53: 4355+ A? client.dropbox.com. (36)
13:57:24.203104 IP 192.168.1.2.61693 > 192.168.1.100.53: 4355+ A? client.dropbox.com. (36)
13:57:28.213121 IP 192.168.1.2.61693 > 192.168.1.100.53: 4355+ A? client.dropbox.com. (36)
13:57:30.140625 IP 192.168.1.2.54588 > 192.168.1.100.53: 32854+ A? profile.accounts.firefox.com. (46)
13:57:30.144316 IP 192.168.1.2.59084 > 192.168.1.100.53: 19035+ A? sync-1-us-west1-g.sync.services.mozilla.com. (61)
13:57:31.152030 IP 192.168.1.2.54588 > 192.168.1.100.53: 32854+ A? profile.accounts.firefox.com. (46)
13:57:31.152058 IP 192.168.1.2.59084 > 192.168.1.100.53: 19035+ A? sync-1-us-west1-g.sync.services.mozilla.com. (61)
13:57:32.155065 IP 192.168.1.2.59084 > 192.168.1.100.53: 19035+ A? sync-1-us-west1-g.sync.services.mozilla.com. (61)
13:57:32.155082 IP 192.168.1.2.54588 > 192.168.1.100.53: 32854+ A? profile.accounts.firefox.com. (46)
13:57:32.219544 IP 192.168.1.2.54584 > 192.168.1.100.53: 42920+ A? Home.Home. (27)
13:57:33.230522 IP 192.168.1.2.54584 > 192.168.1.100.53: 42920+ A? Home.Home. (27)
13:57:34.160154 IP 192.168.1.2.54588 > 192.168.1.100.53: 32854+ A? profile.accounts.firefox.com. (46)
13:57:34.160308 IP 192.168.1.2.59084 > 192.168.1.100.53: 19035+ A? sync-1-us-west1-g.sync.services.mozilla.com. (61)
13:57:35.240497 IP 192.168.1.2.54584 > 192.168.1.100.53: 42920+ A? Home.Home. (27)
13:57:38.173853 IP 192.168.1.2.59084 > 192.168.1.100.53: 19035+ A? sync-1-us-west1-g.sync.services.mozilla.com. (61)
13:57:38.173873 IP 192.168.1.2.54588 > 192.168.1.100.53: 32854+ A? profile.accounts.firefox.com. (46)
13:57:42.869495 IP 192.168.1.2.54334 > 192.168.1.100.53: 21078+ A? services.addons.mozilla.org. (45)
13:57:43.880351 IP 192.168.1.2.54334 > 192.168.1.100.53: 21078+ A? services.addons.mozilla.org. (45)
13:57:44.886789 IP 192.168.1.2.54334 > 192.168.1.100.53: 21078+ A? services.addons.mozilla.org. (45)
13:57:46.893584 IP 192.168.1.2.54334 > 192.168.1.100.53: 21078+ A? services.addons.mozilla.org. (45)
13:57:50.905696 IP 192.168.1.2.54334 > 192.168.1.100.53: 21078+ A? services.addons.mozilla.org. (45)
13:57:54.917530 IP 192.168.1.2.57850 > 192.168.1.100.53: 11729+ A? Home.Home. (27)
13:57:55.924767 IP 192.168.1.2.57850 > 192.168.1.100.53: 11729+ A? Home.Home. (27)
13:57:57.929346 IP 192.168.1.2.57850 > 192.168.1.100.53: 11729+ A? Home.Home. (27)
13:58:10.346963 IP 192.168.1.2.49900 > 192.168.1.100.53: 22480+ A? incoming.telemetry.mozilla.org. (48)
13:58:11.350531 IP 192.168.1.2.49900 > 192.168.1.100.53: 22480+ A? incoming.telemetry.mozilla.org. (48)
13:58:12.365703 IP 192.168.1.2.49900 > 192.168.1.100.53: 22480+ A? incoming.telemetry.mozilla.org. (48)
13:58:13.772651 IP 192.168.1.2.57016 > 192.168.1.100.53: 1914+ A? duckduckgo.com. (32)
13:58:14.378491 IP 192.168.1.2.49900 > 192.168.1.100.53: 22480+ A? incoming.telemetry.mozilla.org. (48)
13:58:14.780529 IP 192.168.1.2.57016 > 192.168.1.100.53: 1914+ A? duckduckgo.com. (32)
13:58:15.790443 IP 192.168.1.2.57016 > 192.168.1.100.53: 1914+ A? duckduckgo.com. (32)
13:58:17.796892 IP 192.168.1.2.57016 > 192.168.1.100.53: 1914+ A? duckduckgo.com. (32)
13:58:18.386932 IP 192.168.1.2.49900 > 192.168.1.100.53: 22480+ A? incoming.telemetry.mozilla.org. (48)
13:58:21.800833 IP 192.168.1.2.57016 > 192.168.1.100.53: 1914+ A? duckduckgo.com. (32)
13:58:22.395642 IP 192.168.1.2.53227 > 192.168.1.100.53: 15200+ A? pipeline-incoming-prod-elb-149169523.us-west-2.elb.amazonaws.com. (82)
13:58:23.406562 IP 192.168.1.2.53227 > 192.168.1.100.53: 15200+ A? pipeline-incoming-prod-elb-149169523.us-west-2.elb.amazonaws.com. (82)
13:58:24.420479 IP 192.168.1.2.53227 > 192.168.1.100.53: 15200+ A? pipeline-incoming-prod-elb-149169523.us-west-2.elb.amazonaws.com. (82)
13:58:26.431337 IP 192.168.1.2.53227 > 192.168.1.100.53: 15200+ A? pipeline-incoming-prod-elb-149169523.us-west-2.elb.amazonaws.com. (82)
13:58:26.648528 IP 192.168.1.2.49955 > 192.168.1.100.53: 10310+ AAAA? links.duckduckgo.com. (38)
13:58:27.515368 IP 192.168.1.2.52525 > 192.168.1.100.53: 2322+ AAAA? external-content.duckduckgo.com. (49)
13:58:27.662418 IP 192.168.1.2.49955 > 192.168.1.100.53: 10310+ AAAA? links.duckduckgo.com. (38)
13:58:28.517970 IP 192.168.1.2.52525 > 192.168.1.100.53: 2322+ AAAA? external-content.duckduckgo.com. (49)
13:58:28.672092 IP 192.168.1.2.49955 > 192.168.1.100.53: 10310+ AAAA? links.duckduckgo.com. (38)
13:58:29.525232 IP 192.168.1.2.52525 > 192.168.1.100.53: 2322+ AAAA? external-content.duckduckgo.com. (49)
13:58:30.432610 IP 192.168.1.2.53227 > 192.168.1.100.53: 15200+ A? pipeline-incoming-prod-elb-149169523.us-west-2.elb.amazonaws.com. (82)
13:58:30.679465 IP 192.168.1.2.49955 > 192.168.1.100.53: 10310+ AAAA? links.duckduckgo.com. (38)
13:58:31.535226 IP 192.168.1.2.52525 > 192.168.1.100.53: 2322+ AAAA? external-content.duckduckgo.com. (49)
13:58:34.434851 IP 192.168.1.2.59259 > 192.168.1.100.53: 63756+ A? Home.Home. (27)
13:58:34.687675 IP 192.168.1.2.49955 > 192.168.1.100.53: 10310+ AAAA? links.duckduckgo.com. (38)
13:58:35.438651 IP 192.168.1.2.59259 > 192.168.1.100.53: 63756+ A? Home.Home. (27)
13:58:35.546433 IP 192.168.1.2.52525 > 192.168.1.100.53: 2322+ AAAA? external-content.duckduckgo.com. (49)
13:58:37.452560 IP 192.168.1.2.59259 > 192.168.1.100.53: 63756+ A? Home.Home. (27)
13:58:39.561809 IP 192.168.1.2.52579 > 192.168.1.100.53: 6526+ AAAA? Home.Home. (27)
13:58:40.563689 IP 192.168.1.2.52579 > 192.168.1.100.53: 6526+ AAAA? Home.Home. (27)
13:58:42.574852 IP 192.168.1.2.52579 > 192.168.1.100.53: 6526+ AAAA? Home.Home. (27)
13:58:57.814338 IP 192.168.1.2.54828 > 192.168.1.100.53: 43320+ A? telemetry.dropbox.com. (39)
13:58:58.821829 IP 192.168.1.2.54828 > 192.168.1.100.53: 43320+ A? telemetry.dropbox.com. (39)
13:58:59.830547 IP 192.168.1.2.54828 > 192.168.1.100.53: 43320+ A? telemetry.dropbox.com. (39)
13:59:01.834569 IP 192.168.1.2.54828 > 192.168.1.100.53: 43320+ A? telemetry.dropbox.com. (39)
13:59:05.839382 IP 192.168.1.2.54828 > 192.168.1.100.53: 43320+ A? telemetry.dropbox.com. (39)
13:59:36.410438 IP 192.168.1.2.54268 > 192.168.1.100.53: 17851+ A? secure20.sync.com. (35)
13:59:37.419503 IP 192.168.1.2.54268 > 192.168.1.100.53: 17851+ A? secure20.sync.com. (35)
13:59:38.425796 IP 192.168.1.2.54268 > 192.168.1.100.53: 17851+ A? secure20.sync.com. (35)
13:59:40.438754 IP 192.168.1.2.54268 > 192.168.1.100.53: 17851+ A? secure20.sync.com. (35)
13:59:44.444015 IP 192.168.1.2.54268 > 192.168.1.100.53: 17851+ A? secure20.sync.com. (35)
14:00:40.087359 IP 192.168.1.2.58097 > 192.168.1.100.53: 475+ A? secure10.sync.com. (35)
14:00:40.130490 IP 192.168.1.2.58097 > 192.168.1.100.53: 475+ A? secure10.sync.com. (35)
14:00:41.131581 IP 192.168.1.2.58097 > 192.168.1.100.53: 475+ A? secure10.sync.com. (35)
14:00:43.134179 IP 192.168.1.2.58097 > 192.168.1.100.53: 475+ A? secure10.sync.com. (35)
14:00:43.404085 IP 192.168.1.2.60003 > 192.168.1.100.53: 65337+ A? duckduckgo.com. (32)
14:00:43.404260 IP 192.168.1.2.53561 > 192.168.1.100.53: 23914+ A? external-content.duckduckgo.com. (49)
14:00:43.448156 IP 192.168.1.2.53561 > 192.168.1.100.53: 23914+ A? external-content.duckduckgo.com. (49)
14:00:43.448177 IP 192.168.1.2.60003 > 192.168.1.100.53: 65337+ A? duckduckgo.com. (32)
14:00:44.455639 IP 192.168.1.2.60003 > 192.168.1.100.53: 65337+ A? duckduckgo.com. (32)
14:00:44.455656 IP 192.168.1.2.53561 > 192.168.1.100.53: 23914+ A? external-content.duckduckgo.com. (49)
14:00:46.458476 IP 192.168.1.2.53561 > 192.168.1.100.53: 23914+ A? external-content.duckduckgo.com. (49)
14:00:46.458493 IP 192.168.1.2.60003 > 192.168.1.100.53: 65337+ A? duckduckgo.com. (32)
14:00:47.138164 IP 192.168.1.2.58097 > 192.168.1.100.53: 475+ A? secure10.sync.com. (35)
14:00:50.463190 IP 192.168.1.2.60003 > 192.168.1.100.53: 65337+ A? duckduckgo.com. (32)
14:00:50.463218 IP 192.168.1.2.53561 > 192.168.1.100.53: 23914+ A? external-content.duckduckgo.com. (49)
14:00:52.123187 IP 192.168.1.2.49681 > 192.168.1.100.53: 57314+ A? incoming.telemetry.mozilla.org. (48)
14:00:52.163197 IP 192.168.1.2.49681 > 192.168.1.100.53: 57314+ A? incoming.telemetry.mozilla.org. (48)
14:00:53.169495 IP 192.168.1.2.49681 > 192.168.1.100.53: 57314+ A? incoming.telemetry.mozilla.org. (48)
14:00:55.186971 IP 192.168.1.2.49681 > 192.168.1.100.53: 57314+ A? incoming.telemetry.mozilla.org. (48)
14:00:59.192602 IP 192.168.1.2.49681 > 192.168.1.100.53: 57314+ A? incoming.telemetry.mozilla.org. (48)
14:01:03.208145 IP 192.168.1.2.49302 > 192.168.1.100.53: 10981+ A? Home.Home. (27)
14:01:04.214726 IP 192.168.1.2.49302 > 192.168.1.100.53: 10981+ A? Home.Home. (27)
14:01:06.221064 IP 192.168.1.2.49302 > 192.168.1.100.53: 10981+ A? Home.Home. (27)
14:01:18.972328 IP 192.168.1.2.56487 > 192.168.1.100.53: 54904+ A? img-getpocket.cdn.mozilla.net. (47)
14:01:19.014553 IP 192.168.1.2.56487 > 192.168.1.100.53: 54904+ A? img-getpocket.cdn.mozilla.net. (47)
14:01:20.023063 IP 192.168.1.2.56487 > 192.168.1.100.53: 54904+ A? img-getpocket.cdn.mozilla.net. (47)
14:01:22.032056 IP 192.168.1.2.56487 > 192.168.1.100.53: 54904+ A? img-getpocket.cdn.mozilla.net. (47)
14:01:26.038839 IP 192.168.1.2.56487 > 192.168.1.100.53: 54904+ A? img-getpocket.cdn.mozilla.net. (47)
14:01:27.986250 IP 192.168.1.2.59542 > 192.168.1.100.53: 55970+ A? profile.accounts.firefox.com. (46)
14:01:28.030811 IP 192.168.1.2.59542 > 192.168.1.100.53: 55970+ A? profile.accounts.firefox.com. (46)
14:01:29.042391 IP 192.168.1.2.59542 > 192.168.1.100.53: 55970+ A? profile.accounts.firefox.com. (46)
14:01:30.042575 IP 192.168.1.2.56481 > 192.168.1.100.53: 5905+ A? img-prod.pocket.prod.cloudops.mozgcp.net. (58)
14:01:30.082261 IP 192.168.1.2.56481 > 192.168.1.100.53: 5905+ A? img-prod.pocket.prod.cloudops.mozgcp.net. (58)
14:01:31.045828 IP 192.168.1.2.59542 > 192.168.1.100.53: 55970+ A? profile.accounts.firefox.com. (46)
14:01:31.092104 IP 192.168.1.2.56481 > 192.168.1.100.53: 5905+ A? img-prod.pocket.prod.cloudops.mozgcp.net. (58)
14:01:33.096122 IP 192.168.1.2.56481 > 192.168.1.100.53: 5905+ A? img-prod.pocket.prod.cloudops.mozgcp.net. (58)
14:01:35.077362 IP 192.168.1.2.59542 > 192.168.1.100.53: 55970+ A? profile.accounts.firefox.com. (46)
14:01:37.107212 IP 192.168.1.2.56481 > 192.168.1.100.53: 5905+ A? img-prod.pocket.prod.cloudops.mozgcp.net. (58)
14:01:41.110007 IP 192.168.1.2.54831 > 192.168.1.100.53: 16550+ A? Home.Home. (27)
14:01:42.125695 IP 192.168.1.2.54831 > 192.168.1.100.53: 16550+ A? Home.Home. (27)
14:01:42.506508 IP 192.168.1.2.61189 > 192.168.1.100.53: 40571+ A? getpocket.com. (31)
14:01:42.551864 IP 192.168.1.2.61189 > 192.168.1.100.53: 40571+ A? getpocket.com. (31)
14:01:42.567153 IP 192.168.1.2.57723 > 192.168.1.100.53: 55352+ AAAA? getpocket.com. (31)
14:01:42.613782 IP 192.168.1.2.57723 > 192.168.1.100.53: 55352+ AAAA? getpocket.com. (31)
14:01:42.983071 IP 192.168.1.2.51637 > 192.168.1.100.53: 6355+ AAAA? cdn.cookielaw.org. (35)
14:01:43.017365 IP 192.168.1.2.51637 > 192.168.1.100.53: 6355+ AAAA? cdn.cookielaw.org. (35)
14:01:43.559742 IP 192.168.1.2.61189 > 192.168.1.100.53: 40571+ A? getpocket.com. (31)
14:01:43.622497 IP 192.168.1.2.57723 > 192.168.1.100.53: 55352+ AAAA? getpocket.com. (31)
14:01:44.029378 IP 192.168.1.2.51637 > 192.168.1.100.53: 6355+ AAAA? cdn.cookielaw.org. (35)
14:01:44.138768 IP 192.168.1.2.54831 > 192.168.1.100.53: 16550+ A? Home.Home. (27)
14:01:45.574516 IP 192.168.1.2.61189 > 192.168.1.100.53: 40571+ A? getpocket.com. (31)
14:01:45.638110 IP 192.168.1.2.57723 > 192.168.1.100.53: 55352+ AAAA? getpocket.com. (31)
14:01:46.042101 IP 192.168.1.2.51637 > 192.168.1.100.53: 6355+ AAAA? cdn.cookielaw.org. (35)
14:01:49.583603 IP 192.168.1.2.61189 > 192.168.1.100.53: 40571+ A? getpocket.com. (31)
14:01:49.644537 IP 192.168.1.2.57723 > 192.168.1.100.53: 55352+ AAAA? getpocket.com. (31)
14:01:50.051302 IP 192.168.1.2.51637 > 192.168.1.100.53: 6355+ AAAA? cdn.cookielaw.org. (35)
14:01:53.660507 IP 192.168.1.2.54179 > 192.168.1.100.53: 11043+ A? use.typekit.net. (33)
14:01:53.706073 IP 192.168.1.2.54179 > 192.168.1.100.53: 11043+ A? use.typekit.net. (33)
14:01:53.751153 IP 192.168.1.2.64012 > 192.168.1.100.53: 12667+ AAAA? a1988.dscg1.akamai.net. (40)
14:01:53.784190 IP 192.168.1.2.64012 > 192.168.1.100.53: 12667+ AAAA? a1988.dscg1.akamai.net. (40)
14:01:54.720152 IP 192.168.1.2.54179 > 192.168.1.100.53: 11043+ A? use.typekit.net. (33)
14:01:54.797313 IP 192.168.1.2.64012 > 192.168.1.100.53: 12667+ AAAA? a1988.dscg1.akamai.net. (40)
14:01:56.721139 IP 192.168.1.2.54179 > 192.168.1.100.53: 11043+ A? use.typekit.net. (33)
14:01:56.797569 IP 192.168.1.2.64012 > 192.168.1.100.53: 12667+ AAAA? a1988.dscg1.akamai.net. (40)
14:02:00.723672 IP 192.168.1.2.54179 > 192.168.1.100.53: 11043+ A? use.typekit.net. (33)
14:02:00.802303 IP 192.168.1.2.64012 > 192.168.1.100.53: 12667+ AAAA? a1988.dscg1.akamai.net. (40)
14:02:04.732970 IP 192.168.1.2.49944 > 192.168.1.100.53: 30592+ A? Home.Home. (27)
14:02:04.809560 IP 192.168.1.2.60930 > 192.168.1.100.53: 59741+ AAAA? Home.Home. (27)
14:02:05.734166 IP 192.168.1.2.49944 > 192.168.1.100.53: 30592+ A? Home.Home. (27)
14:02:05.811679 IP 192.168.1.2.60930 > 192.168.1.100.53: 59741+ AAAA? Home.Home. (27)
14:02:07.742809 IP 192.168.1.2.49944 > 192.168.1.100.53: 30592+ A? Home.Home. (27)
500 packets captured
500 packets received by filter
0 packets dropped by kernel
Last edited by Rhizome on Sat Jul 03, 2021 7:04 pm, edited 1 time in total.
Post Reply