2023-11-03 03:22:56 +01:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
|
|
|
|
/* PASST - Plug A Simple Socket Transport
|
|
|
|
* for qemu/UNIX domain socket mode
|
|
|
|
*
|
|
|
|
* PASTA - Pack A Subtle Tap Abstraction
|
|
|
|
* for network namespace/tap device mode
|
|
|
|
*
|
|
|
|
* port_fwd.c - Port forwarding helpers
|
|
|
|
*
|
|
|
|
* Copyright Red Hat
|
|
|
|
* Author: Stefano Brivio <sbrivio@redhat.com>
|
|
|
|
* Author: David Gibson <david@gibson.dropbear.id.au>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <stdint.h>
|
|
|
|
#include <errno.h>
|
|
|
|
#include <fcntl.h>
|
|
|
|
#include <sched.h>
|
2023-11-29 14:19:06 +01:00
|
|
|
#include <unistd.h>
|
|
|
|
#include <stdio.h>
|
2023-11-03 03:22:56 +01:00
|
|
|
|
|
|
|
#include "util.h"
|
|
|
|
#include "port_fwd.h"
|
|
|
|
#include "passt.h"
|
|
|
|
#include "lineread.h"
|
|
|
|
|
2023-11-03 03:22:57 +01:00
|
|
|
/* See enum in kernel's include/net/tcp_states.h */
|
|
|
|
#define UDP_LISTEN 0x07
|
|
|
|
#define TCP_LISTEN 0x0a
|
|
|
|
|
2023-11-03 03:22:56 +01:00
|
|
|
/**
|
|
|
|
* procfs_scan_listen() - Set bits for listening TCP or UDP sockets from procfs
|
2023-11-03 03:22:59 +01:00
|
|
|
* @fd: fd for relevant /proc/net file
|
2023-11-03 03:22:57 +01:00
|
|
|
* @lstate: Code for listening state to scan for
|
2023-11-03 03:22:56 +01:00
|
|
|
* @map: Bitmap where numbers of ports in listening state will be set
|
|
|
|
* @exclude: Bitmap of ports to exclude from setting (and clear)
|
|
|
|
*
|
|
|
|
* #syscalls:pasta lseek
|
|
|
|
* #syscalls:pasta ppc64le:_llseek ppc64:_llseek armv6l:_llseek armv7l:_llseek
|
|
|
|
*/
|
2023-11-03 03:22:59 +01:00
|
|
|
static void procfs_scan_listen(int fd, unsigned int lstate,
|
2023-11-03 03:22:57 +01:00
|
|
|
uint8_t *map, const uint8_t *exclude)
|
2023-11-03 03:22:56 +01:00
|
|
|
{
|
|
|
|
struct lineread lr;
|
|
|
|
unsigned long port;
|
|
|
|
unsigned int state;
|
2023-11-03 03:22:57 +01:00
|
|
|
char *line;
|
2023-11-03 03:22:56 +01:00
|
|
|
|
2023-11-07 12:04:33 +01:00
|
|
|
if (fd < 0)
|
|
|
|
return;
|
|
|
|
|
2023-11-03 03:22:59 +01:00
|
|
|
if (lseek(fd, 0, SEEK_SET)) {
|
|
|
|
warn("lseek() failed on /proc/net file: %s", strerror(errno));
|
2023-11-03 03:22:56 +01:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2023-11-03 03:22:59 +01:00
|
|
|
lineread_init(&lr, fd);
|
2023-11-03 03:22:56 +01:00
|
|
|
lineread_get(&lr, &line); /* throw away header */
|
|
|
|
while (lineread_get(&lr, &line) > 0) {
|
|
|
|
/* NOLINTNEXTLINE(cert-err34-c): != 2 if conversion fails */
|
|
|
|
if (sscanf(line, "%*u: %*x:%lx %*x:%*x %x", &port, &state) != 2)
|
|
|
|
continue;
|
|
|
|
|
2023-11-03 03:22:57 +01:00
|
|
|
if (state != lstate)
|
2023-11-03 03:22:56 +01:00
|
|
|
continue;
|
|
|
|
|
|
|
|
if (bitmap_isset(exclude, port))
|
|
|
|
bitmap_clear(map, port);
|
|
|
|
else
|
|
|
|
bitmap_set(map, port);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2023-11-03 03:23:03 +01:00
|
|
|
* port_fwd_scan_tcp() - Scan /proc to update TCP forwarding map
|
|
|
|
* @fwd: Forwarding information to update
|
|
|
|
* @rev: Forwarding information for the reverse direction
|
2023-11-03 03:22:56 +01:00
|
|
|
*/
|
2023-11-03 03:23:03 +01:00
|
|
|
void port_fwd_scan_tcp(struct port_fwd *fwd, const struct port_fwd *rev)
|
2023-11-03 03:22:56 +01:00
|
|
|
{
|
2023-11-03 03:23:02 +01:00
|
|
|
memset(fwd->map, 0, PORT_BITMAP_SIZE);
|
|
|
|
procfs_scan_listen(fwd->scan4, TCP_LISTEN, fwd->map, rev->map);
|
|
|
|
procfs_scan_listen(fwd->scan6, TCP_LISTEN, fwd->map, rev->map);
|
2023-11-03 03:23:01 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2024-02-28 12:25:19 +01:00
|
|
|
* port_fwd_scan_udp() - Scan /proc to update UDP forwarding map
|
2023-11-03 03:23:03 +01:00
|
|
|
* @fwd: Forwarding information to update
|
|
|
|
* @rev: Forwarding information for the reverse direction
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
* @tcp_fwd: Corresponding TCP forwarding information
|
|
|
|
* @tcp_rev: TCP forwarding information for the reverse direction
|
2023-11-03 03:23:01 +01:00
|
|
|
*/
|
2023-11-03 03:23:03 +01:00
|
|
|
void port_fwd_scan_udp(struct port_fwd *fwd, const struct port_fwd *rev,
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
const struct port_fwd *tcp_fwd,
|
|
|
|
const struct port_fwd *tcp_rev)
|
2023-11-03 03:23:01 +01:00
|
|
|
{
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
uint8_t exclude[PORT_BITMAP_SIZE];
|
|
|
|
|
|
|
|
bitmap_or(exclude, PORT_BITMAP_SIZE, rev->map, tcp_rev->map);
|
|
|
|
|
2023-11-03 03:23:02 +01:00
|
|
|
memset(fwd->map, 0, PORT_BITMAP_SIZE);
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
procfs_scan_listen(fwd->scan4, UDP_LISTEN, fwd->map, exclude);
|
|
|
|
procfs_scan_listen(fwd->scan6, UDP_LISTEN, fwd->map, exclude);
|
2023-11-03 03:23:01 +01:00
|
|
|
|
|
|
|
/* Also forward UDP ports with the same numbers as bound TCP ports.
|
|
|
|
* This is useful for a handful of protocols (e.g. iperf3) where a TCP
|
|
|
|
* control port is used to set up transfers on a corresponding UDP
|
|
|
|
* port.
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
*
|
|
|
|
* This means we need to skip numbers of TCP ports bound on the other
|
|
|
|
* side, too. Otherwise, we would detect corresponding UDP ports as
|
|
|
|
* bound and try to forward them from the opposite side, but it's
|
|
|
|
* already us handling them.
|
2023-11-03 03:23:01 +01:00
|
|
|
*/
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
procfs_scan_listen(tcp_fwd->scan4, TCP_LISTEN, fwd->map, exclude);
|
|
|
|
procfs_scan_listen(tcp_fwd->scan6, TCP_LISTEN, fwd->map, exclude);
|
2023-11-03 03:22:56 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* port_fwd_init() - Initial setup for port forwarding
|
|
|
|
* @c: Execution context
|
|
|
|
*/
|
|
|
|
void port_fwd_init(struct ctx *c)
|
|
|
|
{
|
2023-11-03 03:22:59 +01:00
|
|
|
const int flags = O_RDONLY | O_CLOEXEC;
|
2023-11-03 03:22:56 +01:00
|
|
|
|
2023-11-03 03:23:02 +01:00
|
|
|
c->tcp.fwd_in.scan4 = c->tcp.fwd_in.scan6 = -1;
|
|
|
|
c->tcp.fwd_out.scan4 = c->tcp.fwd_out.scan6 = -1;
|
|
|
|
c->udp.fwd_in.f.scan4 = c->udp.fwd_in.f.scan6 = -1;
|
|
|
|
c->udp.fwd_out.f.scan4 = c->udp.fwd_out.f.scan6 = -1;
|
2023-11-03 03:22:56 +01:00
|
|
|
|
|
|
|
if (c->tcp.fwd_in.mode == FWD_AUTO) {
|
2023-11-03 03:23:02 +01:00
|
|
|
c->tcp.fwd_in.scan4 = open_in_ns(c, "/proc/net/tcp", flags);
|
|
|
|
c->tcp.fwd_in.scan6 = open_in_ns(c, "/proc/net/tcp6", flags);
|
2023-11-03 03:23:03 +01:00
|
|
|
port_fwd_scan_tcp(&c->tcp.fwd_in, &c->tcp.fwd_out);
|
2023-11-03 03:22:56 +01:00
|
|
|
}
|
|
|
|
if (c->udp.fwd_in.f.mode == FWD_AUTO) {
|
2023-11-03 03:23:02 +01:00
|
|
|
c->udp.fwd_in.f.scan4 = open_in_ns(c, "/proc/net/udp", flags);
|
|
|
|
c->udp.fwd_in.f.scan6 = open_in_ns(c, "/proc/net/udp6", flags);
|
2023-11-03 03:23:03 +01:00
|
|
|
port_fwd_scan_udp(&c->udp.fwd_in.f, &c->udp.fwd_out.f,
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
&c->tcp.fwd_in, &c->tcp.fwd_out);
|
2023-11-03 03:22:56 +01:00
|
|
|
}
|
2023-11-03 03:22:59 +01:00
|
|
|
if (c->tcp.fwd_out.mode == FWD_AUTO) {
|
2023-11-03 03:23:02 +01:00
|
|
|
c->tcp.fwd_out.scan4 = open("/proc/net/tcp", flags);
|
|
|
|
c->tcp.fwd_out.scan6 = open("/proc/net/tcp6", flags);
|
2023-11-03 03:23:03 +01:00
|
|
|
port_fwd_scan_tcp(&c->tcp.fwd_out, &c->tcp.fwd_in);
|
2023-11-03 03:22:59 +01:00
|
|
|
}
|
|
|
|
if (c->udp.fwd_out.f.mode == FWD_AUTO) {
|
2023-11-03 03:23:02 +01:00
|
|
|
c->udp.fwd_out.f.scan4 = open("/proc/net/udp", flags);
|
|
|
|
c->udp.fwd_out.f.scan6 = open("/proc/net/udp6", flags);
|
2023-11-03 03:23:03 +01:00
|
|
|
port_fwd_scan_udp(&c->udp.fwd_out.f, &c->udp.fwd_in.f,
|
port_fwd, util: Don't bind UDP ports with opposite-side bound TCP ports
When pasta periodically scans bound ports and binds them on the other
side in order to forward traffic, we bind UDP ports for corresponding
TCP port numbers, too, to support protocols and applications such as
iperf3 which use UDP port numbers matching the ones used by the TCP
data connection.
If we scan UDP ports in order to bind UDP ports, we skip detection of
the UDP ports we already bound ourselves, to avoid looping back our
own ports. Same with scanning and binding TCP ports.
But if we scan for TCP ports in order to bind UDP ports, we need to
skip bound TCP ports too, otherwise, as David pointed out:
- we find a bound TCP port on side A, and bind the corresponding TCP
and UDP ports on side B
- at the next periodic scan, we find that UDP port bound on side B,
and we bind the corresponding UDP port on side A
- at this point, we unbind that UDP port on side B: we would
otherwise loop back our own port.
To fix this, we need to avoid binding UDP ports that we already
bound, on the other side, as a consequence of finding a corresponding
bound TCP port.
Reproducing this issue is straightforward:
./pasta -- iperf3 -s
# Wait one second, then from another terminal:
iperf3 -c ::1 -u
Reported-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Analysed-by: David Gibson <david@gibson.dropbear.id.au>
Fixes: 457ff122e33c ("udp,pasta: Periodically scan for ports to automatically forward")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-21 17:18:26 +01:00
|
|
|
&c->tcp.fwd_out, &c->tcp.fwd_in);
|
2023-11-03 03:22:59 +01:00
|
|
|
}
|
2023-11-03 03:22:56 +01:00
|
|
|
}
|