Instructions for testing MFP and NAT traversal

Tests for MFP and NAT traversal are described below and should be performed in given order. Please collect logs and account details of all entered parties in case of test failure.

Please tell us your NAT model.

1. Peers must have following in their user preferences to enable MFP and to use direct MFP connection approach :
   • user_pref(”allpeers.enable_mfp”, true);
   • user_pref(”allpeers.mfp_approach”, 1);
   • user_pref(”allpeers.superhub”, “213.246.37.54:36001”);
2. MFP is preferred connection mechanism so it will be tried first when attempting to establish connection with other peer. Add following to disable connectivity with non-MFP peers altogether :
   • user_pref(”allpeers.binding_address”, “1.1.1.1”);

1. Start AllPeers.
2. Share some files with other MFP-enabled peers in your buddy list.
3. Add new MFP-enabled contacts.
4. Repeat 2nd and 3rd steps few times.

1. Only MFP will be used for outgoing connections with directly accessible MFP-enabled peers. Transfer statistics page at ‘chrome://allpeers/content/workbench/apTransportStatistics.xhtml’ might be of assistance to see what mechanisms are used.
2. In case of using preference in 2nd prerequisity, all incomming connections from other directly accessible peers must go through MFP.
3. MFP must not fail to establish connection with any directly accessible MFP-enabled peer. For each “mfp:<context>” log entry “establisher finished with <status code>” where status code != 0, there is another entry with same context reading “establish to <IP address>, resolving”. The test fails when such IP address belongs to MFP-enabled client which was online and accessible at that time.
4. All traffic through MFP must be error free. There should be no corrupted files, no parsing errors etc. - search logs for @ERROR and @WARN entries.

1. Use following user preferences for peers :
   • user_pref(”allpeers.enable_mfp”, true);
   • user_pref(”allpeers.mfp_approach”, 5);
   • user_pref(”allpeers.superhub”, “213.246.37.54:36001”);
2. At least one MFP-enabled relay peer/server is necessary. It must have ‘user_pref(”allpeers.enable_mfp”, true);’ in its user preferences and must be used by the peer(s) behind NAT as their relay.
3. Some, preferably all, MFP-enabled peers must be behind different NATs. Only pairs of peers behind different NATs are of value in this test. Currently, it is possible to traverse only non-symmetric NATs. You can find out the type of most restrictive NAT between you and the internet by following instructions posted here .

Like in 1st test with emphasis to exercising connection establishing and acceptation.

1. #5 If there is a MFP connection between two peers behind different NATs, try restarting AllPeers at one or both peers to see whether the connection will come up again.

Identical to those in 1st test with addition of :

1. #5 Peers behind different NATs should use MFP mediation to traverse NAT. In tranfer statistics page, there should be “mfp mediated” in Fashion column of corresponding transfer.

1. Relay server(s) as described in 2nd prerequisity of prior test.
2. Add following to user preferences for peers :
   • user_pref(”allpeers.enable_mfp”, true);
   • user_pref(”allpeers.mfp_approach”, 6);
   • user_pref(”allpeers.superhub”, “213.246.37.54:36001”);
3. Part of peers must be behind one or more NATs while some should be directly accessible by others.

Identical to 2nd test.

Like in 2nd test with addition of :

1. #6 Peers directly accessible should not try mediation. Easy to verify by comparing results with 2nd test assuming the same group of peers was used.