Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #246035 > unrolled thread

cups/avahi-daemon - worrying logs

Started byRichard Hector <richard@walnut.gen.nz>
First post2022-03-08 01:30 +0100
Last post2022-03-17 07:50 +0100
Articles 3 — 1 participant

Back to article view | Back to linux.debian.user

Contents

  cups/avahi-daemon - worrying logs Richard Hector <richard@walnut.gen.nz> - 2022-03-08 01:30 +0100
    Re: cups/avahi-daemon - worrying logs Richard Hector <richard@walnut.gen.nz> - 2022-03-17 06:20 +0100
      Re: cups/avahi-daemon - worrying logs Richard Hector <richard@walnut.gen.nz> - 2022-03-17 07:50 +0100

#246035 — cups/avahi-daemon - worrying logs

FromRichard Hector <richard@walnut.gen.nz>
Date2022-03-08 01:30 +0100
Subjectcups/avahi-daemon - worrying logs
Message-ID<DYvTH-eBD-3@gated-at.bofh.it>
Hi all,

I've recently set up a small box to run cups, to provide network access 
to a USB-only printer. It's a 32-bit machine running bullseye.

I'm seeing log messages like these:

> Mar  7 15:47:47 whio avahi-daemon[310]: Record [Brother\032HL-2140\032\064\032whio._ipps._tcp.local#011IN#011SRV 0 0 631 whio.local ; ttl=120] not fitting in legacy unicast packet, dropping.
> Mar  7 15:47:47 whio avahi-daemon[310]: Record [whio.local#011IN#011AAAA fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not fitting in legacy unicast packet, dropping.
> Mar  7 15:47:48 whio avahi-daemon[310]: Record [Brother\032HL-2140\032\064\032whio._ipp._tcp.local#011IN#011SRV 0 0 631 whio.local ; ttl=120] not fitting in legacy unicast packet, dropping.
> Mar  7 15:47:48 whio avahi-daemon[310]: Record [whio.local#011IN#011AAAA fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not fitting in legacy unicast packet, dropping.

Those link-local IPv6 addresses belong to the machine itself. It 
currently has no other IPv6 address(es) (other than loopback), but I 
should probably set that up.

Any hints as to what's going on?

Most of the hits I get from a web search are full of 'me too' with no 
answers.

Cheers,
Richard

[toc] | [next] | [standalone]

#246370

FromRichard Hector <richard@walnut.gen.nz>
Date2022-03-17 06:20 +0100
Message-ID<E1QIh-2hfG-1@gated-at.bofh.it>
In reply to#246035
On 8/03/22 13:25, Richard Hector wrote:
> Hi all,
> 
> I've recently set up a small box to run cups, to provide network access 
> to a USB-only printer. It's a 32-bit machine running bullseye.
> 
> I'm seeing log messages like these:
> 
>> Mar  7 15:47:47 whio avahi-daemon[310]: Record 
>> [Brother\032HL-2140\032\064\032whio._ipps._tcp.local#011IN#011SRV 0 0 
>> 631 whio.local ; ttl=120] not fitting in legacy unicast packet, dropping.
>> Mar  7 15:47:47 whio avahi-daemon[310]: Record 
>> [whio.local#011IN#011AAAA fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not 
>> fitting in legacy unicast packet, dropping.
>> Mar  7 15:47:48 whio avahi-daemon[310]: Record 
>> [Brother\032HL-2140\032\064\032whio._ipp._tcp.local#011IN#011SRV 0 0 
>> 631 whio.local ; ttl=120] not fitting in legacy unicast packet, dropping.
>> Mar  7 15:47:48 whio avahi-daemon[310]: Record 
>> [whio.local#011IN#011AAAA fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not 
>> fitting in legacy unicast packet, dropping.
> 
> Those link-local IPv6 addresses belong to the machine itself. It 
> currently has no other IPv6 address(es) (other than loopback), but I 
> should probably set that up.
> 
> Any hints as to what's going on?
> 
> Most of the hits I get from a web search are full of 'me too' with no 
> answers.

Nobody? Not even another 'me too'? :-)

Any suggestions for further/better questions to ask, or info to provide?

Thanks,
Richard

[toc] | [prev] | [next] | [standalone]

#246371

FromRichard Hector <richard@walnut.gen.nz>
Date2022-03-17 07:50 +0100
Message-ID<E1S7n-2i3a-9@gated-at.bofh.it>
In reply to#246370
On 17/03/22 19:37, mick crane wrote:
> On 2022-03-17 05:09, Richard Hector wrote:
>> On 8/03/22 13:25, Richard Hector wrote:
>>> Hi all,
>>>
>>> I've recently set up a small box to run cups, to provide network 
>>> access to a USB-only printer. It's a 32-bit machine running bullseye.
>>>
>>> I'm seeing log messages like these:
>>>
>>>> Mar  7 15:47:47 whio avahi-daemon[310]: Record 
>>>> [Brother\032HL-2140\032\064\032whio._ipps._tcp.local#011IN#011SRV 0 
>>>> 0 631 whio.local ; ttl=120] not fitting in legacy unicast packet, 
>>>> dropping.
>>>> Mar  7 15:47:47 whio avahi-daemon[310]: Record 
>>>> [whio.local#011IN#011AAAA fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not 
>>>> fitting in legacy unicast packet, dropping.
>>>> Mar  7 15:47:48 whio avahi-daemon[310]: Record 
>>>> [Brother\032HL-2140\032\064\032whio._ipp._tcp.local#011IN#011SRV 0 0 
>>>> 631 whio.local ; ttl=120] not fitting in legacy unicast packet, 
>>>> dropping.
>>>> Mar  7 15:47:48 whio avahi-daemon[310]: Record 
>>>> [whio.local#011IN#011AAAA fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not 
>>>> fitting in legacy unicast packet, dropping.
>>>
>>> Those link-local IPv6 addresses belong to the machine itself. It 
>>> currently has no other IPv6 address(es) (other than loopback), but I 
>>> should probably set that up.
>>>
>>> Any hints as to what's going on?
>>>
>>> Most of the hits I get from a web search are full of 'me too' with no 
>>> answers.
>>
>> Nobody? Not even another 'me too'? :-)
>>
>> Any suggestions for further/better questions to ask, or info to provide?
> 
> I have no idea. Could it be something to do with this old report ?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517683

I don't think so - that seems to relate to too many packets, rather than 
packets being too big.

> I would probably fiddle about to get rid of the IPV6 thing.

I don't want to get rid of IPv6 - I use it. It could be connected with 
IPv6 due to IPv6 (IIRC) not allowing fragmentation of packets.

Cheers,
Richard

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web