Every time my Linux PC gets new Ip address, I can't access remotely, how can I access?/

Everytime when I boot (sometimes kids reboots) it gets new IP address,
I did port mapping in the Router (any ssh requests to this Ip addr),
when it changed Ip address, I can't access rempotely, any solution.

Also I added its names as "dhcppc3" in /etc/hosts files (ip address
machine-name), also when I do "hostname" it shows different name, how
can I name this machine as "tiger" so always I want the machine name as
tiger (if I do "ping tiger" with LAN shoud work), how can I do that?.
Thanks.

On 12 Oct 2005 17:08:57 -0700, GS <(E-Mail Removed)> wrote:


>Everytime when I boot (sometimes kids reboots) it gets new IP address,
>I did port mapping in the Router (any ssh requests to this Ip addr),
>when it changed Ip address, I can't access rempotely, any solution.

>Also I added its names as "dhcppc3" in /etc/hosts files (ip address
>machine-name), also when I do "hostname" it shows different name, how
>can I name this machine as "tiger" so always I want the machine name as
>tiger (if I do "ping tiger" with LAN shoud work), how can I do that?.
>Thanks.

DDNS

GS wrote:
> Everytime when I boot (sometimes kids reboots) it gets new IP address,
> I did port mapping in the Router (any ssh requests to this Ip addr),
> when it changed Ip address, I can't access rempotely, any solution.
>
> Also I added its names as "dhcppc3" in /etc/hosts files (ip address
> machine-name), also when I do "hostname" it shows different name, how
> can I name this machine as "tiger" so always I want the machine name as
> tiger (if I do "ping tiger" with LAN shoud work), how can I do that?.
> Thanks.
>

The solution is called Dynamic DNS. Google for it.

--

Tauno Voipio
tauno voipio (at) iki fi

You Can use a client for dynamic DNS called DynDNS (www.dyndns.com), or
NO-IP (no-ip.com). I believe that both clients have a linux version...
enjoy

GS wrote:

> Everytime when I boot (sometimes kids reboots) it gets new IP address,
> I did port mapping in the Router (any ssh requests to this Ip addr),
> when it changed Ip address, I can't access rempotely, any solution.

Configure your Linux box to use a static IP address within the router's LAN
subnet but outside its DHCP pool. Change your portmap to point to the
static IP address. For example, the default Linksys WRT54G DHCP pool is
192.168.1.100 to 192.168.1.149 so you are free to use 192.168.1.2 to
192.168.1.99 (and 150 to 254) for fixed IP addresses.


> Also I added its names as "dhcppc3" in /etc/hosts files (ip address
> machine-name), also when I do "hostname" it shows different name,

In Mandriva 2005LE, hostname is set in the file /etc/sysconfig/network

> how
> can I name this machine as "tiger" so always I want the machine name as
> tiger (if I do "ping tiger" with LAN shoud work), how can I do that?.

Populate the hosts file on each computer to map "tiger" to a specific IP
address (you'll need a static IP address as above) or install and configrue
nmbd to answer netbios requests for tiger on the network.
http://linuxreviews.org/man/nmbd/

Snowbat <(E-Mail Removed)> wrote:
>GS wrote:
>
>> Everytime when I boot (sometimes kids reboots) it gets new IP address,
>> I did port mapping in the Router (any ssh requests to this Ip addr),
>> when it changed Ip address, I can't access rempotely, any solution.
>
>Configure your Linux box to use a static IP address within the router's LAN
>subnet but outside its DHCP pool. Change your portmap to point to the
>static IP address. For example, the default Linksys WRT54G DHCP pool is
>192.168.1.100 to 192.168.1.149 so you are free to use 192.168.1.2 to
>192.168.1.99 (and 150 to 254) for fixed IP addresses.

With a Linksys WRT54G, that will be a problem! I'm not sure
what the Linksys is doing to accomplish this, but it will *not*
route to addresses outside the range that its DHCP server will
assign.

This can make for some real problems with static IP's. However,
on a small LAN it is very unlikely that the upper limit of the
pool will ever be reached... hence assigning the last few IPs
from the pool range is probably safe. It might be best to
configure the pool to have a larger range though, say 100
addresses.

If third party firmware (dd-wrt is highly recommended) is
installed in the Linksys, there are a large number of other
options available, such as assigning static IP addresses via the
DHCP server, which can be accomplished because there is command
line access to the WRT54G.

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) (E-Mail Removed)

Floyd L. Davidson wrote:

> Snowbat <(E-Mail Removed)> wrote:
>>For example, the default Linksys WRT54G DHCP pool is
>>192.168.1.100 to 192.168.1.149 so you are free to use 192.168.1.2 to
>>192.168.1.99 (and 150 to 254) for fixed IP addresses.
>
> With a Linksys WRT54G, that will be a problem! I'm not sure
> what the Linksys is doing to accomplish this, but it will not
> route to addresses outside the range that its DHCP server will
> assign.

This was certainly not a problem for my WRT54G running Linksys firmware
1.42.2 (until very recently the latest available for the ETSI model). My
WRT54G now runs Sveasoft Alchemy V1.0 and no problem there either.

Snowbat <(E-Mail Removed)> wrote:
>Floyd L. Davidson wrote:
>
>> Snowbat <(E-Mail Removed)> wrote:
>>>For example, the default Linksys WRT54G DHCP pool is
>>>192.168.1.100 to 192.168.1.149 so you are free to use 192.168.1.2 to
>>>192.168.1.99 (and 150 to 254) for fixed IP addresses.
>>
>> With a Linksys WRT54G, that will be a problem! I'm not sure
>> what the Linksys is doing to accomplish this, but it will not
>> route to addresses outside the range that its DHCP server will
>> assign.
>
>This was certainly not a problem for my WRT54G running Linksys firmware
>1.42.2 (until very recently the latest available for the ETSI model). My

The way this typically manifests itself is that you try to
connect to the HTTP server of a brand new WRT54G using a host
that has no interface with an IP address in the range served up
by the WRT54G's DHCP server. The interface lights blink, and it
is obvious that each command causes a significant amount of
traffic, but no response...

Until an interface on that host has an IP address which is
within the appropriate range, and then all works just fine.

Obviously if you just happen to be using an IP address within
that range, or if you get an IP address with DHCP, you'll never
notice it does that.

I have not checked the newer releases from Linksys, so I can't
be positive that they didn't change that. I think mine were all
back about firmware version 1.37 or some such.

>WRT54G now runs Sveasoft Alchemy V1.0 and no problem there either.

I don't recall ever checking to see if it does the same thing or
not.

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) (E-Mail Removed)