[Swan-dev] the coding twine holding end's .host_addr, .client, .port, .protocol and .has_client together

Andrew Cagney andrew.cagney at gmail.com
Tue Mar 2 18:38:20 UTC 2021


> - .has_client implies that .client's subnet is valid
> even though the actual connection's subnet/port was written into
> .client the subnet part is assumed to be unchange
>
> - .protocol+.port (which presumably are never unchanged) are used when
> trying to match connections
> The .client's port has presumably been scribbled on with the last
> active connection's port, maybe.
>
> - strange combinations of (subnetishost(.client) &&
> addrinsubnet((.host_addr), (.client)) are used to client's matching
> the external interface

More cases:

- either .that.port==0 or .that.has_port_wildcard is used to detect
remote wild-ports (perhaps something scribbles on .that.port)

(is "coding twine" original?)


More information about the Swan-dev mailing list