http://www.multicastdns.org/
Might make a good read sometime
http://www.makeuseof.com/pages/best-linux-distributions
Read an article similar to this recently, and can’t quite figure out where I misplaced it. Either way, thinking of loading up one of my newer boxes with Linux Mint to see how it will handle as a daily driver.
GoDaddy – $2.99/mo, generally feature rich, does lack dynamic DNS support.
ZoneEdit – quite possibly free for present needs, supports dynamic DNS.
Dyn – $30/yr, easy/obvious client support, some (admittedly high) limitations on querys and the like.
easyDNS – $20/yr, appears to support dynamic, (high) limits.
As a whole you’re really becoming a giant frustration. Your secure transfer protocols still aren’t VRF aware (client applications – i.e., scp) after how many years and incantations of IOS. The sole benefit I get from maintaining SmartNet contracts on equipment (software updates… TAC would be a joke, but it’s not funny) is becoming pointless, as the updates are just as broken as the software the boxes shipped with, they’ve just shuffled the bugs to new locations in the code. You finally get a system to the point where it’s just about stable, and you end-of-life it. Your supply chain is among the worst I’ve ever seen, to put it nicely. And with the last couple of generations of ISR’s, I’ve even had some doubts about the quality of the hardware. I’ve dealt with a few really sharp individuals in your organization over the years, and I hate to take anything away from them, but this slide on the whole makes me wonder if it’s just rime to find something… anything… else.
Looking towards configuring StrongSwan as an IPSec VPN endpoint for Android. The long-term goal is to set up a VPN configuration in which the phone automatically forwards all traffic through the IPSec VPN tunnel to be routed via my home connection unless 1.) the phone is connected to my private wireless network (perhaps one dedicated to the phone) or 2.) I manually disable forwarding, possibly to be resumed automatically after a timeout, and definitely to be resumed at phone reboot. On the private network, will be doing some HTTP filtering, mangling, redirecting, and blocking; some file sync’ing and/or “private cloud” streaming; some monitoring; some outright blocking; some home automation… all kinds of wonderful, fun and exciting things. I’m coming up on a year since I left the giant red atrocity that is Verizon and purchased an Android phone and plan from US Cellular (which has been an outstanding upgrade in every way… both the phone and the carrier), and I’m just now getting things in place to begin configuring the VPN hub, hence “long term”. This post is primarily to note a few pages with hints, tips, and configurations for Android (and iPhone) device connections to a (Open|Strong)Swan server. The biggest problem I seem to be encountering thus far is that I don’t think any I have yet encountered are descriptive in setting up an “always on, automatic at boot” connection, and I’m thinking I’ll need to get a working tun.ko module for my phone to really make this happen as I would like. We shall see.
http://www.semicomplete.com/articles/dynamic-dns-with-dhcp/
May get around to setting this up a little while down the road.
Trying to get ntpd to stop creating listening sockets is a royal pain in the ass. Sure, I can set a firewall rule that blocks access to the port on undesired interfaces, but it's more work to make that happen, and it's just not as clean. Here's what I finally ended up doing to stop creating default (0.0.0.0:123 for IPv4 and :::123 for IPv6) listeners and just set a listening socket on one address on my internal interface. Hopefully it helps someone else out. # Add to ntp.conf, in order interface ignore all interface ignore ipv4 interface ignore ipv6 interface listen 192.168.0.1
While there’s not a gaping security window with NTP, I just feel a little safer not having anything listening at all.
You are currently browsing the archives for the Technology category.
