Michael Mckeown
2016-12-29 14:59:55 UTC
Hi,
external_ip_alert used to when the session was first started pop an
alert for the ipv4 connection then pretty much straight away an alert
for the ipv6 connection (if any) then as time went on in the session you
would get alerts each time the ip changed (turning on a VPN, going from
WiFi to wired) but now when the session is first started you might get
an alert to know the ipv4 and likely won't get the follow up ipv6 alert
and likely won't get any alerts caused through adapter changes.
I'm not really seeing anything depreciated in the change-log that would
stop external_ip_alert functioning as it did, anyway do you think this
could be restored to it's former behavior as I think it's better to have
LibTorrent tell you when it's IP has changed rather than the client
monitor things instead.
Thanks.
external_ip_alert used to when the session was first started pop an
alert for the ipv4 connection then pretty much straight away an alert
for the ipv6 connection (if any) then as time went on in the session you
would get alerts each time the ip changed (turning on a VPN, going from
WiFi to wired) but now when the session is first started you might get
an alert to know the ipv4 and likely won't get the follow up ipv6 alert
and likely won't get any alerts caused through adapter changes.
I'm not really seeing anything depreciated in the change-log that would
stop external_ip_alert functioning as it did, anyway do you think this
could be restored to it's former behavior as I think it's better to have
LibTorrent tell you when it's IP has changed rather than the client
monitor things instead.
Thanks.