It does indeed support this feature.
To select the output port, where you connect the packet sniffer, use the command
<b>mirror-port <port></b>
where <port> is the port you want to use for the output.
To select the ports you want to monitor, use the command
<b>interface ethernet < monitor-list > monitor</b>
where: < monitor-list > includes port numbers and static trunk names such as a4, c7, b5-b8, and trk1.
To turn either of these off, prefix the command with '<b>no</b>'.
These are also available through the web interface, but the CLI is an easy way, and the way that I configure any of these switches.
Hope this helps.
I think the question is about ACL’s or traffic filters for certain traffic types.
It clearly says ‘port monitoring’ and that is what I posted the commands for !
Yeah, that’s the unfortunate part of a “submitted question” — sometimes difficult to interpret exactly what is being asked. Just wanted to say that I appreciate both of your responses and input.
p.s. BlankReg – love your avatar. Is that a punk rocker I should recognize or is that you?
That was the ‘real’ Blank Reg from the Max Headroom TV series. He was a close friend of Edison Carter, and pirated the education tv channels so the poor kids could have some schooling as everything was delivered and run by the TV companies.
Further thought, I have come across web filters that do the job by sniffing packets and then make block or allow decisions based on the first few content replies. So using a monitor port is actually a possibility for this user.
If you can get them to clarify, and I guessed wrong, then I can possibly have another stab at it, but the HP 4104GL is layer 2 so the filtering capabilities are limited. Not a bad switch, for the price, but not very feature rich.