Lines Matching refs:bind

268 After the successful creation of the socket, you would normally use the ``bind(2)``
269 and/or ``connect(2)`` system call to bind the socket to a CAN interface. After
275 In order to send data, a ``bind(2)`` must have been successful. ``bind(2)`` assigns a
280 to ``bind(2)``, ``connect(2)``, ``sendto(2)`` and ``recvfrom(2)``. A ``write(2)`` with size 4 will
314 The ``bind(2)`` system call assigns the local address, i.e. the source address when
315 sending packages. If a PGN during ``bind(2)`` is set, it's used as a RX filter.
328 Both ``write(2)`` and ``send(2)`` will send a packet with local address from ``bind(2)`` and the
342 - ``SO_J1939_PROMISC`` - disable filters set by ``bind(2)`` and ``connect(2)``
370      | bind() + connect() +      |        |
435 ``bind(2)`` and ``connect(2)`` is insufficient for specific use cases. By
436 default, ``bind(2)`` and ``connect(2)`` allow a socket to be associated with a
465 - The ``bind(2)`` and ``connect(2)`` functions only allow binding to a single
522 of any filters set by ``bind()`` or ``connect()``. This is analogous to
883 ``j1939.name`` member and provide it to ``bind(2)``. If the name had claimed an address
900 			.pgn = J1939_NO_PGN,	/* to disable bind() rx filter for PGN */
905 	bind(sock, (struct sockaddr *)&baddr, sizeof(baddr));
937 	 * NAME provided, does not match the j1939.name provided to bind(2), EPROTO
949 claim another address, some socket bound to NAME, must ``bind(2)`` again, but with
979 	bind(sock, (struct sockaddr *)&baddr, sizeof(baddr));