Falconevo

AirPrint uses multicast, most access points disable LAN to WLAN multicast and broadcast traffic by default as it can cause unwanted performance issues. This is generally due to length of time to send broadcast data to all WLAN devices. You should have an option somewhere to allow for multicast and broadcast traffic on the Wireless device, I'm unfortunately not familiar with the Rukus R700 but I would assume it has options to enable/disable this type of traffic.

SSD's are consumables, people really need to digest and understand this. Eat their rated write endurance and it will be a door stop in no time. What bugs me is the article from BackBlaze is missing vital information, because i am assuming that they buy consumer grade SSD's and mechanical disks then throw them in to the fray expecting enterprise levels of endurance... not sure what else they would expect besides early failure rates. The article is incredibly misleading, an SSD will die within weeks if you obliterate it's potato flash write endurance in that time. What the article is missing What SSD models they were using and why What the budget per server was for the SSDs vs Mechanical drives What was the TBW at the point of failure (was it inside or outside manufacturer rated spec) Were SSDs behind a RAID/HBA controller with/without trim support and was the OS in use providing said support Are they utilising or reading the additional manufacturer specific S.M.A.R.T data provided As someone who has put over 50k SSD's in to environments from consumer to DC grade devices I find the whole thing misleading. I have seen numerous SSD's fail for all sorts of reasons but the biggest one by far is exceeding the manufacturer rated endurance, followed by Intel's 'DISABLE LOGICAL STATE' which still gives me nightmares to this day.

Last time I saw something like this it was a fake Intel network card. Does the card have a yottamark validation sticker on it?

Then it is very likely you have exceeded the write endurance of the drive. I have seen similar behaviour on SSD controllers in the past when a drive has expired all its flash write endurance.

I would suggest checking the write endurance left on the drive, people seem to forget that SSD's are a consumable.

In UK money, that would be around £60 which is about 66 Brexit currency

When you flashed to IT mode, did you enter the original configuration for the controllers SAS address as part of the end process? I've seen this when the controllers SAS address isn't specified during the flashing process as a few guides miss it and its quite important as it provides the pathing for the pass-through to the disks (SAS Addresses) behind the controller. Some OS's don't require it to be present but Windows 2012 R2+ has always needed it. If you are unsure what the SAS address of the controller is, it is usually labelled on the device physically (assuming the label hasn't gone awol)

AData SSD's are absolutely garbage, always have been and always will be. Did some testing with 8 su800 sata units as cheap consumer replacements on request of a purchasing manager to try and save on costs...... 3 units failed within weeks of the testing and verification phase they went straight in to the shredder, not even worth a warranty replacement. Buy shite, buy twice.

As the old saying goes, buy shite buy twice.

I'm with @Electronics Wizardy here, this is going to be a whole load of pain for very little gain unless you are solely doing this to expand your knowledge.

Yea it can be virtualised but you are not going to get 10Gbit throughput from a virtualised network interface. You will have to use PCIe pass-through for the network interface(s) to reach that and place the interface in the dataplane

Build a custom TNSR installation, its free now for home/non-commercial use. This is what the pfSense guys have been working on along side the pfSense project but uses a different way of handling traffic using VPP (Vector Packet Processing) and DPDK (Data Plane Development Kit) to minimise CPU cycles. These are developments on Linux to substantially improve per core packet processing capability. From around 1Gbit/s per core to around 10Gbit/s per core. https://www.tnsr.com/ https://www.tnsr.com/tnsr-vs-pfsense-software Can do 10G with ease, I would probably use Intel 10G, Mellanox Connect-X or SolarFlare cards in the installation. Can pick them up pretty cheap, I'm using a SolarFlare SFN5121 in my colo/test chassis running TNSR. Has no GUI, but does have a REST API and console access, can get it setup for normal internet usage pretty easily and may teach you something new.

I'm assuming you have a dual socket motherboard with only 1 CPU populated? Only half of the memory banks are available if both sockets aren't populated. You will need to verify which are active in your manual but these are usually labelled A1,A2,A3 etc and the B1,B2,B3 etc slots are usually inactive as they require a 2nd CPU to be available. This is entirely dependant on your motherboard manufacturer of course so I would advise reviewing the manual to find out which dimm slots are inactive when using a single socket configuration. Also be aware that a number of PCI-Express Lanes will also be inactive in a single CPU configuration, so expect some of the PCIe slots to not function.

You should really speak to network specialists about this and the ISPs you plan to be peering with to see what they do/don't support. I can suggest some additional reading for you; FastNetMon for detection based on custom parameters and upstream black holes to reduce network infrastructure impact BGPFlowSpec for more advanced upstream black hole rules to allow known good traffic types etc I would also suggest you to avoid trying to mitigate/filter attacks until you have 200Gbit/s+ of internet bandwidth capacity at a data centre. Considering you are asking this question, it is doubtful you have capacity to handle even a small attack. Write it in to your terms & conditions regarding what you would do in the event of an attack.

Thats only part of the testing suite, thats the MSSQL testing which can be done on Linux but I certainly wouldn't want to use Linux for MSSQL at the moment.