March 10, 201511 yr I am assuming this is my fault because I defined 2 bridges via the "go" file so that my pfSense VM is able to have an in0 & out0 network port but wanted to post this and see what others thought. I have disabled the bridge in unRAID's web gui and put the following in my "go" file: # Start Bridges brctl addbr out0 brctl addbr in0 brctl stp out0 on brctl stp in0 on brctl addif out0 eth2 brctl addif in0 eth1 ifconfig eth1 up ifconfig eth2 up ifconfig out0 up ifconfig in0 up With recent beta's I noticed the following being repeated: Mar 10 17:04:34 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:06:11 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:07:49 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:08:05 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:08:34 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:12:45 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:13:14 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:14:50 Pithos avahi-daemon[2237]: Received packet from invalid interface. I am sort of hoping that this is unRAID's way of saying you're not using the standard bridge option so I am going to throw an error in the log? Is there anyway to test if this is the case? Also, I haven't noticed anything weird happening to my internet or unRAID data speeds but could this be affecting either of those?
March 12, 201511 yr I'm also seeing the same issue. Mar 8 01:13:46 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:13:50 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:13:50 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:13:51 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:13:51 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:13:53 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:13:53 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:00 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:00 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:01 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:01 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:03 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:03 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:10 Server avahi-daemon[15039]: Received packet from invalid interface. Mar 8 01:14:10 Server avahi-daemon[15039]: Received packet from invalid interface. My bridge setup is identical to archedrafts's and I have tried installing a completely "vanilla" unraid with no plugins or dockers and can reproduce this by entering the brctl & ifconfig commands via telnet after boot. The error occurs even if I don't have any KVM VMs running .
March 12, 201511 yr I am assuming this is my fault because I defined 2 bridges via the "go" file so that my pfSense VM is able to have an in0 & out0 network port but wanted to post this and see what others thought. I have disabled the bridge in unRAID's web gui and put the following in my "go" file: # Start Bridges brctl addbr out0 brctl addbr in0 brctl stp out0 on brctl stp in0 on brctl addif out0 eth2 brctl addif in0 eth1 ifconfig eth1 up ifconfig eth2 up ifconfig out0 up ifconfig in0 up With recent beta's I noticed the following being repeated: Mar 10 17:04:34 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:06:11 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:07:49 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:08:05 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:08:34 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:12:45 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:13:14 Pithos avahi-daemon[2237]: Received packet from invalid interface. Mar 10 17:14:50 Pithos avahi-daemon[2237]: Received packet from invalid interface. I am sort of hoping that this is unRAID's way of saying you're not using the standard bridge option so I am going to throw an error in the log? Is there anyway to test if this is the case? Also, I haven't noticed anything weird happening to my internet or unRAID data speeds but could this be affecting either of those? So if you create an unRAID bridge (no manually created bridges via brctl), this issue doesn't occur, but after creating custom bridges, you both can see these messages and it doesn't matter if you have the Docker or Libvirt service running or not?
March 12, 201511 yr Author So if you create an unRAID bridge (no manually created bridges via brctl), this issue doesn't occur, but after creating custom bridges, you both can see these messages and it doesn't matter if you have the Docker or Libvirt service running or not? Correct, If I use unRAID's web gui to create a bridge, I do not get a message. It only happens after I manually specify the bridges.
March 12, 201511 yr So if you create an unRAID bridge (no manually created bridges via brctl), this issue doesn't occur, but after creating custom bridges, you both can see these messages and it doesn't matter if you have the Docker or Libvirt service running or not? Correct, If I use unRAID's web gui to create a bridge, I do not get a message. It only happens after I manually specify the bridges. Ok, can't look into this right now, but I know eric has some plans for making this a little better.
March 12, 201511 yr That's exactly the situation Jon, I tried without libvrt and docker running and on a completely new Unraid boot without even setting an array up. Starts to happen as soon as I issue ifconfig bridge0 up. Does not occur when using the Unraid bridge feature.
March 13, 201511 yr Ok, thanks for confirming. Will look into this more after the next release or two.
April 4, 201511 yr Author So I changed all my in0 bridges in my go file to br0, changed all my VM's to br0, and then message goes away. I suppose I will mark this as "solved-ish". The issue is gone but it would be nice if unRAID had more robust networking options.
April 13, 201511 yr So I changed all my in0 bridges in my go file to br0, changed all my VM's to br0, and then message goes away. I suppose I will mark this as "solved-ish". The issue is gone but it would be nice if unRAID had more robust networking options. My config as far as I can tell is the same as archedraft's. Following a server reboot, I am now seeing this happen again. Seems a bit random as sometimes it appears and sometimes it doesn't so I was wondering if it had anything to do with the speed at which the bridges come up.
August 19, 201510 yr Any news on this? I only have two network cards (eth0 and eth1) and I use the unRAID network settings to create br0 In my go file I have this: brctl addbr br1 brctl stp br1 on brctl addif br1 eth1 ifconfig eth1 up ifconfig br1 up It seems to work fine and I can remove the error by killing avahi: /etc/rc.d/rc.avahidaemon stop But I would rather find a solution to understand the problem instead of a hack
August 20, 201510 yr Author Depends on what you are trying to accomplish but what I ended up doing was removing all the bridge settings from my "go" file. Then I followed this guide form JonP on how to hide my second NIC from unRAID. Then I was able to pass-through my NIC's to a pfSense VM. All the "Received packet from invalid interface." messages went away. http://lime-technology.com/forum/index.php?topic=39499.msg368812#msg368812
August 22, 201510 yr The avahi message your seeing is harmless and is suppressed in the latest 6.1 release candidate.
November 1, 201510 yr The avahi message your seeing is harmless and is suppressed in the latest 6.1 release candidate. Did this end up happening? I'm on 6.1.3 and still have tons of these in my logs. No manually-created bridges, just a few Docker containers. Nov 1 01:42:56 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:48:01 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:48:01 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:48:02 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:48:04 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:48:08 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:53:11 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:53:12 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:53:13 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:53:15 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:53:19 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:58:22 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:58:22 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:58:23 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:58:25 Hyperion avahi-daemon[12881]: Received packet from invalid interface. Nov 1 01:58:29 Hyperion avahi-daemon[12881]: Received packet from invalid interface.
November 1, 201510 yr The avahi message your seeing is harmless and is suppressed in the latest 6.1 release candidate. Did this end up happening? I'm on 6.1.3 and still have tons of these in my logs. No manually-created bridges, just a few Docker containers. AFAIK yes it did, I haven't seen any of these messages for quite a time..
February 24, 201610 yr The message: Feb 24 09:02:32 tower avahi-daemon[30960]: Received packet from invalid interface. seems to be coming from the Plex docker when running "docker logs -f plex"
Archived
This topic is now archived and is closed to further replies.