1 - 2 - 3 - 6 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
IP
Click on the red underlined text to get to the source
...
Direction (in or out)
Source and destination IP address (possibly masked)
Protocol
Source and destination port ...
... terminal.
proto An IP protocol specified by number. The "ip"
keyword means any protocol will match.
...
... rule.
ipno/bits An IP number as above with a mask
width of the form 1.2.3.4/24. In
this case, all IP ...
... IP number as above with a mask
width of the form 1.2.3.4/24. In
this case, all IP numbers from
1.2.3.0 to 1.2.3.255 will match.
The bit ...
... NOT have bits set beyond the mask.
For a match to occur, the same IP
version must be present in the
packet that was used in describing
the IP address ...
... IP
version must be present in the
packet that was used in describing
the IP address. To test for a
particular IP version, the bits ...
... ipoptions spec
Match if the IP header contains the comma
separated list of options specified in spec. The
supported IP options ...
... IP header contains the comma
separated list of options specified in spec. The
supported IP options are:
ssrr (strict source route ...
... router advertisement (9), router
solicitation (10), time-to-live exceeded (11), IP
header bad (12), timestamp request (13),
timestamp ...
...
There is one kind of packet that the access device MUST always
discard, that is an IP fragment with a fragment offset of one. This
is a valid ...
...
Direction (in or out)
Source and destination IP address (possibly masked)
Protocol
Source and destination port ...
... connections
to span multiple interfaces and multiple IP addresses, the
Capabilities-Exchange-Request message MUST contain one Host ...
... Address AVP for each potential IP address that MAY be locally used
when transmitting Diameter ...
... connections to
span multiple interfaces, hence, multiple IP addresses, the
Capabilities-Exchange-Answer message MUST contain one Host ...
... Capabilities-Exchange-Answer message MUST contain one Host-IP-Address
AVP for each potential IP address ...
... IP-Address
AVP for each potential IP address that MAY be locally used when
transmitting Diameter ...
... to inform a Diameter peer of the sender's IP address. All source
addresses that a Diameter node expects to use with SCTP ...
... identifier in the request is saved, and replaced with
a locally unique value. The source of the request is also saved,
which includes the IP address, port and protocol.
...
... Firmware-Revision |0-1|0-1|0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |
Host-IP-Address |1+ |1+ |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |
Inband-Security-Id |0+ |0+ |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |
...
... configured. A statically configured Diameter peer would require
that either the IP address or the fully qualified domain name
(FQDN ...
... identification data. However, when used in conformant
implementations, each ID Payload MUST carry a single IP address and a
single non-zero port number ...
... single non-zero port number, and MUST NOT use the IP Subnet or IP
Address Range formats. This allows the Phase 2 security association ...
... non-zero port number, and MUST NOT use the IP Subnet or IP
Address Range formats. This allows the Phase 2 security association
...
... pre-shared keys are configured with Diameter peers,
who are identified by their IP address (Main Mode), or possibly their
FQDN (Aggressive Mode). As a result, it is necessary for the set of
...
... Shacham, A., Monsour, R., Pereira, R. and M. Thomas, "IP Payload Compression Protocol (IPComp)", RFC 3173prop ...
... Piper, D., "The Internet IP Security Domain of Interpretation for ISAKMP", RFC 2407(-> 4306prop), November 1998. ...
... Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373(-> 3513(-> 4291draft)), July 1998. ...
... Glass, S., Hiller, T., Jacobs, S. and C. Perkins, "Mobile IP Authentication, Authorization, and Accounting Requirements", RFC 2977 ...