From owner-freebsd-questions@FreeBSD.ORG Fri Dec 6 10:54:03 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1BCE21E3 for ; Fri, 6 Dec 2013 10:54:03 +0000 (UTC) Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A20D11D9 for ; Fri, 6 Dec 2013 10:54:02 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id y10so468488wgg.24 for ; Fri, 06 Dec 2013 02:53:54 -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=fTA4uQFoAwRVhrF6JGa1Pnn/YYrhJXOgt+h3ncT/wTs=; b=j9NjK3UGUbyZkWYAml9owvw02n71K/Tl4A2xzU8wtrRyq3b9cv/QCprphU2yj72H7W xhDw5o/+wPaNlrs0lsr7ZJuo/rJBurpa/q8GFyb4+gll/dvlrgbX+ruiBMeS73vd9gLq AETN8bGr7rKEfQUQPut90G63BW6O/xYRTuj81V2footIPO6ej6ww0kspGfX4WgUHobZE uGoDSOdvpa4RK1+F0yfuqAeyppURzh8OcKseoZ1WPEbFnY+68xjNy2/o5UUk+Pqm42I1 CsZTiiHcdalf7ai+H6XfJP58zqCCg8cQsEF1CTxNoFgbkq7mvdPrbU2sbo548SqQi88W /+iA== X-Gm-Message-State: ALoCoQljIU+zOSWdePfxPUcI20VAhwJ/yTqdjJ8eA+DfgbBQswcvHwrVi5WpXj4XycPI1TvTjXOK X-Received: by 10.180.206.41 with SMTP id ll9mr1802237wic.7.1386326813816; Fri, 06 Dec 2013 02:46:53 -0800 (PST) Received: from dfleuriot.paris.hi-media-techno.com ([83.167.62.196]) by mx.google.com with ESMTPSA id s20sm5067577wib.1.2013.12.06.02.46.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 02:46:53 -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: Fri, 6 Dec 2013 11:46:51 +0100 Message-Id: <9909F4F0-623F-46F1-BD21-B3D2D9E4653A@my.gd> 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: Fri, 06 Dec 2013 10:54:03 -0000 As I said earlier, you might not need to rebuild it, but I can't say if = IPsec Nat Traversal is enabled in the module. On Dec 5, 2013, at 9:41 PM, "firmdog@gmail.com" = wrote: >=20 > I ran #kldload crypto. Did you see that? Then I ran kldstat and it = shows the module loaded. >=20 > Why do I have to recompile the kernel if I can run kldload or use = loader.conf to load the module at boot time? >=20 >=20 >=20 >=20 >=20 > On Thu, Dec 5, 2013 at 12:13 PM, Fleuriot Damien wrote: > Merely adding the options and rebooting is not sufficient to get the = options from your kernel as opposed to a module. >=20 > You need to actually recompile the kernel, I hope you did that. >=20 >=20 > On Dec 5, 2013, at 5:48 PM, "firmdog@gmail.com" = wrote: >=20 >>=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 >=20 >=20