Unbound 1.3.0 or unbound 1.4.8 in latest pfSense 2.0-BETA5?

salvor

Is unbound version really 1.3.0? That is the version number shown in package manager.

If so, is there any chance of updating it to 1.4.8 before releasing pfSense 2.0 RC1?

Using the same machine for router/firewall and unbound 1.4.8 is important to me so I hope it gets included soon.

Thanks!

salvor

I guess the package manager's description of unbound needs to be updated. I found unbound.log and it says "1.4.8".

_igor_

Unbound is 1.4.8.
Package-version is 1.3.0

Hope that helps. :)

johnpoz

A simple query of currently installed unbound returns that its version 1.4.8

; <<>> DiG 9.7.2-P3 <<>> version.bind chaos txt
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28547
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;version.bind. CH TXT

;; ANSWER SECTION:
version.bind. 0 CH TXT "unbound 1.4.8"

;; Query time: 3 msec
;; SERVER: 192.168.1.253#53(192.168.1.253)
;; WHEN: Sat Feb 05 10:16:47 2011
;; MSG SIZE rcvd: 56

wagonza

@_igor_:

Unbound is 1.4.8.
Package-version is 1.3.0

Hope that helps. :)

100% correct - this is purely a package version id. I am not exactly sure how it go to 1.3.0 so quickly, I am sure I lost count somewhere.

jimp

It may help to lessen confusion if you use the unbound version combined with your own, such as:

"1.4.8 r1.3.0", or "1.4.8,130", or "1.4.8_130" - There are some other packages in the list that use similar version numbering.

wagonza

Good idea jimp - will change and revert.

wagonza

I have changed the version numbering to unbound version number_pkg version number for example 1.4.8_130. Thanks @jimp for the inspiration :)