avahi-daemon reports "Received response with invalid source port # on interface 'eth0.0'" all the time

Bug #447442 reported by avlas on 2009-10-09
64
This bug affects 12 people
Affects Status Importance Assigned to Milestone
libvirt
Unknown
Unknown
libvirt (Ubuntu)
Medium
Unassigned

Bug Description

Both in my syslog and in daemon.log these messages are repeated again and again:

Received response with invalid source port 21604 on interface 'eth0.0'
Invalid response packet.
Invalid legacy unicast query packet.

The number of the port changes but the messages don't stop.

Description: Ubuntu 9.04
Release: 9.04

avahi-daemon:

  Installed: 0.6.23-4ubuntu4
  Candidate: 0.6.23-4ubuntu4
  version table:
 *** 0.6.23-4ubuntu4 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: avahi-daemon 0.6.23-4ubuntu4
ProcEnviron:
 LANGUAGE=
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: avahi
Uname: Linux 2.6.28-15-generic x86_64

avlas (avlas) wrote :
Franz (franz-scherf) on 2009-11-10
description: updated
Adam Gibbins (adamgibbins) wrote :

I'm also receiving a similar problem:
Nov 25 16:00:29 box1.example.com avahi-daemon[3310]: Received response with invalid source port 35558 on interface 'br0.0'
Nov 25 16:00:29 box1.example.com avahi-daemon[3310]: Invalid legacy unicast query packet.
Nov 25 16:00:29 box1.example.com avahi-daemon[3310]: Invalid legacy unicast query packet.
Nov 25 16:00:29 box2.example.com avahi-daemon[4616]: Invalid legacy unicast query packet.
Nov 25 16:00:29 box2.example.com avahi-daemon[4616]: Received response with invalid source port 35558 on interface 'eth0.0'
Nov 25 16:00:29 box2.example.com avahi-daemon[4616]: Invalid legacy unicast query packet.
Nov 25 16:00:29 box2.example.com avahi-daemon[4616]: Invalid legacy unicast query packet.
Nov 25 16:00:30 box1.example.com avahi-daemon[3310]: Received response with invalid source port 35558 on interface 'br0.0'
Nov 25 16:00:30 box1.example.com avahi-daemon[3310]: Received response with invalid source port 35558 on interface 'br0.0'
Nov 25 16:00:30 box2.example.com avahi-daemon[4616]: Received response with invalid source port 35558 on interface 'eth0.0'
Nov 25 16:00:30 box2.example.com avahi-daemon[4616]: Received response with invalid source port 35558 on interface 'eth0.0'
Nov 25 16:00:31 box1.example.com avahi-daemon[3310]: Received response with invalid source port 35558 on interface 'br0.0'
Nov 25 16:00:31 box2.example.com avahi-daemon[4616]: Received response with invalid source port 35558 on interface 'eth0.0'
Nov 25 16:00:32 box1.example.com avahi-daemon[3310]: Received response with invalid source port 35558 on interface 'br0.0'
Nov 25 16:00:32 box2.example.com avahi-daemon[4616]: Received response with invalid source port 35558 on interface 'eth0.0'
Nov 25 16:00:33 box1.example.com avahi-daemon[3310]: Received response with invalid source port 35558 on interface 'br0.0'
Nov 25 16:00:33 box2.example.com avahi-daemon[4616]: Received response with invalid source port 35558 on interface 'eth0.0'

box1:
Package: avahi-daemon
State: installed
Automatically installed: yes
Version: 0.6.23-4ubuntu4

box2:
Package: avahi-daemon
State: installed
Automatically installed: yes
Version: 0.6.23-2ubuntu2.1

Please let me know if I can provide any additional information that may be of use.

starslights (starslights) wrote :

Hello,

I run kubuntu karmic 9.10 on x86 64 and i have the same problem, sometimes i become this warn in my log:

 avahi-daemon[1095] Received response from host xxxxxxxxxxxx with invalid source port 42076 on interface 'eth1.0'
  kernel [ 7746.017432] [UFW BLOCK] IN=eth1 OUT= MAC=xxxxxxxxxxxxxxxxxxx SRC=xxxxxxxxxx DST=xxxxxxxxxxx LEN=40 TOS=0x00 PREC=0x00 TTL=94 ID=31337 DF PROTO=TCP SPT=58858 DPT=9090 WINDOW=65535 RES=0x00 ACK FIN URGP=0
  kernel [ 7748.860188] [UFW BLOCK] IN=eth1 OUT= MAC=xxxxxxxxxxxxxxxxxxxxxxxxxSRC=xxxxxxxxxxx DST=xxxxxxxxxxxx LEN=40 TOS=0x00 PREC=0x00 TTL=94 ID=31348 DF PROTO=TCP SPT=59387 DPT=9090 WINDOW=65535 RES=0x00 ACK FIN URGP=0
 moon kernel [ 7754.328035] [UFW BLOCK] IN=eth1 OUT= MAC=0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx SRC=xxxxxxxxxxxxxxx DST=xxxxxxxxxxxxxxxxxx LEN=40 TOS=0x00 PREC=0x00 TTL=94 ID=31367 DF PROTO=TCP SPT=59387 DPT=9090 WINDOW=65535 RES=0x00 ACK FIN URGP=0
  avahi-daemon[1095] Invalid legacy unicast query packet.
  avahi-daemon[1095] Invalid legacy unicast query packet.
  avahi-daemon[1095] Received response from host xxxxxxxxxxxxxxx with invalid source port 42076 on interface 'eth1.0'

I am not sure but it seem that's the bug come if we boot and run a VM (virtualbox oso) , it's the message i become right when i push on starting the VM

2010-02-24 11:40:09 avahi-daemon[1095] Invalid legacy unicast query packet.
2010-02-24 11:40:09 avahi-daemon[1095] Received response from host xxxxxxxxxxxx with invalid source port 34534 on interface 'eth1.0'
2010-02-24 11:40:09 avahi-daemon[1095] Invalid legacy unicast query packet.

Linux moon 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:02:26 UTC 2010 x86_64 GNU/Linux

Ante Karamatić (ivoks) wrote :

Do you guys, by any chance, have multiple machines (including the one with this problem) with the same hostname? Cause if you have two or more machines with the same hostname, avahi will go crazy.

Changed in avahi (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
avlas (avlas) wrote :

No, this is not my case. Let me know if you want me to try something :)

Ante Karamatić (ivoks) wrote :

Salva, just to make sure, could you configure /etc/avahi/avahi-daemon.conf to include:

host-name=randomhostname

and then restart avahi-daemon:

service avahi-daemon-restart (lucid)
/etc/init.d/avahi-daemon restart (pre lucid)

avlas (avlas) wrote :

I uncommented the hostname in /etc/avahi/avahi-daemon.conf, section [server] and I give it a random name as you asked (different of the real hostname).

Then I restarted the avahi-daemon with sudo service avahi-daemon restart (I use Lucid and I tried with service avahi-daemon-restart, but it complained)

The problem persists afterwards (there are two IPS, #IP1 and #IP2, neither the two is the one I have in my computer):

Aug 25 09:54:09 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 40420 on interface 'eth0.0'
Aug 25 09:54:18 sis wpa_supplicant[1022]: WPS-AP-AVAILABLE
Aug 25 09:54:26 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 9918 on interface 'eth0.0'
Aug 25 09:54:39 sis avahi-daemon[2731]: Invalid legacy unicast query packet.
Aug 25 09:54:39 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 24240 on interface 'eth0.0'
Aug 25 09:54:39 sis avahi-daemon[2731]: Invalid legacy unicast query packet.
Aug 25 09:54:40 sis avahi-daemon[2731]: Invalid legacy unicast query packet.
Aug 25 09:54:40 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 24240 on interface 'eth0.0'
Aug 25 09:54:40 sis avahi-daemon[2731]: Invalid legacy unicast query packet.
Aug 25 09:54:41 sis avahi-daemon[2731]: Invalid legacy unicast query packet.
Aug 25 09:54:41 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 24240 on interface 'eth0.0'
Aug 25 09:55:13 sis avahi-daemon[2731]: last message repeated 7 times
Aug 25 09:55:13 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 40420 on interface 'eth0.0'
Aug 25 09:55:18 sis wpa_supplicant[1022]: WPS-AP-AVAILABLE
Aug 25 09:55:23 sis avahi-daemon[2731]: Invalid legacy unicast query packet.
Aug 25 09:55:27 sis avahi-daemon[2731]: last message repeated 5 times
Aug 25 09:55:27 sis avahi-daemon[2731]: Received response from host #IP with invalid source port 9918 on interface 'eth0.0'
Aug 25 09:55:28 sis avahi-daemon[2731]: Received response from host #IP2 with invalid source port 46459 on interface 'eth0.0'
Aug 25 09:55:28 sis avahi-daemon[2731]: Received response from host #IP2 with invalid source port 45543 on interface 'eth0.0'

and continues all the time...

On 25.08.2010 16:01, Salva wrote:

> The problem persists afterwards (there are two IPS, #IP1 and #IP2,
> neither the two is the one I have in my computer):

Do you know what OS is on IP1 and IP2?

avlas (avlas) wrote :

I'm sorry, I have no idea. What I can tell is that I use my laptop at the university. What they are exactly, I can't tell

starslights (starslights) wrote :

Hi,

The bug still on lucid 10.04.1 x86 64 but it happend only with VM box.

I have try to edit avahi-daemon.conf with "randomhost" and it don't fix the problem...

With the right name of the computer , in that case was used "ubuntu", it seem working and not complaint

It the log after have reload the conf .

2010-08-25 19:12:14 moonlights avahi-daemon[17333] Got SIGTERM, quitting.
2010-08-25 19:12:14 moonlights avahi-daemon[17333] Leaving mDNS multicast group on interface eth1.IPv4 with address xxxxxxxxxxxxxxx
2010-08-25 19:12:15 moonlights init avahi-daemon main process (17333) terminated with status 255
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Found user 'avahi' (UID 105) and group 'avahi' (GID 111).
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Successfully dropped root privileges.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] avahi-daemon 0.6.25 starting up.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Successfully called chroot().
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Successfully dropped remaining capabilities.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] No service file found in /etc/avahi/services.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Joining mDNS multicast group on interface eth1.IPv4 with address xxxxxxxxxxxxxxxxx.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] New relevant interface eth1.IPv4 for mDNS.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Network interface enumeration completed.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Registering new address record for xxxxxxxxxxxxxxxxxx on eth1.*.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Registering new address record for xxxxxxxxxxxx on eth1.IPv4.
2010-08-25 19:12:15 moonlights avahi-daemon[17434] Registering HINFO record with values 'X86_64'/'LINUX'.
2010-08-25 19:12:16 moonlights avahi-daemon[17434] Server startup complete. Host name is ubuntu.local. Local service cookie is xxxxxxxxxxxxxxx

