alternative version isc-dhcp-server

[bart357]

I was wondering if there is a repo to get an alternative version of isc-dhcp-server

the current version is 4.2.2 and has a bug I believe that has been fixed in 4.2.3

if there is no repo with a more current version is there anything special that needs to be done to compile from source?

thanks

[bart357]

I tried to compile from source and it does not look liked it worked.
i tried
./configure
make
make install
I didnt see anything that looked like errors. but it did not install.

any ideas?
take care

[bamache]

I have had success with other packages by running
./configure --prefix=/usr
...
so that the target is placed in /usr/... rather than /usr/loacal/...
I try to find where the original is located and modify the --prefix= appropriately. Just a suggestion, YMMV.

I am currently working on getting OpenSSL and OpenSSH to here latest patch levels. It seems Raspian does not keep up with bugs or the patches to the bugs as much as Kubuntu-current 8^). Good Luck, and let us know how you get it to work out for you, please.?

I tried to compile from source and it does not look liked it worked.
i tried
./configure
make
make install
I didnt see anything that looked like errors. but it did not install.

any ideas?
take care

[rpdom]

It seems Raspian does not keep up with bugs or the patches to the bugs as much as Kubuntu-current 8^).

Of course it doesn't. Debian (and therefore Raspbian) has a well deserved reputation for stability.

That means that the software in the "Stable" version (currently "wheezy") will only be updated for critical bugs or security fixes.

If you want newer versions (and are prepared to risk a little breakage now and then) you use the "Testing" version (currently called "jessie") which is available for Raspbian. It has continuous updates on software that has already been through the "Unstable" version (always called "sid" but not available for Raspbian) for initial testing and is deemed stable enough to go to general testing until the next time the releases change (wheezy will become "Old Stable", jessie will become "Stable" and something else will become "Testing"). That could be a year or two away.

[bart357]

well for some reason I cant get it to install.
it doesn't seem like there is an error but there probably is something I am missing.
my week point is compiling and iptables. other than that i get around ok.

anyway isc-dhcp-server should update dns zone and that works fine.
after a lease expires it should remove the dns entry from the zone and that does not work.
you can remove it with nsupdate but it should happen automatically.
from ISC mail archives there is a bug in version 4.2.2 that prevents the removal of expired leases from dns and has been fixed in 4.2.3 and above.

I am also not sure where the testing repo is where I can grab a pre compiled deb file.

anyway
thanks for the help
take care

[rpdom]

I am also not sure where the testing repo is where I can grab a pre compiled deb file.

You can migrate to jessie/testing by changing all the raspbian lines in /etc/apt/sources.list to say jessie instead of wheezy. Then sudo apt-get update and then sudo apt-get dist-upgrade. Warning: This will update a lot of programs on your system including isc-dhcp-server (to version 4.2.4-7).

Only change the raspbian lines. Other Pi specific sources only have wheezy, but they will coexist quite happily.

[bart357]

thanks for the reply rpdom
is there a way to just grab isc-dhcp-server (to version 4.2.4-7) and install with "sudo dpkg -i package_file.deb"
I don't necessarily want to upgrade the whole os to testing.

on ubuntu or fedora you can just grab the file from testing but I don't see that with the pi.
I am still learning the diffrent layout of debian pi repos

here is a link to the isc mail list with my problem. https://lists.isc.org/pipermail/dhcp-us ... 15489.html

at the end of the thread it was recomended to upgrade to 4.2.3 or above.

anyway thanks for the help

take care

[rpdom]

The URL is http://mirrordirector.raspbian.org/rasp ... _armhf.deb

You can try and install it with dpkg -i but you may hit dependency problems. Try it and see. I can give you links to anything else it asks for.

There are ways to use apt-preferences to say "Install only from Stable(wheezy) unless I say otherwise", but I'd have to look at a few manpages and run a test or two to check how that works.

[ripat]

The Debian way to mix packages from two repo's is to use the pinning process which enables you to run packages from, say, testing while remaining in stable.

First you need to add the testing repo to your /etc/apt/source.list file:

Code: Select all

# Stable
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi

#Testing
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi

Then determine which version will get priority in a new file that you will name /etc/apt/preferences

Code: Select all

Package: *
Pin: release n=wheezy
Pin-Priority: 900

Package: *
Pin: release n=jessie
Pin-Priority: 800

Run apt-get update and try to first install isc-dhcp-seerver from testing using the stable dependencies:

Code: Select all

sudo apt-get install isc-dhcp-server/jessie

