## Description

The current implementation of the project only allows tunneling UDP traffic over TCP ports. I am proposing the addition of an option to bind UDP traffic directly over UDP ports. This would provide an alternative to the existing TCP-based tunneling solution.

## Motivation

The motivation behind this feature request is to enhance the performance and scalability of the project. By allowing UDP traffic to be tunneled over UDP ports, we can reduce the latency and increase the throughput of the system. This is particularly important for applications that require real-time communication, such as video streaming and online gaming.

## Possible Solutions

One possible solution to implement this feature is to modify the existing configuration file to include a new option, `bindUdpPort`. When this option is enabled, the project will bind the UDP traffic to the specified port, rather than using the default TCP port.

## Impact

The impact of this feature will be twofold. Firstly, it will improve the performance of the system by reducing latency and increasing throughput. Secondly, it will provide users with more flexibility in terms of configuring their tunneling options.

## Alternatives Considered

I have considered alternative solutions, including modifying the existing TCP-based tunneling solution to handle UDP traffic. However, this approach would require significant changes to the underlying architecture and may introduce additional complexity.

## Uhldiated Area

The primary affected area of this feature request is Performance and Scalability.

## Markdown Notes

* Added ~~strikethrough~~ to indicate already considered alternatives
* Used ~~checkbox~~ to indicate affected areas