In computer networking, promiscuous traffic, or cross-talking,[1] describes situations where a receiver configured to receive a particular data stream receives that data stream and others. Promiscuous traffic should not be confused with the promiscuous mode, which is a network card configuration.
In particular, in multicastsocket networking, an example of promiscuous traffic is when a socket configured to listen on a specific multicast address group A with a specific port P, noted A:P, receives traffic from A:P but also from another multicast source. For instance, a socket is configured to receive traffic from the multicast group address 203.0.113.70, port 36000 (noted 203.0.113.70:36000), but receives traffic from both 203.0.113.70:36000 and 203.0.113.71:36000.
This type of promiscuous traffic, due to a lack of address filtering, has been a recurring issue with certain Unix and Linux kernels,[2][3] but has never been reported on Microsoft Windows operating systems post Windows XP.
Another form of promiscuous traffic occurs when two different applications happen to listen on the same group address. As the former type of promiscuous traffic (lack of address filtering) can be considered a bug at the operating system level, the latter reflects global configuration issues.
promiscuous, traffic, computer, networking, promiscuous, traffic, cross, talking, describes, situations, where, receiver, configured, receive, particular, data, stream, receives, that, data, stream, others, should, confused, with, promiscuous, mode, which, net. In computer networking promiscuous traffic or cross talking 1 describes situations where a receiver configured to receive a particular data stream receives that data stream and others Promiscuous traffic should not be confused with the promiscuous mode which is a network card configuration In particular in multicast socket networking an example of promiscuous traffic is when a socket configured to listen on a specific multicast address group A with a specific port P noted A P receives traffic from A P but also from another multicast source For instance a socket is configured to receive traffic from the multicast group address 203 0 113 70 port 36000 noted 203 0 113 70 36000 but receives traffic from both 203 0 113 70 36000 and 203 0 113 71 36000 This type of promiscuous traffic due to a lack of address filtering has been a recurring issue with certain Unix and Linux kernels 2 3 but has never been reported on Microsoft Windows operating systems post Windows XP Another form of promiscuous traffic occurs when two different applications happen to listen on the same group address As the former type of promiscuous traffic lack of address filtering can be considered a bug at the operating system level the latter reflects global configuration issues References edit Inspired from the electronics term crosstalk Red Hat Bug 231899 multicast incorrect handling https bugzilla redhat com show bug cgi id 231899 Sun Microsystems forum Multicast socket problem http forums sun com thread jspa threadID 566608External links editTool to detect promiscuous traffic with the JBoss product Cross talking between clusters with same multicast ports but different multicast addresses multicast same port different IP address this thread relates of a practical case where a developer wants to use several addresses with a same port nbsp This computer networking article is a stub You can help Wikipedia by expanding it vte Retrieved from https en wikipedia org w index php title Promiscuous traffic amp oldid 1203653235, wikipedia, wiki, book, books, library,
