11-14-2016 11:14 AM - edited 03-12-2019 01:32 AM
11-14-2016 11:52 AM
The first important thing to consider is, that the legacy 5540 can't do Policy-Based-Routing. You have to control with static routes which destinations should be reached through this line.
You need a static route with higher AD pointing to the CM next-hop.
For NAT, I wouldn't NAT on the ASA. Better configure a static route for the internal networks on the cable-modem and use the NAT/PAT that is done there.
11-14-2016 01:17 PM
Thanks for your answer Karsten. Maybe I didn't make my self clear. Sorry for that and sorry for my English.
Network 10.13.0.0/16 is for CMTS with almost 1000 clients, so I need to do NAT on ASA. Right now I have that network accesing to internet just fine, but through a public IP (200.X.X.152) in the outside interface:
nat (CABLE,outside) source dynamic net10.13.0.0-16 ip152
What I need is that CMTS (10.13.0.0/16) reach the internet through the Management interface with the other ISP (Cable Modem) connected to it. I thought it was so simple as change the interface and the NAT ip but obviously I'm wrong.
I don't know what I'm doing wrong. Any ideas???
BR.
11-14-2016 02:29 PM
ok, so the new exitpoint is the interface "CableModem"? Then add the default-route to the modem, remove the old route and configure the NAT as you have done above. Make sure to put the NAT-rule at the end by specifying the keyword "after-auto":
nat (CABLE,CableModem) after-auto source dynamic net10.13.0.0-16 CM
Also make sure that there are no conflicting rules above.
11-14-2016 03:35 PM
Didn't work. I'm seeing no traffic on CableModem interface.
what I don't understand is why when I set up a static ip to my lap (192.168.1.4) and connect it directly to CM I can reach the internet, but when I connect the CM to the ASA interface (192.168.1.2) and set that very same ip address (192.168.1.4) for NAT it doesn't work...
This thing is driving me crazy!!
I think I don't need to modify routes in the CM since the ASA is translating network 10.13.0.0/16 in 192.168.1.4, right???
11-15-2016 01:39 PM
can you share the rest of your NAT- and routing-config?
11-15-2016 01:44 PM
would you like something specific?? coz the ASA has a big big configuration....it's nearly impossible copy it here. BR.
11-16-2016 07:16 AM
At least it's very likely that the problem is NAT- or routing related.
Or after configuring it in a way that you think it should work, you can run the packet-tracer
packet-tracer input CABLE tcp ANY-ALLOWED-INTERNAL-IP 1234 1.2.3.4 80
and share the result.
11-16-2016 08:47 AM
this is the result:
PIX-COSMOCABLE# packet-tracer input CABLE tcp ANY-ALLOWED-INTERNAL-IP 1234 1.2$
packet-tracer input CABLE tcp ANY-ALLOWED-INTERNAL-IP 1234 1.2.3.4 80
^
ERROR: % Invalid input detected at '^' marker.
it seems to be an error on the ANY-ALLOWED-INTERNAL-IP.
But I'm thinking, the CABLE interface works fine when the NAT is throuhg OUTSIDE interface. The problem is when the NAT is through CABLEMODEM interface
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide