Private Hosts

Private Hosts



πŸ›‘ ALL INFORMATION CLICK HERE πŸ‘ˆπŸ»πŸ‘ˆπŸ»πŸ‘ˆπŸ»

































Private Hosts


One more step
Please complete the security check to access www.atlantic.net


Please stand by, while we are checking your browser...
Completing the CAPTCHA proves you are a human and gives you temporary access to the web property.
If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.
If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices.
Another way to prevent getting this page in the future is to use Privacy Pass. You may need to download version 2.0 now from the Chrome Web Store .

Cloudflare Ray ID: 61b98ba578c12de6
β€’
Your IP : 45.155.53.18
β€’
Performance & security by Cloudflare



You are being redirected...
What is Private Cloud Hosting - Atlantic.Net
Release 15.1SY Supervisor Engine 2T Software Configuration Guide... - Cisco
Dedicated hosting - Webmaster. Help
Private - Hosting .eu Review 2021 – Is It Worth Your Money?













Search







Log In





Log Out









Choose Language Selection







us


en







More






























Home Support Product Support Switches Cisco Catalyst 6500 Series Switches Configuration Guides






Release 15.1SY Supervisor Engine 2T Software Configuration Guide



Was this Document Helpful?

Yes
No




Feedback



Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract )


About Us

About Us
About Cisco
Customer stories
Investor relations
Social responsibility
Environmental sustainability
The Trust Center


Contact Us

Contact Us
Contact Cisco
Meet our partners
Find a reseller


Work with Us

Careers
We Are Cisco
Our People Deal
Partner with Cisco


Cisco Sites

Meraki
All new Webex
Cisco Umbrella


Note ● For complete syntax and usage information for the commands used in this chapter, see these publications:
Do not apply IP-based ACLs to any port configured for private hosts or you will defeat the private hosts feature (because the switch will not be able to apply a private hosts MAC ACL to the port).
– VLAN interfaces with no IP address
– Physical LAN ports that support EoMPLS
– Logical LAN subinterfaces that support EoMPLS
The private hosts feature prevents MAC address spoofing but does not validate the customer MAC or IP address. To prevent MAC address spoofing, the private hosts feature does the following:
Multicast traffic that originates from an upstream device (such as a BRAS or a multicast server) is always permitted. In addition, the private hosts PACLs are not applied to multicast control packets (such as IGMP query and join requests). This operation allows isolated hosts to participate in multicast groups, respond to IGMP queries, and receive traffic from any groups of interest.
Multicast traffic that originates from a host is dropped by the private hosts PACLs. However, if other hosts need to receive multicast traffic originating from a host, the private hosts feature adds a multicast permit entry to the PACLs.
Service providers typically deliver triple-play services (voice, video, and data) using three different VLANs over a single physical interface for each end user. The service infrastructure would be simpler and more scalable if the service provider could deploy a single set of VLANs to multiple end users for the same set of services, but the service provider must be able to isolate traffic between the users (hosts) at Layer 2. The private hosts feature provides this isolation, allowing VLAN sharing among multiple end users.
The private hosts feature provides these key benefits:
The private hosts feature uses protocol-independent port-based access control lists (PACLs) to provide Layer 2 isolation between hosts on trusted ports within a strictly Layer 2 domain. The PACLs isolate the hosts by imposing Layer 2 forwarding constraints on the switch ports.
By isolating the hosts, a service provider can use a single set of VLANs to deliver the same set of broadband or metro Ethernet services to multiple end users while ensuring that none of the hosts in the VLAN can communicate directly with each other. For example, VLAN 10 can be used for voice traffic, VLAN 20 for video traffic, and VLAN 30 for data traffic.
When the switch is used as a Digital Subscriber Line Access Multiplexer (DSLAM) gigabit Ethernet aggregator, the DSLAM is connected to the switch through a trunk port that can carry data for multiple VLANs. The service provider uses a single physical port and a single set of VLANs to deliver the same set of services to different end users (isolated hosts). A separate VLAN is used for each service (voice, video, and data).
Figure 18-1 shows an example of triple-play services being delivered from the switch to multiple end users attached to a DSLAM. In the figure, note the following:
The DSLAM maps voice, video, and data traffic between VLANs and VCs.
Individual VCs carry voice, video, and data traffic between the DSLAM and each host.
The private hosts feature uses PACLs to restrict the type of traffic that is allowed to flow through each of the ports configured for private hosts. A port’s mode (specified when you enable private hosts on the port) determines what type of PACL is applied to the port. Each type of PACL restricts the traffic flow for a different type of traffic (for example, from content servers to isolated hosts, from isolated hosts to servers, and traffic between isolated hosts).
The following list describes the port modes used by the private hosts feature (see Figure 18-2 ):
The private hosts feature restricts traffic flow in these ways:
Figure 18-2 shows the different types of port modes (isolated, promiscuous, and mixed) used in a private hosts configuration.
Figure 18-2 Private Hosts Port Types (Modes)
Permit all traffic from a BRAS to hosts.
Permit broadcast traffic from a BRAS.
Redirect broadcast traffic from hosts to promiscuous and mixed-mode ports.
Permit traffic from a BRAS to hosts and from hosts to a BRAS.
Deny all other host to host traffic.
Permit unicast traffic from host to a BRAS only; block unicast traffic between ports.
Redirect all broadcast traffic from host to a BRAS.
Deny traffic from a BRAS (to prevent spoofing).
Permit multicast traffic (IPv4 and IPv6).
Note In this description of port types, the term BRAS represents an upstream devices such as a BRAS, a multicast server (such as a video server), or a core network device that provides access to these devices.
The private hosts feature creates several types of port ACLs (PACLs) to impose Layer 2 forwarding constraints on switch ports. The software creates PACLs for the different types of private hosts ports based on the MAC addresses of the content servers providing broadband services and the VLAN IDs of the isolated hosts to deliver those services to. You specify the mode in which each private hosts port is to operate and the software applies the appropriate PACL to the port based on the port’s mode (isolated, promiscuous, or mixed).
The following are examples of the different types of PACLs that are used by the private hosts feature.
This example shows a PACL for isolated ports:
This example shows a PACL for promiscuous ports:
This example shows a PACL for mixed ports:
1. Determine which switch ports (interfaces) to use for the private hosts feature. You can configure the feature on trunking switch ports or port-channel interfaces. Private hosts must be enabled on the port-channel interface; you cannot enable the feature on member ports.
2. Configure each port (interface) for normal, non-private hosts service. Configure the access group mode of the port as prefer port mode. You can configure the VLANs at this step or later.
3. Determine which VLAN or set of VLANs will be used to deliver broadband services to end users. The private hosts feature will provide Layer 2 isolation among the hosts in these VLANs.
4. Identify the MAC addresses of all of the BRASs and multicast servers that are being used to provide broadband services to end users (isolated hosts).
Note If a server is not connected directly to the switch, determine the MAC address of the core network device that provides access to the server.
5. (Optional) If you plan to offer different types of broadband service to different sets of isolated hosts, create multiple MAC and VLAN lists.
6. Configure promiscuous ports and specify a MAC and VLAN list to identify the server and receiving hosts for a particular type of service.
Note You can specify multiple MAC and VLAN combinations to allow different types of services to be delivered to different sets of hosts. For example, the BRAS at xxxx.xxxx.xxxx could be used to deliver a basic set of services over VLANs 20, 25, and 30, and the BRAS at yyyy.yyyy.yyyy could be used to deliver a premium set of services over VLANs 5, 10, and 15.
8. Enable private hosts on individual ports (interfaces) and specify the mode in which the port is to operate. To determine port mode, you need to know if the port faces upstream (toward content servers or core network), faces downstream (toward DSLAM and isolated hosts), or is connected to another switch (typically, in a ring topology). See the β€œRestricting Traffic Flow (Using Private Hosts Port Mode and PACLs)” section .
After you enable the feature on individual ports, the switch is ready to run the private hosts feature. The private hosts software uses the MAC and VLAN lists you defined to create the isolated, promiscuous, and mixed-mode PACLs for your configuration. The software then applies the appropriate PACL to each private hosts port based on the port’s mode.
To configure the private hosts feature, perform the following steps. These steps assume that you have already configured the Layer 2 interfaces that you plan for private hosts.
Note You can configure private hosts only on trunking switch ports or EtherChannel ports. In addition, you must enable private hosts on all of the switches between the DSLAMs and upstream devices.
Router(config)# private-hosts mac-list mac_list_name mac_address [ remark device-name | comment ]
Creates a list of MAC addresses that identify the BRAS and multicast servers providing broadband services.
Specify the MAC address of every content server being used to deliver services. If you plan to offer different types of services to different sets of hosts, create a separate MAC list for each server or set of servers providing a particular service.
Note If a server is not directly connected to the switch, specify the MAC address of the core network device that provides access to the server.
Router(config)# private-hosts vlan-list vlan-IDs
Creates a list of the VLANs ( vlan-IDs ) whose hosts need to be isolated so that the hosts can receive broadband services.
Create separate VLAN lists if you plan to offer particular services to different sets of hosts. Otherwise, all of the broadband services will be delivered to all isolated hosts.
Router(config)# private-hosts promiscuous mac-list-name [ vlan-list vlan-IDs ]
Identifies the content servers for broadband services and the end users (isolated hosts) to which to deliver the services.
Note You can enter this command multiple times to configure multiple MAC and VLAN combinations, each defining the server and receiving hosts for a particular type of service.
Globally enables private hosts on the switch.
Router(config)# interface interface
Selects the trunking switch port or EtherChannel to enable for private hosts.
Router(config-if)# access-group mode prefer port
Specifies that any existing VACLs or RACLs on the trunk port will be ignored.
Router(config-if)# private-hosts mode { promiscuous | isolated | mixed }
Enables private hosts on the port. Use one of the following keywords to define the mode that the port is to operate in:
Note You must perform this step on each port being used for private hosts.
Exits interface and global configuration modes and returns to privileged EXEC mode. Private Hosts configuration is complete.
The following example creates a MAC address list and a VLAN list and isolates the hosts in VLANs 10, 12, 15, and 200 through 300. The BRAS-facing port is made promiscuous and two host-connected ports are made isolated:
The following example shows the interface configuration of a private hosts isolated port:
The following example shows the interface configuration of a private hosts promiscuous port:

Pierced Long Nails Xxx Xxx Porn Video
Voyeur Pee
Beautiful Girl Lingerie
Private Things
Masturbating With Soap

Report Page