General discussion

  • Creator
    Topic
  • #2194358

    What was EZ for Linksys, tuff for Cisco?

    Locked

    by cincinnerdi ·

    I’m sure this has been addressed before, but a search hasn’t yielded much.
    I want a Cisco 2514 router to be serve as a NAT router on my DSL line for my lab. Sounds easy, but my DSL provider assigns me an IP with a DHCP lease of 1 hour, so my outside IP address is changing several times a day. My Linksys home router, which I’m trying NOT to use for my lab, let’s you obtain the outside interface IP from the ISP’s DHCP.
    As for the 2514, I only know how to assign it’s interface IP statically (i.e., “ip address 1.1.1.1 255.0.0.0”)
    I know my router can be a DHCP server, but does IOS support obtaining a DHCP IP for an interface?

All Comments

  • Author
    Replies
    • #3269290

      Reply To: What was EZ for Linksys, tuff for Cisco?

      by paul.desjardins ·

      In reply to What was EZ for Linksys, tuff for Cisco?

      I would say, if you know how to set the Cisco with a static IP, then just do that. Your DHCP from your Linksys should allow you to set a certain IP range for DHCP, right? So, set your Cisco outside that IP range. For example, if you set DHCP range to 192.168.100.50 – 192.168.100.100, then set your cisco router to say 192.168.100.10. Since your Linksys is probably 1 on the 32nd octet (the last number), then try to keep your cisco close to it so it’s easier to remember and manage since they are both gateways. Of course, I’m sure we are talking about setting the “WAN” connection or gateway on the Cisco to a static IP, right? Then your internal on the Cisco will be a different range and you can set that to DHCP for your computer lab. Then with NATing turned on, everything should pass correctly. I have 2 routers for double firewall with a VPN router setup so I have a very similar situation to what you describe. Hopefully this helps.

      • #3269285

        Reply To: What was EZ for Linksys, tuff for Cisco?

        by cincinnerdi ·

        In reply to Reply To: What was EZ for Linksys, tuff for Cisco?

        Poster rated this answer.
        Paul, Thanks for the feedback. My initial post said “My Linksys home router, which I’m trying NOT to use for my lab…” I want to solve the problem using ONLY the Cisco router. In fact, I can set it up to use overload NAT and it works fine, for about an hour! Then, my ISP changes my outside IP address and all is lost.

    • #3269264

      Reply To: What was EZ for Linksys, tuff for Cisco?

      by paul.desjardins ·

      In reply to What was EZ for Linksys, tuff for Cisco?

      I’m sorry redboot, I guess I misread. I thought you wanted to use both, but just didn’t want to use the linksys for the lab part.

      As far as I can tell, it doesn’t appear to have the ability to receive IP by DHCP. It’s a complex networking router so I don’t believe it was ever intended for that type of situation. Here is a link to the docs that I looked through and could not find anything. Maybe you’ll have better luck. Your only other option may be to get a static IP from your ISP, which probably isn’t favorable because of cost I’m sure. Sorry I couldn’t help more.

    • #3270523

      Reply To: What was EZ for Linksys, tuff for Cisco?

      by cg it ·

      In reply to What was EZ for Linksys, tuff for Cisco?

      Cisco commercial routers like your 2500 series does not support DHCP addressing on the WAN s0 link. Their 1700 800 series does [consumer level and SOHO]. Further, the consumer level digital subscriber line requires a modem to operate which again is not supported with Cisco commercial routers. use the AUI0 or AUI1 to link to your consumer level LAN port and let the consumer router handle the the dynamic addressing. or get a static address and then get a serial to ethernet cable converter because WAN on 2500 series is s0 or s1.

      • #3142898

        Reply To: What was EZ for Linksys, tuff for Cisco?

        by cincinnerdi ·

        In reply to Reply To: What was EZ for Linksys, tuff for Cisco?

        I guess the topic ‘What was EZ for Linksys, tuff for Cisco?’ was fitting. Thanks. FWIW, I was using the 2 ethernet ports, not serial ports, and it was a patch cable from a DSL modem, but I don’t think that changes your answer. I am now working on getting a linux box with 2 NICs to be a poor-man’s router. I can set one up for DHCP and one to be static. I can’t seem to get it to route properly yet. But, that’s another issue. Thanks , CG IT.

    • #3142897

      Reply To: What was EZ for Linksys, tuff for Cisco?

      by cincinnerdi ·

      In reply to What was EZ for Linksys, tuff for Cisco?

      This question was closed by the author

Viewing 3 reply threads