Cisco :: Possible Public IP Can Be Automatically Routed To Another
Mar 20, 2013
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 understand router on a stick for inter-vlan routing but where I'm having trouble is having one of the vlans be public addresses. One of my clients has a rack in a colo where there is no router, i.e. their /24 public network has .1 of the network assigned to a colo router, then they have a 2960G switch in the rack that all the gear is connected to. Public IP's are assigned to certain devices / servers with .1 as their GW. Problem is, they also have a private range on the same switch with no vlans and things are a little 'cluttered' and there is no control of traffic.
The assets I have are a 2821 router with (2) GigE interfaces and the 2960G switch. A /30 network is going to assigned on the colo gear to use to push the entire /24 down to the cabinet. I'm going to NAT the local 10.100.x addresses on vlan 10 and I want the public traffic on vlan 20. During a recent test, the private traffic worked as expected but the public traffic didn't work. I don't need a complete config, more of a 10,000 ft. view of how this needs to be done so (a) traffic is vlan'd to keep things segmented, (b) I can static inside / outside public addresses from the /24 to reduce the number of public addresses being assigned directly to servers (some of this is unavoidable, but the less the better), and (c) I can NAT the local subnet to either to the /24 or the /30 (not much very much traffic in this way).
EDIT: The switch is a C2960S, not G. I cannot enable lanbase-routing, it is apparently unavailable.
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
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 am working for a small business that decided to a public address block ip addressing scheme for their private LAN (192.0.10.0). It was setup this way before I started working here. I have noticed something I think is odd on the network. This just recently started happening. I have some devices that have different subnet masks in order to keep them from being viewed from other computers on the LAN. For example, I have an wireless router with the ip address 192.0.11.50 subnet 255.255.252.0 . All the other computers on the LAN have ip's in the 192.0.10.0 255.255.255.0 range. When I want a computer to see the 192.0.11.0 , I change its subnet to 255.255.252.0 I noticed today that when I do a traceroute on 192.0.11.50 , I get this:
Code: C:Useruser>tracert 192.0.11.50 Tracing route to 50.11.0.192.in-addr.arpa [192.0.11.50] over a maximum of 30 hops:
I am using a company called Zen for adsl, I have 8 IP from XXX.XXX.XXX.248 to - XXX.XXX.XXX.255, Gateway is 254, Address 249-250-251-252-253 I would like to appear at the 4 sockets at back of router, and 252,253 will be used for a server...I understand I should be using Routed IP , but I cannot get it to work, I can ping out to google from the server, but the server is not live to the world. [code]
I have an old Nortel network with a bunch of servers attached. Connected to it is the new Cisco core, by way of a routed port. My task is to migrate servers over to the Cisco side of the network, with minimal downtime, and have full network connectivity, retain IP addresses/remain on the same subnet, and retire the Nortels. The Nortels are running VRRP, so I can fail the gateway over by becoming part of that group and later dropping the Nortels, but I can't seem to get a host on the Cisco side to participate in the original subnet. The routed port kills VLAN traffic, so I tried bridging the VLAN with the routed port, to no avail.
Any way to test throughput on a routed SG-300. I tried using iperf with netbook on VLAN1 to netbook on routed interface running @ 100mb. I was getting results as low as 40mb upto 200mb (sometimes even 2gb, I assumed these to be flukes). Since implementing it, the throughtput seems worse, I'm getting between 10 - 40mb of throughput. I have about 30 clients behind it routing across a 100mb leased link. I don't see why the SG300 shouldn't be able to do wire speed routing (upto 100 hosts). How to verify the expected throughput consistently?
I got the SG 300-20 small business L2/L3 switch. I've read through the 325 page pdf manual and I still can't figure out how to do what I need to do. Here is my setup using example ips.[code]
I want to be able to have any workstation I put on the workstations vlan to use 69.30.44.2.34 as a gw and from there route to 170.4.5.5 and from there to the outside. Basiclly, I want to be able to route ips from two different subnets on two different vlans. I've read through the docs and so far I have vlan1 setup and vlan 2 setup fine but I have no clue how to get the routing to cross vlans. The docs say the only way to have vlans talk to each other is by routing through the vlans ip interfaces but I have no clue how. There isn't a simple step 1,2,3 chapter that gets you to route between two vlans. What am I doing wrong? I put in some IP route entries but nothing seems to work.
I want to know whether NAT loop back is possible with the RV220W router/firewall, or when can we expect a firmware update that addresses this?For terminology sake, what I mean is that I've got a rule that maps HTTP/S to 192.168.1.2. However, when accessing my external ip from an internal ip, I don't get routed to 192.168.1.2.
have a Cisco ASA that I am trying to configure in a unique way, I want it to perform a variety of tasks;
VPN SSL VPN Tunnels Firewall Inside to Outside via versa
But the difficult task, is creating a DMZ with devices that are assigned fully routed IP addresses from our ISP directly, these are H323 and SIP devices that cannot use NAT, and must have a fully routed IP address assigned to them.
Obviously the problem I have with the Firewall in its default routed mode, is that it wont allow me to overlap IP addresses on the outside interface with the DMZ interface.
Could the Firewall be configured for Transparent mode between Outside and DMZ, but Routed mode between Outside and Inside?
I have my main branch router (3825) and two remote routers (2821's). They are connected through leased lines that do not touch the internet. For various security reasons I have to ensure that the traffic from the remote's are encrypted in a VPN tunnel even though it is still part of a private network.I have went ahead and created the tunnels and I can verify that they are up. I have applied the cryptomap to the correct interfaces, etc.So the question is - How do I ensure that traffic is not just being router out of the interface from the remote sites back to the branch router with or without using the VPN tunnel? I've taken down the tunnels and of course, the traffic is still being passed back and fourth.
We currently have ACE20's, which only support multicast in bridge mode.Was wondering if it's the same on ACE30's, or if Cisco finally implemented support for mcast in routed mode.
I am trying to set up a LAN-to-LAN VPN tunnel between two sites. One site has a 5505, and the other site has a 5510. It looks like the tunnel is being established fine (both ISAKMP and IPSEC SAs look OK), but traffic doesn't appear to be routing across the internet between the devices. [code]
I have 2 3550's connected across a wireless link. [code] However, from Switch A, I cannot reach 10.1.3.9Can this 3550 not route traffic between 2 routed ports?
I have a subnet (vlan 104) working great across a WAN. At site 1, Router A (3745) has the L2TPv3 tunnel configured while Router B (7204) has a routed interface on vlan 104.
The only thing router A is doing is the tunnel, so I'd like put the tunnel on Router B and eliminate Router A.
The trouble is, when I move the configs to Router B, the tunnel comes up, but the far side does not receive traffic over the tunnel.
Router B shows sending and receiving packets (per the 'sh l2tun session all' command). The far end router shows sending packets but receiving 0.
Is it a problem to have both the vlan 104's L2TPv3 xconnect interface and the vlan 104's routed inteface on the SAME router?
we are trying to configure one to one NAT translations on a Cisco 527W-U, but are having some problems. We are running firmware version 1.2.4 (003) on the 527.
The DSL line is assigned with a /29 address range x.x.x.64 /29?
The DSL WAN interface picks up x.x.x.65 /32 from the Radius server. We are using the default private IP address range 192.168.15.0 /24 on the LAN (VLAN1), and can get to the internet ok with a PC connected to the LAN.
However when we try to set up a public IP address in the same range (eg x.x.x.66 /29) on VLAN1 (with x.x.x.67 on the PC) it will not connect. (won't allow us to configure an address from the same range as the WAN on a new VLAN interface).
we would want to be able to do one to one NAT translations eg x.x.x.66 on the outside to 192.168.15.2 inside, x.x.x.67 outside to 192.168.15.3 inside etc, but this will not either. We have tried this on a normal IOS router (887) and it worked ok. We have also tried the same on a small DSL router / modem product similar to the 527 from another manufacturer and it worked ok on that, but we wanted it to be able to work on the 527.
We have tried the NAT bypass feature without any success, reading several other discussion forums on this website leads me to believe that one to one NAT is not supported on this equipment at the moment, or at least not at the current firmware release.
One work around would be to just assign a /32 to the WAN interface on the DSL and route statically to a different routed subnet configured on the LAN, however we were wanting to avoid having to do that if possible.
1.create a drawing showing a private routed network.
2. On this drawing you will show your placement of the following,why they were placed there (you can use one or more of the servers/router listed in your drawing):
This question is in the context of servers sitting in a colocation environment behind an ASA5510 with security plus license.Our colo provider is going to be statically routing a /28 public subnet to our ASA5510 (say 1.1.1.0/28). We will also be getting a single IP (say 2.2.2.2/30) on a small router-to-router subnet (2.2.2.0/30) to which the 1.1.1.0/28 subnet will be statically routed to our ASA5510 from our colo provider.I will obviously set the outside interface of the ASA to be 2.2.2.2/30 so that the colo provider can route the 1.1.1.0/28 subnet to it. I will also set a default route to 2.2.2.1 which is the IP of our colo providers gateway (and the router that will be statically routing the 1.1.1.0/28 subnet to us).
We have various servers in the same rack as the ASA (connected via a 3750G switch). Some of these servers need to be exposed to the internet (web, email, etc servers) and some do not (database servers).I'm considering 2 different ways of designing the network but I have questions about both and not sure which way to go:
1) Scenario #1: Using NAT and private IP's for all servers.In this scenario where/how do I assign the internal network (say 10.1.1.0/24) and the public routed subnet (1.1.1.0/28)? I assume the internal 10.1.1.0/24 is an inside network assigned to the interface connected to the 3750G (to which all the servers connect). However, where do I assign the public routed subnet (1.1.1.0/28) since it is somewhat "nebulous" in that it has to reside somewhere on the ASA so that it can then NAT to the internal (10.1.1.0/24) IP's. Also, is it considered an outside or inside network - and on which interface? My confusion is that If its added to the outside interface then won't that conflict with the 2.2.2.2 IP to which the colo provider is routing our 1.1.1.0/28 subnet to? And if its on the inside interface connected to the 3750G then wont that conflict with the 10.1.1.0/24 private IP range of the servers?
2) Scenario #2: Using public IP's for all servers:This scenario seems more straightforward to me: I would want to assign IP's from the statically routed subnet (1.1.1.0/28) to my servers so that range would be configured as an inside network on the interface connected to the 3750G (to which all the servers connect). This would be configured on a specific VLAN (say vlan 50). I would then have another VLAN (say VLAN 100) on the 3750G that has a private IP range (say 10.1.1.0/24) so that non-public servers (database, etc) would reside on there. All public servers that need access to private servers would have a NIC on both VLANS (50 + 100). My question is is this the correct way of approaching this? I also like this because I dont have to worry about NAT and the ASA can act as a router/firewall and things are clear in terms of whats happening.
Ultimately I'm not sure which is the best way to go in terms of having all servers on a private IP range and just NAT to them (as per scenario 1), or implement scenario 2 where servers have two interfaces.The main thing thats bugging me from scenario 1 is I'm not sure where/how to assign the statically routed subnet (1.1.1.0/28) on the ASA? (inside? outside? which interface?).
Is it possible to have context in transperant mode and routed mode. Means if i need three context then 2 of them is in routed mode and one of them is in transperant mode. If yes then how, i can 't find this info in cisco website.?I am havin 5585-x and asa version 8.4?
Current topology in network is such: web servers with content needing to be load balanced are in vlan 35 and these servers are directly connected to Core switch (two 6509 VSS) via 20 Gb EtherChannel. Vlan 35 also spans some other switches with other servers residing in this vlan. Additionally, there are dozens of another vlans (including external users) that need to communicate with web servers. IP addresses of these two web servers are: 192.168.35.1/24 and 192.168.35.2/24 accordingly with default gateway 192.168.35.254/24 (SVI on Core switch). Currently these ip addresses are used by management and other purposes and need to be reachable for same purposes after configuring load balancing with ACEs - it is needed to have direct access to servers behind ACE. How I can do that using ACE in routed mode?
During an installation, we plugged a Ruckus wireless bridge (powered by a PoE injector) into G0/0 on the 1941. The port status remained down/down. We then tried connecting it to G0/1. Again, the port status remained down/down. We took another wireless bridge, plugged it into G0/0 and the port changed to up/up status within a few seconds. The same happened when connected to G0/1. Both ports are have speed/duplex set to auto/auto.We took the cable from the first wireless bridge and connected it a 3550 switch, the FastEthernet port went up/up. We then took the cable and connected it to a switchport card (HWIC-4ESW) that was installed in the 1941 router. The port came up/up.We connected to wireless bridge back to G0/0 in the 1941 and manually set the speed/duplex to 1000/full. The link light on the router became illuminated after a few seconds but no console message was displayed (nor did any events appear in the log) and a "show int g0/0" showed the port status as down/down. This was could not be duplicated as this only happened one time The wireless bridges sit atop of a water tower and are connected each via a shielded ethernet cable. The cable that we're having trouble with is cat5e STP and about 310feet in length. I should note that we have not yet swapped the PoE injector but it seams to be functioning properly as power is getting to the wireless bridge and its accessible. Also because if the wireless bridge for some reason didn't come back up after a power cycle it would potentially mean climbing the tower to perform a hard reset. We tried another 1941 with same results however we have not tried another router model to rule out a potential platform issue. Can you recommend any troubleshooting steps to determine why the port status of the gig interfaces on the 1941 don't come up?
We are looking for a solution that to use Sub-interface on a routed port on 6509, instead of using a SVI on it.Are there any different when using Sub-interface?
We are currently looking at design models for a Multi-Tenancy solution.The firewall layer will be 2 X ASA's running 9.X to take advantage of VPN's in multiple context mode and mixed L3 and L2 contexts.
We will be delivering services through multiple L3 contexts (between 2 and 5 L3 contexts for services) and 1 transparent context for customers infrastructure who will then have virtual firewalls for NAT's and VPN's etc withing their own environment.
I am not very experienced with IPS so my query is; if we were to get an IPS license for both ASA's how would the IPS fit in, can we use it to inspect traffic for all the L3 contexts and the transparent context?
I would like to do the following architecture with the same C3750 : network X,Y,Z connected to 3750 in VRF D the 3750 uses a routed interface on subnet E for the default route in VRF D on this routed interface a BYPASS EQUIPMENT the other BYPASS EQUIPMENT interface is connected also to another routed interface on subnet E "also" this routed interface is in another VRF C with other network A and B.do you know if it will work because of 2 routed interfaces on the same IP subnet or is there a way to do that ? the only goal for me is to catch traffic from network X,Y,Z on SYN and ACK.
We are in the situation we have a active configuration with ACE30 doing normal load balancing in routed mode, we have tons of rservers going out on a VIP.we now had to add a new private network to a provider that strangely enough does not want to see our public or private addresses. we need to loadbalance towards him on a priovided subnet (still rfc1918) (IOS VRF bug? is that correct?)I have two options, add the network (new interface) to the active loadbalancers (contexts) and then tie in new policies to the active serverfarms or make a new context just to load balance towards this provider.(preferred)Now - If I do this, the rservers see the client source addresses from this new provider. as the loadbalancer does not "hide" the client IP's. I would then have to add static routers toward the new context - I would want to skip that.
is there a way, to make the loadbalancer hide the client addresses towards the rservers ? perhaps I'm just needing the correct search term to find the config example.
We have a 6509 that was connected to 2 other locations(location A and B) and our local lan (location MAIN). We wanted to move the location A and B to a 3750 switch and only allow the traffic that needed to access our location MAIN to come through the firewall. The only problem I ran into is that before location A and B were on different interfaces so in the 6509 firewall the routes for traffic to our MAIN location was done by static routes.
because it has a static overlap, which makes sense to me, but my question is how do I configure the network to get this to work? Do I have to reconfigure my network and access-list? Do I need to add more ports between the 6509 and 3750? I'm not sure if this is the best way to do what we want. If something is not clear I'll try my best to explain the setup, but I just took over for our I.T. guy when he left.
I put 10.10.10.72 instead I should have put 10.94.10.72. the routed port is on a different subnet than the computer I'm trying to access.
I have an ASA 5505 with the security plus software and I'm trying to find out how to assign 2 public IPs to the outside interface and have each IP routed to a separate internal VLAN. For example, IP 1 = X.X.X.1 routed to 192.168.1.0 and IP 2 X.X.X.2 routed to 192.168.2.0. I was told this was possible and I've been trying to find configuration examples, but I can't seem to get anywhere and now I'm getting desperate because I'm scheduled to install it this weekend.