ipcop-devel Mailing List for IPCop Firewall

On 06/26/2012 08:08 AM, Eric Shubert wrote:
> Is it possible to build an IPCop with IPSec that supports the DES_CBC
> encryption algorithm?
>
> DES_CBC is what the iPad/iPhone native IPSec implementation appears to
> be using:
> pluto[21485]	"StephIPad"[4] 174.26.92.118 #4: OAKLEY_DES_CBC is not
> supported. Attribute OAK LEY_ENCRYPTION_ALGORITHM
>
> TIA for any pointers.
>

I see now that des_cbc is insecure. Openswan could be build with a 
USE_WEAKSUFF?=true setting, but that would not be advisable.

Pardon the noise as I sort this stuff out.

-- 
-Eric 'shubes'

Is it possible to build an IPCop with IPSec that supports the DES_CBC 
encryption algorithm?

DES_CBC is what the iPad/iPhone native IPSec implementation appears to 
be using:
pluto[21485]	"StephIPad"[4] 174.26.92.118 #4: OAKLEY_DES_CBC is not 
supported. Attribute OAK LEY_ENCRYPTION_ALGORITHM

TIA for any pointers.

-- 
-Eric 'shubes'

I am trying to build the latest 2.0 tfrom trunk revision 6649.

I am not able to get to the server www.zweije.nl.eu.org, and therfore 
not able to build.

the CnxADSL driver requires access to this server, but it is not 
connecting now for over 4 days.

I have tried from many locations in the US to verify the connection in 
case there is something blacklisting my home IP.  Also tried from other 
than the usual DNS situation that exists here with the reverse DNS in 
case they have the http port set to reject connections.

Anyone have any alternate locations?  As near as I can tell this is 
required and this is the home system for the driver in IPcop.

Also the current trunk needed to have linux-headers from 
http://mirror.anl.gov/linux/kernel/  The file patch-2.6.32.21.bz2 is 
required to satisfy this and it not present on that server, so I had to 
download it from elsewhere (redhat) and put in manually.

I have a friend who may have gotten the CnxADSL as he has been trying to 
build for about a month.  He may have gotten it, as he only recalls that 
linux-headers is his only missing bit.  the server may have been up a 
month ago, and is not up now.

Perhaps some in europe or elsewhere can reach it as well.  I do not have 
a remote method to try other than in the US.

Thanks
Jim

Bugs item #3534162, was opened at 2012-06-10 10:54
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=3534162&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Kernel
Group: 2.0.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Pierre-Luc Plourde ()
Assigned to: Nobody/Anonymous (nobody)
Summary: ASIX Driver

Initial Comment:
I would like to have a recent build of the asix usb net driver.

The current one flood the kernel message with asix_rx_fixup()

Thanks

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=3534162&group_id=40604

On 2 June 2012 22:12, Olaf Westrik <wei...@ip...> wrote:

> There are some libraries that link to libpcre.so.0 that need to be included
> into the update package. Especially the pango/cairo stuff.
>
> Olaf

Thanks Olaf

SVN 6638 has fixed this problem, and I'm also running the 3.0-1 kernel
via the upgrade process :)

Eric

Daniel,

I too would like to see IPCOP able to install on HP servers without a lot of
manual work.  To help this along, I have setup a Debian system to develop on
and begun to make the necessary changes to accomplish this.  Unfortunately,
because of the way the CCISS driver displays the arrays to Linux (as you
pointed out in your message), it will require a number of changes to
different parts of the installer to work and not break the current devices
it installs to.  Currently, I got it to display the Logical Volumes in the
drive selection screen.  Once I get the selection screen working, will move
on to partitioning.  I will keep you informed of my progress.  Hopefully, if
I can get it to work correctly and continue to work for current devices, the
changes can be added to the main distribution.

Will be testing on a DL380 G4, DL380 G5, and DL360 G5 (the three systems I
have available) but expect it would work for any array controller supported
by the CCISS driver.

Rich Fabian


-----Original Message-----
From: Daniel Challen [mailto:dan...@oc...]
Sent: Friday, March 09, 2012 6:42 AM
To: ipc...@li...
Subject: [IPCop-devel] IPcop 2.0 on Proliant servers/RAID controllers


Begging your pardon if this is better on the user mailing list...

