-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LiveTraffic sending data over wrong NIC #65
Comments
Similar to TwinFan/LiveTraffic#221. Totally different functionality, but behind the scenes similar networking code at play. |
The "Remote" functionality uses UDP Multicast. Reading through some Stackoverflow threads I believe the receiving side of Mutlicast is fine with binding to Also see section 6.3 IP_MULTICAST_IF in this document, offering a way to specify the sending interface via a call to The basic idea to solve this is "to send to where we received from", making use of the fact that also the Remote Client sends out a Beacon if no actual traffic data is yet broadcasted:
|
Works with IPv6, probably not yet with IPv4
@Eggman1414 . would you want to try updated software? Here's a beta version of LiveTraffic together with an updated version of the Remote Client. "Beta" means time-limited for one month, but I plan to publish official versions long before that. Two things yet missing, one is a configuration option to tell the remote functionality the interface to use. But I'd actually appreciate feedback on this version without the config option because I try hard to keep the Remote Client a zero-config software: It shall auto-discover the correct network interface to use. For that both sender (LiveTraffic) and receive (Remote Client) need to be updated. For more details refer to the two From your issue I guess you are on Windows, only Windows included here: Thanks in advance for any feedback! In case of any issue please add |
@TwinFan Sure thing! I will test tomorrow and let you know the results. Thank you |
@TwinFan Installed the new build and same issue. I have included both logs (1 from Master and 1 from one of the Clients (there are 4 in total). Looks like clients are sending beacon back correctly over multicast but not Master to Client. Everything should be going out DIS NIC. Master - 10.100.40.100 |
Hm, that's a pitty given all the effort put into that code... In the Wireshark screenshot
Latest BuildAnyway...I provide you here with the latest build: This adds a little more output for the log: It will show which interfces the clients are aware of. And it now also includes the possibility to explicietly specify the interface the remote functionality is to use only, meant as a last resort. Without Config FilePlease try the new version once again without config file and let's check the output on identified interfaces. Should look something like this:
Specifying the Interface to UseI don't expect it to work, though, nothing should have changed in that respect. Then go ahead and configure the interface to use: Copy the
Do that on both Master and Client. (Obviously, the configured interface could be named differently on those two hosts, but both hosts need that |
Ok I think I might of found something. Im pretty sure XPMP2-Remote is working fine. I am receiving the beacon packets from Client(10.100.40.101) on Master(10.100.40.100). Packet: 239.255.1.1 and Port 49788. But it seems like LiveTraffic is not responding to the requests. On the master PC I have 3 NIC's (1 for Sim Traffic, 1 for Avionics Traffic, and a Docker NIC). If I disable the First NIC (Avionics), and reload the plugin, BAM!. Traffic is now being sent by LiveTraffic on Master to Clients. So in short, XPMP2-Remote is probably fine, but LiveTraffic might be having problems with multiple nics. |
Adding XPMP2.prf to Master Client and Changing remoteSendIntf to "remoteSendIntf DIS" worked on launch. Did not have to change Client (But Im guessing because the client only has one interface so not an issue) |
Thanks for trying it. So the specific config did its intended work, great. And, yes, no need to configure the client when it just has one NIC. |
@Eggman1414 , would you do me the favour to try these versions without using a With LiveTraffic now explicetely joing all interfaces I have the hope that specifying the interface is no longer required. In DEBUG mode, LiveTraffic will state which interfaces it joined like this:
But if still LiveTraffic doesn't receive the beacon and hence doesn't start sending, then |
Great to hear, thanks for verifying! The interesting parts of the log are these:
|
Describe the bug
When used in a master client configuration with external views (each running XPMP2-Remote), LiveTraffic (Master) sends out the position data for the remote clients on the first NIC listed in windows. When first NIC is disabled, traffic is seen on clients.
Expected behavior
Send multicast data over same nic used for external view configuration. Or have a drop down selection for which NIC to use for sending data.
Technical Info
Log.txt
Log.txt
The text was updated successfully, but these errors were encountered: