Re: [SOLVED]dhclient renewal

2012-01-10 Thread Camaleón
On Mon, 09 Jan 2012 08:10:49 -0600, hvw59601 wrote:

 hvw59601 wrote:
 hvw59601 wrote:
 hvw59601 wrote:
 Camaleón wrote:
 
 snip

 And there you see IMO where those renewals of 57 secs. come from:
 '[renewtime] = 60'
 Now I have to find a way to change that :-)


 But whenever I try to change that value of '60', I get:
 
 Error : Unable to configure LAN_private
 
 Any hints?
 
 
 I found this:
 http://www.o2help.co.uk/router-change-dns/
 
 and so:
 
 {TELMEX}=dhcp server config state=disabled 
 {TELMEX}=dhcp server lease flush
 {TELMEX}=dhcp server pool config name=LAN_private renewtime=86400
 {TELMEX}=dhcp server config state=enabled {TELMEX}=saveall
 {TELMEX}=exit
 Connection closed by foreign host.
 
 and in syslog:
 
 Jan  9 07:41:55 HDBB dhclient: DHCPREQUEST on eth0 to 192.168.1.254 port 67 
 Jan  9 07:41:56 HDBB dhclient: DHCPACK from 192.168.1.254  
 Jan  9 07:41:56 HDBB dhclient: bound to 192.168.1.190 -- renewal in 56700 
 seconds.
 
 Camaleón thanks a lot for all your help! Great job!

Wohooo!! Glad you could finally solve this. 

Congrats, you did it all by your own ;-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jehn6i$r4p$7...@dough.gmane.org



Re: [SOLVED]dhclient renewal

2012-01-09 Thread hvw59601

hvw59601 wrote:

hvw59601 wrote:

hvw59601 wrote:

Camaleón wrote:


snip


And there you see IMO where those renewals of 57 secs. come from: 
'[renewtime] = 60'

Now I have to find a way to change that :-)



But whenever I try to change that value of '60', I get:

Error : Unable to configure LAN_private

Any hints?



I found this:
http://www.o2help.co.uk/router-change-dns/

and so:

{TELMEX}=dhcp server config state=disabled
{TELMEX}=dhcp server lease flush
{TELMEX}=dhcp server pool config name=LAN_private renewtime=86400
{TELMEX}=dhcp server config state=enabled
{TELMEX}=saveall
{TELMEX}=exit
Connection closed by foreign host.

and in syslog:

Jan  9 07:41:55 HDBB dhclient: DHCPREQUEST on eth0 to 192.168.1.254 port 67
Jan  9 07:41:56 HDBB dhclient: DHCPACK from 192.168.1.254
Jan  9 07:41:56 HDBB dhclient: bound to 192.168.1.190 -- renewal in 
56700 seconds.


Camaleón thanks a lot for all your help! Great job!

Hugo



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jeesha$9cd$1...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread Camaleón
On Sat, 07 Jan 2012 12:57:34 -0600, hvw59601 wrote:

 Camaleón wrote:

(...)

 Mmm, since when 192.168.1.x is an external IP? :-)
 
 
 No, that is internal. My external IP is changed every hour or so:
 
 Jan  7 09:18:41 HDBB ddclient[1730]: SUCCESS:  updating 
 esquipulas-index.dyndns.org: good: IP address set to 189.188.156.182 
 Jan  7 09:44:10 HDBB ddclient[1730]: SUCCESS:  updating 
 esquipulas-index.dyndns.org: good: IP address set to 189.188.159.254 
 Jan  7 10:59:15 HDBB ddclient[1730]: SUCCESS:  updating 
 esquipulas-index.dyndns.org: good: IP address set to 187.136.115.174 
 Jan  7 11:54:28 HDBB ddclient[1730]: SUCCESS:  updating 
 esquipulas-index.dyndns.org: good: IP address set to 187.136.114.47

Mmm, you're using DynDNS...

 Since I got on around 8AM, it is now 1PM, 5 hours, 4 changes.

