mirror of
https://passt.top/passt
synced 2025-08-11 09:53:12 +02:00
Allow different external interfaces for IPv4 and IPv6 connectivity
It's quite plausible for a host to have both IPv4 and IPv6 connectivity, but only via different interfaces. For example, this will happen in the case that IPv6 connectivity is via a tunnel (e.g. 6in4 or 6rd). It would also happen in the case that IPv4 access is via a tunnel on an otherwise IPv6 only local network, which is a setup that might become more common in the post IPv4 address exhaustion world. In turns out there's no real need for passt/pasta to get its IPv4 and IPv6 connectivity via the same interface, so we can handle this situation fairly easily. Change the core to allow eparate external interfaces for IPv4 and IPv6. We don't actually set these separately for now. Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
This commit is contained in:
parent
0aae39d73a
commit
4b2e018d70
4 changed files with 27 additions and 21 deletions
2
tcp.c
2
tcp.c
|
@ -2207,7 +2207,7 @@ static void tcp_conn_from_tap(struct ctx *c, int af, const void *addr,
|
|||
struct sockaddr_in6 addr6_ll = {
|
||||
.sin6_family = AF_INET6,
|
||||
.sin6_addr = c->addr6_ll,
|
||||
.sin6_scope_id = c->ifi,
|
||||
.sin6_scope_id = c->ifi6,
|
||||
};
|
||||
if (bind(s, (struct sockaddr *)&addr6_ll, sizeof(addr6_ll))) {
|
||||
close(s);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue