Cisco WAN :: Big Prefix Block Separation To Different Public AS 65200
Jan 7, 2013
Imagine AS65200 anouncing block 10.10.0.0/22 to the internet.Now for some reason we need to announce block 10.10.2.0/24 from AS65333.How should routes from AS65200 be announced now?
Can I maintain the whole /22 block since 10.10.2.0/24 from AS65333 is more specific? Or should I now break AS65200 announcement into smaller prefixes completelly excluding .2.0/24 ?( .0.0/23 and .3.0/24)
My web server is out of public IPs. I requested more from my ISP and I got a different range with a different gateway. How do I handle the configuration on my Cisco ASA? Without any configuration changes to the firewall I saw the traffic hitting it and being blocked. I added an access rule to allow the traffic. I added a virtual interface on the ASA. I added a virtual interface on the web server. Using "Packet Tracer" the traffic flows from the outside interface to the new virtual interface. But I'm unable to access my web server and I don't see any traffic on that IP reaching the web server.Using Cisco ASA 5510.
My ISP insists on using a /30 IP WAN block to connect to its equipment even though it is an ethernet handoff. They wil then route a /27 public IP block to my firewall. I would have liked to skip the WAN block and connect my PIX directly to the interface but now have to deal with two sets of IP blocks and routing between them but I still want to avoid having to use a router in between their equipment and my firewall.Is it possible to use one of the switch ports on the PIX and configure it as a separate VLAN to handle the WAN block and then route internally to another VLAN with the public block and still be able to use NAT, ACL and IPSec on the PIX?
We are installing 1260 Access Point (AIR-LAP1262N-E-K9) with 2 sets of external antenna:AIR-ANT2460NP-R (2.4Ghz, Patch Wall-mount, 6dBi Directional) & AIR-ANT5160NP-R (5Ghz, Patch Wall-mount, 6dBi Directional).What would be the recommended separation of the 2 antennas if they will be mounted beside each other?
I'm building a new colo presence with a full class C of public IP's. The idea is to connect to our ISP with a 3750x switchstack and they will be providing two ethernet drops that conect directly into two seperate switches on their side with HSRP and BGP at the routing level, so we will just point to their virtual IP (gateway address).I'm not sure how to either segment the public ip block or statically route each ip address and the interaction of vlans/svi with HSRP groups. Just use the switch at layer 2 or handle the internal routing with eigrp or ospf at layer3?
Is there an easier way to locate what an ACL, prefix-list, etc is applied to?ometimes its a bit tedious especially on some devices with a lot of config. I would like to see what route-maps a prefix-list is applied to[CODE]
We have been testing out IPv6 configurations on a 5520 running 8.2(4). We have assigned EUI-64 prefix addresses to sub-interfaces to allow clients to auto-configure there IPv6 IPs and it works correctly. I used ASDM to do the original configuration and noticed that there were two different ways to do it, both of which seem to work. I can add a prefix under the Interface IPv6 Addresses dialog box and check EUI64 or I can add it under the Interface IPv6 Prefixes. But using the two methods yields two different interface configurations:
1. interface GigabitEthernet0/1.40 vlan 40 nameif test
We have an ACS 5.2 server connected to an AD domain controller which has several trusted domains. (domain1, domain2, domain3) We currently have to specify which domain each user belongs to (ie, domain1user) in order to connect. We would like to only have to enter the user name without the prefix, (ie, user1) and have ACS automatically check each domain for a match. Is this possible with ACS 5.2? I seem to remember this was possible with ACS 4.2.
I have configure my ACS 5.3 to strip the prefix of the radius username (Domain week wang) it received and I also configured my ACS as the External Radius Server. However, this does not seem to work. The authentication protocol that I am using is PEAP Mschap v2.
I have read inside this forum that due to the fact that the radius username and password is transited inside the TLS tunnel of the PEAP MsChap v2 thus ACS is not able to do the stripping as it is not allow to touch anything inside the TLS tunnel.
I noticed that the recently released firmware version 1.2.0.9 for the RV110W router mentions in the release notes that DHCPv6 Prefix Delegation is now supported.
Does that mean that this feature will also be implemented in some future firmware release (if we ever see one) for the RV220W router? This is the method used by most if not all ISPs around the world (e.g. Comcast) for IPv6 and the only one RV220W does not currently support. P.S. As of beta version 1.0.4.13 there is no support for IPv6 Prefix Delegation.
BGP prefix list is not updated when other party having new downstream with different AS number.BGP filter has disabled but the prefix list is still not updated.BGP soft reset is performed, but the prefix list is still not updated.BGP prefix list is only updated when the other party having new prefix with the same AS number.Can explain why?
Since this router already set up for IPv6 and Dual-Stack traffic, would it be possible to give it the ability to get its IPv6 prefix from the WAN side of the router.
Example:
I have Comcast, and as long as my modem and router support IPv6, with the router also supporting DHCPv6-PD to get the /64 prefix from comcast.
I now have an RV180W so this is not an issue for me, but my father is inheriting the WRVS4400N from me and he is also on Comcast.
I am trying to configure this router to obtain an IPv6 address from my ISP who offers a dual stack IPv4/IPv6 DHCPv6 Prefix Delegation service.
I did a WAN packet capture to see the type of DHCPv6 packets the router sends to the ISP in order to obtain an IPv6 address and I saw that the router is sending DHCPv6 solicitation packets of type IA_NA i.e. for Identity Association for Non-temporary Address. However, most ISPs that offer a dual stack IP4/IPv6 service, they use DHCPv6 Prefix Delegation in which case the router is expected to send DHCPv6 solicitation packets of type IA_PD i.e. for Identity Association for Prefix Delegation.
I then downloaded its configuration file and saw the following:
So, the option for the DHCPv6 client to perform a prefixDelegation request is disabled. Does that mean that if I set this flag to "1" it is going to work? Well, I edited the configuration file and changed this flag but the router refuses to load it! It complains about the file being changed. How does it know that? Is it computing some type of checksum? How can I manually edit this flag and update the router's configuration?
One of our vendors requires using a public ip address to setup a site-to-site IPSEC vpn. We only have one public ip address and that will be used for the vpn endpoint and for internet access for the local network. I've setup policy NAT from our local network to the outside interface. I'm also using the outside ip address for the crypto map. The tunnel setups successfully and the Tx count increases anytime I try to ping the remote network, but the ping fails and the Rx count does not increase. According to our vendor, we should be able to ping the remote network and connect using port 443. When trying to connect using port 443, I see a SYN timeout in the logs. I'm not sure if the problem is on their end and they're rejecting our traffic, or if something is misconfigured on our end. I'd like to make sure that I have everything configured correctly before I go and point fingers at them.
Local Network - 10.10.9.0/24 Remote Network - 20.20.41.0/24 Remote Peer - 20.20.60.193 .ASA Version 8.2(5) ! hostname ciscoasa
My ISP (OTEnet, Greece) offers IPv6 connectivity in the form of dual-stack IPv4/IPv6 with the requirement that the router supports DHCPv6 Prefix Delegation for establishing an IPv6 connection.Using other routers (Cisco 887W, DrayTek Vigor2130n), I have established an IPv4/IPv6 connection but I am unable to do so with the EA4500. As a matter of fact, when I have the "IPv6 - Automatic" option enabled the router not only cannot obtain an IPv6 prefix from the ISP but it gets stuck in the connection attempt and never obtains an IPv4 or an IPv6 address. I have to disable the IPv6 option in order to simply establish an IPv4-only connection without problems.So, my questions are:
1. Does the latest (2.1.38.38880) firmware support dual-stack IPv6 and DHCPv6 Prefix Delegation?
2. If the router cannot negotiate an IPv6 connection why is it not establishing an IPv4 connection only but gets stuck in the process?
i need to allow https traffic to a server in the DMZ that will have a routable IP address will just an ACL suffice ?which interface do i apply it to ? wan or dmz ?i dont need a NAT since the DMZ is a routable space?
I'm trying to setup my DMZ so all my servers will have public IPs assigned to them. I'm currently trying to use two interfaces on each server, one with a private IP and then one with a public IP. All my internal traffic will go over the private interfaces...this is working. However, I'm having a problem trying to get it so the public interfaces work. Ultimately, these will be VM Hosts and have VM guests on them, each guest will have it's own public IP.
I am trying to configure a SSL VPN on a Cisco ASA5520. Unfortunately the port 443 of the OUTSIDE interface of ASA is already in use by Microsoft Outlook Web Access and I cannot change the configuration of Outlook. This configuration already in place prevents me to use the public IP of the ASA as Cisco VPN ip address for the webpage. I don't either want to use a different port so to keep life easy for the users.I have some public IPs available that I can use so I wanted to use one of them instead of the ASA's OUTSIDE interface.
My ASA 5510 is configured with a single PUBLICIP1 on the outside interface. All internal hosts 192.168.0.x are behind the ASA firewall and NATed to PUBLICIP1 including a few site-to-site VPN tunnels. This is also true for DMZ. Now, I would like to add a second PUBLICIP2 to the ASA and map it to one internal host ONLY - For eg: 192.168.0.25. How can I do this without effecting the existing setup? Since my entire internal subnet 192.168.0.0/24 is NATed to an existing PUBLICIP1 how can I exclude just one host (192.168.0.25) and bond it to the PUBLICIP2 for all ports.
This is what my current OUTSIDE interface looks like.
interface Ethernet0/0 duplex full nameif OUTSIDE security-level 0 ip address PUBLICIP1 255.255.255.224 !
We have a T1 connection at our office with a block of 5 IPs. The external interface is simply one RJ45 jack. Currently we have a home spec router connected to the external interface, and then a switch connected to the router. Certain ports are forwarded to our server in the home spec router for things like OWA, etc.I would like to start putting our other IPs to use. Is this usually done by having a switch connected to the external device and then have multiple routers connected to the switch? Or is it one router capable of VLAN or is it something entirely differentReally, what I want to know is what the rest of the industry typically does to use their multiple IPs.
I will be provided with /29 public IP address from my ISP. The idea is to run OSPF between ISP and my ASAs over private IPs so /29 is presented to ASA. This is because I will be using 5 out 6 available IPs on my ASA so I cannot use them on the routers.I need to run HA in Active/Standby mode on ASA, terminate site-to-site and remote access VPNs on ASA, and use static NAT for kit in DMZ network I am trying to figure out how to present this public IP range on ASA. Should I create two subinterfaces on physical interface towards OSPF area and assigned private IP address on one of them for OSPF and public IP on another and then setup a failover on each subinterface.
command for port forwarding to a few applications (inside hosts) when you only have one Static IP (Public) which is used for many to one NAT (Overloading)?This is the config for the many to one NAT.access-list 1 permit 172.16.0.0 0.0.255.255 ip nat inside source list 1 interface Dialer1 overload What command is necessary to forward ports to certain applications?
Is it possible to use 1 private IP through VPN and same private IP mapped with Public IP? For example 192.168.0.1 is configured in VPN tunnel. i m able to ssh on both ends. ( VPN phase 1 and phase 2 gets completed)But when i map 192.168.0.1 with some public IP problem starts. when i try ssh i see public IP in my destination firewall logs. IPSEC: Received an ESP packet xx.xx.xx.xx "mapped public IP". The decapsulated inner packet doesn't match the negotiated policy in the SA, The packet specifies its destination as
I've currently got my ASA (5505) serving a /28 public subnet. I've ran out of IPs, so my DC has issued me an additional /24 subnet that they have routed to my ASA. What needs to be done on my ASA so be able to use these new addresses? I've been trying to search and not been able to find a good answer (some say I shouldn't have to do anything, everything else references NATing, which I currently don't do and would rather not do).The servers I assign these to, I'd like them to have the public ip assigned directly to them.
is it possible that a public IP can be automatically routed to another public ip.For example I have two routers A and B. router B has a LanB in 10.0.0.0 network and the public ips are in the x.x.x.0 for internet access. router A is located at a remote location and has a public ip of y.y.y.0 network.
I have setup Cisco Asa 8.4 Lab in GNS3 to understand new Nat changes in asa 8.4 because im new to asa.
I have configured one of my internal webserver to static NAT with one public ip. Im able to access hosted webpage from static public ip 192.168.1.4 means NAT is working fine, the problem here Im facing i'm not able to ping to Mapped public IP 192.168.1.4 from outside interface sitting on pc (ip 192.168.1.100) which is also connected to same outside network and neither from ASA console but Im able to ping outside interface ip address which is 192.168.1.3 from pc (192.168.1.100) and from asa console.
This how my network topology
Inside Network 192.168.72.0/24 outside Network 192.168.1.0 inside ip 192.168.72.2/24---------------ASA8.4-----------------------outside ip 192.168.1.3/24 (connected to ADSL router 192.168.1.1)
I've replaced my dead ASA5505 with a 861-K9.Our ISP provides a subnet of public address /29 (wan side) by example: 200.200.200.xxx /29,we have 3 servers (lan side) in the example 10.1.1.xxx /24 is the same case than Johnatan, the only difference are the public addresses. [URL], everything is ok when NAT via the FE4 public address, but when do the same with other public IPs doesn't work.