<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GCP on BrainBit Latest Articles</title><link>https://brainbit.uk/tags/gcp/</link><description>Recent content in GCP on BrainBit Latest Articles</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 23 Dec 2020 13:22:03 +0000</lastBuildDate><atom:link href="https://brainbit.uk/tags/gcp/index.xml" rel="self" type="application/rss+xml"/><item><title>GCP Internal LBs , How dirty?</title><link>https://brainbit.uk/posts/gcp-internal-lbs-how-dirty/</link><pubDate>Wed, 23 Dec 2020 13:22:03 +0000</pubDate><guid>https://brainbit.uk/posts/gcp-internal-lbs-how-dirty/</guid><description>If you ever decide to tcpdump on a node behind an GCP internal Loadbalancer you will be surprised to see that the packets aren’t destined to the interface ip on your VM , the ip headers maintain the destination address of the load balancer , let me draw it:
I have a normal NLB passing traffic to a instance group with a bunch of dnsmasq nodes , nothing out of the ordinary.</description></item></channel></rss>