rjstott Posted April 10, 2019 Share Posted April 10, 2019 (edited) I just upgraded to 6.7.0 rc7 and I lost internet access from unraid. The rest of my network is fine, I can access the GUI and I can ping my router from unraid. I can't ping 8.8.8.8 or any other internet address and some unraid functionality is lost such as docker updates (access to GitHub). A downgrade to 6.6.7 brings it all back! Any ideas? Edited April 10, 2019 by rjstott Release details Quote Link to comment
Frank1940 Posted April 10, 2019 Share Posted April 10, 2019 First, try this: Settings >>> Network Settings Then under 'IPv4 DNS server assignment:' set it to: 8.8.8.8 and click on 'Apply'. If that does not work, Tools >>> Diagnostics and post up your Diagnostics file with your next post. Quote Link to comment
rjstott Posted April 10, 2019 Author Share Posted April 10, 2019 I saw that suggestion in another thread so I tried it even though it can't possbly solve the problem if the server won't ping 8.8.8.8. It would resolve a problem with named sites of course. It didn't work when I tried it. I have added the diagnostics but of course they are for the reverted 6.6.7 but I guess all the basic data should be the same between the two releases! I note that the 8.8.8.8 is still resident in the first DNS entry and I must remember to put it back to my SmartDNS setting! tower-diagnostics-20190410-1315.zip Quote Link to comment
Frank1940 Posted April 10, 2019 Share Posted April 10, 2019 It was a bit of long shot. Unfortunately, if you want help, you are going to have to reload 6.7.0-rc7 and get the Diagnostics file from that version. (You should also edit your first post to indicate that you are using 6.7.0-rc7 as your Unraid version.) Quote Link to comment
rjstott Posted April 12, 2019 Author Share Posted April 12, 2019 Did a quick update again, same problems. Have attached the diagnostics from the 6.7.0.rc7. In the meantime I reverted back and its working again! tower-diagnostics-20190412-2155.zip Quote Link to comment
dreamstation Posted April 22, 2019 Share Posted April 22, 2019 Same problem here. I sovled it by adding a default gateway for my network setting. Somehow 6.7.0rc7 missed adding this on start up. And looks like it will remove it after rebooting. Quote Link to comment
rjstott Posted April 22, 2019 Author Share Posted April 22, 2019 When I look in Network Settings the gateway is already set? Did you do something different. Quote Link to comment
rjstott Posted June 1, 2019 Author Share Posted June 1, 2019 Tried again with the latest 6.7 release and same problem, internat access is gone. Someone on the unRaid team must know of changes to networking that might have caused the problem. I've gone back, again, to 6,6,7 and network access is working again. My diagnostice are on this thread! One more crumb, I'm fairly certain that internet access is working for Dockers. It just seems to be unRaid core functionality like updates and checking for them! Quote Link to comment
bonienl Posted June 2, 2019 Share Posted June 2, 2019 7 hours ago, rjstott said: Tried again with the latest 6.7 release and same problem, internat access is gone. Someone on the unRaid team must know of changes to networking that might have caused the problem. I've gone back, again, to 6,6,7 and network access is working again. My diagnostice are on this thread! One more crumb, I'm fairly certain that internet access is working for Dockers. It just seems to be unRaid core functionality like updates and checking for them! You have a duplicate assignment, both eth0 and eth1 have the same settings. # Generated settings: IFNAME[0]="eth0" DESCRIPTION[0]="etho" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.103" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" METRIC[0]="24" DNS_SERVER1="8.8.8.8" DNS_SERVER2="54.93.173.153" DNS_SERVER3="8.8.8.8" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" VLANS[0]="1" IFNAME[1]="eth1" DESCRIPTION[1]="Intel" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.1.103" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.1.1" SYSNICS="2" Open and edit the file "network.cfg" in the /config folder on your USB device. Remove all [1] entries (i.e. remove the eth1 settings) Change SYSNICS="1" Save the file and reboot your system Quote Link to comment
rjstott Posted June 2, 2019 Author Share Posted June 2, 2019 Hi bonieni, I think to do this I have to remove the flash drive and edit the file through my Mac. Before I do this, there are two entries because there is an on board Realtek ethernet port and I have a PCIe network card with the Intel chip. There was some suggestion a long while back that the Realtel card was the issue so I added the Intel. As far as I can see eth1 is disabled (though where this setting is I don’t know). In any event there is currently no ethernet plugged into eth1 so it must be disabled? Additionally the Network.cfg file is identical between 6.6.7 and 6.7.7 so is there a difference between how the two versions use the .cfg data. I could believe that your suggestion could well fix this but being a curious old fart I like to know why? Any thought? Regards Richard Quote Link to comment
Frank1940 Posted June 2, 2019 Share Posted June 2, 2019 27 minutes ago, rjstott said: I think to do this I have to remove the flash drive and edit the file through my Mac. Go to Apps and search for a tool called 'CA Config editor'. That will allow you to edit the file from the GUI. Quote Link to comment
rjstott Posted June 2, 2019 Author Share Posted June 2, 2019 Bonieni, Frank1940, Thanks for all that. I am going to say that as far as I can tell the edit has fixed the problem and we can now connect to the internet from core activities including updates and terminal! My curiosity is still asking what changed in the new releases to cause the problem. But we have at last moved on and I have an up to date release. For some reason none of the OS X file tags show up but although I religously set these I never found a good use! 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.