But the external IP your ISP assigns to the WAN interface of your 
router has nothing to do with the internal IP your routers assings to 
the 4 LAN ports (you) :-)

Anyway, query your ISP about this because is not normal (at least not for 
my provider) to have the remote IP changing every hour :-?

 Your dhcp server (the router) is configured right (it keeps the lease
 for almost one day), so maybe is your dhcp client which requests for a
 lease? Look at /etc/dhcp/dhcpclient.conf file and search for any
 lease stanza. If it is commented, edit accordingly to enable you can
 define there your client settings.
 
 
 That's all commented out. Let me play with it. My feeling is that the
 short lease times for both devices have to do with the external IP
 changes.

It should not be related at all. Look, my external IP remains the same 
even when I power cycle the router, but the local DHCP lease is set to be 
renewed every 9 hours.

I would try by enforcing the local lease time renew from the client side 
(i.e., your debian computer).

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jebu87$tvi$2...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread Camaleón
On Sat, 07 Jan 2012 17:25:42 -0600, hvw59601 wrote:

(...)

 That's all commented out. Let me play with it. My feeling is that the
 short lease times for both devices have to do with the external IP
 changes.


 And also the changes in leasetime occurred when the router changed, so
 IMO it is hardware related :-)
 
 
 Have no idea of how to get rid of the 57 sec. renewals.

Did you configure your dhclient to request a lease every 12 hours?

 Configured the TG585V8 with the only configurable item: Always use the
 same IP address set to yes that sets DHCP Lease Time: Infinite:
 http://debian-oaxaca.blogspot.com/2012/01/blog-post.html

That options (use the same IP) is not available for me. Have you tried 
to disable?

 Then I did a new install of the Wheezy netinst.iso of today (Jan.7,
 2012). Did not install any software, did not change anything, just the
 base installation. Result: lease renewal every 56 secs. Weird.

Yup, it's not normal. But it can be a bug in the router's firmware that 
makes it to behave weirldy. To start discarding culprits, I would try 
with another DHCP server, if you have another device than can be 
configured in that way.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jebv2b$tvi$3...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread hvw59601

Camaleón wrote:

On Sat, 07 Jan 2012 17:25:42 -0600, hvw59601 wrote:

(...)


That's all commented out. Let me play with it. My feeling is that the
short lease times for both devices have to do with the external IP
changes.



And also the changes in leasetime occurred when the router changed, so
IMO it is hardware related :-)



Have no idea of how to get rid of the 57 sec. renewals.


Did you configure your dhclient to request a lease every 12 hours?



I set /etc/dhcp/dhcp.conf (on Jan. 08 09:20) to:

lease {
  interface eth0;
  fixed-address 192.168.1.190;
  option subnet-mask 255.255.255.0;
  option dhcp-lease-time 86400;
  option routers 192.168.1.254;
  option dhcp-message-type 5;
  option dhcp-server-identifier 192.168.1.254;
  option domain-name-servers 192.168.1.254;
  option dhcp-renewal-time 43200;
  option domain-name lan;
  renew 6 2012/01/08 22:53:20;
  rebind 6 2012/01/08 22:53:20;
  expire 6 2012/01/08 22:53:20;
}

Makes no diff. whatsoever.




Configured the TG585V8 with the only configurable item: Always use the
same IP address set to yes that sets DHCP Lease Time:   Infinite:
http://debian-oaxaca.blogspot.com/2012/01/blog-post.html


That options (use the same IP) is not available for me. Have you tried 
to disable?




Default is disabled. Makes no diff. whatsoever.


Then I did a new install of the Wheezy netinst.iso of today (Jan.7,
2012). Did not install any software, did not change anything, just the
base installation. Result: lease renewal every 56 secs. Weird.


Yup, it's not normal. But it can be a bug in the router's firmware that 
makes it to behave weirldy. To start discarding culprits, I would try 
with another DHCP server, if you have another device than can be 
configured in that way.




Where does one get another DHCP server?

