4 ms·

There is enable p2p, its called disabling client isolation mode. This isn't even specifically about multicast. Its just the peers (clients) cannot make unicast

by g45y45 8y ago

There is enable p2p, its called disabling client isolation mode. This isn't even specifically about multicast. Its just the peers (clients) cannot make unicast connections to each other.

Spivak 8y ago
The peers can't discover each other without multicast.
- g45y45 8y ago
  Very likely! But it could scan the subnet, like say a printer driver does. Multicast is the easiest, but not the only way. The issue mentioned in the article is likely related to both mDNS blocking and client isolation (peer to peer).
  - syshum 8y ago
    >>Very likely! But it could scan the subnet, Do you have documentation on this product that indicates it scans the subnet?
    - g45y45 8y ago
      I have no idea of the peer discovery mechanism in this product -- I was just stating that multicast is not the only peer discovery mechanism, ala printers and other consumer kit that scans the subnet.
syshum 8y ago
>> its called disabling client isolation mode. So then you proved your statement wrong, there is not a setting or feature called "enable p2p" >This isn't even specifically about multicast According to the article it is
- g45y45 8y ago
  Buddy, client isolation mode or lack there of is sometimes called allowing 'peer to peer' traffic. I understand the ambiguity over TCP P2P networks, but given the context most network engineers know what you are talking about. Regarding the article mentioning multicast -- the engineer SUSPECTS its to do with multicast. Im saying it could be due to several configuration issues, but most likely client isolation mode (aka not allowing peer-to-peer traffic). Why pick a fight over this?
  - syshum 8y ago
    I am not your buddy, pal... as far as picking a "fight" I was not, I was being technical. When it comes to talking about Technical things I prefer when people are technical. This is key when writing technical documentation. For example, if you were writing a technical doc you would not put in the doc "Turn on P2P feature" as that feature does not exist, instead you would say "To enable P2P communication, turn off Client Isolation" One should be technical when talking about technical things, and assuming "most network engineers know what you are talking about" is often how mistakes are made... I have seen companies lose millions because one engineer assumed another engineer knew or thought about, or would preform steps not included implicitly in an instruction set

by g45y45 8y ago

There is enable p2p, its called disabling client isolation mode. This isn't even specifically about multicast. Its just the peers (clients) cannot make unicast connections to each other.

Spivak 8y ago

The peers can't discover each other without multicast.

g45y45 8y ago
Very likely! But it could scan the subnet, like say a printer driver does. Multicast is the easiest, but not the only way. The issue mentioned in the article is likely related to both mDNS blocking and client isolation (peer to peer).
- syshum 8y ago
  >>Very likely! But it could scan the subnet, Do you have documentation on this product that indicates it scans the subnet?
  - g45y45 8y ago
    I have no idea of the peer discovery mechanism in this product -- I was just stating that multicast is not the only peer discovery mechanism, ala printers and other consumer kit that scans the subnet.

syshum 8y ago

>> its called disabling client isolation mode. So then you proved your statement wrong, there is not a setting or feature called "enable p2p" >This isn't even specifically about multicast According to the article it is

g45y45 8y ago
Buddy, client isolation mode or lack there of is sometimes called allowing 'peer to peer' traffic. I understand the ambiguity over TCP P2P networks, but given the context most network engineers know what you are talking about. Regarding the article mentioning multicast -- the engineer SUSPECTS its to do with multicast. Im saying it could be due to several configuration issues, but most likely client isolation mode (aka not allowing peer-to-peer traffic). Why pick a fight over this?
- syshum 8y ago
  I am not your buddy, pal... as far as picking a "fight" I was not, I was being technical. When it comes to talking about Technical things I prefer when people are technical. This is key when writing technical documentation. For example, if you were writing a technical doc you would not put in the doc "Turn on P2P feature" as that feature does not exist, instead you would say "To enable P2P communication, turn off Client Isolation" One should be technical when talking about technical things, and assuming "most network engineers know what you are talking about" is often how mistakes are made... I have seen companies lose millions because one engineer assumed another engineer knew or thought about, or would preform steps not included implicitly in an instruction set