VMware vSphere Automation SDK for .NET 7.0.0.1
|
The Inbound
interface provides methods to manage inbound firewall rules.
More...
Inherited by vmware::appliance::networking::firewall::InboundStub.
Public Member Functions | |
void | Set (global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > rules) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. | |
void | Set (global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > rules, global::System.Action< vmware.vapi.std.Progress > _progress, vmware.vapi.bindings.client.InvocationConfig _invocationConfig) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. | |
global::System.Threading.Tasks.Task | SetAsync (global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > rules) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. | |
global::System.Threading.Tasks.Task | SetAsync (global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > rules, global::System.Action< vmware.vapi.std.Progress > _progress, vmware.vapi.bindings.client.InvocationConfig _invocationConfig) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. | |
global::System.Collections.Generic.List < vmware.appliance.networking.firewall.InboundTypes.Rule > | Get () |
Get the ordered list of firewall rules. | |
global::System.Collections.Generic.List < vmware.appliance.networking.firewall.InboundTypes.Rule > | Get (global::System.Action< vmware.vapi.std.Progress > _progress, vmware.vapi.bindings.client.InvocationConfig _invocationConfig) |
Get the ordered list of firewall rules. | |
global::System.Threading.Tasks.Task < global::System.Collections.Generic.List < vmware.appliance.networking.firewall.InboundTypes.Rule > > | GetAsync () |
Get the ordered list of firewall rules. | |
global::System.Threading.Tasks.Task < global::System.Collections.Generic.List < vmware.appliance.networking.firewall.InboundTypes.Rule > > | GetAsync (global::System.Action< vmware.vapi.std.Progress > _progress, vmware.vapi.bindings.client.InvocationConfig _invocationConfig) |
Get the ordered list of firewall rules. |
The Inbound
interface provides methods to manage inbound firewall rules.
This interface was added in vSphere API 6.7.1.
global::System.Collections.Generic.List<vmware.appliance.networking.firewall.InboundTypes.Rule> vmware::appliance::networking::firewall::Inbound::Get | ( | ) |
Get the ordered list of firewall rules.
Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
Implemented in vmware::appliance::networking::firewall::InboundStub.
global::System.Collections.Generic.List<vmware.appliance.networking.firewall.InboundTypes.Rule> vmware::appliance::networking::firewall::Inbound::Get | ( | global::System.Action< vmware.vapi.std.Progress > | _progress, |
vmware.vapi.bindings.client.InvocationConfig | _invocationConfig | ||
) |
Get the ordered list of firewall rules.
Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
Implemented in vmware::appliance::networking::firewall::InboundStub.
global::System.Threading.Tasks.Task<global::System.Collections.Generic.List<vmware.appliance.networking.firewall.InboundTypes.Rule> > vmware::appliance::networking::firewall::Inbound::GetAsync | ( | global::System.Action< vmware.vapi.std.Progress > | _progress, |
vmware.vapi.bindings.client.InvocationConfig | _invocationConfig | ||
) |
Get the ordered list of firewall rules.
Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
Implemented in vmware::appliance::networking::firewall::InboundStub.
global::System.Threading.Tasks.Task<global::System.Collections.Generic.List<vmware.appliance.networking.firewall.InboundTypes.Rule> > vmware::appliance::networking::firewall::Inbound::GetAsync | ( | ) |
Get the ordered list of firewall rules.
Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
Implemented in vmware::appliance::networking::firewall::InboundStub.
void vmware::appliance::networking::firewall::Inbound::Set | ( | global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > | rules, |
global::System.Action< vmware.vapi.std.Progress > | _progress, | ||
vmware.vapi.bindings.client.InvocationConfig | _invocationConfig | ||
) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses.
This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows:
Address | Prefix | Interface Name | Policy |
---|---|---|---|
10.112.0.1 | 0 | * | REJECT |
10.112.0.1 | 0 | nic0 | ACCEPT |
In the above example, the first rule drops all packets originating from 10.112.0.1 and the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
rules | List of address-based firewall rules. |
_progress | Progress notification call back |
_invocationConfig | Configuration for the method invocation |
Implemented in vmware::appliance::networking::firewall::InboundStub.
void vmware::appliance::networking::firewall::Inbound::Set | ( | global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > | rules | ) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses.
This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows:
Address | Prefix | Interface Name | Policy |
---|---|---|---|
10.112.0.1 | 0 | * | REJECT |
10.112.0.1 | 0 | nic0 | ACCEPT |
In the above example, the first rule drops all packets originating from 10.112.0.1 and the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
rules | List of address-based firewall rules. |
Implemented in vmware::appliance::networking::firewall::InboundStub.
global::System.Threading.Tasks.Task vmware::appliance::networking::firewall::Inbound::SetAsync | ( | global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > | rules | ) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses.
This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows:
Address | Prefix | Interface Name | Policy |
---|---|---|---|
10.112.0.1 | 0 | * | REJECT |
10.112.0.1 | 0 | nic0 | ACCEPT |
In the above example, the first rule drops all packets originating from 10.112.0.1 and the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
rules | List of address-based firewall rules. |
Implemented in vmware::appliance::networking::firewall::InboundStub.
global::System.Threading.Tasks.Task vmware::appliance::networking::firewall::Inbound::SetAsync | ( | global::System.Collections.Generic.List< vmware.appliance.networking.firewall.InboundTypes.Rule > | rules, |
global::System.Action< vmware.vapi.std.Progress > | _progress, | ||
vmware.vapi.bindings.client.InvocationConfig | _invocationConfig | ||
) |
Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses.
This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows:
Address | Prefix | Interface Name | Policy |
---|---|---|---|
10.112.0.1 | 0 | * | REJECT |
10.112.0.1 | 0 | nic0 | ACCEPT |
In the above example, the first rule drops all packets originating from 10.112.0.1 and the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set. This method was added in vSphere API 6.7.1.
vmware.vapi.std.errors.Error | Generic error |
rules | List of address-based firewall rules. |
_progress | Progress notification call back |
_invocationConfig | Configuration for the method invocation |
Implemented in vmware::appliance::networking::firewall::InboundStub.