Anyway it must be fixed to can reconize it own the domain used by the VM , because it create a few trouble with the VM about reachability. Between i have on my system eth0 and eth1 by defaut with my ethernet card

If i have new complaint , i give news

Best Regards

starslights (starslights) wrote :

No , i still warned when i shutdown the VM ..

2010-08-25 20:16:38 moonlights avahi-daemon[17434] Received response from host 192.168.0.199 with invalid source port 49109 on interface 'eth1.0'

avlas (avlas) wrote :

This is still happening to me in Kubuntu Lucid 10.04.1 x86 64 (avahi deb version 0.6.25-1ubuntu6) as mentioned above. Did starslights upgrade Lucid from Karmic or installed it from scratch? I'm wondering if it could be happening because of some previous configuration.

I also tried to put the real hostname of my computer but it didn't work either

starslights (starslights) wrote :

Salva,

My system come from fresh install of kubuntu Lucid 10.04 LVM LTS 10.04 , the 10.04.1 come just from the recent update but no upgrade or install new

Launchpad Janitor (janitor) wrote :

[Expired for avahi (Ubuntu) because there has been no activity for 60 days.]

Changed in avahi (Ubuntu):
status: Incomplete → Expired
nils (internationils) wrote :

https://forums.virtualbox.org/viewtopic.php?f=7&t=48040

Here is a possible explanation, VMs running avahi have the same IP as the host (NATed) and this is where the error seems to come from. Recommended solution is to run the VMs in bridge mode, and get them a real unique address via DHCP or whatever. HTH...

Kevin Stone (kevin-stone) wrote :

In my case:

- Running several VMs under libvirt.
- Host and VMs have avahi and mDNS setup.
- VMs are in NAT'd network (192.168.122.0/24)
- /var/log/syslog contains

avahi-daemon[17165]: Received response from host 192.168.122.1 with invalid source port 1049 on interface 'virbr0.0'

What's happening here is NAT translation. This is because the destination address for mDNS is 224.0.0.251 and the default iptables setup is:

# iptables -t nat -L POSTROUTING -n
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE tcp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535
MASQUERADE udp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535
MASQUERADE all -- 192.168.122.0/24 !192.168.122.0/24

One solution is to not masquerade mDNS packets:

iptables -t nat -I POSTROUTING 1 -m udp -p udp --sport 5353 --dport 5353 -j ACCEPT

A more general fix for multicast and broadcast would probably be better.

Here's tcpdump output from the virbr0 interface showing a mDNS request / response:

13:19:55.618332 IP 192.168.122.114.5353 > 224.0.0.251.5353: 0 A (QM)? test.local. (32)
13:19:55.619205 IP 192.168.122.6.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) A 192.168.122.6 (42)

Alex Vorona (alex-vorona) wrote :

>One solution is to not masquerade mDNS packets:
I had this fix working.

Gionn (giovanni.toraldo) wrote :

Workaround works for me too, this was driving me crazy.

Changed in avahi (Ubuntu):
status: Expired → Confirmed
Alan Jenkins (aj504) wrote :

Upstream bug is <https://bugzilla.redhat.com/show_bug.cgi?id=657918>. I wasn't able to use the launchpad bug link thingy because _this_ (downstream) bug is filed against the wrong package.

no longer affects: avahi
Ted (tedks) wrote :

This is actually a bug in libvirt's iptables rules.

affects: avahi (Ubuntu) → libvirt (Ubuntu)
Serge Hallyn (serge-hallyn) wrote :

The following patch

https://bugzilla.redhat.com/attachment.cgi?id=661710&action=diff

is from the bugzilla bug. The patch author was asked to send it to the list but I don't believe that has happened yet. Perhaps we should test and shepherd it.

Chris J Arges (arges) wrote :

Please test with the latest Wily release to see if this issue still persists. If so please attach any relevant information and mark the bug back to the New state.
Thanks!

Changed in libvirt (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.