The network interface name '' can be used to receive packetsįrom all network interfaces of this family.ĬAN_ISOTP protocol require a tuple (interface, rx_addr, tx_addr) Where interface is a string representing a network interface name like If addr_type is TIPC_ADDR_ID, then v1 is the node, v2 is theĪ tuple (interface, ) is used for the AF_CAN address family, Is the lower port number, and v3 is the upper port number. If addr_type is TIPC_ADDR_NAMESEQ, then v1 is the server type, v2 If addr_type is TIPC_ADDR_NAME, then v1 is the server type, v2 is Scope is one of TIPC_ZONE_SCOPE, TIPC_CLUSTER_SCOPE, and (addr_type, v1, v2, v3 ), where:Īddr_type is one of TIPC_ADDR_NAMESEQ, TIPC_ADDR_NAME, Tuple, and the fields depend on the address type. TIPC is an open, non-IP based networked protocol designedįor use in clustered computer environments. Linux-only support for TIPC is available using the AF_TIPCĪddress family. This information is superfluous and mayĪF_NETLINK sockets are represented as pairs (pid, groups). Note, however, omission of scope_id can cause problemsĬhanged in version 3.7: For multicast addresses (with scope_id meaningful) address may not contain Socket module methods, flowinfo and scope_id can be omitted just forīackward compatibility. Therefore, you may want to avoid these if you intend to support IPv6 with yourįor AF_INET6 address family, a four-tuple (host, port, flowinfo, scope_id) is used, where flowinfo and scope_id represent the sin6_flowinfoĪnd sin6_scope_id members in struct sockaddr_in6 in C. This behavior is not compatible with IPv6, Notation like '' or an IPv4 address like '100.50.200.5',įor IPv4 addresses, two special forms are accepted instead of a hostĪddress: '' represents INADDR_ANY, which is used to bind to all Where host is a string representing either a hostname in internet domain Changed in version 3.5: Writable bytes-like object is now accepted.Ī pair (host, port) is used for the AF_INET address family,