GiuseppeAndTheYeti

I've been using Weatherbug as my "gold standard" for years as an athletic trainer to track incoming storms and lightning strike data during outdoor sports events, so those features are pretty important to me. I've just gotten so fed up with their shitty practices. The ads are getting worse and worse(to the point that they're almost exclusively clickbait malware) and they keep nudging me with push notifications to buy the ad free version. Which is of course a subscription instead of a one time payment. They even tested locking the future radar behind a paywall briefly. They must have gotten hammered by uninstalls because it didn't last very long, but I'm not comfortable with staying engaged with a company that's constantly trying to see what features they can get away with removing.

Thanks!

I'm trying to set up a Pi-hole on my in-laws' home network. I've got everything configured on the pi but ad-blocking wasn't working. So I did some digging into the logs and found that DNS requests were all coming from the router.

After some reading it seems that the DHCP server that the router used was adding a DNS suffix to all requests (search.charter), so I turned off the DHCP server on the router and used pi-hole's built-in DHCP to see if this would resolve the issue. I didn't have enough time to test the fix, but here's my understanding of what was happening before I changed the configuration:

I set the primary DNS server to the IP address of the pi-hole in the router settings so they would have network wide adblocking. All of the clients get a DHCP assigned DNS server address which was set to the router's address. I would input example.com into a client's browser, the DNS request would be sent to the router, then the router would act as a client in the pi-hole logs. Pi-hole tells the router that example.com is found at 192.158.1.38 and the ads being hosted on the website are at 0.0.0.0. The router sees that the DNS server didn't return a result for one of the queries, so it goes to an upstream DNS server hosted by the ISP where they provide the IP for the ad. Both addresses are sent along to the client device and the pi-hole shows the ad domain as being blocked.

Is that true? Did changing the DHCP server to the Pi-hole fix the problem? Is there anything more that I need to do? Did I totally whiff on troubleshooting? Let me know if you need more information. Any help would be appreciated since I'm trying to learn a little bit more about networking and take a little more control of my home network. Thanks!

Some background. I set up a Jellyfin server for my family to host TV shows and movies for them for free. I finally had enough of Xfinity and switched to T-Mobile 5G home internet, but in doing so, I lost the ability to control my network's port forwarding. I'm spending literally half the previous amount on internet and getting the same speeds, so I don't plan on going back.

What I do plan on doing is setting up a new server at my parent's house and running it on their network. Problem is that I'm 2 hours away. My plan is to use Qbit, jackett, and the arrs to automatically download torrents. Is there any way to automatically rename torrents to match Jellyfin's naming convention for organization and metadata downloads?

(Disclaimer: yes, I bought a $180 4TB Crucial SSD too, but my family split the cost with me since they're going to use my Jellyfin server. Whether that counts towards the final cost is up to you. And the electricity cost is pretty negligible to run a Le Potato as a server, but I guess you can count that too.)

So this all started rather innocently. I was fed up with all the ads being shoved in my face with everything I do, so I finally decided that it was time to set up a Pi-hole on a single board computer. For me, it ended up being a Le Potato. I had never even touched Linux prior to this, so it took me a day or so to get everything set up. I love learning new things so I kind of got hooked on learning my way around Linux basics and decided that I was going to upgrade my setup to a Pi-hole + VPN using wireguard. That was kind of a beast to configure as a novice but I got that to work after about a week. Now I was getting ad free content anywhere I wanted on my phone. I rode that high for a few weeks until I realized that I was just scratching the surface of what I could do with my little $30 Linux server setup and this is where I really got to upgrade.

I had learned of Jellyfin from LTT and decided that I was going to test it out. I set up the Jellyfin server on the Le Potato and I was off to the races. Now I just needed content. I read through some of the wiki and settled on Mullvad+qbittorrent to find the content I wanted. With everything configured it still didn't really feel complete, so I set up profiles for my family members and gave them their own passwords to access the content. I quickly realized that 64 GB was not nearly enough (without a rolling library) and I was getting annoyed with having to constantly swith the flash drive I was using between the Le Potato and the laptop where I was downloading my content. So I went out and bought a 4TB USB SSD from Crucial and set up access as a NAS on Ubuntu with Samba.

It's just now finally set up. My family texts me to let me know what it is they're wanting to watch, I torrent it, upload it to my NAS, and Jellyfin streams that content to my family 100% free. I've turned my 6 family members into pirates and they barely even realize it.