Hugo



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jeccp9$84v$1...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread Camaleón
On Sun, 08 Jan 2012 09:29:44 -0600, hvw59601 wrote:

 Camaleón wrote:

 Did you configure your dhclient to request a lease every 12 hours?
 
 
 I set /etc/dhcp/dhcp.conf (on Jan. 08 09:20) to:
 
 lease {
interface eth0;
fixed-address 192.168.1.190;
option subnet-mask 255.255.255.0;
option dhcp-lease-time 86400;
option routers 192.168.1.254;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.1.254; 
option domain-name-servers 192.168.1.254; 
option dhcp-renewal-time 43200;
option domain-name lan;
renew 6 2012/01/08 22:53:20;
rebind 6 2012/01/08 22:53:20;
expire 6 2012/01/08 22:53:20;
 }
 
 Makes no diff. whatsoever.

(...)

My bad. 

It was not the lease stanza what you had to edit. I overlooked the 
dhclient.conf file but man dhclient.conf confirmed the lease is used 
when the client cannot connect to an existing DHCP server, which is not 
your case :-)

And from man page I can't see an option which you can configure from the 
client side to define a renewal interval... hum.

 Yup, it's not normal. But it can be a bug in the router's firmware that
 makes it to behave weirldy. To start discarding culprits, I would try
 with another DHCP server, if you have another device than can be
 configured in that way.
 
 
 Where does one get another DHCP server?

I usually have several devices that can act as DHCP servers but well, if 
you only have a router available you can install a DHCP server (or run a 
LiveCD with DHCP server configured) in a separate computer... unless you 
only have one computer in such case no DHCP server is needed at all :-P

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jech3c$tvi$1...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread Camaleón
On Sun, 08 Jan 2012 16:43:24 +, Camaleón wrote:

(...)

 And from man page I can't see an option which you can configure from the
 client side to define a renewal interval... hum.

Hugo... let's go debugging.

Open a console and type: 

telnet 192.168.0.190
username: 1234 (type yours)
password:  (type yours)

Then type:

dhcp server lease list ↵

And see what's the current TTL (Time To Live) value for the current 
assigned lease (it should be 24 hours minus the time of the last renewal 
request from client).

From here (telnet) you can also configure the router's LAN DHCP settings:

