archedraft Posted March 10, 2015 Share Posted March 10, 2015 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? Quote Link to comment
CHBMB Posted March 12, 2015 Share Posted March 12, 2015 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 . Quote Link to comment
jonp Posted March 12, 2015 Share Posted March 12, 2015 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? Quote Link to comment
archedraft Posted March 12, 2015 Author Share Posted March 12, 2015 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. Quote Link to comment
jonp Posted March 12, 2015 Share Posted March 12, 2015 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. Quote Link to comment
CHBMB Posted March 12, 2015 Share Posted March 12, 2015 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. Quote Link to comment
jonp Posted March 13, 2015 Share Posted March 13, 2015 Ok, thanks for confirming. Will look into this more after the next release or two. Quote Link to comment
archedraft Posted April 4, 2015 Author Share Posted April 4, 2015 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. Quote Link to comment
CHBMB Posted April 13, 2015 Share Posted April 13, 2015 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. Quote Link to comment
steini84 Posted August 19, 2015 Share Posted August 19, 2015 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 Quote Link to comment
archedraft Posted August 20, 2015 Author Share Posted August 20, 2015 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 Quote Link to comment
jonp Posted August 22, 2015 Share Posted August 22, 2015 The avahi message your seeing is harmless and is suppressed in the latest 6.1 release candidate. Quote Link to comment
Gizmotoy Posted November 1, 2015 Share Posted November 1, 2015 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. Quote Link to comment
CHBMB Posted November 1, 2015 Share Posted November 1, 2015 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.. Quote Link to comment
ColonelRhodes Posted February 22, 2016 Share Posted February 22, 2016 I am still seeing these repeated messages on 6.1.8 Was there any solution? Quote Link to comment
ColonelRhodes Posted February 24, 2016 Share Posted February 24, 2016 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" Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.