Author Archives: George Ross

The project to replace EdLAN reached another milestone recently, with the completion of the migration of all subnets away from the old EdLAN core routers across to the new EdLAN distribution routers.  There’s now some tidying-up to be done, and … Continue reading →

As you’ll all be aware, the University is tightening up on network security in response to outside threats.    Within Informatics we have also been looking at ways to improve our security, and one area we have identified is that of … Continue reading →

As you’ll be aware by now, EdLAN is changing, though rather more slowly than was originally anticipated for various reasons, and the way that Informatics connects to it has to change too. Under the old EdLAN, the Informatics network in … Continue reading →

It’s time for us to arrange to reboot most of our network switches again.  We need to do this for a couple of reasons. The first is that the clocks that they use for management and reporting purposes tick in … Continue reading →

As part of the EdLAN replacement project, contractors are working their way round all of the University’s buildings to swap out the wireless access points for new ones.  The Bayes building has already been done (on Tuesday 18th January), and … Continue reading →

We’ve had IPv6 enabled on the “self-managed server” subnets (164 and 197) for quite a while now, and mostly it has been trouble-free.  Recently, however, we’ve had reports of login slowness to some self-managed servers following a system upgrade. What … Continue reading →

For many years we have used the OSPF routing protocol to exchange IPv4 and IPv6 routes with the rest of EdLAN as well as internally within Informatics.  As a result of the University’s network replacement project, however, that’s going to … Continue reading →

EdLAN is increasingly embracing site-local (“RFC1918“) addresses, and as a consequence we are beginning to see services being given such addresses. (A good argument could be made that the use of such addresses implies that they should never be accessible … Continue reading →

As we prepare to enable IPv6 on the “static self-managed” wires, there are a few aspects to IPv6 addressing which you need to know. The most obvious difference between IPv4 and IPv6 addresses is that the latter are 128 bits … Continue reading →

Following the introduction of IPv6 for the Forum self-managed dynamic-address subnet (and the ironing out of a couple of teething problems), we would now like to roll IPv6 out to the two “static-self-managed” subnets (“SM164” and “SM197”). We propose enabling … Continue reading →