Skip to main content
K
kuba_mrowczynski
Participant
August 17, 2011
Answered

RTMFP stream issue when computers are behind the same NAT

  • August 17, 2011
  • 1 reply
  • 796 views

Hi there,

I've noticed an issue while creating one way (A publish B play) stream through RTMFP. When I try to create connection between computers behind the same NAT (same IP) stream playing is not fired at all, but on the other hand the same code works on remote computers (different IPs).

This issue arose after releasing final release of Flash Player, in a beta release everything works fine, so I'm really confused.

We checked NAT settings and there are no differences for this cases. I wonder where problem lies, any help will be appreciated.

Thanks in advance,

Jakub

    This topic has been closed for replies.
    Correct answer Michael Thornburgh

    if the publishing computer has some kind of local firewall and your NAT doesn't do hairpinning, the publisher may not accept a connection from the subscriber behind the same NAT because the RTMFP server can't UDP hole-punch for the right address (the subscriber's behind-NAT address).

    i checked the logs from the Codename Cirrus service and i can see the behind-NAT addresses being reported for Mac and Windows computers with Flash Player 10.3.183.5 (the latest release).

    you can improve the connectivity chances between peers by having both peers try to connect to each other simultaneously.  that will perform the UDP hole-punch from both ends, so each end's behind-NAT addresses will be tried by the other end.

    1 reply

    M
    Adobe Employee
    Michael ThornburghCorrect answer
    Adobe Employee
    August 18, 2011

    if the publishing computer has some kind of local firewall and your NAT doesn't do hairpinning, the publisher may not accept a connection from the subscriber behind the same NAT because the RTMFP server can't UDP hole-punch for the right address (the subscriber's behind-NAT address).

    i checked the logs from the Codename Cirrus service and i can see the behind-NAT addresses being reported for Mac and Windows computers with Flash Player 10.3.183.5 (the latest release).

    you can improve the connectivity chances between peers by having both peers try to connect to each other simultaneously.  that will perform the UDP hole-punch from both ends, so each end's behind-NAT addresses will be tried by the other end.

    K
    kuba_mrowczynskiAuthor
    Participant
    August 19, 2011

    Thank you for the hint

    You were right - it seems like creating two way connection solved the problem. Anyway, I don't know why it worked on beta 1 of FP 10.3, but now it doesn't matter at all.

    Best,

    Kuba

    M
    Adobe Employee
    Michael Thornburgh
    Adobe Employee
    August 19, 2011

    when it worked with the beta Flash Player, was everything else in your setup exactly the same?  the computers you were using were the same, the roles for each computer (subscriber or publisher) were the same, and there were no system configuration differences?  your code was exactly the same?

    that it doesn't work when you don't do the bidirectional thing and does work when you do the two-way connection suggests that the publisher has a local firewall configured.  is that new?  perhaps a result of a software update?

    no changes were made to RTMFP that would account for the difference in behavior between the beta and final release of FP 10.3.

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