
I envision the capsule mounted on a metal rod / pipe that can be inserted through a hole from the back (approx. I have L-shaped hive entrances, so coming from the front will unlikely yield good results. Furthermore (what I find the most attractive), the capsule has a very small size of 6mm at the biggest dimension. Sheets/Panasonic Electronic Components/WM-61A.pdfĪs you can see from the datasheet the frequency response is flat. The Panasonic WM-60AY that they used is not being manufactured anymore apparently, however I understand the WM-61A is the replacement for it. Of course, you have options if you want to expand from there.I'll be attempting to build this over the winter: For non-commercial use, the free account tier works fine for this. A Maxmind account with which to download the "GeoIP Countries CSV" database. apt instead of yum) but you can probably muddle through it. If using something Debian / Ubuntu based, your package management commands will differ (e.g. I'm using Amazon Linux 2 on EC2, but the steps are probably similar for any CentOS / RHEL based Linux distribution.

But I thought someone else might find it useful.

You are responsible for your own systems. Note: I'm mostly documenting this so that I can repeat it again later without having to rediscover the dependencies / steps. Useful if you're building, say, a game server or similar for only a small group of friends and you know where they all are! With the geoip module you can easily use iptables to restrict traffic to only those countries you know your service will be accessed from.

As doing so not only reduces the load on your service, but also reduces the likelihood of your service being tagged by some unforeseen exploit.Įnter: Maxmind's GeoIP database and the xtables-addons GeoIP filter. But "defense in depth" dictates that if you can filter out a large percentage of these requests, you should. No big deal, just build secure services, right? Generally, I restrict "important" / remote access services to my home egress IPs, but for services that I expect to be generally available I cannot do that.Īnyone who has hosted a service on the public Internet knows that it's a matter of minutes after the service comes online before it starts being probed by all manner of scanners, exploit scripts, curious hackers, botnets, &etc. I have a few Amazon Linux 2 EC2 instances that I run for personal use.