If apt complains that it can not install the newer version from jessie using the wheezy dependencies, you can use the other syntax:

Code: Select all

sudo apt-get -t jessie install isc-dhcp-server

For more information, google "apt-get pinning"

[bart357]

thanks so much ripat,
I have been able to install isc-dhcp-4.2.4 with no problems.
that is a real nice trick with pinning.
it looks like my problem has been fixed, I can see records being removed when a client is powered off.
I will have to spend some more time with it to make sure everything is working but so far everything looks good.
anyway my hats off to you sir, thanks so much for the help.
thank you as well rpdom, I need to learn the repos better with raspian.
take care

[bamache]

It seems Raspian does not keep up with bugs or the patches to the bugs as much as Kubuntu-current 8^).

Of course it doesn't. Debian (and therefore Raspbian) has a well deserved reputation for stability.

That means that the software in the "Stable" version (currently "wheezy") will only be updated for critical bugs or security fixes.

If you want newer versions (and are prepared to risk a little breakage now and then) you use the "Testing" version (currently called "jessie") which is available for Raspbian. It has continuous updates on software that has already been through the "Unstable" version (always called "sid" but not available for Raspbian) for initial testing and is deemed stable enough to go to general testing until the next time the releases change (wheezy will become "Old Stable", jessie will become "Stable" and something else will become "Testing"). That could be a year or two away.

I thought OpenSSH v6.5p1 / OpenSSL v1.0.1f are both security updates compared to what my wheezy is currently running?

wheezy Ubuntu Trusty Tahr (development branch)
Openssl OpenSSL 1.0.1e 11 Feb 2013 OpenSSL 1.0.1f 6 Jan 2014

OpenSSH OpenSSH_6.0p1 Debian-4 OpenSSH_6.5p1 Ubuntu-4

Please give me the link to jessie/sid for Raspberry Pi. Thank you for your help!

[ripat]

Please give me the link to jessie/sid for Raspberry Pi. Thank you for your help!

Please read the above post.
http://www.raspberrypi.org/phpBB3/viewt ... 56#p506856

FYI, in jessie, openssh version is 6.5

Code: Select all

$ sudo apt-cache policy openssh-client
openssh-client:
  Installé : 1:6.0p1-4
  Candidat : 1:6.0p1-4
 Table de version :
     1:6.5p1-4 0
        800 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
 *** 1:6.0p1-4 0
        900 http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages
        100 /var/lib/dpkg/status

[bamache]

Please give me the link to jessie/sid for Raspberry Pi. Thank you for your help!

Please read the above post.
http://www.raspberrypi.org/phpBB3/viewt ... 56#p506856

FYI, in jessie, openssh version is 6.5

Code: Select all

$ sudo apt-cache policy openssh-client
openssh-client:
  Installé : 1:6.0p1-4
  Candidat : 1:6.0p1-4
 Table de version :
     1:6.5p1-4 0
        800 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
 *** 1:6.0p1-4 0
        900 http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages
        100 /var/lib/dpkg/status

I want to go to an ALL jessie distro on my RPi. I am not knowledgeable in doing this, so please help. This is what I think I need to do:
1) Edit /etc/apt/source.list and populate it with:

#Testing
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi

2)Run $ sudo apt-get update
3)Run $ sudo apt-get upgrade
4)Run $ sudo apt-get dist-upgrade
5)Run $ sudo apt-get autoremove
Then reboot?
Is there an easier / better way. Is there a standard jessie-raspberry-Pi.img?
I saw on http://www.raspberrypi.org/forum/viewto ... 66&t=57783 but it looks scary, F2FS root filesystem that can not be resized...

Thanks again!

[rpdom]

The steps you list are the correct way to upgrade to Jessie.

Don't worry about F2FS, the partition type will not be changed unless you install from an image file (which overwrites everything).

Take a backup first, if possible.

I upgraded to jessie and didn't hit any problems.

[bamache]

I had success with my proposed steps! The only thing is SSH is still an old version:
$ ssh -V
$ OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1f 6 Jan 2014

I'll be working on that.

I wish to to thank all who read my questions and especially rpdom and others who answered and helped!

[rpdom]

I had success with my proposed steps! The only thing is SSH is still an old version:
$ ssh -V
$ OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1f 6 Jan 2014

I'll be working on that.

Strange. I get

Code: Select all

