
This external documentation for pyVmomi was generated using Googly Docs (aka Google Standard Documentation) which renders very cleanly in GitHub. Internal documentation for a class should be done in Sphinx format because tools like pyCharm and Eclipse can use that documentation as a hint for code completion. Note: External docs as Googly Docs, internal docs as Sphinx. Closes bug#15
37 lines
1.4 KiB
ReStructuredText
37 lines
1.4 KiB
ReStructuredText
.. _vim.IpAddress: ../../../vim/IpAddress.rst
|
|
|
|
.. _vSphere API 5.5: ../../../vim/version.rst#vimversionversion9
|
|
|
|
.. _vim.IntExpression: ../../../vim/IntExpression.rst
|
|
|
|
.. _vim.dvs.TrafficRule.IpPort: ../../../vim/dvs/TrafficRule/IpPort.rst
|
|
|
|
.. _vim.dvs.TrafficRule.Qualifier: ../../../vim/dvs/TrafficRule/Qualifier.rst
|
|
|
|
|
|
vim.dvs.TrafficRule.IpQualifier
|
|
===============================
|
|
This class defines the IP Rule Qualifier. Here IP addresses of source and destination will be used for classifying packets.
|
|
:extends: vim.dvs.TrafficRule.Qualifier_
|
|
:since: `vSphere API 5.5`_
|
|
|
|
Attributes:
|
|
sourceAddress (`vim.IpAddress`_, optional):
|
|
|
|
IP qualifier for source. If this property is NULL, it will match "any IPv4 or any IPv6 address".
|
|
destinationAddress (`vim.IpAddress`_, optional):
|
|
|
|
IP qualifier for destination. If this property is NULL, it will match "any IPv4 or any IPv6 address".
|
|
protocol (`vim.IntExpression`_, optional):
|
|
|
|
Protocols like TCP, UDP, ICMP etc. The valid value for a protocol is got from IANA assigned value for the protocol. This can be got from RFC 5237 and IANA website section related to protocol numbers.
|
|
sourceIpPort (`vim.dvs.TrafficRule.IpPort`_, optional):
|
|
|
|
Source IP Port.
|
|
destinationIpPort (`vim.dvs.TrafficRule.IpPort`_, optional):
|
|
|
|
Destination IP Port.
|
|
tcpFlags (`vim.IntExpression`_, optional):
|
|
|
|
TCP flags. The valid values can be found at RFC 3168.
|