First of all, I realize there are probably more ways to do this than can be reasonably listed. In fact, there are probably a bunch of tools that do this exact same thing. This was a one off thing, really, so I didn’t spend time looking for a package that did everything. It was only after I did it once that I decided to turn it into a shell script to make it easy to use again in the future.

Note: You need mplayer and lame for this.

[james@fractal ~]$ lame -?
LAME 64bits version 3.98.3 (http://www.mp3dev.org/)
...

[james@fractal ~]$ mplayer -h
...
MPlayer SVN-r31628-4.4.4 (C) 2000-2010 MPlayer Team

#!/bin/bash
#
# EDWARDS RESEARCH
# www.edwards-research.com
#
# This converts the audio from .mp4 files that include video (e.g. youtube.com streams) to
# .mp3 files.
#

# If file exists, set $FILE
#   I know this is a sloppy way to handle command line arguments -- I'm ok with that.  (I
#   was going to provide for options, blah blah...)
if [[ -e ${1} ]] ; then
    FILE=${1}
fi

# Ensure input file exits
if [[ -z $FILE ]] ; then
    echo "File not found -- exiting."
    exit
fi

# Extract Filename
base=$(basename "${FILE}" .mp4)

# Dump audio from .mp4 to .wav with mplayer
#   So, it looks as if it doesn't make a difference in terms of the output (at least from
#   my small test group) whether you pick pcm:waveheader or pcm:fast. pcm:waveheader takes
#   more than twice as long to convert but pcm:fast complains.  I'm going to leave it at
#   waveheader because I'm not in a rush and I'd rather not have the warnings.  Feel free
#   to change this to pcm:fast and experiment.
#       -ao pcm:waveheader -> 59 seconds, 4625553 byte .mp3
#       -ao pcm:fast       -> 22 seconds, 4625553 byte .mp3
#
#   mplayer  -vc null -vo null -nocorrect-pts -ao pcm:fast "${FILE}"
#
mplayer -vc null -vo null -nocorrect-pts -ao pcm:waveheader "${FILE}"
RV=$?
if [[ $RV != 0 ]] ; then
    echo "mplayer completed unsuccessfully -- exiting."
    exit
fi

# Convert .wav to .mp3
lame -h -b 192 audiodump.wav "${base}.mp3" ${VERB}
RV=$?
if [[ $RV != 0 ]] ; then
    echo "lame completed unsuccessfully -- exiting."
    exit
fi

# Cleanup Temporary File
rm audiodump.wav

echo "Conversion complete."

I use AMPL a lot in my research and I wanted gedit (my linux IDE of choice) to color the syntax to make programming easier.

Below is a quick run down of how to get syntax coloring / syntax highlighting working in Fedora 14 (same procedure works in F12 and F13 as far as I can tell).

Create AMPL Language File

This should be placed in:

~/.local/share/gtksourceview-2.0/language-specs/ampl.lang

<?xml version="1.0" encoding="UTF-8"?>
<!--

 Author: Edwards Research <http://www.edwards-research.com>
 Copyright (C) 2010 Edwards Research <http://www.edwards-research.com>

-->
<language id="ampl" _name="AMPL" version="2.0" _section="Scripts">
  <metadata>
    <!-- <property name="mimetypes">text/x-ampl;text/plain</property> -->
    <property name="mimetypes"></property>
    <property name="globs">*.mod;*.dat;*.run</property>
    <property name="line-comment-start">#</property>
  </metadata>

  <styles>
    <style id="comment" _name="Comment" map-to="def:comment"/>
    <style id="keyword" _name="Keyword" map-to="def:keyword"/>
    <style id="operator" _name="Operator" map-to="def:operator"/>
    <style id="math" _name="math" map-to="def:string"/>
    <style id="logic" _name="logic" map-to="def:special-constant"/>
    <style id="bracket" _name="Bracket" map-to="def:operator"/>
    <style id="floating-point" _name="Floating point number" map-to="def:floating-point"/>
    <style id="decimal" _name="Decimal number" map-to="def:decimal"/>
    <style id="type" _name="Type" map-to="def:type"/>
  </styles>

  <default-regex-options case-sensitive="false"/>

  <definitions>
    <context id="ampl">
      <include>
        <context id="comment" style-ref="comment" end-at-line-end="true">
          <start>#</start>
          <end>\n</end>
        </context>

        <context id="comment-multiline" style-ref="comment" class="comment" class-disabled="no-spell-check">
            <start>/\*</start>
            <end>\*/</end>
            <include>
                <context ref="def:in-comment"/>
            </include>
        </context>

        <context id="keyword" style-ref="keyword">
          <keyword>minimize</keyword>
          <keyword>maximize</keyword>
          <keyword>subject to</keyword>
          <keyword>check</keyword>
          <keyword>within</keyword>
          <keyword>cross</keyword>
          <keyword>in</keyword>
          <keyword>from</keyword>
          <keyword>to</keyword>
          <keyword>obj</keyword>
          <keyword>net_in</keyword>
          <keyword>net_out</keyword>
        </context>

        <context id="type" style-ref="type">
          <keyword>var</keyword>
          <keyword>set</keyword>
          <keyword>param</keyword>
          <keyword>node</keyword>
          <keyword>arc</keyword>
          <keyword>let</keyword>
          <keyword>model</keyword>
          <keyword>data</keyword>
          <keyword>display</keyword>
        </context>

        <context id="math" style-ref="math">
          <keyword>abs</keyword>
          <keyword>acos</keyword>
          <keyword>acosh</keyword>
          <keyword>asin</keyword>
          <keyword>ainsh</keyword>
          <keyword>atan</keyword>
          <keyword>atan2</keyword>
          <keyword>atanh</keyword>
          <keyword>cos</keyword>
          <keyword>cosh</keyword>
          <keyword>exp</keyword>
          <keyword>log</keyword>
          <keyword>log10</keyword>
          <keyword>max</keyword>
          <keyword>min</keyword>
          <keyword>sin</keyword>
          <keyword>sinh</keyword>
          <keyword>sqrt</keyword>
          <keyword>tan</keyword>
          <keyword>tanh</keyword>
          <keyword>sum</keyword>
          <keyword>prod</keyword>
          <keyword>\+</keyword>
          <keyword>-</keyword>
          <keyword>/</keyword>
          <keyword>\*</keyword>
        </context>

        <context id="logic" style-ref="logic">
          <keyword>if</keyword>
          <keyword>then</keyword>
          <keyword>else</keyword>
          <keyword>or</keyword>
          <keyword>exists</keyword>
          <keyword>forall</keyword>
          <keyword>for</keyword>
          <keyword>and</keyword>
          <keyword>not</keyword>
          <keyword>in</keyword>
          <keyword>not in</keyword>
        </context>

        <context id="operators" style-ref="operator" extend-parent="false">
          <match>[:;\=&lt;&gt;]</match>
        </context>

        <context id="brackets" style-ref="bracket" extend-parent="false">
          <match>[\{\}()\[\]]</match>
        </context>

        <context id="float" style-ref="floating-point">
          <match extended="true">
            (?&lt;![\w\.])
            ([0-9]+[Ee][+-]?[0-9]+ |
             ([0-9]*\.[0-9]+ | [0-9]+\.[0-9]*)([Ee][+-]?[0-9]+)?)
            (?![\w\.])
          </match>
        </context>

        <context id="decimal-number" style-ref="decimal">
          <match extended="true">
            (?&lt;![\w\.])
            [+-]?([1-9][0-9]*|0)
            (?![\w\.])
          </match>
        </context>

      </include>
    </context>

  </definitions>
</language>

Since this overloads the text/plain MIME-type, this is all you need to do, however AMPL files may not open in gedit automatically colored correctly. To fix this, you will want to define a MIME-type of text/x-ampl.

Define AMPL MIME-type

This should be placed in:

~/.local/share/mime/text/x-ampl.xml

<?xml version="1.0" encoding="utf-8"?>
<mime-type xmlns="http://www.freedesktop.org/standards/shared-mime-info" type="text/x-ampl">
  <!--Created automatically by update-mime-database. DO NOT EDIT!-->
  <comment>AMPL Source</comment>
  <glob pattern="*.mod"/>
  <glob pattern="*.dat"/>
  <glob pattern="*.run"/>
</mime-type>

Alternatively, you could add lines 2-8 to

/usr/share/mime/packages/freedesktop.org.xml

… and then run

sudo update-mime-database /usr/local/share/mime

… to update the mime database.

Found this nice trick out today:

exec su -l $USER

(Note: it makes you re-enter your password, but you don’t have to restart sessions)

Trying to get it to run successfully on Fedora was kind of a hassle.

Also, I’ve done this twice now and have had to do different things, so I’ll list them all.

First I downloaded the Adobe Air Installer.

wget http://airdownload.adobe.com/air/lin/download/latest/AdobeAIRInstaller.bin

… you could also have downloaded it through Firefox or whatever.

Now change the permissions and attempt to run it:

chmod u+x AdobeAIRInstaller.bin
./AdobeAIRInstaller.bin

Here I got a little dialog window, it looked like it began to install but then failed when it said that I needed gnome-keyring-daemon to be running.

The fact is, I had the gnome-keyring-daemon running. A simple ps confirmed this:

ps aux | grep keyring

The problem, it turned out, was that I had the x64 version of the keyring daemon running and was missing some x86 libraries.

I installed the x86 version of the gnome-keyring:

sudo yum install gnome-keyring.i686

… but that didn’t seem to do it — I was still missing something.

After some googling I came across a forum post saying these packages were also necessary:

yum install ld-linux.so.2 gtk2-devel.i686 libxml2.i686 libXt.so.6
yum install xterm rpm-libs.i686 nss.i686 libcanberra-gtk2.i686

This helped run the installer and it completed but threw an error that didn’t seem to cause any problems. For good measure I installed this package too to address the error:

sudo yum install PackageKit-gtk-module.i686

So now I had Adobe Air successfully installed, but whenever I tried to install an Air application, I would get a segfault.

Application crashed with an unhandled SIGSEGV

I was able to see this message by running “Adobe AIR Application Installer” from command line, not the Application menu. Otherwise, the installer would pop up for a split second and immediately disappear.

Anyway, after some more googling, I came across a forum post regarding certificates and a fix.

The command basically goes through the Adobe certificates and marks them as trusted (aucm is the Adobe Unix Certificate-Store Manager)

for c in /etc/opt/Adobe/certificates/crypt/*.0; do sudo aucm -n $(basename $c) -t true; done

(I added the sudo because I wasn’t running as root and that gave me a ton of “Root permissions are required to modify the certificate store.” errors.)

After running that, I got a lot of “Certificate Found, processing… Property changed.” messages.

Once that was complete, I was able to install the Pandora Air Application and run it without problems.

To summarize without the details:

cd /tmp
wget http://airdownload.adobe.com/air/lin/download/latest/AdobeAIRInstaller.bin
chmod u+x AdobeAIRInstaller.bin
./AdobeAIRInstaller.bin
sudo yum install gnome-keyring.i686 ld-linux.so.2 gtk2-devel.i686
sudo yum install libxml2.i686 libXt.so.6 xterm rpm-libs.i686
sudo yum install nss.i686 libcanberra-gtk2.i686 PackageKit-gtk-module.i686
for c in /etc/opt/Adobe/certificates/crypt/*.0; do sudo aucm -n $(basename $c) -t true; done

Moving a subversion repository usually consists of two steps:

1. Moving the repository
2. Updating the working copy to reflect the repository move

This post will handle both steps.

Move the repository

Instead of actually moving the repository as one would expect, we’re going to backup our existing repository, import out backup into a newly created one.  First we’ll list the commands, then break down what we’re doing.

svnadmin dump /path/to/old-repository > ~/repo.dmp
svnadmin create /path/to/new-repository
(Update file/directory permissions)
(Update repository permissions)
svnadmin load repository-name < ~/repo.dmp

1. L1: We dump the repository into a backup file.
2. L2: Create a new repository.
3. L3: Update file / directory permissions (by using some combination of chown, chgrp and chmod)
4. L4: Update repository permissions (by editing files like /path/to/new-repository/conf/passwd and /path/to/new-repository/conf/svnserve.conf)
5. L5: Extract the backup into the new repository.

Update the working copy

Once we’ve moved our repository, we now need to update the working copy so that commits and updates will reference our new repository.

cd /path/to/working-copy
svn info
svn switch --relocate svn://hostname/path/to/old-repository svn://hostname/path/to/new-repository
svn info

1. L1: We change to the path of the working copy.
2. L2: Display the path to the old repository through the svn info command.
3. L3: Switch the working copy’s repository.
4. L4: Display the path the the working copy’s repository (verify that the switch worked) through the svn info command.

Clean up

Now that we’re done moving the repository, we want to verify the move and clean up.  To verify the move, we can just check the output of the svn info command.  To further verify, we can run svn update to ensure that nothing is updated.

We will probably also want to remove both the old repository and the backup file.  A simple rm -r for the repository and rm for the backup file is fine.

Lastly, its possible that you would want to use a trimmed down set one of these steps. For example, if you didn’t care about keeping the version history and just wanted to move the repository location, you could skip steps 1 and 5 in the first section. Also, if you didn’t care about moving the working directory but just wanted to make a complete copy of the repository including the version history, you could complete the whole second section.

It looks like this:

[james@workstation ~]$  ping google.com
ping: unknown host google.com

[james@workstation ~]$  dig google.com +short
72.14.204.147
72.14.204.99
72.14.204.103
72.14.204.104

What ended up happening was that the VPN was configured to tunnel all traffic through it, so when it re-wrote the /etc/resolv.conf file, it didn’t append the VPN nameservers to the nameservers provided to us by our DHCP lease, but completely overwrote them. I’m assuming that when you closed the VPN it would replace the resolv.conf file with the one containing the non-VPN nameservers but since I killed it, it was not restored.

Anyway, the fix was easy but finding it out was annoying.

All you have to do is release and renew your DHCP lease.

You could try:

dhclient -r; dhclient

… but I was on an SSH connection and I didn’t quite trust the second command to be run after I lost the connection when the lease was released (this seems like a silly fear but whatever).

Instead I wrote a bash script and put it in a file:

#!/bin/bash
#refreshlease.sh
IFACE="eth0"

dhclient -r ${IFACE}
dhclient ${IFACE}

… and ran that over the SSH connection. The connection seemed to get dropped for a few seconds but then came back up. Checking /etc/resolv.conf showed that my original nameservers were, in fact, back and I was able to resolve DNS queries:

[james@workstation ~]$  ping google.com
PING google.com (64.233.169.105) 56(84) bytes of data.
64 bytes from yo-in-f105.1e100.net (64.233.169.105): icmp_seq=1 ttl=238 time=31.1 ms

The quick brown fox
jumps over the
lazy dog

… displayed on your screen list this:

1  The quick brown fox
2  jumps over the
3  lazy dog

Of course, you could use cat -n if you’re using cat and want line numbers, but if you want to, say, add a 4 space indent to the output of iwconfig, the following technique will work.

First, we run the program / script and capture the output:

output=$(iwconfig 2>/dev/null)

Here we’re running iwconfig in a subshell and capturing the output. In this case, I’m redirecting stderr to /dev/null, otherwise iwconfig returns lines like lo no wireless extensions. up through the subshell to the shell thats calling the bash script. I don’t want this so I’m throwing it out.

Next, we loop through the output using a for loop:

for LINE in ${output} ; do

    echo ${LINE}

done

Running this will not get us the output we’re expecting, it will return each space-separated word/phrase on it’s own line. If we are still talking about the pangram above, we would see:

The
quick
brown
fox
jumps
over
the
lazy
dog

The problem is, the IFS (Internal Field Separator) contains the space character.

(Quick Aside)
To see what the IFS is, type:

echo -n "$IFS" | hexdump

My IFS contains 0×09, 0×20, 0x0a (tab, space and newline respectively).
(End Aside)

We can change the $IFS in our script (to only contain the newline character) which lets us iterate through the output where separated by newlines.

First, we save the original IFS and define the newline IFS:

OIFS="${IFS}"
NIFS=$'\n'

Next we set the IFS to our newline IFS:

IFS="${NIFS}"

Then, we loop through the output (in the loop we reset the IFS incase we expect it to include the space, etc. and then set it to newline IFS before our next iteration)

for LINE in ${output} ; do
    IFS="${OIFS}"

    echo "---- ${LINE}"

    IFS="${NIFS}"
done

Lastly, we reset the IFS:

IFS="${OIFS}"

The final code looks like this:

        output=$(iwconfig 2>/dev/null)

        OIFS="${IFS}"
        NIFS=$'\n'

        IFS="${NIFS}"

        for LINE in ${output} ; do
            IFS="${OIFS}"

            echo "---- ${LINE}"

            IFS="${NIFS}"
        done
        IFS="${OIFS}"

… and we get what we had hoped:

---- The quick brown fox
---- jumps over the
---- lazy dog

In closing, it should be noted that I’ve done this a few different ways (including splitting the output with awk / sed) but I like the simplicity of this method. I may try to find the other methods and write them up to if I get some time.

P.S. If you ever need to reset your IFS but don’t want to close the terminal, type this:

IFS=$'\n\t '

I wasn’t satisfied though.

My LAN’s throughput chokepoint was my router, limiting connections to 100Mbps so I went ahead and ordered a Gigabit switch and upgraded my cabling (it was pretty shoddy) and one of my NICs.  Before they come in though, I decided to explore some ways to improve tunneling without hardware changes.

The first thing I looked into was changing SSH cipers.

You can look at the available ciphers in PuTTY by going into the configuration window, and under Connection, clicking SSH.  You should see something like this:

You can change the the order that these ciphers are considered simply by clicking Up or Down and rearranging them.  I like to put the one I want at the top, then immediately following it with the “–warn below here–” tag, so I know definitively whether I’m getting my #1 choice.

But how do I know which ciper to choose?

Thats a good question, and I didn’t know either.  I did some extremely quick googling and I didn’t get a very definitive answer in the 2 or 3 pages I landed on, but I did find a nice command to run a benchmark on your local system so you can find out for yourself.  The command was:

openssl speed -engine padlock -evp *ciper* 

Where *ciper* is replaced by the name of the cipher you wish to test.  Executing this command starts an OpenSSL script which runs through the algorithm on locally on your computer, measuring the number of computations it can perform per second.

I extended this command with a simple tweak that allowed me to loop through the script using mulitple different ciphers:

for ENC in aes-256-cbc bf bf-ecb rc4 rc4-40 bf-cfb bf-ofb des3 des ; do openssl speed -engine padlock -evp ${ENC} ; done

After executing this, I walked away for a little (probably takes less than 5 mintutes but I didn’t want to introduce any more variability by messing around during the benchmark) and when I cameback it has maybe 150 lines of output, about 15 for each ciper.

Being the quantitative dude that I am, I immediately threw the data into Excel and plotted the processing throughput (in KBps and given on the last line of each iteration) vs block size (given on the second to last line).

The results were really surprising.  Here’s the table I compiled:

Where the highlighted cells indicate maximum throughput for each column or blocksize.  Its pretty apparent from this that RC4 really flys, but the table above doesn’t do the improvement justice.  Lets look at the data plotted:

Note: The label on the vertical axis incorrectly states the units as KBps when they are, in fact, MBps.

(click for full-size)

Wow, that is really a tremendous difference between the two RC4 ciphers and the rest, more often than not doubling the throughput of their alternatives.

So with such a huge difference in performance, certainly the RC4 cipher is the default cipher in PuTTY, right?  Actually, no.  At least in my vanilla PuTTY installations, RC4 (AKA Arcfour in PuTTY) is fairly low on the list, only preferred over DES.

I’m not a cryptographer, and I’m not well versed on the differences between the ciphers certainly not well enough to give any informed opinion on which cipher to choose from a security point of view, but from a sheer speed point of view, it would seem that RC4 would preferred.

Now our network is secured from the WAN side by a firewall on our router which we are trusting to prevent unauthorized access to the LAN side, so for us, encrypting SSH sessions that strictly live on the LAN side with a possibly sub-par cipher was acceptable if it provided the latency improvement that it looked like it would.  Your circumstances may differ and I urge you to consider all of them before you go changing settings.

Given that you’ve considered them, and you’re comfortable, lets go ahead and change the ciper priorities and see if we get any improvement.

Simply by clicking the cipher we want to move, then the Up / Down buttons, we were able to configure our priorities to this:

The idea here being that if, for some reason, we can’t establish a link with RC4, we’ll be notified.  We could then go back into the settings and move the “–warn below here–” line down a line and try again, hoping to connect with the Blowfish ciper, the second quickest cipher or otherwise receive a warning.

Results

Unfortunately, I don’t have any quantitative data to show the latency improvement, although I suppose you could demonstrate a bandwidth / throughput increase by doing a file transfer, however it is abundantly clear that there was, in fact, a huge latency improvement.  Things that caused annoying lag (eg clicking on the scrollbar to scroll quickly) showed a noticeable improvement.

As it is, without real data to show the improvement, you are left to experiment with the settings yourself, and, given you feel comfortable, I strongly encourage doing so — as it really seems to make a difference.

I’ll be sure to check back here when we receive the Gigabit hardware and present a before and after look at our LAN transfer speeds.

echo "Enabling zsh-specific configuration..."

# Useful Aliases
#alias l.='ls -d .* --color=tty'
#alias ll='ls -l --color=tty'
#alias ls='ls --color=tty'
alias lsa='ls -al'
alias lsd='ls -al | grep "^d"'
alias rezsh='. ~/.zshrc'

# Change Prompt
        # Left Hand Prompt
        export PS1="%B%n@%M%#%b "
                # Bold-username-hostname-magicprompt-endbold "
        # Right Hand Prompt
        export RPROMPT="%~"

if [[ $TERM = "xterm" ]] ; then
        echo "  configuring xterm settings..."

        # Fix Backspace
        stty erase "^?"

        # Add some useful keybindings
                # Home Key
                bindkey '^[[1~' beginning-of-line
                # End Key
                bindkey '^[[4~' end-of-line
                # Insert
                bindkey '^[[2~' overwrite-mode
                # Delete Key
                bindkey '^[[3~' delete-char
                # Page Up
                bindkey '^[[5~' beginning-of-history
                # Page Down
                bindkey '^[[6~' end-of-history
                # Ctrl+Left
                bindkey '^[OD' emacs-backward-word
                # Ctrl+Right
                bindkey '^[OC' emacs-forward-word

fi

Also, as an interesting aside, I didn’t have permissions to change my default shell (which was tsch), so I just edited the startup script (.login) of the tsch shell and made it change my shell:

echo "Switching shell to zsh..."
setenv SHELL /bin/zsh
exec /bin/zsh --login

… probably not the most elegant solution, but it works for now.

I have a quad-core AMD box (running Fedora 11), an AMD Phenom II X4 955 Black Edition box (running Windows 7), a few random head-less desktops, a laptop (F11) and a netbook (F11).

I run a fileserver on one box, I run an X session through ssh on my Windows box to access linux GUI stuff, I frequently transfer files between computers and I wanted to be able to access them by my defined hostname rather than the dynamic IP address my router assigned them (WRT54G running DD-WRT v24 SP1).

Now you may say, “dude, just give them static IP’s and be done with it.”  I considered that, but I would much rather remember “tophat” and “fractal” than 192.168.1.5 and 192.168.12.  Plus I’m a nerd and if there’s a way, I’ll figure it out.

… so I figured it out.

Windows will automatically report the Hostname of the computer (I think Windows calls it the Computer Name), so you won’t have to configure that.  You will however, have to allow your router to cache the hostnames and resolve them to IPs, and you will need to configure Linux to report the hostname when a DHCP lease is acquired.

Configure Router

1. Login to your router
2. Click on the “Services” tab
3. Under DNSMasq enable both options (“Enable DNSMasq” and “Enable Local DNS”)
4. Click “Apply Settings”

Configure Linux to Report Hostnames

1. Disclaimer: This is using Fedora 11 – other distros/versions may vary.
2. You should really pick a unique hostname per interface, so in the case that they’re both connected there isn’t a conflict.
3. As root, or with appropriate permissions, edit /etc/sysconfig/network-scripts/ifcfg-{interface} (ie /etc/sysconfig/network-scripts/ifcfg-eth0).
4. Add this line:

DHCP_HOSTNAME=fractal

1. Save the file
2. Restart the network service (sudo service restart network, or use the GUI)
3. Release your DHCP lease (sudo dhclient -r)
4. Renew your DHCP lease (sudo dhclient or ifconfig {interface} down; ifconfig {interface} up)

Configure Windows 7 to resolve hostnames (source)

1. Go into Network Connections (I just typed “Network Connections” om the start icon -> run box)
2. Right click on your Network Adapter and go into Properties
3. Select “Internet Protocol Version 4 (TCP/IPv4)”
4. Under the General Tab click Advanced
5. Under the DNS Tab select the radio button that says “Append these DNS suffixes (in order)”
6. Click “Add…”
7. Enter a single period in the text box and click “Add.”
8. Click OK in the “Advanced TCP/IP Settings” Dialog
9. Click OK in the “Local Area Connection Properties” Dialog

And there you go.