Lines Matching refs:node
83 6.1 KAME node as correspondent node
84 6.2 KAME node as home agent/mobile node
120 * KAME supports node required addresses, and conforms to the scope
280 (actually from the node itself) and considers it as a sign of
283 address on an inbound packet, and reject it if it is from the node
288 (1) when there was no neighbor cache entry, node received unsolicited
317 The notion of the default interface is also disabled when the node is
321 the word "host" and "node" in several places in Section 5.2 of RFC
322 2461. We basically read the word "node" in this section as "host,"
345 node which does proxy NDP.
422 almost no code for site boundary node support (neither forwarding nor
448 index is meaningful only within the sending/receiving node.
578 multi-sited node and suppose that more than one interface of the node
706 node-local multicast group ff01::1.
713 node is a router or a host (router if it is 1, host if it is 0).
715 It is NOT recommended to change net.inet6.ip6.forwarding while the node
751 or multi-interface hosts. A misconfigured node can behave strange
756 accept_rtadv forwarding role of the node
974 the node will allow an arbitrary number of headers. As of writing this
988 node, to avoid possible DoS attacks. KAME kernel implements two rate-
999 of link layer devices directly attached to the node. In some cases the
1192 (per-node), or setsockopt (per-socket).
1205 (::ffff:10.1.1.1), if the node is configured to accept IPv4 connections
1352 SIIT translator is specified in RFC2765. KAME node cannot become a SIIT
1353 translator box, nor SIIT end node (a node in SIIT cloud).
1358 There are multiple reasons that we are unable to become SIIT end node.
1361 SIIT end node. (2) As presented in 1.12.6, some of our userland code assumes
1364 common). Effectively KAME node will reject any packets via SIIT translator
1369 node to be able to construct IPv4 IPsec headers. If a node knows how to
1370 construct IPv4 IPsec headers, that is not an IPv6-only node, it is a dual-stack
1371 node. The requirements imposed in SIIT document contradict with the other
1450 only if we have no legal source address for the node. The legal situations
1452 to the node and (2) DAD.
1473 node. The section talks about how KAME stack manages those required
1478 The following items are automatically assigned to the node (or the node will
1486 - Solicited-node multicast address for link-local addresses
1775 destination IPv4 node (163.221.202.12)
1778 FAITH-relay dual stack node
1781 source IPv6 node
1783 faithd must be invoked on FAITH-relay dual stack node.
2017 Note that the behavior is configurable in per-node manner, not per-SA manner
2243 6.1 KAME node as correspondent node
2249 6.2 KAME node as home agent/mobile node