Autumn 2007 Timetable

	Monday	Tuesday	Wednesday	Thursday	Friday
8am	Bluearc			Bluearc
9am
10am
11am		Project Management & Quality Assurance (31478) Lec1, 01 CM05B.01.11
12pm
1pm
2pm		Project Management & Quality Assurance (31478) Tut1, 05 CB10.02.320			Mobile IP and Wireless LANs (31089) CB10.02.440/CB01.23.16/CB10.03.440
3pm
4pm		Information Technology Professional & Society (31479) Tut1, 05 CB10.02.470
5pm
6pm		Information Technology Professional & Society (31479) Lec1, 01 CB02.04.13
7pm
8pm
9pm

We got another letter today. Looks like the owner of our new house wants to sell it. We've only been here about 2 months.



Grrrr.

I want to setup something like this.



So basically it would include:

• VPN (ipsec) links to each user
• BGP or OSPF running tunneled through the VPN (to advertise the networks everyone is running)
  
• Internal DNS system

I've got a stack of networking gear now (netscreen and cisco stuff), most of it is fairly old but should be more than capable of doing what I want.



If anyone is interested send me an email.

I finally got an IPv6 tunnel going on my Netscreen SSG 5. So I thought I'd post the relevant configuration details here.



I'm currently running ScreenOS 5.4.0r3a0; there seems to be some WebUI bugs with IPv6 so it is best to do it via the command line.



Update: I just got a response back from JTAC. IPv6 is only supported on the ISG2000. So I'm unsure when/if it the WebUI bugs will be fixed.



Update2: IPv6 is now supported on the SSG 5 under screenos 6, the WEBUI bug has been fixed.



Background info:

• Trust interface 10.0.0.254/22 - bgroup0
• Untrust interface - bgroup2
• IPv6 broker (broker.aarnet.net.au) - 202.158.196.131
• IPv6 subnet - 2001:388:c021::1/64

The first step is to enable IPv6 on your Netscreen.



Type the following then save your config and restart the device:




Now let's setup the trust interface:




So we've setup my trust interface with the IPv6 subnet and autoconfiguration should be working.



Now let's setup a tunnel interface for the traffic to run through:




Now we'll setup a static route for IPv6 traffic to go through:




And finally we need to setup a policy to allow traffic out:




You may want to setup some policies to allow traffic in too.



That should be all you need to do.

Our web server died a few weeks ago, I was lucky enough to borrow a spare DL380 G1 from work. Although we still have it, I'm not sure if we'll be able to keep it.



So this new server is a DL360 G1 (1 rack unit):

• Dual Pentium 3 1.266GHz (512K L2 Cache)
• 256mb Ram (we will upgrade it if it goes into production)
• 18gb SCSI HDD
• 2 100mbit onboard nics

Here is what it looks like:

I finally setup LDAP on Kerio. I now have my contacts synced with webmail, mac address book and my phone. Awesome.







Anyone who uses our email server can now make use of this too.



The server (mail.lttd.net) allows secure LDAP connections on port 16360 (636 is the standard port but the mail server is also a domain controller, so that port is in use).



More details can be found in the Kerio User Manual:

http://download.kerio.com/dwn/kmsug6-en.pdf