-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Meyer wrote:
James Knott wrote:
(Ted Harding) wrote:
On 14-Oct-07 21:42:59, Aniruddha wrote:
On Sun, 2007-10-14 at 14:34 -0700, joe wrote:
Aniruddha wrote:
My brother get his ip adres through DHCP from a large college lan, his ip changes with regular intervals. I wonder is it possible reserve one particular ip for his machine and if so how do I do this?
Sure - are you the admin of the dhcp server?
Joe
Errr, I am afraid not. He just receives his ip adress through dhcp.
There is one thing he could try, which may or may not work often enough to to be useful.
Say he gets a particular IP address one time. Let him note that, and configure his own machine to have that IP address statically configured in his machine (this may involve setting up a static DNS and gateway too, so it might not be trivial).
<snip>
If it failed at any time, of course, then he'd just have to revert to DHCP for that connection.
Some networks will refuse connections from a computer that doesn't have a MAC address that's currently assigned an IP. Also, network admins can turn into nasty trolls (not that they aren't already <g>) when they find someone using a static address.
I must have gotten into this thread a little too late. Why, exactly, would you want a static ip in a dhcp environment? Sorry for the new question, but it's better than asking people if they prefer "top or bottom" (not in that way, of course) ;-)
Static assignment of DHCP addresses is often used to identify which devices are allowed to connect to a network. In an academic institution it is not unknown for students (or staff for that matter) to use their machines for purposes that what not entirely appropriate to the normal business of the institution (Not just "Anyone want to hack the Pentagon today?" but the use of things like Doom which could have a serious impact on network performance :-) ). It is often considered rather important to have a good idea of who owned what so you you know who to blame when something went wrong:-) In the institution I used to work all devices were registered with an appropriate entry in our domain with an appropriate address in our class B address space. This registration was assigned to an individual (or department). Anyone who was a member of the institution who was found doing the above would quite likely face disciplinary action as they would be violation of the institutions regulations. (The institution could get quite nasty about this). As at various times we had individuals accidentally set up machines that among other things were assigned the external gateway address, and the addresses of routing kit, so I think you can understand the general viewpoint on this issue. With later generation switches one can lock down connections by MAC address, or monitor which access points were being used which machines and in theory "alien" machines could be quickly identified and isolated if required. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHEyV+asN0sSnLmgIRAlZlAJ4qg77Ne6ZjBy+7HEDSsYmhk5jPfACghWaS 9bSFo333V6vbssNzKDXZ1q8= =lAmA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org