Geoff

Do you get any noise complaints from using that setup anywhere (library, offices, etc?)

Yes, you'd only want IPv6 if something upstream required it (Do any RBCs even support IPv6? Plus almost all IPv6 enabled websites have an IPv4 address too)

If you still have kit kicking around that doesn't know what IPv6 is or worse misbehaves if it sees some then you should patch the software/firmware or replace it. IPv6 has been an IETF standard since 1998 and widely deployed since 2008 after all. But of course I'm sure everyone refreshes their hardware/software regularly enough for this not to be an issue? Also if you try and disable IPv6 on Win8 the whole networking stack stops working (unticking it in the network adapter settings does nothing. Using the Win7 reghack breaks the whole IP stack).

Just be aware ventilation on it's own may not enough. Ventilation will do very little for you if the outside ambient temperature is high enough (granted we've not had a hot summer for a while now). More of a concern for me is that you don't have any control over the humidity (venting directly to the outside might make the humidity higher in some cases too). Condensation tends to love to collect on all those metal surfaces that make up your racks and equipment casings. So my advice if you can then do go for full climate control air conditioning.

Yes there's aspects of Foursquare (you get 'points' for going places) but the places can be anything and you don't know about them until you are in the immediate area, so it's got a lot of similarities to Geo-caching too.

If you want to embark in setting up DHCPv6 then you might want to familiarise yourself with basic IPv6 networking first.

This is the basic problem though isn't' it? You're endlessly playing whack a mole with no end in sight. It doesn't matter what you do technically there will always be something you miss or are unable to combat.

It depends what temperature it is. Anything over 30C is problematic and anything over 40C is dangerous. If the room is getting in this temperature range ('borrow' the thermal sensor kit science departments always have, or a simple greenhouse thermometer with min/max on it) then you will need to fit air con or reduce the amount of equipment you have in that room.

You probably want Login=PASSTHRU so that your proxy passes the request to the swgfl proxy with whatever credentials provided by your users.

To bridge ISDN to Asterisk (trixbox or whatever) you'll need an interface card. The dual port Sangoma A102's I usually use cost ~£500 each. http://sangoma.com/products/telecom_boards/digital/a102.html You'll also need an E1 crossover cable.

Just use the serial console. It's massively easier to sort this out with local access.

Next stop your LEA helldesk.

If the proxy you are going through is being nice it should identify itself on the HTTP headers it sends to websites. Therefore you can inspect the headers on special websites setup to tell you what you're asking of them. xhaus.com: HTTP header check

Your teachers will have to bypass your internal proxy then.

You can't chain proxy authentication like that. If you used the staff proxy as an upstream it would end up authenticating your proxy with whatever staff member happened to login first. Then all subsequent accesses via you proxy will be handled as if that staff member was accessing the websites. I imagine this isn't what you want to happen.

What is the purpose of the 'LEA staff proxy' and why do you want to access it via your internal squid proxy?

I've never used one myself. Not a big Nortel fan. A bit of googling turned up this though. Nortel BCM Interoperability SIP and TRIXBOX - voip-info.org

I use Polycom IP501/550's. They have a Ethernet pass through port and understand VLANS. I don't actually use the pass through port normally although I have a couple of places where I do. No problems.

It supports SIP out of the box.

Ok then, my back of a napkin apache config looks like this? LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule headers_module modules/mod_headers.so LoadFile /usr/lib/libxml2.so LoadModule proxy_html_module modules/mod_proxy_html.so LoadModule xml2enc_module modules/mod_xml2enc.so ProxyRequests off ProxyPass /frog/ http://frog.internal.example.com/ ProxyHTMLURLMap http://frog.internal.example.com /frog ProxyPassReverse / ProxyHTMLEnable On ProxyHTMLURLMap / /frog/ RequestHeader unset Accept-Encoding For the purposes of the above configuration I've ignored the possibility of any caching/load balancing/etc.

Be aware that this will break SSL.

The other option if it's not a netbios name clash is that you are still(!) running a WINS server and there are old bad records in there that need clearing out.

Yep, if you have physical access to a machine it's game over.

Pop the battery.

Sometimes poorly grounded power cables are a blessing.