Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

2022-11-29 Thread Mobeets
On Mon, 2 May 2022 11:40:54 +0800 Yangfl wrote: > This does not help a lot. Please, consider filling at least the > following information: > * The hardware type and software version of the clients; > * Network captures of IGD1 and IGD2 miniupnpds; > * miniupnpd log, if any. > > Hello, I believe

Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

2022-05-01 Thread Yangfl
This does not help a lot. Please, consider filling at least the following information: * The hardware type and software version of the clients; * Network captures of IGD1 and IGD2 miniupnpds; * miniupnpd log, if any.

Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

2022-04-11 Thread Matteo Croce
Hi, I don't know what differs, but after several tries, I found that only the compile time change fixes it. If you look on some online forums it seems a known issue, and recompilation is the only workaround by now. -- per aspera ad upstream

Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

2022-04-02 Thread Yangfl
Control: tags -1 moreinfo On Fri, 01 Apr 2022 20:41:29 +0200 Matteo Croce wrote: > Package: miniupnpd > Version: 2.2.1-1 > Severity: normal > > Dear Maintainer, > > miniupnpd has the force_igd_desc_v1 config option to use the v1 IGD descriptor. > Unfortunately, the runtime behaviour differs

Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

2022-04-01 Thread Matteo Croce
Package: miniupnpd Version: 2.2.1-1 Severity: normal Dear Maintainer, miniupnpd has the force_igd_desc_v1 config option to use the v1 IGD descriptor. Unfortunately, the runtime behaviour differs between the daemon compiled with and without --igd2, even when force_igd_desc_v1 set. This makes the