1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Trying to convert to Static IP..

Discussion in 'Cisco/Linksys Wireless Routers' started by AllthatufeaR, Jan 19, 2007.

  1. AllthatufeaR

    AllthatufeaR LI Guru Member

    Well im trying to convert my stuff over to static ip, i dont have a problem doing it on my internet connection, but i do have a problem doing it on my router settings, what all do i edit to convert it over to a fully working Static IP? I see at the start of setup you can change it to static ip and change all the info, but when i do that i get 'Invalid Gateway Address'. Also i notice more stuff about static routing in the Setup > Advanced Routing tab. Should i fill out that stuff too? When i have got it to work it kills my internet connection...im confused as to why and what im doing wrong. If it helps any i have a v4.1 router.


    Thanks,
    Justin
     
  2. ifican

    ifican Network Guru Member

    Unless you get a static IP from your ISP then you just leave it as dynamic or you will have potential problems down the road. As far as your lan goes, if you dont want to use dhcp then turn on the dhcp feature of the router and make sure that all of your static settings on all the machines you have are set up correctly, thats going to be based on your subnet mask. There will be no need to mess with the advanced router settings.
     
  3. AllthatufeaR

    AllthatufeaR LI Guru Member

    How do you go about getting a static ip from the ISP? Never heard of that...and about turning off DHCP, where do i do that in the config? I see this on the main setup page...

    Local DHCP Server: Enable Disable

    Do i just disable? Is that all there is to do?

    I hope this helps my problems, i have 2 pcs and have alot of trouble trying to play pc games together cause of this....and downloading problems, im always shown as not connectable, so im trying to fix both problems.

    Thanks for you're help...

    Justin
     
  4. Max Monroe

    Max Monroe LI Guru Member

    Oh dear. Are you sure you know what you are doing? :hmm: There are IP's inside your LAN, on "your side" of your router, and IP's outside your LAN, on the "other (WAN) side" of your router, the ones that everybody else on the internet sees from you. I, for one, am certainly not sure what exactly would you like to do, so - sorry if this gets too obvious, elementary and/or verbose:

    The outside IP's are given to you by your ISP, the one you connect to for net access. They generally only give you exactly ONE, and a DYNAMIC one. There's nothing you can change about that, except perhaps getting a different type of subscription with your ISP, one that might grant you fixed and/or multiple IP's. Therefore, your WAN settings in the router usually MUST stay set to dynamic IP (DHCP client) - but that's OK, there's normally no need to have a static IP. If you'd like to somehow be able to address your LAN / computer from the outside without being able to know your single - potentially changing - IP, you can use a "Dynamic DNS" service with one of the free providers; you set up a domain name with them, and your router makes sure to update that domain name to whatever your outside IP changes to. Tomato (and most other current router firmwares) support this, you can set it up under "Basic" -> "DDNS".

    Your inside IP's are a different matter altogether, and they're your own business to choose, as long as you're behind a router and it knows how to relate your outside IP to your internal ones when needed. That's what a router is for, after all.

    • Again, normally you set those up as "Dynamic" or "DHCP" on you individual machines and enable the DHCP (server!) on your router, which only means that all your machines can turn to your router to get an interal IP (each their own, on your LAN), but it also means that they will get a dynamic, changing IP, as the router decides what IP is free when they ask for one. Note that you still have to instruct your router regarding the "pool" of available IP's you grant it to distribute among it's DHCP clients
      ("Basic" -> "Network" -> "DHCP server"; default is 192.168.1.100 to 192.168.1.149, since 192.168.xxx.xxx happens to be a range of IP's meant to be used internally. See this for more ).
    • You can change that if you wish, by STILL setting up each of your machines as "Dynamic IP / DHCP", but instructing your router to give them the SAME, fixed IP each time they ask for one, based on their MAC addresses. This way, your machines still use DHCP, but are actually getting known, predetermined IP's ("Basic" -> "Network" -> "Static DHCP"). Of course, you need to know your MAC addresses to do that. You can see them under "Device List", when connected to the router. Also, the IP's you set up as static DHCP should be removed from your router's DHCP server's IP pool.
    • Finally, you can use truly static IP's by setting up each of your machines as "Static IP", which you actually have to enter right there on each machine; you would preferably use the same IP's that your router would have granted when using DHCP, namely values such as 192.168.1.100, 192.168.1.101, 192.168.1.102... taking great care as to NOT GIVE the same IP to two different machines on your LAN. Also note that your router is typically using the IP 192.168.1.1, unless you configure it otherwise, so that one's usually taken already, but you COULD also use 192.168.1.2, 192.168.1.3.... or, say, 192.168.2.100, 192.168.2.101 - if you use 192.168.2.xxx everywhere. In this case, you can disable the DHCP server on the router, it has no use (unless new computers show up in your LAN, asking for DHCP service).

    In case 2 and 3, you would know your computer's inside (local) IP's on your LAN (since you have set them), and would be able to use them if one of your computers wants to see another one. That would have nothing to do with your outside IP, the one your ISP gives you. If another computer from the internet would want to access one of yours, however, it would need to use that outside IP, BUT your router would need to be set up and ready to connect that outside computer to a specific one on your LAN. There are several ways to set that up, since this is what routers do, but that's a different story.

    This is a problem you encounter not so much going from one of your machines on your LAN towards the net, such as when surfing; for that, you only need to know the way out from your LAN - that is the gateway, your router, whose address gets either set up automatically along with the IP if you use DHCP on your machines (case 1 or 2), or must be entered manually in case 3, beside each static IP, in each of your machines, as gateway address 192.168.1.1, or whatever IP your router is set to be at.

    You DO encounter it however, when someone from the outside tries to contact you. That outsider can only see you by your single outside IP, which leads to your router, and you router needs to figure out which machine on your LAN should actually be addressed. By default, if you don't set it up, it figures that none of them, and rejects the outsider...

    Aaaaaanyway, this is more than long enough already :knock: - please try to be more specific about what exactly are you trying to do, what have you done, and what/how fails.

    Max

    P.S. Sorry, I've just realized this was not in the tomato-thread, so the specific interface layout is useless; still, most routers / firmwares can set up mostly the same general stuff, so the essence is still true...
     

Share This Page