<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>MaddHat.comMaddHat.com | MaddHat.com</title>
	<link>http://maddhat.com</link>
	<description></description>
	<lastBuildDate>Fri, 30 Sep 2011 17:39:10 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.1.3" -->

	<item>
		<title>Remove X Cursor in XBMC</title>
		<description><![CDATA[I&#8217;ve found a few annoying issues while configuring my HTPC with XBMC &#8211; one being the X cursor re-appearing after long idle states.  The cursor will go away after restarting XBMC, but this is annoying to do several times a day.  The fix is quite simple &#8211; the steps are listed below. sudo nano /etc/X11/xorg.conf In the text editor &#8211; find the section of the file labeled Section &#8220;Device&#8221;.  The ending of this section is simply EndSection.  Add the following line before the EndSection statement: Option    "HWCursor" "false" Simply restart X either by restarting XBMC or the machine completely.  The cursor should now stay gone for good!]]></description>
		<link>http://maddhat.com/remove-x-cursor-in-xbmc</link>
			</item>
	<item>
		<title>XBMC HDMI Audio Troubleshooting</title>
		<description><![CDATA[I ran into some issues while configuring my XBMC HTPC with HDMI audio.  After some time with various troubleshooting steps I was able to repair the issue by completing the following steps: &#160; Relevant system specific information: OS: Ubuntu Desktop 11.04 HDMI Device: XFX ATI 5770 sudo alsamixer Ensure no devices are muted (indicated by &#8220;MM&#8221;). sudo alsactl store 0 This step saves the running alsa configuration sudo aplay -l This command will list the installed alsa devices.  Choose the device which you want to output the HDMI audio from &#8211; paying attention to the card number and device number. card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] The above information is used to configure a custom audio device within XBMC.  Within the XBMC system configuration settings, change the output device and output passthrough device to custom with the following name: plughw:1,3  (Note that yours may differ &#8211; it is based on the output of the aplay command. &#160; After saving, restarting the machine, and re-launching XBMC, I was now receiving audio over HDMI &#8211; though sounds for the system menus no longer functioned (an issue I&#8217;ve since ignored).  However, when I played audio, it did not [...]]]></description>
		<link>http://maddhat.com/xbmc-hdmi-audio-troubleshooting</link>
			</item>
	<item>
		<title>Change VPN Credentials on ASA 5510</title>
		<description><![CDATA[Another addition to my posts about Cisco ASA 5510 tasks.  The following is to change the password for a user within the device.  Simple and straight forward &#8211; but ensure that you backup your running configuration before making any system changes. enable config t username USER password PASSWORDHERE privilege 0 write mem Here&#8217;s a good article which covers Cisco Privileges.]]></description>
		<link>http://maddhat.com/change-vpn-credentials-on-asa5510</link>
			</item>
	<item>
		<title>Configure SNMP on ASA5510</title>
		<description><![CDATA[Configuring SNMP on ASA 5510 is straight forward &#8211; but once again I prefer a more straight forward list of the commands vs. the verbose explanation by Cisco.  See below to enable traps to a community name &#8220;SNMPCOMMUNITY&#8221;, the server IP being 192.168.1.1.  As with any commands that creates changes to your device &#8211; ensure you backup before making any changes. enable config t snmp-server host Inside 192.168.1.1 snmp-server community SNMPCOMMUNITY snmp-server enable traps snmp authentication linkup linkdown coldstart That&#8217;s it!  Thanks for reading.]]></description>
		<link>http://maddhat.com/configure-snmp-on-asa5510</link>
			</item>
	<item>
		<title>Mediacom’s DNS Hijacking Scheme</title>
		<description><![CDATA[Friends of mine have consistently heard my complaints about Mediacom’s overcrowded nodes which they neglect to split, the uncoordinated and unreliable customer service, and dangerously ignorant installers (hell, my Mediacom VoIP installer didn’t know what RJ-11 was as I discussed the install with him).  However, with the current U.S. duopoly in regards to broadband – I’m forced to stick with it, as the DSL provider in the area is unable to provide more than a 1.5mbit line.  I’ve tried to make peace with these existing issues, but this week I found yet another issue with Mediacom to add to my list – which I cannot accept. I run a local DNS server on my network – and had made the decision to move away from Mediacom’s DNS servers as my forwarders after testing the speed of theirs in relation to the alternatives.  I am in NO WAY directing my traffic toward the Mediacom DNS servers.  This left me quite confused when I received a Mediacom re-direction page this week after typing a URL incorrectly.  I hopped onto DSLReports and got the scoop.  I found Mediacom has initiated a campaign to increase advertising revenue by automatically redirecting clients to their ad-based [...]]]></description>
		<link>http://maddhat.com/mediacom%e2%80%99s-dns-hijacking-scheme</link>
			</item>
	<item>
		<title>Configure Syslog Forwarding on ASA 5510</title>
		<description><![CDATA[Forwarding logs from an ASA 5510 to an external syslog server is simple &#8211; but I can seldom find a straight forward list of commands for specific tasks for the ASA.  So here it is &#8211; but note this is highly customizable: logging enable logging timestamp logging trap notifications logging asdm notifications logging facility 23 logging device-id HOSTNAME logging host inside SYSLOG SERVER HOSTNAME OR IP logging debug-trace logging permit-hostdown Here&#8217;s the syslog section from Cisco&#8217;s site if you need more information.]]></description>
		<link>http://maddhat.com/configure-syslog-forwarding-on-asa5510</link>
			</item>
	<item>
		<title>Backing Up ASA 5510 Configuration</title>
		<description><![CDATA[Though us network nerds may work in a terminal most of the day &#8211; our workstations are largely Windows based.  This is a quick guide to backing up a Cisco device configuration to a Windows machine.  It&#8217;s fairly simple: Download WinAgents TFTP Server Manager and run through the installation process. This will setup a tftp server on that Windows machine that you will use to direct the configuration to.  Once installed, connect to the local server. Once configuration is complete and you are connected to your machine &#8211; find the IP of the Windows workstation (we&#8217;ll need this in a moment). Now, connect to the Cisco device.  Login and also enter enable mode: enable Once in enable mode, use the copy configuration using the following command: copy startup-config tftp You will be prompted for the server address. Type in the Windows workstation IP address here. You will also be prompted for the name of which to save.  I usually save this as the date and time of the configuration and save it in a folder for the device&#8217;s configuration backups &#8211; so do whatever method works for you. Press ENTER and the transfer will begin.  You should notice statistics on [...]]]></description>
		<link>http://maddhat.com/backing-up-asa5510-configuration</link>
			</item>
	<item>
		<title>Packet Pushers Podcast</title>
		<description><![CDATA[Wanted to give a shout-out to my new favorite podcast – Packet Pushers. With a lengthy commute every work day I listen to many technical podcasts. I’m a fan of most twit.tv shows such as TWIT, TWIG, etc. but they rarely cover anything about the in-depth networking topics I enjoy. Packet Pushers on the other hand is like sitting in on a group meet-up of “world-class” networking gurus and being able to absorb knowledge about the real networking world. I’m nowhere near the level of knowledge about the topics as the hosts – but it really allows me to escape to that networking side of my mind and take it all in. I recommend this to anyone interested in such topics, and if you read this blog in any sort of regularity – it probably means you. Check it out at packetpushers.net]]></description>
		<link>http://maddhat.com/packet-pushers-podcast</link>
			</item>
	<item>
		<title>Ubuntu Server PXE Install</title>
		<description><![CDATA[I was working on a set of Ubuntu servers for a cluster in my network lab and wanted to look into alternative boot methods to streamline the process.  I followed a lot of tutorials which recommended setting up a new DHCP server that could assign the machines leases and then direct the machines to the correct boot file.  After some failed attempts with running a temporary DHCP and TFTP server on a Windows machine I sifted through my DHCP server settings for pfSense and found that it actually had support for network boot built in.  This was great and allowed me to skip the whole DHCP server step and just change the following in the Services &#62; DHCP Server tab in pfSense: Of course for this to work I had to have pfSense’s DHCP server enabled.  Having this setup will now allow the bootable machines to be assigned a DHCP lease then look for the TFTP server at the address specified (192.168.2.200 in my situation) and to look for pxelinux.0 to boot from.  The next portion of this setup is a slightly modified version of the article found here https://help.ubuntu.com/community/PXEInstallServer , modified in the sense that I left out any [...]]]></description>
		<link>http://maddhat.com/ubuntu-server-pxe-install</link>
			</item>
	<item>
		<title>Squid3 Transparent Proxy Setup</title>
		<description><![CDATA[Introduction Being a networking geek, I often try to figure out every aspect I can about different network technologies being used, how to configure them, and what benefits they have to provide when implemented. My home network/lab is a great place to test these technologies in a non-crucial environment. One such networking aspect I haven’t researched much is proxies. Sure, I’ve run into it with application installation that needs a connection configured, and had setup a CGI proxy in the past on a windows machine after my frustrations with my high school’s network blocking my once favorite social new site digg.com, but overall I hadn’t had much knowledge about why else proxies were implemented on a network, so I decided to play with Squid3 to educate myself. Squid3 Squid3 works as a web-cache proxy which means that while you browse, the content you are retrieving can also be cached for faster retrieval on the machine running the proxy – based on a set of rules in the proxy’s configuration files. This is not to say that ALL content gets cached, due to the fact that most content you are retrieving is dynamic, and it wouldn’t make sense to cache it [...]]]></description>
		<link>http://maddhat.com/squid3-transparent-proxy-setup</link>
			</item>
</channel>
</rss>

