Hi to everybody,
I am trying to install shrew software in OpenSuse 11.3.
So , i do cmake … and finished correctly , but when i do make i got the following error:
uic: File generated with too old version of Qt Designer (3.3)
I checked the repositories and i got the lowest version of qt available : qt3
So can someone tell me how can i get an older version of qt ?
Thanks in advanced
Alejorosado wrote:
> uic: File generated with too old version of Qt Designer (3.3)
it says the 3.3 you have is too old…so, don’t look for older, look
for newer, like maybe 3.4 or 4.1 or or or…
i’ve not done it, but i have to guess that the source for shrew
includes a README file (or something somewhere in the documentation
must) tells you the requirements for the package…
once you know the level qt you can use (it must be newer than 3.3)
then you can install that dependency using YaST and hopefully proceed
to happiness…
–
DenverD
When it comes to chocolate, resistance is futile.
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
I kind of read it in the other way …
I will keep fighting to get it working , at least now i go in the right direction …
Thank you DenverD .
Alejorosado wrote:
> Thank you DenverD .
welcome…
say, i’ve not had need for a VPN client, but as i looked at your
problem i was struck by the fact that Shrew is not in the repos, and
has had very little discussion in these fora (http://goo.gl/yXsN)
i don’t know why you want to use Shrew (maybe because you are familiar
with it from using it in another operating system) but you might find
it easier (and better) to give a “native” Linux VPN client a go…you
might find it easier to install/use…
–
DenverD
When it comes to chocolate, resistance is futile.
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
I too read it, that the project’s code is generated by a too old version of Qt designer. You may need a full KDE3 development environment to be installled.
But…then you would create a program for KDE3…
Hi DenverD and Knurpht ,
thank you so much for your interest and answers , as for why i wanna use shrew ? because i work with several firewall in which i tested the shrew client and it works perfectly (for exemple the usg series of zyxel).
I never tried using a Linux vpn client, but as soon i will have a free time i want to try it , and if the i get it working fine i would use it for sure.
I will also try compiling shrew with a kde enviorment …
As i said thank you for your help … i will write any progress in this topic .
Alejandro
If we are talking about this here
(which is just a guess as the OP didn’t think it would be a good idea actually giving this important information what he is actually trying to build), then the answer is “No, the executables do not link against any KDE-libraries”, it is a simple qt3-program (or two of them, to be precise).
The file README.TXT (again, if we are really talking about this) gives detailed instructions on how to build/install and does not use qmake (which produces the error above) but cmake.
The only “trap” is, if the README.TXT say “requires $FOO”, this actually means, you need to install “$FOO-devel” to make it build.
With that I was able to build all the stuff needed (deamon and the two GUI-programs) without any problems on 11.2, as qt3(-devel) is also part of the standard repos in 11.3, this should apply there in the same manner.
Akoellh wrote:
> The only “trap” is, if the README.TXT say “requires $FOO”, this
> actually means, you need to install “$FOO-devel” to make it build.
thanks for bringing your experience into this thread!
i’ve stopped compiling software i don’t need or want to try to figure
out why a poster supplying scant details (and who hasn’t yet found
README.TXT) has problems…
–
DenverD
When it comes to chocolate, resistance is futile.
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Hey Alejorosado,
I’ve been there done that. Had the same errors. But the good news is (if you still need ) that it can be installed from a Repo. It does require some config file editing and file creating but in the end you end up with a working Shrew VPN client . I’ve got it running on openSUSE 11.3 and 11.4 (both 64bits).
I’ll try to be as detailed as I can. Ok here goes:
Install Shrew
If you want your plan to come together you must:
Add a Additional software repositoy.
Install Shrew (IKE)
Create init.d start & stop scripts (optional)
Create a launcher on your desktop (optional)
Add a Repository
StartYast2
Go to:Software
Click on Software Reposities
Clik on ADD.
Choose Specify URL… and click next
Name the repo. E.g : security
The URL is: http://download.opensuse.org/repositories/security/openSUSE_11.x/
Clik on Next.
Read the GNUPG key message . If you agree klik Import. (if you don’t get this message just go ahead)
Next click on OK and close the Repository management.
**
Install Shrew**
Start Yast2
Go to: Software
Choose Software Management
Use the filter Luke and search for “ike”
From the available list of packages select “ike”
Clik op Apply and wait for completion
Close Yast2.
Init script
To make use of the Shrew VPN client the IKE deamon must be started by root. You can do this manually or you can make an INIT script to start if for you on the next boot:
To run at manually run the following command as root
/usr/sbin/iked
To create a init script copy to content of the script below and save it to /etc/init.d/ike
This is script source:
#! /bin/sh
# Copyright (c) 2011 Harald van Bree
# All rights reserved.
#
# Author: Harald van Bree, 2011
#
# /etc/init.d/iked
# and its symbolic link
# /usr/sbin/iked
### BEGIN INIT INFO
# Provides: iked
# Required-Start: $network $local_fs
# Required-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: ike - The Shrew Soft VPN Client
# Description: The Shrew Soft VPN Client for Unix is a free IPsec Client for FreeBSD, NetBSD and Linux based operating systems.
# It was originally developed to provide secure communications between mobile Windows hosts and open source VPN
# gateways that utilize standards compliant software such as ipsec-tools, OpenSWAN, FreeSWAN, StrongSWAN, isakmpd.
# It now offers many of the advanced features only found in expensive commercial software solutions and provides
# compatibility for VPN appliances produced by vendors such as Cisco, Juniper, Checkpoint, Fortinet, Netgear,
# Linksys, Zywall and many others. It supports most of the features availalble in the Windows VPN Client version
# with the exception of those which are not cross platform compatible.
### END INIT INFO
# Check for missing binaries
IKED_BIN=/usr/sbin/iked
test -x $IKED_BIN || { echo "$IKED_BIN not installed";
if "$1" = "stop" ]; then exit 0;
else exit 5; fi; }
# Check for existence of needed config file and read it
#BAR_CONFIG=/etc/bar.cfg
#test -r $BAR_CONFIG || { echo "$BAR_CONFIG not existing";
# if "$1" = "stop" ]; then exit 0;
# else exit 6; fi; }
# Read config
#. $BAR_CONFIG
# Load the rc.status script for this service.
. /etc/rc.status
# Reset status of this service
rc_reset
case "$1" in
start)
echo -n "Starting IKE Deamon"
## Start daemon with startproc(8). If this fails
## the return value is set appropriately by startproc.
startproc $IKED_BIN
# Remember status and be verbose
rc_status -v
;;
stop)
echo -n "Shutting down IKE Deamin "
## Stop daemon with killproc(8) and if this fails
## killproc sets the return value according to LSB.
killproc -TERM $IKED_BIN
# Remember status and be verbose
rc_status -v
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start
# Remember status and be quiet
rc_status
;;
reload)
# If it supports signaling:
echo -n "Reload service bar "
killproc -HUP $IKED_BIN
#touch /var/run/iked.pid
rc_status -v
## Otherwise if it does not support reload:
#rc_failed 3
#rc_status -v
;;
status)
echo -n "Checking for service IKED "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.
# Return value is slightly different for the status command:
# 0 - service up and running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running (unused)
# 4 - service status unknown :-(
# 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)
# NOTE: checkproc returns LSB compliant status values.
checkproc $IKED_BIN
# NOTE: rc_status knows that we called this init script with
# "status" option and adapts its messages accordingly.
rc_status -v
;;
*)
## If no parameters are given, print which are avaiable.
echo "Usage: $0 {start|stop|status|restart|reload}"
exit 1
;;
esac
Save this to /etc/init.d/iked
then do “chmod 744 /etc/init.d/iked”
and then do : “ln -s /etc/init.d/iked /sbin/rciked” to create a symbolic link to the script.
Now you can use the “rciked” command to start stop and check status of the ike deamon. (like in rciked start | rciked stop etc)
To make shure the IKE Deamon is started on the next boot execute the following command (as root)
“chkconfig -a iked”
Now start the deamon by “rciked start” (you don’t have to reboot for this just now)
Launcher
The final step is to create a launcher on your desktop to start the GUI.
Right click on your desktop and choose “Create Launcher…”
Fill in the fields as described below
Type: Application
Name: Shrew
Command: /usr/bin/ikea
Comment: Shrew VPN client
Tadaa…
If you followed the steps outlined above you are able to setup a tunnel but no traffic will pass. This has something to do with a route verification filter setting for the Linux kernel. To resolve this you must edit as root the file /etc/sysctl.conf and make sure the following is in this file.
net.ipv4.conf.all.rp_filter = 0
Just restart your machine at this point and your good to go. Happing tunneling rotfl!
You should consider to post it in the unreviewed how-to forum. This is a really good description, just came across it while googling for a shrewsoft problem solution. Thanks.
Thanks,
I’ll post it in the unreviewed how-to.
hbree wrote:
>
> Thanks,
>
> I’ll post it in the unreviewed how-to.
>
Thanks from my side, when I reinstalled ike on my laptop, I simply forgot
about net.ipv4.conf.all.rp_filter = 0.
You saved me a lot of time.
Also I did not use an init script for shrew before, it is much nicer now
with what you posted.
–
PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | Gnome 2.32 | nVidia
ION | 3GB Ram
your welcome.
As you suggested I’ve post it in the how-to as well.