Maisem Ali b797f773c7 ipn/ipnlocal: add support for funnel in tsnet ... Previously the part that handled Funnel connections was not aware of any listeners that tsnet.Servers might have had open so it would check against the ServeConfig and fail. Adding a ServeConfig for a TCP proxy was also not suitable in this scenario as that would mean creating two different listeners and have one forward to the other, which really meant that you could not have funnel and tailnet-only listeners on the same port. This also introduces the ipn.FunnelConn as a way for users to identify whether the call is coming over funnel or not. Currently it only holds the underlying conn and the target as presented in the "Tailscale-Ingress-Target" header. Signed-off-by: Maisem Ali <maisem@tailscale.com>		2023-03-09 12:53:00 -08:00
..
tsnet-funnel.go	ipn/ipnlocal: add support for funnel in tsnet	2023-03-09 12:53:00 -08:00