<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tom Salmon</title>
	<atom:link href="http://tomsalmon.eu/feed/" rel="self" type="application/rss+xml" />
	<link>http://tomsalmon.eu</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 10:08:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>ipt_ROUTE Netfilter module ported to Linux 2.6.31</title>
		<link>http://tomsalmon.eu/2013/05/ipt_route-netfilter-module-ported-to-linux-2-6-31/</link>
		<comments>http://tomsalmon.eu/2013/05/ipt_route-netfilter-module-ported-to-linux-2-6-31/#comments</comments>
		<pubDate>Sat, 18 May 2013 10:08:29 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=383</guid>
		<description><![CDATA[The ipt_ROUTE module became depreciated in an earlier version of Linux 2.6 &#8211; however I needed it so ported it to Linux Kernel version 2.6.31. Disclaimer: wherever possible iproute2 should be used to achieve the desired effect. The sources include the Kernel module and extensions to iptables. This module and iptables extension create a new [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2013/05/ipt_route-netfilter-module-ported-to-linux-2-6-31/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenVPN &#8211; IPv6 with tun device</title>
		<link>http://tomsalmon.eu/2013/04/openvpn-ipv6-with-tun-device/</link>
		<comments>http://tomsalmon.eu/2013/04/openvpn-ipv6-with-tun-device/#comments</comments>
		<pubDate>Sun, 21 Apr 2013 11:47:32 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=374</guid>
		<description><![CDATA[Note: IPv6 is not supported using OpenVPN on Debian Squeeze (stable). The version used by Debian Wheezy (testing) supports IPv6. Network setup: - 192.168.1.0/24 - Local IPv4 network - 2001:412:abcd::/48 - Local IPv6 network - 192.168.2.0/24 - Tunnel IPv4 network - 2001:412:abcd:2::/64 - Tunnel IPv6 network I have included only the sections of config files [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2013/04/openvpn-ipv6-with-tun-device/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enabling compose key to type unicode on Linux</title>
		<link>http://tomsalmon.eu/2013/02/enabling-compose-key-to-type-unicode-on-linux/</link>
		<comments>http://tomsalmon.eu/2013/02/enabling-compose-key-to-type-unicode-on-linux/#comments</comments>
		<pubDate>Wed, 20 Feb 2013 19:46:26 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=362</guid>
		<description><![CDATA[The compose key may be used to type unicode characters easily on Linux systems… All of these commands should be executed as a normal user, no root access required: Identify the key you want to use as your compose key, I use the ‘Windows’ key: Run the application xev Press the key you want to [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2013/02/enabling-compose-key-to-type-unicode-on-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SIP Trunking between Asterisk 1.4 and Cisco CUBE</title>
		<link>http://tomsalmon.eu/2012/03/sip-trunking-between-asterisk-1-4-and-cisco-cube/</link>
		<comments>http://tomsalmon.eu/2012/03/sip-trunking-between-asterisk-1-4-and-cisco-cube/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 17:34:10 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=288</guid>
		<description><![CDATA[As far as I can tell Cisco CUBE only supports unauthenticated SIP trunks, which isn&#8217;t too much trouble for Asterisk. In sip.conf: type=peer host=x.x.x.x context=trunks-inbound allow=all insecure=invite,port trustrpid=yes sendrpid=no qualify=yes (change &#8216;trunks-inbound&#8217; to the necessary context) In extensions.conf: exten=>_0.,1,Set(CALLERID(num)=nnn-nnn-${CALLERID(num)}) exten=>_0.,n,Dial(SIP/x.x.x.x/${EXTEN:1}) exten=>_0.,n,Hangup (First line is optional, and simply adds a prefix to the outgoing caller ID) [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/03/sip-trunking-between-asterisk-1-4-and-cisco-cube/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Brute Forcing WPA WiFi Encryption</title>
		<link>http://tomsalmon.eu/2012/03/brute-forcing-wpa-wifi-encryption/</link>
		<comments>http://tomsalmon.eu/2012/03/brute-forcing-wpa-wifi-encryption/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 17:19:18 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=281</guid>
		<description><![CDATA[WPA and WPA2 provide good WiFi security which is mainly susceptible to brute force attacks. Here is how such a brute force attack may be carried out. Using Debian Wheezy (testing) and an Intel Corporation Centrino Wireless-N 1000 card: Stop Network Manager: /etc/init.d/network-manager stop Enter monitor mode: airmon-ng start wlan0 Find nearby networks: airodump-ng mon0 [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/03/brute-forcing-wpa-wifi-encryption/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Breaking WEP Encryption</title>
		<link>http://tomsalmon.eu/2012/03/breaking-wep-encryption/</link>
		<comments>http://tomsalmon.eu/2012/03/breaking-wep-encryption/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 17:03:00 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=271</guid>
		<description><![CDATA[Using Debian Wheezy (testing) with a Intel Corporation Centrino Wireless-N 1000 card&#8230; Stop network manager: /etc/init.d/network-manager stop Enter monitor mode: airmon-ng start wlan0 Find nearby networks: airodump-ng mon0 Identify the target BSSID, SSID and Channel number (-c option below) Start packet capture and leave running: airodump-ng -c 6 &#8211;bssid 00:11:22:33:44:55 -w capturefile mon0 Run the [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/03/breaking-wep-encryption/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Wireless Network Packet Sniffing</title>
		<link>http://tomsalmon.eu/2012/03/open-wireless-network-packet-sniffing/</link>
		<comments>http://tomsalmon.eu/2012/03/open-wireless-network-packet-sniffing/#comments</comments>
		<pubDate>Sat, 17 Mar 2012 15:43:58 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=262</guid>
		<description><![CDATA[This is easier and more effective than packet sniffing on a wired network: Stop Network Manager: /etc/init.d/network-manager stop Set your WiFi card into monitoring mode: airmon-ng start wlan0 See what&#8217;s around: airodump-ng mon0 Select a target network, and note the BSSID value and channel (used as &#8216;-c&#8217; option below) Collect the packet trace: airodump-ng -c [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/03/open-wireless-network-packet-sniffing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WiFi Card &#8211; Packet Injection in Linux</title>
		<link>http://tomsalmon.eu/2012/03/wifi-card-packet-injection-in-linux/</link>
		<comments>http://tomsalmon.eu/2012/03/wifi-card-packet-injection-in-linux/#comments</comments>
		<pubDate>Sat, 17 Mar 2012 15:25:39 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=253</guid>
		<description><![CDATA[Very simple way to test if your WiFi card supports injection: Stop Network Manager: /etc/init.d/network-manager stop Put the card in monitor mode: airmod-ng start wlan0 Test using: aireplay-ng -9 mon0 With luck, the following output is displayed: Trying broadcast probe requests&#8230; Injection is working! I am using Debian Wheezy (testing) with WiFi card: Network controller: [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/03/wifi-card-packet-injection-in-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Aircrack-ng for Debian Wheezy (testing)</title>
		<link>http://tomsalmon.eu/2012/03/aircrack-ng-for-debian-wheezy-testing/</link>
		<comments>http://tomsalmon.eu/2012/03/aircrack-ng-for-debian-wheezy-testing/#comments</comments>
		<pubDate>Sat, 17 Mar 2012 15:02:51 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=246</guid>
		<description><![CDATA[After discovering that Aircrack-ng isn&#8217;t currently included in Debian Wheezy (but it is in both Stable and Sid), I grabbed the latest version out of SVN (v1.1 &#8211; r2128) and built the package for my x86-64 system. Source and compiled executables are available here. I have included the necessary scripts and binary files in the [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/03/aircrack-ng-for-debian-wheezy-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPv6 DNS Advertisements</title>
		<link>http://tomsalmon.eu/2012/02/ipv6-dns-advertisements/</link>
		<comments>http://tomsalmon.eu/2012/02/ipv6-dns-advertisements/#comments</comments>
		<pubDate>Mon, 20 Feb 2012 21:50:00 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=239</guid>
		<description><![CDATA[DNS client configuration can be handled by the standard Router Advertisement Daemon (radvd) &#8211; apt-get install radvd Edit /etc/radvd.conf on your Linux Router and insert the following at the end of the file to use Google&#8217;s DNS Caching server: RDNS 2001:4860:4860::8888 { }; On your Linux clients install rdnssd. To automatically add the advertised IPv6 [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/02/ipv6-dns-advertisements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Net-SNMP writable attribute</title>
		<link>http://tomsalmon.eu/2012/02/net-snmp-writeable-attributes/</link>
		<comments>http://tomsalmon.eu/2012/02/net-snmp-writeable-attributes/#comments</comments>
		<pubDate>Thu, 09 Feb 2012 16:20:31 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=233</guid>
		<description><![CDATA[Solarwinds NMS verifies the SNMP write configuration of its nodes (agents) by attemping to set the &#8216;sysContact.0&#8242; (1.3.6.1.2.1.1.4.0) value. On Net-SNMP you must first configure the &#8216;rwcommunity&#8217; setting in the snmpd.conf file. Do not set &#8216;sysContact&#8217; value in snmpd.conf. Configuring &#8216;sysContact&#8217; (or any other &#8216;sys&#8217; setting) in the configuration file, results in that value being [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2012/02/net-snmp-writeable-attributes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multiple IPv6 Addresses per Interface</title>
		<link>http://tomsalmon.eu/2011/03/multiple-ipv6-addresses-per-interface/</link>
		<comments>http://tomsalmon.eu/2011/03/multiple-ipv6-addresses-per-interface/#comments</comments>
		<pubDate>Tue, 15 Mar 2011 22:00:55 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=211</guid>
		<description><![CDATA[Using &#8216;ifconfig&#8217; on Debian Lenny, multiple IPv6 addresses can be added using entries in &#8216;/etc/network/interfaces&#8217; with the &#8216;up&#8217; and &#8216;down&#8217; options. For example: iface eth0 inet6 static address 2001:41c8:1:5568::100 netmask 64 gateway fe80::1 pre-up echo 0 > /proc/sys/net/ipv6/conf/eth0/autoconf up /sbin/ifconfig eth0 inet6 add 2001:41c8:1:5568::1:100/64 up /sbin/ifconfig eth0 inet6 add 2001:41c8:1:5568::2:100/64 down /sbin/ifconfig eth0 inet6 del [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2011/03/multiple-ipv6-addresses-per-interface/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Emulating a network connection with packet drop</title>
		<link>http://tomsalmon.eu/2011/02/emulating-a-network-connection-with-packet-drop/</link>
		<comments>http://tomsalmon.eu/2011/02/emulating-a-network-connection-with-packet-drop/#comments</comments>
		<pubDate>Sun, 27 Feb 2011 18:16:47 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=201</guid>
		<description><![CDATA[IP packet drop can be easily emulated on any section of network using a Linux Bridge and a single iptables command: iptables -t mangle -A FORWARD -m statistic --mode random --probability 0.01 -j DROP (where probability is expressed as a value between 0 and 1) If the intention is to emulate packet drop to the [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2011/02/emulating-a-network-connection-with-packet-drop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux Networking Bridge</title>
		<link>http://tomsalmon.eu/2011/02/linux-networking-bridge/</link>
		<comments>http://tomsalmon.eu/2011/02/linux-networking-bridge/#comments</comments>
		<pubDate>Sun, 27 Feb 2011 17:56:22 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Linux General]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=190</guid>
		<description><![CDATA[It is often useful to place a Linux system on a specific network cable, to packet sniff or modify the network behaviour. The network setup: [switch] - ethernet cable - [node] becomes: [switch] - ethernet cable - [[Linux Bridge]] - ethernet cable - [node] The only requirement for the Linux Bridge is two physical network [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2011/02/linux-networking-bridge/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPv6 and IPv4 Preference</title>
		<link>http://tomsalmon.eu/2011/02/ipv6-and-ipv4-preference/</link>
		<comments>http://tomsalmon.eu/2011/02/ipv6-and-ipv4-preference/#comments</comments>
		<pubDate>Sun, 27 Feb 2011 17:23:22 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://tomsalmon.eu/?p=183</guid>
		<description><![CDATA[When a site is reachable using both IPv4 and IPv6, Linux by default has a preference which is roughly: Native IPv6 Native IPv4 6to4 tunnels To change this preference, edit &#8216;/etc/gai.conf&#8217; uncomment most of the labels: label ::1/128 0 label ::/0 1 #label 2002::/16 2 label ::ffff:0:0/96 2 label fec0::/10 3 label fc00::/7 4 label [...]]]></description>
		<wfw:commentRss>http://tomsalmon.eu/2011/02/ipv6-and-ipv4-preference/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
