<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Networks on Holyarmy.org</title>
		<link>https://holyarmy.org/categories/networks/</link>
		<description>Recent content in Networks on Holyarmy.org</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 24 Dec 2016 18:18:25 +0000</lastBuildDate>
		
			<atom:link href="https://holyarmy.org/categories/networks/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Ubuntu USB Ethernet Naming for Alias and VLAN Interfaces</title>
				<link>https://holyarmy.org/2016/12/ubuntu-usb-ethernet-naming-for-alias-and-vlan-interfaces/</link>
				<pubDate>Sat, 24 Dec 2016 18:18:25 +0000</pubDate>
				<guid>https://holyarmy.org/2016/12/ubuntu-usb-ethernet-naming-for-alias-and-vlan-interfaces/</guid>
				<description>&lt;p&gt;In my ongoing adventures of playing with the &lt;a href=&#34;http://www.amazon.com/gp/product/B00IT1WJZQ/ref=as_li_tl?ie=UTF8&amp;amp;camp=1789&amp;amp;creative=9325&amp;amp;creativeASIN=B00IT1WJZQ&amp;amp;linkCode=as2&amp;amp;tag=benjasherm-20&amp;amp;linkId=GCUVONIR4FLBOQSI&#34;&gt;Chromebox&lt;/a&gt; as a firewall, I eventually found a reason to use stock Ubuntu 16.04 instead of VyOS.&lt;/p&gt;&#xA;&lt;p&gt;For the most part, devices just work as you’d expect under Ubuntu. Even my USB ethernet network interface (NIC) devices work fine. But I eventually noticed a problem.&lt;/p&gt;&#xA;&lt;p&gt;By default USB NICs under Ubuntu 16.04 (which uses systemd &amp;amp; udev) are named “enxABCDEF123456” where ABCDEF123456 is the full MAC address of the device.&lt;/p&gt;</description>
			</item>
			<item>
				<title>VyOS on an Asus Chromebox M004U</title>
				<link>https://holyarmy.org/2016/08/vyos-on-an-asus-chromebox-m004u/</link>
				<pubDate>Thu, 04 Aug 2016 15:38:55 +0000</pubDate>
				<guid>https://holyarmy.org/2016/08/vyos-on-an-asus-chromebox-m004u/</guid>
				<description>&lt;p&gt;This is a bit of a follow up from my &lt;a href=&#34;https://holyarmy.org/2015/05/esxi-on-an-asus-chromebox-m004u/&#34;&gt;last post&lt;/a&gt;. I’ve still got my &lt;a href=&#34;http://www.amazon.com/gp/product/B00IT1WJZQ/ref=as_li_tl?ie=UTF8&amp;amp;camp=1789&amp;amp;creative=9325&amp;amp;creativeASIN=B00IT1WJZQ&amp;amp;linkCode=as2&amp;amp;tag=benjasherm-20&amp;amp;linkId=GCUVONIR4FLBOQSI&#34;&gt;Asus Chromebox&lt;/a&gt;. I’m not running ESXi any more… but something I do want to try out is &lt;a href=&#34;http://vyos.net/&#34;&gt;VyOS&lt;/a&gt;. Why? Well, my original intent when purchasing the Chromebox was to play around with it, but then I really did expect it to replace my home router. I’ve used pfSense for a long time, but I’m curious about VyOS because I know several people using EdgeRouter Lite which uses EdgeOS, a fork of VyOS. So I wanted to play around on existing hardware.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ESXi on an Asus Chromebox M004U</title>
				<link>https://holyarmy.org/2015/05/esxi-on-an-asus-chromebox-m004u/</link>
				<pubDate>Sat, 23 May 2015 18:51:55 +0000</pubDate>
				<guid>https://holyarmy.org/2015/05/esxi-on-an-asus-chromebox-m004u/</guid>
				<description>&lt;p&gt;I recently stumbled across the &lt;a href=&#34;http://www.amazon.com/gp/product/B00IT1WJZQ/ref=as_li_tl?ie=UTF8&amp;amp;camp=1789&amp;amp;creative=9325&amp;amp;creativeASIN=B00IT1WJZQ&amp;amp;linkCode=as2&amp;amp;tag=benjasherm-20&amp;amp;linkId=GCUVONIR4FLBOQSI&#34;&gt;ASUS CHROMEBOX-M004U&lt;/a&gt;. It’s a Chromebox, which is cool in its own right, but I was interested in using it’s dual-core Celeron Haswell CPU, expandable RAM (up to 16GB), and M2 Sata storage for other purposes.&lt;/p&gt;&#xA;&lt;p&gt;First things first, you’ve got to enable the box to run things other than ChromeOS… Thankfully that’s well documented ( &lt;a href=&#34;http://kodi.wiki/view/ASUS_Chromebox&#34;&gt;http://kodi.wiki/view/ASUS_Chromebox&lt;/a&gt; ), so I won’t go into detail at this time. But I will say, I used the standalone, custom coreboot firmware and chose the headless option, as my current planned use cases are for servers. Apparently you want non-headless if you plan to use the box as a Plex Home Theater or Kodi box. Oh, also, I set it to boot first from USB if  available.&lt;/p&gt;</description>
			</item>
			<item>
				<title>VPN on Ubuntu Linux with Juniper Network Connect</title>
				<link>https://holyarmy.org/2009/06/vpn-on-ubuntu-linux-with-juniper-network-connect/</link>
				<pubDate>Mon, 15 Jun 2009 23:13:25 +0000</pubDate>
				<guid>https://holyarmy.org/2009/06/vpn-on-ubuntu-linux-with-juniper-network-connect/</guid>
				<description>&lt;p&gt;There’s one standard document on HOWTO get Network Connect working on Ubuntu Linux. It’s mad scientist’s doc: &lt;a href=&#34;http://mad-scientist.us/juniper.html&#34;&gt;http://mad-scientist.us/juniper.html&lt;/a&gt; . However, there are a few things not covered. I’ll assume that you’ve followed mad scientist’s excellent guide before going any further.&lt;/p&gt;&#xA;&lt;h3 id=&#34;issue-1-64-bit-ubuntu&#34;&gt;Issue #1: 64-bit Ubuntu&lt;/h3&gt;&#xA;&lt;p&gt;By default, when you install java on your 64-bit system, you get a 64-bit java. No surprise there, right? Well, Juniper’s tools don’t play nice with 64-bit java. If you attempt to start the &lt;strong&gt;junipernc&lt;/strong&gt; script you’ll promptly see the “VPN has failed!” error message.&lt;figure id=&#34;attachment_400&#34; style=&#34;width: 204px&#34; class=&#34;wp-caption alignnone&#34;&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Fight Back! (When VPN Clients Mis-Behave)</title>
				<link>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</link>
				<pubDate>Wed, 23 Jul 2008 18:20:19 +0000</pubDate>
				<guid>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</guid>
				<description>&lt;p&gt;I have to use VPNs at work. Specifically, to access my production webservers (etc), I have to use a Cisco VPN client. Sadly, the VPN concentrator overrides my choice of allowing local LAN access. So, when I am on the VPN, I have my DNS options changed so I can’t use any local servers. This is a serious, serious pain. So painful in fact, that many times instead of fight with it, I simply would run a Windows session in VMware (on my Mac) and connect the VPN there. This has drawbacks too, but it’s better than not having local network access.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Beating the Cisco VPN Client Error 51 On Leopard</title>
				<link>https://holyarmy.org/2008/07/beating-the-cisco-vpn-client-error-51-on-leopard/</link>
				<pubDate>Tue, 22 Jul 2008 16:10:01 +0000</pubDate>
				<guid>https://holyarmy.org/2008/07/beating-the-cisco-vpn-client-error-51-on-leopard/</guid>
				<description>&lt;p&gt;I had this error popup today on my Mac OS X Lepopard 10.5.4 machine.&lt;/p&gt;&#xA;&lt;img class=&#34;alignnone size-medium wp-image-309&#34; title=&#34;vpnerr51&#34; src=&#34;https://holyarmy.org/files/2008/07/vpnerr51.png&#34; alt=&#34;Cisco VPN Client Error 51&#34; /&gt;&#xA;&lt;p&gt;This is not cool as, well, I NEED MY VPN TO WORK!&lt;/p&gt;&#xA;&lt;p&gt;Thankfully google came to my rescue. The solution is to execute the following in Terminal:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Thanks for the answer, &lt;a href=&#34;http://virtuallyshocking.com/2008/06/26/cisco-vpn-client-error-51-after-leopard-1053-upgrade/&#34;&gt;VirtuallyShocking.com&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Investigating OpenID</title>
				<link>https://holyarmy.org/2008/05/investigating-openid/</link>
				<pubDate>Tue, 27 May 2008 15:02:43 +0000</pubDate>
				<guid>https://holyarmy.org/2008/05/investigating-openid/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://cephas.net/blog/2008/05/24/links-5-23-2008/&#34;&gt;Aaron (one of my co-workers)&lt;/a&gt;, recently posted a link about OpenID. I’ve given &lt;a href=&#34;http://openid.net/&#34;&gt;OpenID&lt;/a&gt; only cursory glances over the last year, but the Coding Horror link in Aaron’s post had a comment to this &lt;a href=&#34;http://video.google.com/videoplay?docid=2288395847791059857&#34;&gt;Google Video where Simon Willison gives a Google Tech Talk on The Implications of OpenID&lt;/a&gt;. The video is nearly a year old, but to date, it’s done more to convince me to get on the OpenID bandwagon than anything else.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Advertising Linux Services via Avahi/Bonjour</title>
				<link>https://holyarmy.org/2008/01/advertising-linux-services-via-avahibonjour/</link>
				<pubDate>Sun, 27 Jan 2008 22:20:42 +0000</pubDate>
				<guid>https://holyarmy.org/2008/01/advertising-linux-services-via-avahibonjour/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; &lt;em&gt;most of this information is still correct but an update for combining service definitions into one file and setting an icon is available here: &lt;a href=&#34;https://holyarmy.org/2008/11/bonjour-avahi-addendum&#34;&gt;bonjour-avahi-addendum&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;In my last post I outlined how I followed others’ directions to enable netatalk on Linux and Time Machine backups to a shared AFP folder. Originally, I also described how to put all your shares on netatalk. I suppose if only have Mac clients or you REALLY want to use AFP, you can do so. As I worked with files over AFP shares, I started noticing that the performance seemed to be quite bad. No, I didn’t benchmark, but copying large video files to a shared folder over my gigabit network was substantially slower over AFP (netatalk) than over CIFS/SMB (samba). I use my network shares pretty heavily, so this was a concern. Also, netatalk tries very hard to replicate an HFS filesystem complete with resource fork support. This means that your shared directories end up with lots of extra folders named “.AppleDouble”(and a few others) containing Mac specific info. (Note: even on CIFS you’ll get the “.AppleDB” folders unless you disable a setting in Finder. I can deal with .AppleDB better than .AppleDouble AND .AppleDB) So, because of these two issues I decided to try using CIFS and samba again.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Time Machine backup to Linux via Netatalk</title>
				<link>https://holyarmy.org/2008/01/time-machine-backup-to-linux-via-netatalk/</link>
				<pubDate>Thu, 24 Jan 2008 07:26:49 +0000</pubDate>
				<guid>https://holyarmy.org/2008/01/time-machine-backup-to-linux-via-netatalk/</guid>
				<description>&lt;div&gt;&#xA;  So, when I got the upgrade from Tiger to Leopard on my MacBook Pro, I was looking for a good backup solution. I&amp;#8217;ve used &lt;a href=&#34;http://samba.anu.edu.au/rsync/&#34; target=&#34;_blank&#34;&gt;rsync&lt;/a&gt; in the past, but when I saw that Apple had a new &lt;a href=&#34;http://www.apple.com/macosx/features/timemachine.html&#34; target=&#34;_blank&#34;&gt;Time Machine&lt;/a&gt; backup tool, I was curious to give it a shot. The catch is you basically needed an external USB or Firewire drive, until they recently came out with the &lt;a href=&#34;http://www.apple.com/timecapsule/&#34; target=&#34;_blank&#34;&gt;Time Capsule&lt;/a&gt;. Anyway, tonight I got the itch to really see if I could make Time Machine work without buying extra hardware. I mean, seriously, I&amp;#8217;ve got a good hunk of mirrored disk sitting on my home server; that seems like a good place to do backups.&#xA;&lt;/div&gt;&#xA;&lt;div&gt;&#xA;  Some googling found me this &lt;a href=&#34;http://www.fey.ca/blarchives/2007/11/18/time_machine_and_netatalk.html&#34; target=&#34;_blank&#34;&gt;link&lt;/a&gt; to a blogger who&amp;#8217;d done it!&#xA;&lt;/div&gt;&#xA;&lt;div&gt;&#xA;&lt;/div&gt;&#xA;&lt;div&gt;&#xA;  I&amp;#8217;ll make my own version of this post, since I had a few differences from the original I where I found the info.&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Network Directory Services</title>
				<link>https://holyarmy.org/2007/10/network-directory-services/</link>
				<pubDate>Sat, 06 Oct 2007 21:00:41 +0000</pubDate>
				<guid>https://holyarmy.org/2007/10/network-directory-services/</guid>
				<description>&lt;p&gt;Network directory services are core to Internet functionality. The &lt;a href=&#34;http://en.wikipedia.org/wiki/Domain_Name_System&#34;&gt;Domain Name System (DNS)&lt;/a&gt; provides a global (and/or local) directory of hosts and services. &lt;a href=&#34;http://en.wikipedia.org/wiki/LDAP&#34;&gt;Lightweight Directory Access Protocol (LDAP)&lt;/a&gt; servers can provide some of the same information as DNS (or be used to back DNS), but are more frequently used to create network user databases, store user group information, providing centralized account information and password storage.&lt;/p&gt;&#xA;&lt;p&gt;I recently completed an upgrade of these two core services on a network I manage. We had been running outdated (but functional) &lt;a href=&#34;http://en.wikipedia.org/wiki/BIND&#34;&gt;BIND&lt;/a&gt; v8 and &lt;a href=&#34;http://en.wikipedia.org/wiki/Openldap&#34;&gt;OpenLDAP&lt;/a&gt; v2.0 instances for of DNS and LDAP servers. Also, throw a Windows Server 2003 into the mix, which, as an &lt;a href=&#34;http://en.wikipedia.org/wiki/Active_directory&#34;&gt;Active Directory&lt;/a&gt; domain controller has to run its own DNS and LDAP (AD is tweaked LDAP) servers.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