pi@raspi2 ~ $ ssh -V
OpenSSH_6.5p1 Raspbian-4, OpenSSL 1.0.1f 6 Jan 2014
pi@raspi2 ~ $ apt-cache show openssh-client | grep Version
Version: 1:6.5p1-4
pi@raspi2 ~ $ apt-cache policy openssh-client
openssh-client:
  Installed: 1:6.5p1-4
  Candidate: 1:6.5p1-4
  Version table:
 *** 1:6.5p1-4 0
        500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
        100 /var/lib/dpkg/status

What does your apt-cache policy openssh-client show?

[bamache]

I had success with my proposed steps! The only thing is SSH is still an old version:
$ ssh -V
$ OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1f 6 Jan 2014

I'll be working on that.

Strange. I get

Code: Select all

pi@raspi2 ~ $ ssh -V
OpenSSH_6.5p1 Raspbian-4, OpenSSL 1.0.1f 6 Jan 2014
pi@raspi2 ~ $ apt-cache show openssh-client | grep Version
Version: 1:6.5p1-4
pi@raspi2 ~ $ apt-cache policy openssh-client
openssh-client:
  Installed: 1:6.5p1-4
  Candidate: 1:6.5p1-4
  Version table:
 *** 1:6.5p1-4 0
        500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
        100 /var/lib/dpkg/status

What does your apt-cache policy openssh-client show?

Thanks for your post. I did this late last night, so I think mine showed:

Code: Select all

 $ apt-cache show openssh-client | grep Version
    OpenSSH_6.0p1
$ apt-cache policy openssh-client
openssh-client:
  Installed: 1:6.0p1-4
  Candidate: 1:6.5p1-4 
....Don't remember the Version Table entries.

When I saw this, I tried
$ sudo apt-get update
$ sudo apt-get upgrade
and
$ ssh -V yielded the same
OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1f 6 Jan 2014
So I tried:
$ sudo apt-get install ssh
And this? worked. It installed the new version, stopped and restarted the sshd daemon.
Now::
$ apt-cache policy openssh-client
openssh-client:
Installed: 1:6.5p1-4
Candidate: 1:6.5p1-4
Version table:
*** 1:6.5p1-4 0
500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
100 /var/lib/dpkg/status
Thank you again for your help!

[bamache]

I had success with my proposed steps! The only thing is SSH is still an old version:
$ ssh -V
$ OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1f 6 Jan 2014

I'll be working on that.

Strange. I get

Code: Select all

pi@raspi2 ~ $ ssh -V
OpenSSH_6.5p1 Raspbian-4, OpenSSL 1.0.1f 6 Jan 2014
pi@raspi2 ~ $ apt-cache show openssh-client | grep Version
Version: 1:6.5p1-4
pi@raspi2 ~ $ apt-cache policy openssh-client
openssh-client:
  Installed: 1:6.5p1-4
  Candidate: 1:6.5p1-4
  Version table:
 *** 1:6.5p1-4 0
        500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
        100 /var/lib/dpkg/status

What does your apt-cache policy openssh-client show?

This is an update of my procedure to update from Wheezy to 'Sid' on a Raspberry Pi.
Previously, I updated / upgraded my "development" R-Pi and saw errors and had to perform more commands to get the latest software that was supposed to have been auto-magically done for me. Well, after checking my code on the 'Sid' machine, I decided to go to 'Sid' on my Production node. I repeated the SAME steps and the results were better. I did get the correct versions of software and did not have trouble with anything else. I can not explain it?. Maybe experience or maybe I did the first upgrade the day of or the day after the kernel was compiled - so perhaps all the scripts were not sync'd with the mirror I used? People and their resources, when/where - ever they come from, from the Linux, et al. community continue to be first rate.That of course includes the Debian and Raspberry Pi. Thank you all !

[rpdom]

It is possible that apt-get upgrade didn't upgrade ssh due to dependencies added since the older version. apt-get upgrade will refuse to upgrade anything that requires extra software (not later versions of installed software) to be installed. It will usually say something like:

x packages will be upgrade. y packages held back.

In this case you need to do an apt-get dist-upgrade instead, which will install any required additional software.

As an example, say you have package "fred" version 1.00 installed, which requires "jim" V2.3. When you did "install fred" it will also install "jim".

If "fred" gets upgraded to version 1.5 and requires "jim" 9.9, that is fine and it will get upgraded as there are already versions of fred and jim installed.

But, if fred 1.6 requires jim 9.9 and additionally sheila 0.1, it won't get upgraded because there is no version of sheila currently on the system.

An apt-get dist-upgrade will upgrade fred to 1.6, jim to 9.9 and install sheila 0.1 at the same time.

apt-get install fred will just go and install/upgrade as required because you have told it "I want the current fred installed (and any software it requires to work as well)".