From owner-freebsd-questions@FreeBSD.ORG Thu Dec 5 18:18:51 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5887248F for ; Thu, 5 Dec 2013 18:18:51 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D45091146 for ; Thu, 5 Dec 2013 18:18:50 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id en1so77307wid.3 for ; Thu, 05 Dec 2013 10:18:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=BiLBOHlnjgZ4PFhV2OKQDYX/h0+dkYJOP71nWEI7Lkc=; b=Sh9wYmFNBTCOc3e4fsICz3v4ZMlOLy7iD4PQZxBaSBoPYiVim6aReaugRJOUZCkNtQ f908RAxerBAIrUN+oo3KQ6dzx9izWddO+UdgSCLDJACRW9Dy+zjP2+AyCZJ3hyqGvY5r v2K6TLh0fEF7inqzfdDXWM9r4HuIGab/hVtzxrxGvW3amQOZVKLfPjCmiSDdoPN3kA1i nnXC7W2tiGrgwz/c2r1YKJOOZ+XRVw/CnUY84D5RMq+tJAGZ5IC1qu9ES4ZV41NnSTZy 72vh8WpheiDDZdz5tOb+F5lqZ3o7UzCZmiMpCDk9I0e3XR13bHC8LLzvYkE/Bp5YN/FV 19yA== X-Gm-Message-State: ALoCoQnThIk4nIYNqzXwTUOszfp48Um1wt6WFMID22nOujn14fMw/w2ZXu0VgVtdCWx3qZVKnxW7 X-Received: by 10.180.108.42 with SMTP id hh10mr13075876wib.15.1386263640692; Thu, 05 Dec 2013 09:14:00 -0800 (PST) Received: from dfleuriot.paris.hi-media-techno.com ([83.167.62.196]) by mx.google.com with ESMTPSA id w20sm8059078wia.5.2013.12.05.09.13.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Dec 2013 09:13:59 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: do I have to compile a new kernel? or just add options somehow? From: Fleuriot Damien In-Reply-To: Date: Thu, 5 Dec 2013 18:13:58 +0100 Message-Id: References: <1A249B2C-B341-4270-B343-627901FD9562@my.gd> To: "firmdog@gmail.com" X-Mailer: Apple Mail (2.1510) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 18:18:51 -0000 Merely adding the options and rebooting is not sufficient to get the = options from your kernel as opposed to a module. You need to actually recompile the kernel, I hope you did that. On Dec 5, 2013, at 5:48 PM, "firmdog@gmail.com" = wrote: >=20 > Looks like it "might have" worked for me. First I added a couple of = options to the GENERIC config: >=20 > root@:~ # grep IPSEC /usr/src/sys/i386/conf/GENERIC > options IPSEC # IP security (requires device crypto) > options IPSEC_NAT_T # NAT-T support, UDP encap of ESP >=20 > Then rebooted: >=20 > root@:~ # uname -a > FreeBSD 8.4-RELEASE FreeBSD 8.4-RELEASE #0 r251259: Mon Jun 3 = 01:14:28 UTC 2013 = root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 >=20 > root@:~ # kldload crypto > root@:~ # kldstat=20 > Id Refs Address Size Name > 1 5 0xc0400000 d5c4ec kernel > 2 1 0xc58eb000 23000 crypto.ko > 3 1 0xc58da000 a000 zlib.ko >=20 >=20 > The reason I am doing this is because a new Cisco VPN router will not = work with my IPF Freebsd firewall. The IPF firewall blocks the UDP ipsec = packets on port 4500. So now I need to see if doing the above exercise = helps with IPF blocking IPsec traversal across NAT >=20 >=20 >=20 >=20 > On Thu, Dec 5, 2013 at 10:57 AM, Fleuriot Damien wrote: > Oh but you can load modules at boot time for GENERIC just fine. >=20 > While there is a "crypto" module nested under = /usr/src/sys/modules/crypto/ , I'm not familiar enough with it to say = whether it incorporates both the device and the IPSEC options you're = interested in. >=20 > You're better off rebuilding GENERIC, or your own kernel, IMHO. >=20 >=20 >=20 > If you're curious, you can always run : > kldload crypto >=20 > If kldload says the module doesn't exist (I think it should, for = GENERIC), you'll need to build it: > cd /usr/src/sys/modules/crypto/ && make && make install >=20 >=20 >=20 > Here's little me trying to load it under a brand new 8.4 box: >=20 > # kldload /boot/kernel/crypto.ko > kldload: can't load /boot/kernel/crypto.ko: Exec format error >=20 >=20 > If you run into this error like me, "dmesg" will provide you with a = clue, as it does in my case: > KLD crypto.ko: depends on zlib - not available or version mismatch > linker_load_file: Unsupported file type >=20 >=20 >=20 > I really encourage you to rebuild your own kernel, stripped of all the = stuff you don't want/need (ISA NICs, wifi, firewire, floppy = controller... ) >=20 >=20 > Warren Block has written pretty cool articles, here: > http://www.wonkity.com/~wblock/docs/html/buildworld.html > http://www.wonkity.com/~wblock/docs/html/kernelconfig.html >=20 >=20 >=20 >=20 > I hope that helps, >=20 >=20 > On Dec 5, 2013, at 4:30 PM, "firmdog@gmail.com" = wrote: >=20 >>=20 >> So the answer is that it's NOT possible to load modules at boot time = for GENERIC? I have to actually build a new kernel? >>=20 >> Thanks! >>=20 >>=20 >> On Thu, Dec 5, 2013 at 9:42 AM, Fleuriot Damien wrote: >>=20 >> On Dec 5, 2013, at 3:35 PM, "firmdog@gmail.com" = wrote: >>=20 >> > I am having difficulty understanding what is compiled into the = GENERIC >> > kernel. >> > >> > I need to enable "device crypto" with IPSEC and IPSEC_NAT_T = options. >> > >> > Can I just configure the GENERIC kernel in a config file? Or do I = have to >> > compile a totally new kernel? >> > _______________________________________________ >> > freebsd-questions@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" >>=20 >>=20 >> While it's far from being a good practice, you can simply add your: >> device crypto >> options IPSEC >> options IPSEC_NAT_T >>=20 >> to /sys/amd64/conf/GENERIC (assuming you're running a 64bit release = that is). >>=20 >>=20 >> Then: cd /usr/src && make kernel-toolchain && make buildkernel >>=20 >> Once the kernel is built, you only need to "make installkernel" and = reboot. >>=20 >> It is good practice, before rebooting, to run "mergemaster -p" , even = if you've only done a minor upgrade, let good habits sink in ;) >>=20 >>=20 >>=20 >>=20 >> Regarding what is compiled in the GENERIC kernel, you can find the = included options and devices at: >> /sys/amd64/conf/GENERIC >> or >> /sys/i386/conf/GENERIC >>=20 >> You may also run config -x /boot/kernel/kernel , if your kernel was = built with INCLUDE_CONFIG_FILE , which GENERIC does. >>=20 >>=20 >=20 >=20