On Sat, Mar 03, 2018 at 11:49:35PM +0100, miniupnp wrote:
> Le 03.03.2018 à 04:41, Adam Borowski a écrit :
> > Obviously, it'd be preferable if the daemon listened on all
> > interfaces, but
> > if it needs one, the default route is a reasonable answer.
> >
> You should prefer listening on only
Le 03.03.2018 à 04:41, Adam Borowski a écrit :
> Obviously, it'd be preferable if the daemon listened on all
> interfaces, but
> if it needs one, the default route is a reasonable answer.
>
>
You should prefer listening on only "LAN" network interfaces, the ones
which have a RFC 1918 address.
If
On Fri, Mar 02, 2018 at 03:28:12AM +0100, miniupnp wrote:
> It can happen if minissdpd is run with -6 option to enable IPv6 but the
> network interface to listen to is not specified correctly by name (eth0).
> Please check what command line arguments are used.
> It should be something like
>
Le 26.02.2018 à 01:28, Adam Borowski a écrit :
>> Since upgrading from 1.2.20130907-4.1 to 1.5.20161216-2 this week (as a
>> result of the updated package hitting testing) I'm getting lots of
>> messages of the form:
>>
>> Feb 16 09:36:14 eris minissdpd[15233]: peer a.b.c.d:60644 is not from a LAN
> Since upgrading from 1.2.20130907-4.1 to 1.5.20161216-2 this week (as a
> result of the updated package hitting testing) I'm getting lots of
> messages of the form:
>
> Feb 16 09:36:14 eris minissdpd[15233]: peer a.b.c.d:60644 is not from a LAN
This includes the gateway (both IPv4 and IPv6),
5 matches
Mail list logo