Score:0

Google firewall being saturated and not allowing valid requests through

in flag

We've configured some Firewall rules to block some bad ips. This has been done in the VPC Network -> Firewall area. This is NOT done on the server via IPTables or anything.

Everything is fine until we have floods of traffic from these bad ips. I can see in the firewall log for this rule it was blocking them, but there is either a connection limit or bandwidth limit. For 40 minutes I have a solid wall hit counts of 24,000 for ever minute - no up or down just 24,000 constantly. Traffic Flood

The server was getting no traffic, resource usage was way down. This was a problem because valid traffic was getting bottle necked somewhere.

The only thing I can see in the docs is a limit of 130,000 maximum stateful connections. https://cloud.google.com/vpc/docs/firewalls#specifications

Machine type is n1-standard-4

During this attack when I looked at the quotas page, nothing was maxed out.

Is anyone able to shed some light on this?

Score:0
in flag

The answer is to resize the instance size and add more cores. Don't use instanced with shared cores.

I went for an n2 with 8 cores and this has now resolved it's self.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.