scott wrote:

> For a start you can configure security on a per-port basis, ie limit 
> access to MAC address etc.
> 
> Then you can make rules for dropping packets, based on MAC address, IP 
> address etc.  Ie you could prevent the sockets in your conference room 
> from seeing your mail server unless a known MAC address was plugged in.
> 
> You can also have it notify you if an unknown MAC address appears on the 
> switch.
> 
> And a load of QoS stuff.
> 
> We also have our VoIP network going through the same switch as our data 
> network, this needs to be configured too.
> 
> They're far from simple boxes.

Then it's not a switch, is it?

A switch is a device that just connects network nodes together. What 
you're describing is a firewall and/or router.

Either way, we don't need any of the stuff you're describing.

[I notice HQ is very keen to implement VoIP though, even though we don't 
need it. On further investigation, it turns out that while the UK 
already has a perfectly good telephone system, HQ doesn't. So it would 
be more accurate to say that HQ needs VoIP...]

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message