Forum Discussion
LabanM
Nimbostratus
NimbostratusLoad Balance UDP (Retain Source Client IP)
Good afternoon all. I'm hoping someone on here can point me in the right direction. I am working on a project to load balance UDP traffic to a few backend nodes for some IOT devices. When the IOT d...
The short answer to this is yes - normal SNAT will work fine. When a request comes into a UDP virtual server, the response will be allowed for an Idle Timeout time ie it emulates the TCP functionality. This timeout is configurable in the UDP profile. You can also disable the treating of this traffic as a flow, and instead treat each UDP packet as a new connection ( useful where using iRules and you want to inspect each packet ). This is called Datagram LB.
Take a look at K7535: Overview of the UDP profile for more info
PeteWhite
Employee
EmployeeThe short answer to this is yes - normal SNAT will work fine. When a request comes into a UDP virtual server, the response will be allowed for an Idle Timeout time ie it emulates the TCP functionality. This timeout is configurable in the UDP profile. You can also disable the treating of this traffic as a flow, and instead treat each UDP packet as a new connection ( useful where using iRules and you want to inspect each packet ). This is called Datagram LB.
Take a look at K7535: Overview of the UDP profile for more info
LabanMNimbostratus
NimbostratusThis actually worked perfectly and I did not need to reply back to the source client IP. I was able to respond back to the BIG IP SNAT IP : port and the IOT device receieved the acknowledgment. Ended up being way easier than I anticipated.