I've been running IPcop 1.4 on an HP Proliant (PC server) for a while,
where it works well (thank you). Upon trying to install 2.0 on the
machine, I (and others
http://www.ipcops.com/phpbb3/viewtopic.php?f=16&t=16918 ) have found
that it does not support the hardware RAID controller in these machines.

In more detail, the problem appears to be that the installer does not
handle 'unusual' disk device names. My machine (Proliant DL380 G3)
contains an integrated "SmartArray 5i", this is handled by the "cciss"
driver, which is definitely included in the IPcop 2.0 kernel, however
that driver presents the configured RAID disks as block devices (rather
than SCSI disks) with names in /dev like
/dev/cciss/c0d0     first controller, first disk
/dev/cciss/c1d2p1   second controller, third disk, first partition (yes,
controller and disk are zero-indexed, partitions are indexed from 1)

This is handled fine by the 1.4 installer routine. The following is from
my current 1.4 machine:
root@milton:~ # ls -l /dev/harddisk*
lrwxrwxrwx 1 root root 15 2006-02-09 11:35 /dev/harddisk
-> /dev/cciss/c0d0
lrwxrwxrwx 1 root root 17 2006-02-09 11:35 /dev/harddisk1
-> /dev/cciss/c0d0p1
lrwxrwxrwx 1 root root 17 2006-02-09 11:35 /dev/harddisk2
-> /dev/cciss/c0d0p2
lrwxrwxrwx 1 root root 17 2006-02-09 11:35 /dev/harddisk3
-> /dev/cciss/c0d0p3
lrwxrwxrwx 1 root root 17 2006-02-09 11:35 /dev/harddisk4
-> /dev/cciss/c0d0p4

I have tried switching to a VC with a shell while the 2.0 installer is
running, and linking /dev/sda to /dev/cciss/c0d0 and /dev/sda1
to /dev/cciss/c0d0p1 etc, then back to the ncurses interface and
pressing the "Rescan" button, however that did not make it work.

I work for an HP reseller and have access to a number of Proliants, so I
can do some testing on various configurations if that helps.


Further detail on Linux on the "Proliant" range:
Older Compaq-badged proliants (e.g.
http://marc.info/?l=ipcop-devel&m=127844232704113&w=2) usually have the
cpqarray module, and devices like /dev/ida/c0d0 (I don't think we have
any of these for testing - they're bit too old)
More recent (generation 3 to 5 or 6) HP-badged proliants have
"SmartArray" hardware, driven by the cciss module, and device nodes
like /dev/cciss/c0d0     http://cciss.sourceforge.net/
The latest generation of SmartArray hardware is handled by a the 'hpsa'
module, which presents the disks as standard SCSI disks, so that they
have /dev/sda entries, and should not need any special case handling.

- Daniel Challen

________________________________

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
This communication may be legally privileged. If you are not the intended
recipient, please be advised that you have received this email in error and
that any use, dissemination, forwarding, printing or copying of this email
is strictly prohibited. If you have received this email in error, please
notify the OCSL switchboard on +44 845 6052100. OCSL Registered Office: East
House, New Pound Common, Wisborough Green, West Sussex, RH14 0AZ. Registered
No: 2563193
----------------------------------------------------------------------------
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
IPCop-devel mailing list
IPC...@li...
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

On 2012-06-02 16:42, Eric Oberlander wrote:
>> This is my error.
>> While looking at libffi usage in our build, I have seen only libgio linked and miss libgobject.
>>
>> While testing, you should include every files that is spotted as DIFF from previous version in doc/IPCop-2.1.0-diff-list.i486.txt.
>> Some difference are related to openssl upgrade, other to glib upgrade.
>>
>> Gilles
>
> Gilles
>
> I've just noticed that these files are also missing from my system,
> after applying the 2.1.0 update:
> /usr/lib/perl5/site_perl/5.10.1/i486-linux/RRDs.pm
> /usr/lib/perl5/site_perl/5.10.1/i486-linux/auto/RRDs/RRDs.so
>
> Which may be connected to the breakage of 'makegraphs'. I've looked
> around for a fix, but I'm not sure where the RRDs are included in the
> build. Sorry.

There are some libraries that link to libpcre.so.0 that need to be 
included into the update package. Especially the pango/cairo stuff.


Olaf

> This is my error.
> While looking at libffi usage in our build, I have seen only libgio linked and miss libgobject.
>
> While testing, you should include every files that is spotted as DIFF from previous version in doc/IPCop-2.1.0-diff-list.i486.txt.
> Some difference are related to openssl upgrade, other to glib upgrade.
>
> Gilles

Gilles

I've just noticed that these files are also missing from my system,
after applying the 2.1.0 update:
/usr/lib/perl5/site_perl/5.10.1/i486-linux/RRDs.pm
/usr/lib/perl5/site_perl/5.10.1/i486-linux/auto/RRDs/RRDs.so

Which may be connected to the breakage of 'makegraphs'. I've looked
around for a fix, but I'm not sure where the RRDs are included in the
build. Sorry.

Eric