weird reports for LAN and Guest blocks

[michmoor]

@motivio I would first correlate the IP and MAC to make sure it’s the charger.

[motivio]

@michmoor said in weird reports for LAN and Guest blocks:

@motivio I would first correlate the IP and MAC to make sure it’s the charger.

I did.

[michmoor]

@motivio Then your device made a DNS query to snapchat.
If you really want to disprove me or even hunt down what your charger is doing, run a pcap off the pfsense interface specifically looking for dns queries.

[NogBadTheBad]

@michmoor Don't even need to do a packet capture if you're running unbound / DNS Resolver, add the following to the custom options and lookups will show in the logs:-

log-queries: yes
log-replies: yes
log-tag-queryreply: yes

[michmoor]

@NogBadTheBad yep you're absolutely right.

[motivio]

@nogbadthebad @michmoor

Here the results from the Log of the DNS Resolver and the report for the same time from pfBlockerNG.
The IP 192.168.100.99 did not send any DNS for snapchat. But in the report it's showing.

[NogBadTheBad]

@motivio The second line shows 192.168.1.202 doing a lookup to a snapchat FQDN.

What is 192.168.1.202?

[motivio]

@nogbadthebad said in weird reports for LAN and Guest blocks:

@motivio The second line shows 192.168.1.202 doing a lookup to a snapchat FQDN.

What is 192.168.1.202?

That’s an iPhone of my kids. They are using Snapchat.

[NogBadTheBad]

@motivio I'd just leave it logging for a while and check later.

Might even be a issue with the pfBlocker report.

[michmoor]

@motivio lets get that pcap started on pfsense.
Not sure how often it's querying for snapchat but let it run until the alert in pfblocker comes up.
Make sure count is set to 0
Stop the capture
Download the capture
Open the capture
search for the string in the capture. Edit > Find Packet > Set to string