Releases: alanmcgovern/Mono.Nat
Releases · alanmcgovern/Mono.Nat
v3.0.4
v3.0.3
General
- Minor improvement to performance when listening for broadcast messages from multiple sockets.
Full Changelog: release-v3.0.2...release-v3.0.3
v3.0.2
General
- Fixes a NullReferenceException caused by
StackFrame.GetMethod ().ReflectedType
when running under UWP.
v3.0.1
v3.0.0
General:
- Removed
NatUtility.DeviceLost
as it was never a usable event. - Added the ability to manually pass messages into Mono.Nat if another part of the application has already bound to the normal upnp listening port.
- Improved logging via Logger.Factory
- Searchers are disposed when
NatUtility.StopDiscovery
is invoked, and (re-)created whenNatUtility.StartDiscovery
is invoked. In addition any previously detected devices are cleared whenStopDiscovery
is invoked.
v2.0.2
General
- Minor memory optimisations contributed by Bond-009.
- Improved support for some devices which do not correctly respond to an
ssdp:all
message. In addition to sending a request for all services, the library additionally searches for WanPPPConnection and WanIPConnection services. - Calling
NatUtility.StopDiscovery
clears the detected devices, thus allow devices to be reliably re-discovered if StartDiscovery is called again at a later point.
v2.0.1
General
-
Mono.Nat now tries to generate a reasonably unique
Description
for each port mapping. Some routers will refuse to create a new port map if the description matches the description of an existing port mapping, even if the ports are different. -
Improved diagnostic logs are emitted when when NatUtility.Logger is not null.
-
Mono.Nat issues uPnP discovery requests using each enabled network adapter. If a device is discovered, Mono.Nat will now ensure all network requests use the same adapter.
v2.0.0
General
-
Migrated to .NET Standard 2.0 and migrated to a Task based system, which works much better with the modern async/await support.
-
Some minor bugfixes to uPnP to better support Virgin Media Superhub 3 routers.