On 03.05.2002 at 09:52:03, Steve Kotzmoyer <[EMAIL PROTECTED]> wrote:
> I thought it was a good question. Agreed, a great question. > Knowing that IBM hardware/software generally does not support promiscuous > mode, I was waiting to see a response too. Ethernet hardware from any manufacturer should support promiscuous mode, because all it has to do is become interested in all packets rather than just its own. If the manufacturer chooses to restrict the features they provide in their software driver, however, that's a different story. ;) IBM's Token Ring adapters were generally the ones that didn't support promiscuous mode. They had certain adapters that did, that they charged a heap for, so that you could do data analysis with products like TAP and DatagLANce. Apparently, promiscuous mode is not as simple in Token Ring, since you don't want to set the normal 'frame copied' bits, etc. In the OSA case, it might not be enough to put it in promiscuous mode, because of the OAT. If the LPAR that puts the OSA into promiscuous mode is the primary router, you'll probably be ok. If not, you might not see all the traffic -- like when you try and sniff your LAN from a switch port; you see all of your own traffic, and none of anyone else's. Also, what about how a *shared* OSA handles promiscuous mode -- does it send the traffic to all connected LPARs, or just the one that put it in promiscuous mode? Cheers, Vic Cross -- Vic Cross MACS mailto:[EMAIL PROTECTED] Networking, Linux, on zSeries and S/390