dhcp server pool list (to display the current pool's name)
dhcp server pool config (to configure the pool)

(I remember I had to specifically use the telnet interface for setting up 
one feature of the DHCP server which did not stick when it was configured 
using the web interface)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jecmi6$tvi$1...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread hvw59601

Camaleón wrote:
 On Sun, 08 Jan 2012 16:43:24 +, Camaleón wrote:

 (...)

 And from man page I can't see an option which you can configure from the
 client side to define a renewal interval... hum.

 Hugo... let's go debugging.

 Open a console and type:

 telnet 192.168.0.190
 username: 1234 (type yours)
 password:  (type yours)

 Then type:

 dhcp server lease list ?



 __  Thomson TG585 v8
 ___/_/\
/ /\\  8.6.E.9
  _/__   /  \\
_/   /\_/___ \  Copyright (c) 1999-2010, THOMSON
   //   /  \   /\ \
   ___//___/\ / _\/__
  /  / \   \// //\
   __/  /   \   \  // // _\__
  / /  / \___\// // /   /\
 /_/__/___/ // /___/  \
 \ \  \___\ \\ \   \  /
  \_\  \  /  /\\ \\ \___\/
 \  \/  /  \\ \\  /
  \_/  /\\ \\/
   /__/  \\  /
   \   _  \  /_\/
\ //\  \/___\/
 //  \  \  /
 \\  /___\/ //  \  \  /
 \\  /___\/
  \\/


_{TELMEX}=dhcp server lease list
LeasePoolTTL   State Clientid
0  192.168.1.190 LAN_private 23:59:23  USED  [01] 
e0:cb:4e:ce:bd:8e

{TELMEX}=


 And see what's the current TTL (Time To Live) value for the current
 assigned lease (it should be 24 hours minus the time of the last renewal
 request from client).

From here (telnet) you can also configure the router's LAN DHCP settings:

 dhcp server pool list (to display the current pool's name)

{TELMEX}=dhcp server pool list
Pool   Address Range Intf   Admin  Alloc   State
0  LAN_private 192.168.1.[64-253]LocalNetwork up dynamic static
{TELMEX}=

 dhcp server pool config (to configure the pool)

{TELMEX}=dhcp server pool config
name = LAN_private
[state] = enabled
[allocation] = dynamic
[intf] = LocalNetwork
[index] =
[poolstart] = 192.168.1.64
[poolend] = 192.168.1.253
[netmask] = 24
[gateway] = 192.168.1.254
[server] = 192.168.1.254
[primdns] =
[secdns] =
[dnsmetric] = 0
[primwins] =
[secwins] =
[primwins] =
[secwins] =
[leasetime] = 864000
[renewtime] = 6000
[rebindtime] = 6000
[unnumbered] = disabled
[localgw] = disabled
[localdns] = enabled
:dhcp server pool config name=LAN_private leasetime=864000 
renewtime=6000 rebindtime=6000

Error : Unable to configure LAN_private



 (I remember I had to specifically use the telnet interface for setting up
 one feature of the DHCP server which did not stick when it was configured
 using the web interface)


Going further I discovered a menu interface and froze the whole thing up 
so that I had to do a hardware reset to the box.


What specifically am I trying to reconfigure in that pool?

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jed020$3j4$1...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread hvw59601

hvw59601 wrote:

Camaleón wrote:
  On Sun, 08 Jan 2012 16:43:24 +, Camaleón wrote:
 
  (...)
 
  And from man page I can't see an option which you can configure from 
the

  client side to define a renewal interval... hum.
 
  Hugo... let's go debugging.
 
  Open a console and type:
 
  telnet 192.168.0.190
  username: 1234 (type yours)
  password:  (type yours)
 
  Then type:
 
  dhcp server lease list ?



 __  Thomson TG585 v8
 ___/_/\
/ /\\  8.6.E.9
  _/__   /  \\
_/   /\_/___ \  Copyright (c) 1999-2010, THOMSON
   //   /  \   /\ \
   ___//___/\ / _\/__
  /  / \   \// //\
   __/  /   \   \  // // _\__
  / /  / \___\// // /   /\
 /_/__/___/ // /___/  \
 \ \  \___\ \\ \   \  /
  \_\  \  /  /\\ \\ \___\/
 \  \/  /  \\ \\  /
  \_/  /\\ \\/
   /__/  \\  /
   \   _  \  /_\/
\ //\  \/___\/
 //  \  \  /
 \\  /___\/ //  \  \  /
 \\  /___\/
  \\/


_{TELMEX}=dhcp server lease list
LeasePoolTTL   State Clientid
0  192.168.1.190 LAN_private 23:59:23  USED  [01] 
e0:cb:4e:ce:bd:8e

{TELMEX}=

 
  And see what's the current TTL (Time To Live) value for the current
  assigned lease (it should be 24 hours minus the time of the last renewal
  request from client).
 
 From here (telnet) you can also configure the router's LAN DHCP 
settings:

 
  dhcp server pool list (to display the current pool's name)

{TELMEX}=dhcp server pool list
Pool   Address Range Intf   Admin  Alloc   State
0  LAN_private 192.168.1.[64-253]LocalNetwork up dynamic static
{TELMEX}=

  dhcp server pool config (to configure the pool)

{TELMEX}=dhcp server pool config
name = LAN_private
[state] = enabled
[allocation] = dynamic
[intf] = LocalNetwork
[index] =
[poolstart] = 192.168.1.64
[poolend] = 192.168.1.253
[netmask] = 24
[gateway] = 192.168.1.254
[server] = 192.168.1.254
[primdns] =
[secdns] =
[dnsmetric] = 0
[primwins] =
[secwins] =
[primwins] =
[secwins] =
[leasetime] = 864000
[renewtime] = 6000
[rebindtime] = 6000
[unnumbered] = disabled
[localgw] = disabled
[localdns] = enabled
:dhcp server pool config name=LAN_private leasetime=864000 
renewtime=6000 rebindtime=6000

Error : Unable to configure LAN_private




snip

I did not quite show that right: this is what 'dhcp server pool config' 
looks like:


_{TELMEX}=dhcp server pool config
name = LAN_private
[state] = enabled
[allocation] = dynamic
[intf] = LocalNetwork
[index] =
[poolstart] = 192.168.1.64
[poolend] = 192.168.1.253
[netmask] = 24
[gateway] = 192.168.1.254
[server] = 192.168.1.254
[primdns] =
[secdns] =
[dnsmetric] = 0
[primwins] =
[secwins] =
[leasetime] = 86400
[renewtime] = 60
[rebindtime] =
[unnumbered] = disabled
[localgw] = disabled
[localdns] = enabled
:dhcp server pool config name=LAN_private
{TELMEX}=

And there you see IMO where those renewals of 57 secs. come from: 
'[renewtime] = 60'

Now I have to find a way to change that :-)

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jeddn5$kal$1...@dough.gmane.org



Re: dhclient renewal

2012-01-08 Thread hvw59601

hvw59601 wrote:

hvw59601 wrote:

Camaleón wrote:


snip


And there you see IMO where those renewals of 57 secs. come from: 
'[renewtime] = 60'

Now I have to find a way to change that :-)



But whenever I try to change that value of '60', I get:

Error : Unable to configure LAN_private

Any hints?

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jedf8h$rik$1...@dough.gmane.org



dhclient renewal

2012-01-07 Thread hvw59601

Hi,

The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so 
they gave a new one. It's a Thomson TG585V8.


One thing that I noticed is that the external IP now changes about every 
hour or so, when the internet goes offline and after a minute or so 
comes online again.


The other thing is now I see:

Jan 7 10:09:08 HDBB dhclient: bound to 192.168.1.190—renewal in 55 seconds.

While previously I saw:

Dec 31 08:01:13 HDBB dhclient: bound to 192.168.1.190—renewal in 40438 
seconds.


Why the difference?

That router has 2 systems connected to it, both with ethernet cable, a 
laptop running Squeeze and a desktop running Sid.


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/je9rbe$94j$1...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread Camaleón
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:

 The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so
 they gave a new one. It's a Thomson TG585V8.

Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)

 One thing that I noticed is that the external IP now changes about every
 hour or so, when the internet goes offline and after a minute or so
 comes online again.

