The forwarding table points to the channel, not a specific interface on
the channel.
This also allows adding and dropping links on the fly.
Pete
Don Bowman wrote:
From: Petri Helenius [mailto:pete@;he.iki.fi]
It does not matter if you send using the other link as long
as you send
all packets
> From: Petri Helenius [mailto:pete@;he.iki.fi]
> It does not matter if you send using the other link as long
> as you send
> all packets
> for the same stream over the same link to avoid reordering.
> So yes, it does
> interoperate.
can you end up with a link flap?
e.g. the catalyst does SA le
It does not matter if you send using the other link as long as you send
all packets
for the same stream over the same link to avoid reordering. So yes, it does
interoperate.
Pete
Don Bowman wrote:
Examining the source code to ng_fec, in ng_fec_output(), it uses the
IP address to form the hash
Examining the source code to ng_fec, in ng_fec_output(), it uses the
IP address to form the hash to pick the port. This is the same behaviour
that 802.3ad specifies, and yields good behaviour since:
a: it works in routed environments as well as local area
b: packets are not reordered within L4 se
