July 11, 20196 yr Jul 10 17:30:50 Tower kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Jul 10 17:30:52 Tower ntpd[1725]: Deleting interface #5 eth0, 192.168.1.79#123, interface stats: received=594, sent=696, dropped=0, active_time=182042 secs Jul 10 17:30:52 Tower ntpd[1725]: 171.66.97.126 local addr 192.168.1.79 -> <null> Jul 10 17:30:52 Tower ntpd[1725]: 198.255.68.106 local addr 192.168.1.79 -> <null> Jul 10 17:30:52 Tower ntpd[1725]: Deleting interface #6 eth0, fe80::ae1f:6bff:fe63:2a10%10#123, interface stats: received=0, sent=0, dropped=0, active_time=182042 secs Jul 10 17:32:06 Tower kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None Jul 10 17:32:08 Tower ntpd[1725]: Listen normally on 7 eth0 192.168.1.79:123 Jul 10 17:32:08 Tower ntpd[1725]: Listen normally on 8 eth0 [fe80::ae1f:6bff:fe63:2a10%10]:123 Jul 10 17:32:08 Tower ntpd[1725]: new interface(s) found: waking up resolver Jul 10 17:32:12 Tower kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Jul 10 17:32:14 Tower ntpd[1725]: Deleting interface #7 eth0, 192.168.1.79#123, interface stats: received=1, sent=3, dropped=0, active_time=6 secs Jul 10 17:32:14 Tower ntpd[1725]: 171.66.97.126 local addr 192.168.1.79 -> <null> Jul 10 17:32:14 Tower ntpd[1725]: 198.255.68.106 local addr 192.168.1.79 -> <null> Jul 10 17:32:14 Tower ntpd[1725]: Deleting interface #8 eth0, fe80::ae1f:6bff:fe63:2a10%10#123, interface stats: received=0, sent=0, dropped=0, active_time=6 secs Jul 10 17:32:16 Tower kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None Jul 10 17:32:18 Tower ntpd[1725]: Listen normally on 9 eth0 192.168.1.79:123 Jul 10 17:32:18 Tower ntpd[1725]: Listen normally on 10 eth0 [fe80::ae1f:6bff:fe63:2a10%10]:123 Jul 10 17:32:18 Tower ntpd[1725]: new interface(s) found: waking up resolver I don't remember seening these in the logs before network upgrade. Unraid 6.7.2
July 11, 20196 yr You should post up the Diagnostics file Tools >>> Diagnostics so the the Gurus have some real information to work with. A short snippet of a log file can often be meaningless. 10 hours ago, AinsWorth said: I don't remember seening these in the logs before network upgrade. Explain what the 'network upgrade' was...
July 11, 20196 yr Author You should post up the Diagnostics file Tools >>> Diagnostics so the the Gurus have some real information to work with. A short snippet of a log file can often be meaningless. Explain what the 'network upgrade' was...I upgraded to an all unifi setup.Unifi security gateway proUnifi 24 port switch 250w PoeCloud key gen 2 plus.Sadly, I am not at home right now so I can't upload diagnostics.When I get home in 10 hours I will upload it.Thank you for your reply. Sent from my Moto Z (2) using Tapatalk
July 11, 20196 yr Are you seeing any usual behavior on the performance of the server (other the syslog entries)? EDIT: Have you check on the Ubiquiti forums to see if there are any issues with the firmware that you are using? (I also have a ubiquiti network setup and the firmware situation is quite 'fluid' right now...) Edited July 11, 20196 yr by Frank1940
July 11, 20196 yr Author Are you seeing any usual behavior on the performance of the server (other the syslog entries)? No everything is fine on unraid server. The only weird activity I saw on my new work was my windows pc. Static IP got changed to an out of network IP. And what cought my eye was that out of network IP showed up in unraid logs. However unraid kept going. My PC required a switch reboot. I just want to make sure everything is running smoothly. If it's something in the switch, I will fix it. The extra ips in the logs bother me. My network only runs on 192.168.1. ip address. I did have the unifi controller running on unraid at one point and it was on a sub network 172. I believe. Now all that's ran off the cloud key. Also, I completely reset my unraid network via deleting network config. I wanted to start fresh.Sent from my Moto Z (2) using Tapatalk
July 14, 20196 yr I am no expert on this but I have a question. First, go to Settings >>> Network Settings Now look at the 'Network protocol:' setting. What do you have it set to? I suspect it is set to allow the use of both IPv4 and IPv6 addressing. Do you really need IPv6 ability on your server? (I suspect that you don't.) Try setting it to 'IPv4 only'. Before you do this. Copy the /config/network.cfg from the flash drive to a folder on your PC. (If the worst happens, you can copy the file back, reboot and be back to the current setup.)
Archived
This topic is now archived and is closed to further replies.