Skip to main content
A
Anonymous
April 15, 2011
Question

NetGroup.Neighbor.Connect problem

  • April 15, 2011
  • 1 reply
  • 912 views

While testing p2p in different Internet connection modes, I have come  across the following problem. When a mobile operator modem is being  used, NetGroup.Neighbor.Connect event doesn't get created:



NetConnection.Connect.Success
NetGroup.Connect.Success

That's it.

Neither addMemberHint/addNeighbor, nor sendToAllNeighbors are of any help.

groupspec = new GroupSpecifier('1');
groupspec.serverChannelEnabled = true;
groupspec.multicastEnabled = true;
groupspec.postingEnabled = true;
groupspec.routingEnabled = true;
groupspec.peerToPeerDisabled = false;
groupspec.ipMulticastMemberUpdatesEnabled=true;

ng = new NetGroup(nc,groupspec.groupspecWithoutAuthorizations());

    This topic has been closed for replies.

    1 reply

    M
    Adobe Employee
    Michael Thornburgh
    Adobe Employee
    April 19, 2011

    P2P communication isn't always possible with all combinations of Network Address Translation (NAT) and firewalls.  Matthew Kaufman wrote up a good article on the different kinds of NAT behavior and how that affects P2P communication:

       http://forums.adobe.com/message/1064983#1064983

    most likely your network topology involves one of the kinds of NATs and/or firewalls that can complicate or preclude P2P communication, such as a "symmetric NAT" at one end combined with a port-restricted NAT or firewall at the other end, or possibly a multi-layer NAT situation combined with a local firewall on one or the other peers.

    note also that GroupSpecifier.ipMulticastMemberUpdatesEnabled=true doesn't do anything unless you also add an IP multicast address to the groupspec.

    NetGroup.sendToAllNeighbors() sends a message to all current neighbors; it doesn't add any new neighbors to the local node, so it wouldn't be expected to improve connectivity.

    if you find that peers sometimes connect if the order they join the group is reversed, or after a long delay, then that is also related to a NAT/firewall network topology issue.  the automatic group bootstrap function will be improved in a future release of FMS to address some additional network topologies.  but there will still be some topologies for which P2P communication is not possible.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices