On Wed, 17 Oct 2007, James Carlson wrote: > I'm not sure I understand "physicall network" in this context, but I > suspect that it's a reference to the PCI inteface you've described, > and not to another network interface. > > My assumption (at this point) is that the daemon binds > 127.0.0.1:16992, accepts connections (one or many? can there be > simultaneous sessions?), and then relays the messages to the kernel > driver which sends them over the PCI bus to this card.
>> A: No. Any packet destined to the 16992 port is filtered by the NIC as >> OOB data to the AMT ME. > > NICs don't filter data by themselves, there's no NIC related to > 127.0.0.1, and I don't understand what "OOB" means in this context. Firmware 'near' the NIC (I've never seen an explanation of the exact mechanism) interposes itself between hardware and OS and 'hijacks' traffic to that port. It never makes it to the OS. Essentially, LOMish firmware and host are sharing a NIC, presumably to save money - on hardware in the first instance, and possibly even on IP administration of a LOM in the second. IMLU. (The clean answer of course would have been to just add dual-MAC capability to the NIC, and let the LOMish/OoB-management firmware have it's own MAC address and IP). regards, -- Paul Jakma, Solaris Networking Sun Microsystems, Scotland http://opensolaris.org/os/project/quagga tel: EMEA x73150 / +44 15066 73150
