[NOTAM] Changes to the UDP Broadcast Packet

ThirdParty
1

I’ve made changes to the way the broadcaster works.

We now listen on all interfaces on the device, including IPv6 interfaces. Not sure if it actually does work on an ipv6 only stack since I haven’t tested yet.

So since the app now listens to multiple interfaces, the UDP broadcast packet contains a list of strings instead of just one address.

This is what the class looks like now:

[DataContract]
public class APIServerInfo
{
    [DataMember]
    public string[] Addresses { get; set; }
    [DataMember]
    public int Port { get; set; }
}

Cheers!

23 Likes
2

Does that mean Liveflight connect should work with my device? My device only supports IPV6

3

It won’t without it being updated, but this opens the door to do so.

1 Like
4

Code for dummies.m - Does this mean that we can utilise LiveFlight on mac?

5

Doesn’t LiveFlight connect work on Mac? I’m pretty sure it does. If you mean liveflight standard, it uses a different API and is not a desktop app :)

6

What’s your provider? T-Mobile? Are you able to connect to Live?

1 Like
7

Yes T-Mobile, and I am able to connect to Live.

8

Thanks, we’ve got one user who can’t… it’s a mystery why…

2 Likes
9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.