Depends. I've seen networks where the device was on the ethernet prior to
the routers attaching to the WAN - in larger networks there tend to be multiple
such ethernet "hub LANs" and multiple WAN links for redundancy. (BTW, I'm
referring to the case where the device is on the WAN edge of the client site,
but could be in the server site as well)
The workaround to get the packeteer in the path in both directions was to play
around with ospf costs on the LAN interfaces of the router.
Of course, as you mention, a device that does naughty things could have
in the simple cases as well - just pointing out cases where I've seen failure in
--- jamal <hadi@xxxxxxxxxx> wrote:
> Actually, route asymmetry may not be much of a factor here.
> Most of these devices are at the client's edge as opposed to the server
> end i.e they protect the client's network portion of the resources. So you
> will come and go via them.
> (in any case the above test would be sufficient if done one way).
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/