Puppy lose connection? after request to renew? (Solved)

[disciple]

Hmmm.
Rather than killing dhcpcd then running it again, I think you should be able to use the -n option to force it to renew the lease.
And maybe I'm misunderstanding something, but I don't think there should be any need to run it at a certain interval - if you need to try reducing the lease time you should just run dhcpcd with the -l option.
http://www.digipedia.pl/man/doc/view/dhcpcd-bin.8.html

[nooby]

Thanks, I try to google swedish forums if they tell about this problem with out isp. The isp says they have no support for linux only Windows.

you could be right.

My wild guess is that it is a kind of acknowledge request. They want to assure that the computer is active and still wants to access their service or else they give the IP to somebody else or put it on hold until I ask for it in a proper way. that is how I get it. But could be wrong.

[gyro]

Hi,

"dhcpcd" should handle this automatically.

In Puppy 431, "dhcpcd" logs what it's doing to "/var/log/messages". So could someone who has a problem with "dhcpcd", please execute the following code at a console, after a problem has occurred,

Code: Select all

cat /var/log/messages | grep dhcpcd > /root/xx.txt

and then post the contents of "/root/xx.txt"

gyro

[nooby]

Hi Gyro!

Since February 2010 I have changed from Puppy 431 to Quirky 1.00 which have Simple Network Something and that one solved the problem for me.

But there exists puppy derivatives that don't make use of SNS set up.

[gyro]

Since February 2010 I have changed from Puppy 431 to Quirky 1.00 which have Simple Network Something and that one solved the problem for me.

I'm not convinced that it's SNS.
In all the puppies I have seen, there is a program called "dhcpcd" which has only 2 functions, to get an IP lease from a dhcp server and to keep on renewing that lease from the same dhcp server.

My conclusion is that the old version of dhcpcd in puppy 431, failed to renew the lease, but the much newer version of dhcpcd in Quirky did.
So I have attached a pet containing dhcpcd v5.1.5, compiled on puppy 431, (same version as in Quirky 1.2).

Perhaps someone might revert to their problem situation, install this pet and see if it fixes the problem.

gyro

[nooby]

I guess I should write solved to this one then.

Good that you think about us with this very unique situation.

I guess most users never have this problem. So much appreciated you did care about it.