Re: DDos attack using Antminers (problem and solving from Bitmain)
hey having same problem.
tried a few things from this thread.
firstly, I had the regular firmware from Bitmain site, last published 8/25/2017. I did test that writing the 2 lines for restrict -4,-6 were overwritten, and they were. I did also install the linked software from the Bitmain link for the 4/24/2018 firmware. I again tried and again the ntp.conf lines were overwritten.
Next I did try to set the ntp.conf to only read access by "chmod -w ntp.conf" but it was still overwritten on reboot. So I saw online that the dhcpd can overwrite ntp configs so i found the network.sh in init.d and edited that with a "-N" for what looked like the dhcp daemon (its another name than dhcpd, something mini or whatever). anyways on reboot that network.sh also got overwritten.
Finally I did see online also that you could set a renamed copy of ntp.conf and use the rc.local to copy that as the ntp.conf after whatever is doing the overwrite does its thing but before the system intiializes. meanwhile i couldnt find an rc.local and anyways even the myntp.conf I made to test in /etc/ got overwritten.
so my goal now is just go it the long way, i dont reset these often. ill just add the 2 lines for restrict and restart the ntp anytime i do a restart
unless you figure that bitmain did something else unrelated to ntp.conf in the 4/24/2018 firmware to fix the problem, because the ntp.conf in the linked firmware is identical to the 8/25/2017 firmware ntp.conf
side note, now that my miners are all on static ips, i am havign a hard time keeping them online. its been a week and one participated in an ntp ddoss while 5 others went offline :/
tried a few things from this thread.
firstly, I had the regular firmware from Bitmain site, last published 8/25/2017. I did test that writing the 2 lines for restrict -4,-6 were overwritten, and they were. I did also install the linked software from the Bitmain link for the 4/24/2018 firmware. I again tried and again the ntp.conf lines were overwritten.
Next I did try to set the ntp.conf to only read access by "chmod -w ntp.conf" but it was still overwritten on reboot. So I saw online that the dhcpd can overwrite ntp configs so i found the network.sh in init.d and edited that with a "-N" for what looked like the dhcp daemon (its another name than dhcpd, something mini or whatever). anyways on reboot that network.sh also got overwritten.
Finally I did see online also that you could set a renamed copy of ntp.conf and use the rc.local to copy that as the ntp.conf after whatever is doing the overwrite does its thing but before the system intiializes. meanwhile i couldnt find an rc.local and anyways even the myntp.conf I made to test in /etc/ got overwritten.
so my goal now is just go it the long way, i dont reset these often. ill just add the 2 lines for restrict and restart the ntp anytime i do a restart
unless you figure that bitmain did something else unrelated to ntp.conf in the 4/24/2018 firmware to fix the problem, because the ntp.conf in the linked firmware is identical to the 8/25/2017 firmware ntp.conf
side note, now that my miners are all on static ips, i am havign a hard time keeping them online. its been a week and one participated in an ntp ddoss while 5 others went offline :/