4 ms·

>I suspect a single machine could put out 71M HTTP requests/second without too much difficulty PacketsPerSecond=TransferRate(bytes/second)/PacketSize(bytes/pac

>I suspect a single machine could put out 71M HTTP requests/second without too much difficulty PacketsPerSecond=TransferRate(bytes/second)/PacketSize(bytes/packet) https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=30778 https://community.arubanetworks.com/community-home/digestvie... A single 24port switch with 1Gbps ports would see 48Gbps so with 64byte packets would see 71M packets, 1518byte packets would drop to 3.9M packets. If you are in the business of being the main auditor of your activities, water companies here in the UK being an example, news organisations as another, then does one ever find a problem with one's work? I've had DDOS on my systems before, and how it took my firewall out was simply increasing the number of requests the firewall had to handle using a SYN flood. https://en.wikipedia.org/wiki/SYN_flood https://en.wikipedia.org/wiki/SYN_flood Most firewalls are fixed and not adaptive, so a bit of low hanging fruit could be had by firewall systems that can adapt to SYN floods, like shortening the time the handshake process stays in memory, choosing to dump all that dont complete within a short period of time, choosing to dump those from ip address blocks linked to country's or regions your dont normally trade with. There are so many ways to handle these situations, but not all firewalls and switches provide the facilities that are needed. Hackers will exploit default configurations and industry standard best practices, including RFC's. During one of my lets see what happens if I push this metaphoric button exercises, I was tracing those random packets that appear at firewalls and I happened to have picked one which tracerouted back to a French IP. What was interesting and consistent with behaviour I've seen in the 90's with dead submarine internet connections at the New York exchange, was the trace route delivered its hop data until I crossed the English channel at which point a packet killed the machine, forcing the mains to be pulled as the machine went totally unresponsive. It makes me think the UK internet is like some giant virtual dome like the one seen in the film The Truman Show.

bogomipz 4y ago
>"A single 24port switch with 1Gbps ports would see 48Gbps so with 64byte packets would see 71M packets, 1518byte packets would drop to 3.9M packets." This is not correct. An interface doesn't handle more packets per second with smaller packet sizes it handles less, much less. Getting the full 48 Gbps of 24 ports at line rate would only be possible if the packets were full size packets(1500 bytes). The PPS bottleneck with small packets(64 bytes) would mean you would never see line rate on those 24 interfaces as your throughput would fall off a cliff. Network hardware vendors quote PPS using the lower bound of packet size and line rate at full packet size. The PPS bottleneck on a network device is incurred long before the line rate limit is ever reached.
- moremetadata 4y ago
  The min network packet size is 64 bytes, so if they are bundling several small packets into one pseudo jumbo packet and handling it that way, something only using the same manufacturer switch could do as this would be propriety networking, then that could explain their calculations on their webpage. The data is streamed within time slots, which is why cable lengths of Cat<=5 cable can not be longer than 100 metres @ 100Hz. Cat 6 is 55metres at 250Hz. I dont know what their switch internal workings are, you'll have to ask them why they have quoted that speed, but I know some switches also have built in fibre network connections, as invariably with a network switch with many ports, you could get a queue of packets for one port so there must be some sort of buffering inside a switch to handle and minimise these situations. It is only "clockwork" electrical pulses at the end of the day.
  - bogomipz 4y ago
    This is all complete gibberish. Packets per second is based on the lower bound and Jumbo Frames denotes an MTU or upper bound. Further switches don't aggregate smaller Ethernet frames into Jumbo frames. Packet per second also has zero to do with an Ethernet cable's length. PPS is the "forwarding rate" of the switch which is distinct from the bandwidth of a switch's backplane or switching fabric. Again switching bandwidth and forwarding Bandwidth are two different things. There is also no need for me to "ask them why they have quoted that speed", that's standard with hardware vendors for PPS.

bogomipz 4y ago

>"A single 24port switch with 1Gbps ports would see 48Gbps so with 64byte packets would see 71M packets, 1518byte packets would drop to 3.9M packets." This is not correct. An interface doesn't handle more packets per second with smaller packet sizes it handles less, much less. Getting the full 48 Gbps of 24 ports at line rate would only be possible if the packets were full size packets(1500 bytes). The PPS bottleneck with small packets(64 bytes) would mean you would never see line rate on those 24 interfaces as your throughput would fall off a cliff. Network hardware vendors quote PPS using the lower bound of packet size and line rate at full packet size. The PPS bottleneck on a network device is incurred long before the line rate limit is ever reached.

moremetadata 4y ago
The min network packet size is 64 bytes, so if they are bundling several small packets into one pseudo jumbo packet and handling it that way, something only using the same manufacturer switch could do as this would be propriety networking, then that could explain their calculations on their webpage. The data is streamed within time slots, which is why cable lengths of Cat<=5 cable can not be longer than 100 metres @ 100Hz. Cat 6 is 55metres at 250Hz. I dont know what their switch internal workings are, you'll have to ask them why they have quoted that speed, but I know some switches also have built in fibre network connections, as invariably with a network switch with many ports, you could get a queue of packets for one port so there must be some sort of buffering inside a switch to handle and minimise these situations. It is only "clockwork" electrical pulses at the end of the day.
- bogomipz 4y ago
  This is all complete gibberish. Packets per second is based on the lower bound and Jumbo Frames denotes an MTU or upper bound. Further switches don't aggregate smaller Ethernet frames into Jumbo frames. Packet per second also has zero to do with an Ethernet cable's length. PPS is the "forwarding rate" of the switch which is distinct from the bandwidth of a switch's backplane or switching fabric. Again switching bandwidth and forwarding Bandwidth are two different things. There is also no need for me to "ask them why they have quoted that speed", that's standard with hardware vendors for PPS.