| Address filtering is defined as (Ref Note 895.1) :
- Address filtering: you can tell the bridge that an address is "allowed"
on an arbitrary port or set of ports. This works both as a source address
filter (in that a packet with this address as source will only be
forwarded if it came in on one of the allowed set of ports); and as
a destination address filter (in that a packet with this address as
destination will only be forwarded to the allowed set of ports, and
in particular, only to the port on which the address was learnt if this
information is available).
From Server1's DECswitch's perspective, packets from Client1 will come in from
port1; i.e., the FDDI port.
If we create a source address filter with Client1's MAC address for the FDDI
port of this DECswitch , will this successfully prevent Client1's packets
from entering any of the Ethernet ports, including the one that Server1
connects to ? If not, what effect will such source address filter have ?
Richard
|
| > From Server1's DECswitch's perspective, packets from Client1 will come in from
> port1; i.e., the FDDI port.
> If we create a source address filter with Client1's MAC address for the FDDI
> port of this DECswitch , will this successfully prevent Client1's packets
> from entering any of the Ethernet ports, including the one that Server1
> connects to ? If not, what effect will such source address filter have ?
Sure.. this is what the filtering was designed for. That is, the switch
prevents Client1's packets from entering any port other than the one
it is allowed on. (Also, it sends packets destined to Client 1 only
to the FDDI port.) However I don't see how this would solve your
problem of creating the closed group.
Anil
|