Jump to content

Dhcp Client, Dhcp Server, Static Ip And Subnets

Recommended Posts

Seeing as we seem to be having this question asked at least once a week I'm writing this to hopefully save a lot of support time.

The largest problem people seem to be having is not understanding the difference between a DHCP client and a DHCP server. If you set your Fon to be a DHCP client then it will request an IP address from a DHCP server. If you have one running then it will get an IP and be happy. What that IP address is we can't tell you, you'd have to check with your DHCP server, that is usually your router. We also probably can't tell you how to check as each one is different. If you don't have a DHCP server running then it won't get an IP and you won't be able to talk to it, this is where people think it is bricked, it isn't, it just doesn't have an IP.

DHCP Server - This is where your Fon gives out IP addresses to DHCP clients. It is set up in a completely different place to the DHCP client on the Fon. Having two DHCP servers on your network at once is a bad idea so be careful if you turn two on.

Static IP - Where you tell the machine what IP to work on. This is good if you always want a machine on a specific IP.

Subnets - Very basically, remove the last digit from your IP address and that is your subnet, you can talk to any other machines with the same subnet if they are plugged in to the same switch/modem/AP/router as you. All traffic to other subnets will be sent out of your modem/router. Example:

Laptop can talk to Fon if they are both plugged in to your switch

Laptop can NOT talk to Fon even if they are both plugged in to your switch as the traffic to the Fon will be sent out of your router and not to the Fon.

Always make sure that all machines trying to talk to each other are on the same subnet.

If you have some basic networking knowledge then Jasager is almost plug and play but if you don't then you will have problems and will end up messing things up. It is very hard to brick your Fon so don't automatically assume you have if it stops working. Do some research (that isn't throw a question on here and hope someone gives you the answer), learn a bit about networking in your environment (linux, windows, mac etc) and try to fix it yourself. Play with tools like Wireshark (If you don't know what this is then you probably aren't at the level to fully understand Jasager anyway so learn this first) and tcpdump. Try changing round configs on your network, enable and disable your DHCP server, try putting static IPs on some machines, play with different subnets. If all this scares you then again, you are not ready for Jasager.

You will get much more out of learning networking than just trying to get Jasager working. Even if you get Jasager working and don't understand networking your next question will be "What can I do now?" If you know networking then this will be fairly obvious.

Link to comment
Share on other sites

And from experience, if you know what you are doing enough to get into redboot and edit it then you know enough about what you are doing not to break it or to take it like a man if you do.

And I've messed with redboot a lot and not managed to kill it yet

Link to comment
Share on other sites

One more point, seeing as it has just come up twice, if you get a 169.x.x.x address then it means your machine has tried to get an address via DHCP but has failed.

Either get yourself a DHCP server or set a static IP.

See this for more info http://compnetworking.about.com/cs/protoco...bldef_apipa.htm

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...