<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Shane Cunningham</title><link>https://cunninghamshane.com/tags/networking/</link><description>Recent content in Networking on Shane Cunningham</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 08 Nov 2014 11:32:31 +0000</lastBuildDate><atom:link href="https://cunninghamshane.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenStack Juno All in One</title><link>https://cunninghamshane.com/posts/openstack-juno-all-in-one/</link><pubDate>Sat, 08 Nov 2014 11:32:31 +0000</pubDate><guid>https://cunninghamshane.com/posts/openstack-juno-all-in-one/</guid><description>&lt;p&gt;Quick guide on setting up the &lt;a href="http://www.openstack.org/software/juno/"&gt;OpenStack Juno&lt;/a&gt; release in an all in one server with one NIC using &lt;a href="https://openstack.redhat.com/Main_Page"&gt;RDO&lt;/a&gt;. This is configured for Neutron networking with floating IPs.&lt;/p&gt;&#10;&lt;p&gt;My setup: CentOS 7 minimal, IP: 192.168.1.100&lt;/p&gt;&#10;&lt;p&gt;By default NetworkManager will be running and controlling our NICs. packstack will complain about this later so disable and stop the service.&lt;/p&gt;&#10;&lt;figure class="code-block"&gt;&#10; &lt;figcaption class="code-bar"&gt;&#10; &lt;span class="code-title"&gt;console&lt;/span&gt;&#10; &lt;span class="code-meta"&gt;&#10; &lt;button type="button" class="copy-btn" data-copy&gt;Copy&lt;/button&gt;&#10; &lt;/span&gt;&#10; &lt;/figcaption&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-console" data-lang="console"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="gp"&gt;[root@juno-allinone ~]#&lt;/span&gt; systemctl disable NetworkManager&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="gp"&gt;[root@juno-allinone ~]#&lt;/span&gt; systemctl stop NetworkManager&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Next we&amp;rsquo;ll update some stuff, install the RDO Juno repo and install packstack.&lt;/p&gt;</description></item><item><title>Add Cloud Networks to existing Cloud Server</title><link>https://cunninghamshane.com/posts/add-cloud-networks-to-existing-cloud-server/</link><pubDate>Sat, 15 Jun 2013 06:14:02 +0000</pubDate><guid>https://cunninghamshane.com/posts/add-cloud-networks-to-existing-cloud-server/</guid><description>&lt;p&gt;Cloud Networks is a really cool up and coming feature in the &lt;a href="http://www.rackspace.com/cloud/"&gt;Rackspace Cloud&lt;/a&gt;. It enables you to create private networks only accessible by your Cloud infrastructure. When first released, you could only attach a &lt;a href="http://www.rackspace.com/cloud/servers/"&gt;Cloud Server&lt;/a&gt; to &lt;a href="http://www.rackspace.com/knowledge_center/article/getting-started-with-cloud-networks"&gt;Cloud Networks&lt;/a&gt; when creating a new Cloud Server or by taking an image and then creating a new Cloud Server based off of that image and attaching Cloud Networks at that time. Not the best situation if you already have a stable Cloud infrastructure. Luckily we can now attach Cloud Networks to an already running Cloud Server. Make sure the server is a NextGen Cloud Server based on OpenStack. This tutorial was run on Debian 6 Squeeze, but should be pretty much the same on other Linux distros. If you have any issues with a particular distro please let me know.&lt;/p&gt;</description></item><item><title>VM not sending hostname to DNS/DHCP server</title><link>https://cunninghamshane.com/posts/vm-not-sending-hostname-to-dns-server/</link><pubDate>Wed, 13 Feb 2013 07:23:18 +0000</pubDate><guid>https://cunninghamshane.com/posts/vm-not-sending-hostname-to-dns-server/</guid><description>&lt;p&gt;On some VMs I spin up on ESXi the hostname is not sent to my DNS/DHCP server running in pfSense. Haven&amp;rsquo;t found exactly why because it seems occasionally Ubuntu VMs do send this correctly on first boot. I&amp;rsquo;m probably doing something not smart. Anyway, you can easily fix this problem by adding the following -&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;CentOS/Ubuntu&lt;/strong&gt;&lt;br&gt;&#10;Add this to /etc/sysconfig/network&lt;/p&gt;&#10;&lt;figure class="code-block"&gt;&#10; &lt;figcaption class="code-bar"&gt;&#10; &lt;span class="code-title"&gt;text&lt;/span&gt;&#10; &lt;span class="code-meta"&gt;&#10; &lt;button type="button" class="copy-btn" data-copy&gt;Copy&lt;/button&gt;&#10; &lt;/span&gt;&#10; &lt;/figcaption&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;DHCP_HOSTNAME=hostname&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Replace hostname with your servers hostname and restart networking. It should now send the hostname to your DNS/DHCP server.&lt;/p&gt;</description></item><item><title>pfSense, Squid and logging full URLs</title><link>https://cunninghamshane.com/posts/pfsense-squid-and-logging-full-urls/</link><pubDate>Fri, 02 Nov 2012 04:18:41 +0000</pubDate><guid>https://cunninghamshane.com/posts/pfsense-squid-and-logging-full-urls/</guid><description>&lt;p&gt;By default the Squid package that pfSense installs will cut off the URLs if they are longer than a certain length. If you want it to log the full URL, add this to your squid.conf file. The config file says not to manually edit it, but I inserted this and restarted squid and everything continued working.&lt;/p&gt;&#10;&lt;figure class="code-block"&gt;&#10; &lt;figcaption class="code-bar"&gt;&#10; &lt;span class="code-title"&gt;text&lt;/span&gt;&#10; &lt;span class="code-meta"&gt;&#10; &lt;button type="button" class="copy-btn" data-copy&gt;Copy&lt;/button&gt;&#10; &lt;/span&gt;&#10; &lt;/figcaption&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;strip_query_terms off&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/figure&gt;</description></item><item><title>pfSense firewall/router update</title><link>https://cunninghamshane.com/posts/pfsense-firewallrouter-update/</link><pubDate>Sat, 14 Apr 2012 14:52:21 +0000</pubDate><guid>https://cunninghamshane.com/posts/pfsense-firewallrouter-update/</guid><description>&lt;p&gt;I had some issues with accessing IPMI in my &lt;a href="https://cunninghamshane.com/posts/custom-built-pfsense-router/"&gt;pfSense&lt;/a&gt; build. It seemed like if I let pfSense boot up and I was not accessing IPMI at the same time, pfSense would take over the whole NIC and not let me access IPMI. I read &lt;a href="http://forum.pfsense.org/index.php/topic,28238.0.html"&gt;here&lt;/a&gt; that this is normal to not be able to access IPMI once pfSense boots but that defeats the whole purpose of IPMI so I don&amp;rsquo;t think the system should behave in that way. After messing with it for a few days all I can say is IPMI seems really finicky when sharing a NIC, or maybe I&amp;rsquo;m doing something goofy.&lt;/p&gt;</description></item><item><title>My pfSense firewall/router build</title><link>https://cunninghamshane.com/posts/custom-built-pfsense-router/</link><pubDate>Thu, 05 Apr 2012 02:43:03 +0000</pubDate><guid>https://cunninghamshane.com/posts/custom-built-pfsense-router/</guid><description>&lt;p&gt;I stuck with a D-Link DIR-625 wireless router doing all my routing for entirely too long. I had an old P4 2.66 GHz PC laying around with a 40GB hard drive so I decided to try out &lt;a href="http://www.pfsense.org"&gt;pfSense&lt;/a&gt;. I was hooked, the overall performance and features of this open source FreeBSD firewall/router were impressive. My old P4 machine was using too much electricity for something that was on 24 x 7, though. I decided to custom build something that was 1. powerful enough for my home network and virtual environment lab 2. low power draw 3. quite.&lt;/p&gt;</description></item><item><title>Two Linux notes</title><link>https://cunninghamshane.com/posts/two-linux-notes/</link><pubDate>Thu, 29 Mar 2012 03:17:26 +0000</pubDate><guid>https://cunninghamshane.com/posts/two-linux-notes/</guid><description>&lt;p&gt;&lt;strong&gt;SSH Tunnel for web traffic&lt;/strong&gt;&lt;/p&gt;&#10;&lt;figure class="code-block"&gt;&#10; &lt;figcaption class="code-bar"&gt;&#10; &lt;span class="code-title"&gt;sh&lt;/span&gt;&#10; &lt;span class="code-meta"&gt;&#10; &lt;button type="button" class="copy-btn" data-copy&gt;Copy&lt;/button&gt;&#10; &lt;/span&gt;&#10; &lt;/figcaption&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-sh" data-lang="sh"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;ssh -D &lt;span class="m"&gt;9998&lt;/span&gt; -C shane@myserver.com&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Where &amp;ldquo;myserver.com&amp;rdquo; is a server you operate with SSH setup. Now you need to configure your browser to use the tunnel. In OS X you can go to Network -&amp;gt; Advanced -&amp;gt; Proxies -&amp;gt; Check SOCKS and input &lt;code&gt;localhost:9998&lt;/code&gt; or whatever port you used. Directly from Chrome you can also select Preferences -&amp;gt; Under The Hood -&amp;gt; Change Proxy Settings&amp;hellip; -&amp;gt; and it will go directly to your OS X Network/Proxies tab.&lt;/p&gt;</description></item><item><title>Had to share this… telnet to miku.acm.uiuc.edu enjoy.</title><link>https://cunninghamshane.com/posts/had-to-share-this-telnet-to-miku-acm-uiuc-edu/</link><pubDate>Thu, 01 Dec 2011 10:10:00 +0000</pubDate><guid>https://cunninghamshane.com/posts/had-to-share-this-telnet-to-miku-acm-uiuc-edu/</guid><description>&lt;p&gt;Had to share this…&lt;/p&gt;&#10;&lt;p&gt;telnet to miku.acm.uiuc.edu&lt;/p&gt;&#10;&lt;p&gt;enjoy.&lt;/p&gt;</description></item></channel></rss>