[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian & Contivity VPN



For what it's worth:
--------------- Forwarded message (begin)
 Subject: Re: NAI/Netlock under Debian
 From: Matias A. Vidal Pereyra <matias@ficus.arg.hp.com>
 Date: Fri, 03 Sep 2004 07:37:47 -0700
 Newsgroup: hp.os.linux
 On Fri, 2004-09-03 at 05:06, Eric Lavarde - HP wrote:
 > Hi,
 >
 > I just wanted to ask if the new Netlock version has advantages compared
 > to the old one, beside support of newer kernels without patching the kernel.
 >
 > I am under 2.4.26 (soon 2.4.27) built with gcc 2.95.4, there is a Debian
 > package for Netlock 2.1.1, but only RPMs for 3.0 and these new RPMs seem
 > to be marked for gcc 3.3 (conclusion from the name).
 > So, I'm a bit unsure on which package I should use!?
 Eric,
     I'm currently using debian testing/unstable with nai without
 problems, I build my own kernel.org kernels. Here my setup:
 - matias@ooky:~$ gcc -v
 Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.4/specs
 Configured with: ../src/configure -v
 --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
 Thread model: posix
 gcc version 3.3.4 (Debian 1:3.3.4-6sarge1)
 - Kernel 2.4.27 + ALSA + ACPI + pacth for nai (attached)
 - Using NAI: cvc_linux-rh8-2.1.1.tar.gz
   I tried using SuSe versions of NAI without success.
 Hope it helps!
 --
 Matias A. Vidal Pereyra <matias@ficus.arg.hp.com>
 Enterprise CSC - HP Argentina
`--------------- Forwarded message (end)

--
Olivier Schreiber OSchreiber.ae90@gtalumni.org H323 464 5818
--- linux-2.4.24/include/linux/skbuff.h	2003-08-25 05:44:44.000000000 -0600
+++ linux-2.4.24-netlock/include/linux/skbuff.h	2004-02-18 11:47:26.000000000 -0700
@@ -135,11 +135,6 @@
 	struct sock	*sk;			/* Socket we are owned by 			*/
	 	struct timeval	stamp;			/* Time we arrived				*/
		 	struct net_device	*dev;		/* Device we arrived on/are leaving by		*/
			-	struct net_device	*real_dev;	/* For support of point to point protocols 
			-						   (e.g. 802.3ad) over bonding, we must save the
			-						   physical device that got the packet before
			-						   replacing skb->dev with the virtual device.  */
			-
			 	/* Transport layer header */
				 	union
					 	{
						@@ -219,6 +214,11 @@
						 #ifdef CONFIG_NET_SCHED
						         __u32           tc_index;               /* traffic control index */
							  #endif
							  +	struct net_device	*real_dev;	/* For support of point to point protocols 
							  +						   (e.g. 802.3ad) over bonding, we must save the
							  +						   physical device that got the packet before
							  +						   replacing skb->dev with the virtual device.  */
							  +
							   };
							    
							     #define SK_WMEM_MAX	65535

Reply to: