tag:blogger.com,1999:blog-8361942945221983453.post3835857817498103217..comments2024-03-24T13:09:14.304+00:00Comments on Pete's Blog: Help, I lost all networking on my Raspberry Pi!Petehttp://www.blogger.com/profile/00656449482260202625noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-8361942945221983453.post-44228519791380850792021-01-22T16:00:26.761+00:002021-01-22T16:00:26.761+00:00THANKS!!!!!!!!!!!!!! THANKS!!!!!!!!!!!!!! Anonymoushttps://www.blogger.com/profile/03101111650107176528noreply@blogger.comtag:blogger.com,1999:blog-8361942945221983453.post-62336692696561439502019-03-08T10:09:53.432+00:002019-03-08T10:09:53.432+00:00Just to say that I did a system update today (Marc...Just to say that I did a system update today (March 8 2019) and lost my network after the reboot. The first part of your solution worked a treat and many thanks for that. BUT the persistent rules part didn't work.<br /><br />I have another pi which is running sitting next to the failed one and it doesn't have the rules file in it. There is a set of rules files in /lib/udev/rules.d but the failed pi seems to have the same ones as that.<br /><br />Alan Chandlerhttps://www.blogger.com/profile/12221576522823707704noreply@blogger.comtag:blogger.com,1999:blog-8361942945221983453.post-47887415860252695002017-11-03T18:48:56.290+00:002017-11-03T18:48:56.290+00:00Man! Today I was using Rufus and just came by to t...Man! Today I was using Rufus and just came by to tell THANK YOU for all your GREAT software! What even makes you to code so perfectly?hodokhttps://www.blogger.com/profile/01867941966151288056noreply@blogger.comtag:blogger.com,1999:blog-8361942945221983453.post-1855506399640494292016-10-01T17:56:12.674+01:002016-10-01T17:56:12.674+01:00I cannot restart networking! I get an error: &quo...I cannot restart networking! I get an error: "The name org.freedeaktop.policyKit1 was not provided by any service files."Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8361942945221983453.post-87171408572976987492016-09-17T13:51:13.699+01:002016-09-17T13:51:13.699+01:00Urgh, this is so close, but not 100% there! The sy...Urgh, this is so close, but not 100% there! The symptoms all match, the manual steps work (meaning I can get working eth0 back), but it looks like /etc/udev/rules.d/70-persistent-net.rules is ignored. Nothing I put in there has any effect.<br /><br />What does work is to change the /etc/network/interfaces.d/50-cloud-init.cfg to refer to "enxb827eb0620ea" instead of eth0 - then I have working interface named "enxb827eb0620ea".<br /><br />Which I just KNOW will clutch out the moment I (for example) spin up docker on this device.<br /><br />Anything else one can try?demaniakhttps://www.blogger.com/profile/06704258757544805619noreply@blogger.comtag:blogger.com,1999:blog-8361942945221983453.post-90869386007906994482016-08-12T19:39:15.971+01:002016-08-12T19:39:15.971+01:00On a 16.04 installation, you need to leave out the...On a 16.04 installation, you need to leave out the KERNEL attribute. Otherwise it wont work.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8361942945221983453.post-67562207103008225662016-05-27T02:40:03.023+01:002016-05-27T02:40:03.023+01:00THANK YOU! I've just spent a night pulling my ...THANK YOU! I've just spent a night pulling my hair out over this and could not find any viable solutions that were specific to the RPI. As a bit of a linux novice in some areas, this post was a complete life saver that saved me the time of reflashing (which I was really close to doing!)Stevehttps://www.blogger.com/profile/13612387911215705602noreply@blogger.com