@zyzonix Tried the suggestion from your link. But without success. I still need to run setup after reboot to fix network. Think, I have to live with it, until someone in the ARM team finds a reliably working solution.
@alexand It’s my opinion, too, that it is alway better for firewall management, to have dedicated NICs for at least RED and GREEN. As the Nanopi R4S basically provides. Only one of them changes its MAC address on every boot…
Okay, that sounds weird. The error you get, is exactly the same I got back then. Are you sure, that there was no typo or a wrong PCI device?
Hi all, especially stephen and zyzonix,
back from a relaxing weekend I looked at my last change again and actually found a typo in /etc/udev/rules.d/10-setmacaddress.rules (ACTIOM instead of ACTION).
After correcting it, I get my macaddress set reliably on every cold and warm boot now.
There is only one question remaining: Which is more secure? To use my macadress on green or on red interface? By my own, I’d like to use it on green, but I don’t know, whether my Fritz!Box discovers or may leak it to the internet…
Edit: I’d like to use my macaddress on RED, not on green. Because I else, in case, that it changes again, I still can use green to change red again.
Thanks so far and best regards
Hello @jopa,
I’m glad to hear, that you got it working. Maybe just select my answer als solution, so that it is pinned on top.
I would also recommend to set this workaround for the RED interface, so that you can still access the webinterface via GREEN in case of a failure of this solution.
Best regards