<?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>#!SUITS &#187; ucc</title>
	<atom:link href="http://suits.it.usyd.edu.au/wordpress/tag/ucc/feed/" rel="self" type="application/rss+xml" />
	<link>http://suits.it.usyd.edu.au/wordpress</link>
	<description>Sydney University IT Society</description>
	<lastBuildDate>Sun, 18 Oct 2009 14:50:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>USYD Wireless is coming to SIT</title>
		<link>http://suits.it.usyd.edu.au/wordpress/2008/08/25/usyd-wireless-is-coming-to-sit/</link>
		<comments>http://suits.it.usyd.edu.au/wordpress/2008/08/25/usyd-wireless-is-coming-to-sit/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 08:52:33 +0000</pubDate>
		<dc:creator>Edmund Tse</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[SIT]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[ucc]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://suits.it.usyd.edu.au/wordpress/?p=222</guid>
		<description><![CDATA[Recently, some white squarish objects that have been installed on the walls around School of IT. In case you&#8217;re wondering what they are, they&#8217;re actually Cisco wireless access points that&#8217;s connected to the university network. This means, anyone with a UniKey account will be able to access the internet while connected.
So far I&#8217;ve spotted 2 [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, some white squarish objects that have been installed on the walls around School of IT. In case you&#8217;re wondering what they are, they&#8217;re actually Cisco wireless access points that&#8217;s connected to the university network. This means, anyone with a UniKey account will be able to access the internet while connected.</p>
<p>So far I&#8217;ve spotted 2 APs in the Masters area, and another AP in the SIT lecture theatre. All you have to do is to find the access point (named &#8220;usyd&#8221;), and connect to it. Then, you can connect to the internet via VPN or SSH, just follow our <a href="/wordpress/tutorials/">tutorials</a>.</p>
<p>ET</p>
]]></content:encoded>
			<wfw:commentRss>http://suits.it.usyd.edu.au/wordpress/2008/08/25/usyd-wireless-is-coming-to-sit/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tutorial: SSH Port Forwarding</title>
		<link>http://suits.it.usyd.edu.au/wordpress/2007/12/04/tutorial-ssh-port-forwarding/</link>
		<comments>http://suits.it.usyd.edu.au/wordpress/2007/12/04/tutorial-ssh-port-forwarding/#comments</comments>
		<pubDate>Tue, 04 Dec 2007 07:34:30 +0000</pubDate>
		<dc:creator>James Bunton</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[ucc]]></category>

		<guid isPermaLink="false">http://suits.it.usyd.edu.au/wordpress/?p=20</guid>
		<description><![CDATA[This describes how to use an SSH tunnel to access web sites from the UCC (University Computing Centre) wireless network. This is what you want to read if youâ€™re an SIT student and you want internet access from your laptop in Wentworth, etc.

Please read this page in it&#8217;s entirety. It&#8217;s very useful to understand how [...]]]></description>
			<content:encoded><![CDATA[<p>This describes how to use an SSH tunnel to access web sites from the UCC (University Computing Centre) wireless network. This is what you want to read if youâ€™re an SIT student and you want internet access from your laptop in Wentworth, etc.</p>
<p><span id="more-20"></span></p>
<p>Please read this page in it&#8217;s entirety. It&#8217;s very useful to understand how these techniques work.</p>
<h3>Background</h3>
<p>SIT means School of Information Technologies. This tutorial will only be useful if you&#8217;re an SIT student. UCC means University Computing Centre. They do lots of things, including supplying wireless networks for people to connect to throughout the university.</p>
<p>If you connect to a wireless network in a building like Wentworth, chances are it&#8217;s the UCC network. They supply a rather annoying (to me) VPN client which you&#8217;re supposed to use to access external sites through their wireless.</p>
<p>A proxy, for our purposes, means a computer that has greater network access than you, and can make requests on your behalf and return the result.</p>
<h3>Procedure</h3>
<p>The UCC wireless gives you limited connectivity without their VPN client. Thankfully this connectivity includes the ability to SSH to computers on the SIT network.</p>
<p>The SIT runs a web proxy, which requires an SIT username/password and allows access to web pages on the internet. The server is www-cache.it.usyd.edu.au and runs on port 8000. These are the settings you use when you&#8217;re directly connected to the SIT network, eg using a computer in the labs.</p>
<p>Note that your SIT internet quota is separate and in addition to your UCC quota. So if you&#8217;ve run out of your SIT web quota, you can still connect to the internet using VPN, and keep surfing the net with your UCC internet quota.</p>
<p>You cannot connect directly to the SIT web proxy from the wireless, and you cannot SSH directly to the SIT web proxy. However you can SSH to one of the congos, say congo1. SSH has a nice feature called TCP tunneling. Basically what it does is allow you to forward connections to a port on your computer (localhost) to a port on a remote computer, through an SSH connection. Here&#8217;s a diagram:</p>
<p>You connect to congo1 from your laptop.</p>
<pre>[laptop]  &lt;-ssh connection-&gt;  [congo1]</pre>
<p>You want to use congo1 as a proxy to connect to the SIT web proxy. Nice eh?</p>
<pre>         (forwarded connection
          piggybacks over SSH)
[laptop]  &lt;-ssh connection-&gt;  [congo1]
                                | (forwarded connection)
             [www-cache.it.usyd.edu.au]</pre>
<h3>Details</h3>
<p>Individual forwarding command:<br />
<code><br />
ssh -L 1234:desthost:4321 userXYXY@proxyhost</p>
<ul>
<li> The -L means enable port forwarding.</li>
<li> The first port number is the port to listen to on the machine you're running the SSH client on.</li>
<li> The second field and third fields specify the host and port which you want your connection to end up at. This is from the perspective of the machine you're SSHing to.</li>
<li> The last parameter is the username@host of the computer you want to SSH to, the one doing the forwarding.</li>
</ul>
<p>The end result, is that if you connect to localhost:1234 on your machine locally, then it gets forwarded through proxyhost to port 4321 on desthost.</p>
<h3>Web Proxy Quick HOWTO</h3>
<p>To set this up, you run one command. See above for details on the options.<br />
</code><code>ssh -L 8000:www-cache.it.usyd.edu.au:8000 userXXXX@congo1.ug.it.usyd.edu.au</code><br />
Now you have an SSH tunnel. Whenever you connect to localhost:8000 the connection will be forwarded through congo1 to www-cache.it.usyd.edu.au:8000</p>
<p>So you need to configure your web browser to use as the proxy: Host: localhost Port: 8000</p>
<p>This can be simplified by using the ssh config file (see <a href="http://suits.it.usyd.edu.au/wordpress/2007/04/17/tutorial-ssh/">see SUITS tutorial</a>) instead of typing out this long command.<br />
<code><br />
Host sitproxy<br />
&nbsp;&nbsp;&nbsp;&nbsp;HostName congo1.ug.it.usyd.edu.au<br />
&nbsp;&nbsp;&nbsp;&nbsp;User userXXXX<br />
&nbsp;&nbsp;&nbsp;&nbsp;LocalForward 8000 www-cache.it.usyd.edu.au:8000<br />
</code><br />
Which can then be used via<br />
<code><br />
$ ssh sitproxy<br />
</code></p>
<h3>Jabber (Google Talk) Quick HOWTO</h3>
<p>The SIT network allows unproxied outgoing connections on port 443 to all hosts. This port is usually used for HTTPS, that&#8217;s secure HTTP. Many Jabber servers (google talk, jabber.org.au) also listen on this port.</p>
<p>You can take advantage of this by proxying your Jabber connections from the UCC wireless through one of the congos. Run this command for google talk, or modify it as appropriate for your Jabber server.</p>
<pre>ssh -L 5222:talk.google.com:443 userXXXX@congo1.ug.it.usyd.edu.au</pre>
<p>Then go into your Jabber client and set it to connect to a specific host/port. Host: localhost Port: 5222</p>
<h3>Postgrad Account</h3>
<p>For those with a postgraduate account, you can connect through a postgraduate server, avoiding the proxy/download limit issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://suits.it.usyd.edu.au/wordpress/2007/12/04/tutorial-ssh-port-forwarding/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Tutorial: Email Forwarding</title>
		<link>http://suits.it.usyd.edu.au/wordpress/2007/10/26/tutorial-email-forwarding/</link>
		<comments>http://suits.it.usyd.edu.au/wordpress/2007/10/26/tutorial-email-forwarding/#comments</comments>
		<pubDate>Fri, 26 Oct 2007 07:37:35 +0000</pubDate>
		<dc:creator>Edmund Tse</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[ucc]]></category>
		<category><![CDATA[USYD]]></category>

		<guid isPermaLink="false">http://suits.it.usyd.edu.au/wordpress/?p=24</guid>
		<description><![CDATA[Want to set up your Usyd UniKey email account and/or IT email account to forward to your regular email address?

Forwarding your UniKey Email
UniKey email is your university-wide account. In 2009, the uni has moved student email accounts to a new service running on Outlook Live. Your email address is now unikey@uni.sydney.edu.au. Here are some tips [...]]]></description>
			<content:encoded><![CDATA[<p>Want to set up your Usyd UniKey email account and/or IT email account to forward to your regular email address?</p>
<p><span id="more-24"></span></p>
<h3>Forwarding your UniKey Email</h3>
<p>UniKey email is your university-wide account. In 2009, the uni has moved student email accounts to a new service running on Outlook Live. Your email address is now <a href="mailto:unikey@uni.sydney.edu.au">unikey@uni.sydney.edu.au</a>. Here are some tips from SUITS to get the most out of your new email account.</p>
<p>To <strong>transfer your email </strong>from your old account to your new one, <a href="http://www.usyd.edu.au/ict/switch/SydneyMail/faq.shtml">follow these instructions</a>.</p>
<p>If you like to automatically <strong>forward your uni email </strong>to a non-uni account, you can redirect all emails by <a href="http://www.usyd.edu.au/ict/switch/SydneyMail/forwardemail.shtml">following these instructions</a>.</p>
<p>To <strong>pick up your uni email via POP</strong>, the POP server is <a href="http://outlook.com">outlook.com</a>, port 995 (if you enable SSL). The username to provide is <a href="mailto:unikey@uni.sydney.edu.au">unikey@uni.sydney.edu.au</a>. For more advanced setups including SMTP, <a href="http://www.usyd.edu.au/ict/switch/pdf/email/EML010Othermailservers.pdf">take a look at this</a>.</p>
<p>(This post contains info put together from <a href="http://edmundtse.wordpress.com/2009/05/07/sydney-mail-where-did-my-emails-go/">Edmund&#8217;s blog</a> and <a href="http://www.nointrigue.com/blog/2009/05/07/forwarding-university-of-sydney-student-email/">Enoch&#8217;s blog</a>.)</p>
<h3>Forwarding IT Email</h3>
<p>If you have an account with SIT, then you&#8217;ll have an IT email address. While not much emails are sent this this address (unless you tell people to), you might get the odd email every now and then.</p>
<pre>$ ssh USERNAME@mail.ug.it.usyd.edu.au
$ mailforward -a ADDRESS</pre>
]]></content:encoded>
			<wfw:commentRss>http://suits.it.usyd.edu.au/wordpress/2007/10/26/tutorial-email-forwarding/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