External (routeable) or internal (local network) IP?
 
 The other thing is now I see:
 
 Jan 7 10:09:08 HDBB dhclient: bound to 192.168.1.190—renewal in 55
 seconds.
 
 While previously I saw:
 
 Dec 31 08:01:13 HDBB dhclient: bound to 192.168.1.190—renewal in 40438
 seconds.
 
 Why the difference?

(...)

Maybe the time for the leasing has decreased with the new device, but I 
guess this can be tweakable from the router's web interface (or by means 
of telnet) :-?

Look, this is from the router's configuration page:

***
Home  Home Network  Interfaces  LocalNetwork [ Configure ]

DHCP Lease Time:1 day, 0:00:00
***

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2012.01.07.17.07...@gmail.com



Re: dhclient renewal

2012-01-07 Thread hvw59601

Camaleón wrote:

On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:


The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so
they gave a new one. It's a Thomson TG585V8.


Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)


One thing that I noticed is that the external IP now changes about every
hour or so, when the internet goes offline and after a minute or so
comes online again.


External (routeable) or internal (local network) IP?
 


External IP



The other thing is now I see:

Jan 7 10:09:08 HDBB dhclient: bound to 192.168.1.190—renewal in 55
seconds.

While previously I saw:

Dec 31 08:01:13 HDBB dhclient: bound to 192.168.1.190—renewal in 40438
seconds.

Why the difference?


(...)

