Revision history [back]

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when only 1 NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a dedicated NIC impossible - regardless on Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch.Apparently,, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC?

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when only 1 just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a dedicated NIC impossible - regardless on Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline Freephoneline app allows to bind it to a selected adapter at each launch.Apparently,, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC?PC? Is there any defect in latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incomoing and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless on of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch.Apparently,, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incomoing and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch.Apparently,, launch. Apparently,, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incomoing and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently,, Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incomoing and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incomoing and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incomoing incoming and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incoming and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest latest ForceBindIP that prevent it to completely bind a selected app traffic to a certain adapter, including incoming and outgoing segments? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevent prevents it to from completely bind binding a selected app traffic to a certain adapter, including incoming and outgoing segments? adapter in both directions? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevents it from completely binding a selected app traffic to a certain adapter in both directions? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter with lower Metric. While I'm trying to separate all VoIP traffic to one dedicated adapter.

I'm trying to capture Freephoneline app calls on a dedicated PC NIC by running Wireshark 2.4.2 on a Windows 10 64-bit PC. The captured calls from Freephoneline to an ATA are SIP type, and show up in Wireshark VoIP Calls window. But only when just one PC NIC is enabled. When 2 NICs are enabled, Windows redistributes traffic between them in a way that makes capturing Freephoneline on a single dedicated NIC impossible - regardless of Metric manually set in each NIC Properties or auto assigned.

This happens despite Freephoneline app allows to bind it to a selected adapter at each launch. Apparently, such binding works only for some calls, and even for them handshake goes through an adapter with lower Metric. I also tried using ForceBindIP app to further bind Freephoneline to a certain adapter, yet again not all its traffic went through that adapter, thus preventing capturing it as VoIP call.

Are their other options to completely limit Freephoneline traffic only to one NIC, while several NICs are enabled on the PC? Is there any defect in latest ForceBindIP that prevents it from completely binding a selected app traffic to a certain adapter in both directions? AdapterWatch shows that the app seems to bind traffic OK, but probably some initial SIP packets still pass through the 2nd adapter with lower Metric. While I'm trying to separate all VoIP traffic to one dedicated adapter.