Topic: smeserver-openvpn-bridge update

[timn]

Before I start posting bugs, was this intended to be released with all the other updates this week? It removed my previous version of smeserver-openvpn-bridge-fws and is a significant change to the way it functions. There appears to be no documentation in the wiki, I had to install PHPKi manually and not as a dependency, and it doesn't seem to work 'out of the box'.

I did a yum update via putty on Friday night and it was included with all the other updates. Version is smeserver-openvpn-bridge.noarch 2.0-16.el4.sme. It wasn't in the list of updates shown by server-manager

[Franco]

I have tried it before and it didn't work for me. I went back to routing mode.

[soprom]

Although stuntshell had many problems with this contribs, I had good results so far.

This new version seems to be a big change. On my way to bug report...

The contribs ask for this:
db configuration setprop bridge status enabled

But "bridge" is not known.

[CharlieBrady]

I have tried it before and it didn't work for me.

Did you post a bug report?

[Franco]

Did you post a bug report?

No, they were still beta.
I think they still are

[soprom]

Bug 5060 has been added to the database

[soprom]

No, they were still beta.

I'm sure I updated from smecontribs and not smetests

[cactus]

I'm sure I updated from smecontribs and not smetests

I seriously doubt that AFAIK it is not in smeupdates (http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/smecontribs/i386/repodata/) nor have any packages have been pushed to SME Contribs since Jan 03.

Be sure to check you repository settings. Are you sure you did not accidentally have enabled smetest (temporarily)? What is the output of:

Code: [Select]

db yum_repositories getprop smetest status

[soprom]

Code: [Select]

[root@ca-fichiers ~]# db yum_repositories getprop smetest status
disabled

It is here:

Code: [Select]

http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/smecontribs/i386/RPMS/smeserver-openvpn-bridge-2.0-16.el4.sme.noarch.rpm
instead of smeserver-openvpn-bridge-fws-1.1-2.noarch.rpm
03-Mar-2009 17:19   54K

There was a name change
from smeserver-openvpn-bridge-fws
to     smeserver-openvpn-bridge

[CharlieBrady]

No, they were still beta.

What do you think 'beta' is for, if not for people to try and report any bugs they find?

[cactus]

What do you think 'beta' is for, if not for people to try and report any bugs they find?

AFAIK beta products do not belong in SME Contribs as it is, as stated by soprom. I guess some one pushed this package (too early).

[soprom]

stuntshell refered to a beta version.

Also:

The name change might be confusing since ther is an other openvpn contrib (for routing). This contrib is for bridging.

[soprom]

The rpm execute this script:

Code: [Select]

/sbin/e-smith/db configuration setprop [b]openvpn-bridge[/b] status disabled
sv d /service/openvpn-bridge
and it does not match the info on the server-manager:

Code: [Select]

db configuration setprop [b]bridge [/b]status enabled
/etc/init.d/bridge start
It appears the server-manager message is partly wrong.

I also installed "phpki" to manage to keys.

[Daniel B.]

Hi everyone.
The new version of the contrib smeserver-openvpn-bridge works, but the problem is that there are so many changes between the previous one and this one, that it cannot work just out of the box. In fact, the update has been pushed in smecontribs repo by error. The problem is now corrected and it has been remove from smecontribs to go in smetest repo so automatic upgrades won't causes problems. I just need some time to write the documentation and the upgrade procedure, as soon at it'll be ready, I'll move back the contrib to smecontribs repo.

Sorry for the inconveniance, just let me some time to write the documentation and you'll be able to use the latest and greatest version of the contrib.

Cheers, Daniel

[Franco]

What do you think 'beta' is for, if not for people to try and report any bugs they find?

Yes, and that's why I'm calling it beta, because it's not ready, And it's why it shouldn't be among the updates.