Maybe the time for the leasing has decreased with the new device, but I 
guess this can be tweakable from the router's web interface (or by means 
of telnet) :-?


Look, this is from the router's configuration page:

***
Home  Home Network  Interfaces  LocalNetwork [ Configure ]

DHCP Lease Time:1 day, 0:00:00
***



I see this:

DHCP Lease Time:0 days, 23:59:49

but it is not configurable. And then I still see in syslog:

Jan  7 12:10:48 HDBB dhclient: bound to 192.168.1.190 -- renewal in 59 
seconds.


Hugo



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jea1t9$itl$1...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread hvw59601

hvw59601 wrote:

Camaleón wrote:

On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:


The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so
they gave a new one. It's a Thomson TG585V8.


Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)


One thing that I noticed is that the external IP now changes about every
hour or so, when the internet goes offline and after a minute or so
comes online again.


External (routeable) or internal (local network) IP?
 


External IP



The other thing is now I see:

Jan 7 10:09:08 HDBB dhclient: bound to 192.168.1.190—renewal in 55
seconds.

While previously I saw:

Dec 31 08:01:13 HDBB dhclient: bound to 192.168.1.190—renewal in 40438
seconds.

Why the difference?


(...)

Maybe the time for the leasing has decreased with the new device, but 
I guess this can be tweakable from the router's web interface (or by 
means of telnet) :-?


Look, this is from the router's configuration page:

***
Home  Home Network  Interfaces  LocalNetwork [ Configure ]

DHCP Lease Time:1 day, 0:00:00
***



I see this:

DHCP Lease Time:0 days, 23:59:49

but it is not configurable. And then I still see in syslog:



I take that back, it *is* configurable, but 23 hours is fine with me, 1 
minute is not. Change it to 12 hours maybe? Would I mess things up? I 
hate to talk to Telmex because then you have to hide the fact that you 
are running Linux and pretend you are Window$ :-(


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jea2hu$luo$1...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread Camaleón
On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:

 hvw59601 wrote:
 Camaleón wrote:
 On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:

 The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink
 so they gave a new one. It's a Thomson TG585V8.

 Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)

 One thing that I noticed is that the external IP now changes about
 every hour or so, when the internet goes offline and after a minute
 or so comes online again.

 External (routeable) or internal (local network) IP?
  
  
 External IP

Mmm, since when 192.168.1.x is an external IP? :-)

(...)

 I see this:
 
 DHCP Lease Time:0 days, 23:59:49
 
 but it is not configurable. And then I still see in syslog:
 
 
 I take that back, it *is* configurable, 

Sure it is, rembember that I'm seeing the same as you :-P

 but 23 hours is fine with me, 1 minute is not. 

Let me check my logs... okay, my dhcp client renews the lease every 9 
hours although I also have a 24 hours setup in the router. Weird.

 Change it to 12 hours maybe? Would I mess things up? I hate to talk to
 Telmex because then you have to hide the fact that you are running
 Linux and pretend you are Window$ :-(

Your dhcp server (the router) is configured right (it keeps the lease for 
almost one day), so maybe is your dhcp client which requests for a lease? 
Look at /etc/dhcp/dhcpclient.conf file and search for any lease 
stanza. If it is commented, edit accordingly to enable you can define 
there your client settings.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jea3r4$aqv$1...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread hvw59601

Camaleón wrote:

On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:


hvw59601 wrote:

Camaleón wrote:

On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:


The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink
so they gave a new one. It's a Thomson TG585V8.

Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)


One thing that I noticed is that the external IP now changes about
every hour or so, when the internet goes offline and after a minute
or so comes online again.

External (routeable) or internal (local network) IP?
 
 

External IP


Mmm, since when 192.168.1.x is an external IP? :-)



No, that is internal. My external IP is changed every hour or so:

Jan  7 09:18:41 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 189.188.156.182
Jan  7 09:44:10 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 189.188.159.254
Jan  7 10:59:15 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 187.136.115.174
Jan  7 11:54:28 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 187.136.114.47


