{"id":19353,"date":"2021-01-16T09:53:51","date_gmt":"2021-01-16T14:53:51","guid":{"rendered":"https:\/\/nuxx.net\/blog\/?p=19353"},"modified":"2021-01-16T14:45:11","modified_gmt":"2021-01-16T19:45:11","slug":"a-home-network-troubleshooting-journey","status":"publish","type":"post","link":"https:\/\/nuxx.net\/blog\/2021\/01\/16\/a-home-network-troubleshooting-journey\/","title":{"rendered":"A Home Network Troubleshooting Journey"},"content":{"rendered":"\n
\"\"<\/a><\/figure><\/div>\n\n\n\n

This week I moved from UniFi<\/a> to a new setup that included OPNsense<\/a> on the edge to handle firewall, NAT<\/a>, and other such tasks on the home network. Built in to OPNsense is a basic NetFlow<\/a> traffic analyzer called Insight<\/a>. Looking at this and turning on Reverse lookup<\/em> something strange popped out: ~22% of the traffic coming in from the internet over the last two hours was from just two hosts: dynamic-75-76-44-147.knology.net<\/code> and dynamic-75-76-44-149.knology.net<\/code>.<\/p>\n\n\n\n

While reverse DNS worked to resolve the IPs to hostnames (75.76.44.147<\/code> to dynamic-75-76-44-147.knology.net<\/code> and 75.76.44.149<\/code> to dynamic-75-76-44-149.knology.net<\/code>), forward lookup of those hostnames didn’t work. This didn’t really surprise me as the whole DNS situation on the WOW\/Knowlogy network is poor, but it did make me more curious. Particularly strange was the IPs being are so close together.<\/p>\n\n\n\n

To be sure this is Knology (ruling out intentionally-misleading reverse DNS) I used whois<\/a> to confirm the addresses are owned by them:<\/p>\n\n\n\n

NetRange: 75.76.0.0 - 75.76.46.255
CIDR: 75.76.46.0\/24, 75.76.40.0\/22, 75.76.0.0\/19, 75.76.44.0\/23, 75.76.32.0\/21
NetName: WIDEOPENWEST
NetHandle: NET-75-76-0-0-1
Parent: NET75 (NET-75-0-0-0-0)
NetType: Direct Allocation
OriginAS: AS12083
Organization: WideOpenWest Finance LLC (WOPW)
RegDate: 2008-02-13
Updated: 2018-08-27
Ref: https:\/\/rdap.arin.net\/registry\/ip\/75.76.0.0<\/code><\/p>\n\n\n\n

My home ISP is Wide Open West (WOW)<\/a>, and Knology<\/a> is an ISP that they bought in 2012. While I use my ISP directly for internet access (no VPN tunnel to elsewhere), I run my own DNS to avoid their service announcement redirections, so why would I be talking to something else on my ISP’s network?<\/p>\n\n\n\n

Could this be someone doing a bunch of scanning of my house? Or just something really misconfigured doing a bunch of broadcasting? Let’s dig in and see…<\/p>\n\n\n\n

\"\"<\/a><\/figure><\/div>\n\n\n\n

First I used the Packet capture<\/a> function in OPNsense to grab a capture on the WAN interface filtered to these two IPs. Looking at it in Wireshark<\/a> showed it was all HTTPS. Hmm, that’s weird…<\/p>\n\n\n\n

A couple coworkers and I have Plex<\/a> libraries shared with each other, maybe that’s it? The port isn’t right (Plex usually uses 32400) but maybe one of them are running on it in 443 (HTTPS)… But why the two IPs so close to each other? Maybe one of them are getting multiple IPs from their cable modem, have dual WAN links configured on their firewall, and it’s bouncing between them… (This capture only showed the middle of a session, so there was no certificate exchange present to get any service information from.)<\/p>\n\n\n\n

Next I did another packet capture on the LAN interface to see if it’s a computer on the network or OPNsense as the local endpoint. This showed it’s coming from my main personal computer, a 27″ iMac at 192.168.0.8<\/code> \/ myopia.--------.nuxx.net<\/code>, so let’s look there. (Plex doesn’t run on the iMac, so that’s ruled out.)<\/p>\n\n\n\n

Conveniently the -k<\/code> argument to tcpdump<\/a> on macOS adds packet metadata, such as process name, PID, etc. A basic capture\/display on myopia<\/code> with tcpdump -i en0 -k NP host 75.76.44.149 or 75.76.44.147<\/code> to show all traffic going to and from those hosts identified Firefox<\/a> as the source:<\/p>\n\n\n\n

07:39:57.873076 pid firefox.97353<\/strong> svc BE pktflags 0x2 IP myopia.--------.nuxx.net.53515 > dynamic-75-76-44-147.knology.net.https<\/strong>: Flags [P.], seq 19657:19696, ack 20539524, win 10220, options [nop,nop,TS val 3278271236 ecr 1535621504], length 39
07:39:57.882070 IP dynamic-75-76-44-147.knology.net.https > myopia.--------.nuxx.net.53515: Flags [P.], seq 20539524:20539563, ack 19696, win 123, options [nop,nop,TS val 1535679857 ecr 3278271236], length 39<\/code><\/p>\n\n\n\n

Well, okay… Odd that my browser would be talking so much HTTPS to my ISP directly. I double-checked that DNS-over-HTTPS<\/a> was disabled, so it’s not that…<\/p>\n\n\n\n

Maybe I can see what these servers are? Pointing curl<\/a> at one of them to show the headers, the server header<\/a> indicated proxygen-bolt<\/a> which is a Facebook framework:<\/p>\n\n\n\n

c0nsumer@myopia Desktop % curl --insecure -I https:\/\/75.76.44.147<\/strong>
HTTP\/2 400
content-type: text\/plain
content-length: 0
server: proxygen-bolt<\/strong>
date: Sat, 16 Jan 2021 13:22:57 GMT
c0nsumer@myopia Desktop %<\/code><\/p>\n\n\n\n

Now we’re getting somewhere…<\/p>\n\n\n\n

Finally I pointed openssl<\/a> at the IP to see what certificate it’s presenting and it’s a wildcard cert for a portion of Facebook’s CDN<\/a>:<\/p>\n\n\n\n

c0nsumer@myopia Desktop % openssl s_client -showcerts -connect 75.76.44.149:443 <\/dev\/null<\/strong>
CONNECTED(00000003)
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert High Assurance EV Root CA
verify return:1
depth=1 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
verify return:1
depth=0 C = US, ST = California, L = Menlo Park, O = \"Facebook, Inc.\", CN = *.fdet3-1.fna.fbcdn.net<\/strong>
verify return:1
[SNIP]<\/code><\/p>\n\n\n\n

As a final test I restarted tcpdump<\/code> on the iMac then closed the Facebook tab I had open in Firefox and the traffic stopped.<\/p>\n\n\n\n

So there’s our answer. All this traffic is to Facebook CDN instances on the Wide Open West \/ Knology network. It sure seems like a lot for a tab just sitting open in the background, but hey… welcome to the modern internet.<\/p>\n\n\n\n

\n\n\n\n
\"\"<\/a><\/figure><\/div>\n\n\n\n

I could have received more information from OPNsense’s Insight by clicking on the pie slice shown above to look at that host in the Details view<\/a>, but it seems to have an odd quirk. When the Reverse lookup<\/em> box is checked, clicking the pie slice to jump to the Details<\/em> view automatically puts the hostname in the (src) Address<\/em> field, which returns no results (it needs an IP address). I thought this was the tool failing, so I looked to captures for most of the info.<\/p>\n\n\n\n

Later on I realized that filtering on the IP showed a bunch more useful information, including two other endpoints within the network talking to these servers (mobile phones), and that HTTPS was also running over UDP, indicating QUIC<\/a>.<\/p>\n\n\n\n

(Bug 4609<\/a> was submitted for this issue and AdSchellevis<\/a> fixed it within a couple hours via commit c797bfd<\/a>.)<\/p>\n","protected":false},"excerpt":{"rendered":"

This week I moved from UniFi to a new setup that included OPNsense on the edge to handle firewall, NAT, and other such tasks on…<\/p>\n

Continue readingA Home Network Troubleshooting Journey<\/span><\/a><\/div>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,13],"tags":[],"class_list":["post-19353","post","type-post","status-publish","format-standard","hentry","category-around-the-house","category-computers","entry"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts\/19353","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/comments?post=19353"}],"version-history":[{"count":20,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts\/19353\/revisions"}],"predecessor-version":[{"id":19384,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts\/19353\/revisions\/19384"}],"wp:attachment":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/media?parent=19353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/categories?post=19353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/tags?post=19353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}