Since I got on around 8AM, it is now 1PM, 5 hours, 4 changes.





I see this:

DHCP Lease Time:0 days, 23:59:49

but it is not configurable. And then I still see in syslog:


I take that back, it *is* configurable, 


Sure it is, rembember that I'm seeing the same as you :-P

but 23 hours is fine with me, 1 minute is not. 


Let me check my logs... okay, my dhcp client renews the lease every 9 
hours although I also have a 24 hours setup in the router. Weird.



Change it to 12 hours maybe? Would I mess things up? I hate to talk to
Telmex because then you have to hide the fact that you are running
Linux and pretend you are Window$ :-(


Your dhcp server (the router) is configured right (it keeps the lease for 
almost one day), so maybe is your dhcp client which requests for a lease? 
Look at /etc/dhcp/dhcpclient.conf file and search for any lease 
stanza. If it is commented, edit accordingly to enable you can define 
there your client settings.




That's all commented out. Let me play with it. My feeling is that the 
short lease times for both devices have to do with the external IP changes.


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jea4iu$3lu$1...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread hvw59601

hvw59601 wrote:

Camaleón wrote:

On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:


hvw59601 wrote:

Camaleón wrote:

On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:


The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink
so they gave a new one. It's a Thomson TG585V8.

Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)


One thing that I noticed is that the external IP now changes about
every hour or so, when the internet goes offline and after a minute
or so comes online again.

External (routeable) or internal (local network) IP?
 
 

External IP


Mmm, since when 192.168.1.x is an external IP? :-)



No, that is internal. My external IP is changed every hour or so:

Jan  7 09:18:41 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 189.188.156.182
Jan  7 09:44:10 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 189.188.159.254
Jan  7 10:59:15 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 187.136.115.174
Jan  7 11:54:28 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 187.136.114.47


Since I got on around 8AM, it is now 1PM, 5 hours, 4 changes.





I see this:

DHCP Lease Time:0 days, 23:59:49

but it is not configurable. And then I still see in syslog:


I take that back, it *is* configurable, 


Sure it is, rembember that I'm seeing the same as you :-P

but 23 hours is fine with me, 1 minute is not. 


Let me check my logs... okay, my dhcp client renews the lease every 9 
hours although I also have a 24 hours setup in the router. Weird.



Change it to 12 hours maybe? Would I mess things up? I hate to talk to
Telmex because then you have to hide the fact that you are running
Linux and pretend you are Window$ :-(


Your dhcp server (the router) is configured right (it keeps the lease 
for almost one day), so maybe is your dhcp client which requests for a 
lease? Look at /etc/dhcp/dhcpclient.conf file and search for any 
lease stanza. If it is commented, edit accordingly to enable you can 
define there your client settings.




That's all commented out. Let me play with it. My feeling is that the 
short lease times for both devices have to do with the external IP changes.




And also the changes in leasetime occurred when the router changed, so 
IMO it is hardware related :-)


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jea4o4$3lu$2...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread hvw59601

hvw59601 wrote:

hvw59601 wrote:

Camaleón wrote:

On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:


hvw59601 wrote:

Camaleón wrote:

On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:

The 2wire router from ISP Telmex Infinitum (Mexico) went on the 
blink

so they gave a new one. It's a Thomson TG585V8.

Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)


One thing that I noticed is that the external IP now changes about
every hour or so, when the internet goes offline and after a minute
or so comes online again.

External (routeable) or internal (local network) IP?
 
 

External IP


Mmm, since when 192.168.1.x is an external IP? :-)



No, that is internal. My external IP is changed every hour or so:

Jan  7 09:18:41 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 189.188.156.182
Jan  7 09:44:10 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 189.188.159.254
Jan  7 10:59:15 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 187.136.115.174
Jan  7 11:54:28 HDBB ddclient[1730]: SUCCESS:  updating 
esquipulas-index.dyndns.org: good: IP address set to 187.136.114.47


Since I got on around 8AM, it is now 1PM, 5 hours, 4 changes.





I see this:

DHCP Lease Time:0 days, 23:59:49

but it is not configurable. And then I still see in syslog:


I take that back, it *is* configurable, 


Sure it is, rembember that I'm seeing the same as you :-P

but 23 hours is fine with me, 1 minute is not. 


Let me check my logs... okay, my dhcp client renews the lease every 9 
hours although I also have a 24 hours setup in the router. Weird.



Change it to 12 hours maybe? Would I mess things up? I hate to talk to
Telmex because then you have to hide the fact that you are running
Linux and pretend you are Window$ :-(


Your dhcp server (the router) is configured right (it keeps the lease 
for almost one day), so maybe is your dhcp client which requests for 
a lease? Look at /etc/dhcp/dhcpclient.conf file and search for any 
lease stanza. If it is commented, edit accordingly to enable you 
can define there your client settings.




That's all commented out. Let me play with it. My feeling is that the 
short lease times for both devices have to do with the external IP 
changes.




And also the changes in leasetime occurred when the router changed, so 
IMO it is hardware related :-)




Have no idea of how to get rid of the 57 sec. renewals.

Configured the TG585V8 with the only configurable item: Always use the 
same IP address set to yes that sets DHCP Lease Time:	Infinite:

http://debian-oaxaca.blogspot.com/2012/01/blog-post.html

Then I did a new install of the Wheezy netinst.iso of today (Jan.7, 
2012). Did not install any software, did not change anything, just the 
base installation. Result: lease renewal every 56 secs. Weird.


Hugo













--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jeak9n$v8c$1...@dough.gmane.org



Re: dhclient renewal

2012-01-07 Thread Bob Proulx
Please trim your postings to just the parts you are referring to.
Your quoted parts are waaay tooo large.   Thank you.

hvw59601 wrote:
 hvw59601 wrote:
 hvw59601 wrote:
 Since I got on around 8AM, it is now 1PM, 5 hours, 4 changes.

That is a lot of chagnes.  An unusually large number.

 I take that back, it *is* configurable,
 Change it to 12 hours maybe? Would I mess things up? I hate to talk to
 Telmex because then you have to hide the fact that you are running
 Linux and pretend you are Window$ :-(

12 hours would be fine.  A full day is typical.  It depends upon the
use model.  A coffee shop with a lot of transients needs shorter
times.  A home system with a stable set of machines can use a much
longer time.  Longer times are more robust against temporary network
outages.

 My feeling is that the short lease times for both devices have to
 do with the external IP changes.

External IP address changes should have no effect on your internal
client dhcp leases.  They are unrelated in any sane setup.

 And also the changes in leasetime occurred when the router
 changed, so IMO it is hardware related :-)

Your router box may be too crazy to use.  :-(

 Have no idea of how to get rid of the 57 sec. renewals.

That is way too short!  Crazy too short.

 Configured the TG585V8 with the only configurable item: Always use
 the same IP address set to yes that sets DHCP Lease
 Time: Infinite:
 http://debian-oaxaca.blogspot.com/2012/01/blog-post.html

That does seem like it should give your internal LAN devices the same
IP address each and every time and good forever.

That should have no effect on your router getting a new address often
from the external WAN dhcp server.  That would be completely separate
and unrelated.

 Then I did a new install of the Wheezy netinst.iso of today (Jan.7,
 2012). Did not install any software, did not change anything, just
 the base installation. Result: lease renewal every 56 secs. Weird.

The new install of Wheezy will be unrelated to what your router
allocated for dhcp on the internal LAN.  They are not related.  Your
Wheezy install will ask your dhcp server for an address and it will be
assigned one along with a lease time.  It can only work with what it
has been given.  If your router is crazy then there isn't anything
that a Wheezy system, or any other, can do about it.

I would be inclined to look for a firmware upgrade for the router.
And then try to reset the state back to a default factory setting.
Then start again on changing the configuration.  It really sounds like
something is wrong with the software on that router.

Bob


signature.asc
Description: Digital signature