Comments on: Compiling custom dd-wrt kernel modules

By: Stan

Stan — Thu, 01 Aug 2013 23:26:24 +0000

Thanks Niobos, you`ve answered my question. I read the post for ipsec support above. It seems that they will eventually implement it and it will be a paid service.

I will use the openvpn for now.

Thanks again!

By: Niobos

Niobos — Thu, 01 Aug 2013 18:36:04 +0000

Stan,

I’ve also tried to get IPsec in dd-wrt, but the problem is that the kernel itself is missing support for XFRM. Even when xfrm.ko is a module, there are still some things in the kernel itself that change, so you can’t add xfrm.so afterwards. The forum-link that I posted in my previous comment is precisely about this issue.

If you really want IPsec support, you need to recompile the whole kernel, build a new image with that kernel, and re-flash the device.

Why do you need IPsec? Is OpenVPN an alternative?

Niobos

By: Stan

Stan — Thu, 01 Aug 2013 17:59:58 +0000

Hi Niobos,

thanks very much for your response! I am trying to load the IPSEC and GRE modules. I would like to run the openswan or the strongswan with gre (gre over ipsec) which requires these modules. I am trying to load it with insmod. I have built the kernel with all of the required modules for ipsec and gre and I have copied the “xfrm.ko” and ip_gre.ko modules to my opt dir (usb) but they do not load. Apparently I am missing something..

If you have any ideas I will appreciate it.

Thanks in advance!

By: Niobos

Niobos — Thu, 01 Aug 2013 13:32:38 +0000

Hi Stan, How do you try to insert the module? Using `insmod`, or using `modprobe`? If using `insmod`, you need to take care yourself that all dependencies are loaded. However, I see that an xfrm-symbol is not found. What modules are you trying to build? According to this forum post, the kernel is NOT build with CONFIG_XFRM, and that can't be added as a module. Niobos

By: Stan

Stan — Wed, 31 Jul 2013 23:10:51 +0000

Hi guys,

I have compiled the kernel and modules without a problem but when I try to insert the modules to the dd wrt I am getting the below error:

Jul 31 16:03:48 DD-WRT kern.warn kernel: ip_gre: Unknown symbol __secpath_destroy
Jul 31 15:45:59 DD-WRT kern.warn kernel: xfrm4_mode_transport: Unknown symbol xfrm_unregister_mode

Any ideas?
Thanks in advance!

By: rick

rick — Tue, 30 Oct 2012 03:14:41 +0000

Hi Niobos, Thank’s for your response.
I just solution that problem yesterday and now i will share that.
my system is Ubuntu.10 32 bit and that’s the key point which cause that problem.
some body in ddwrt forum said that toolchains must be running under 64 bit system. so I installed a Ubuntu 10 64 bit, and install all software:
sudo apt-get install bison flex build-essential patch libncurses5-dev
then set PATH
….

everything works perfect now~
hope some one who have this problem can get this information from your website.

By: Niobos

Niobos — Sun, 28 Oct 2012 08:34:45 +0000

Hi rick,
what system are you running this on? Is it a clean ubuntu install? What version?

By: rick

rick — Sun, 28 Oct 2012 04:05:03 +0000

hi~ Niobos.
thanks for your support to all newbies include me. haha~
I got the following errors after run make. have you any idea about that? waiting for you reply.
——————————————————————————————————-
/home/xxx/tools/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-gcc: 1: Syntax error: “(” unexpected
/home/xxx/tools/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-gcc: 1: Syntax error: “(” unexpected
/home/xxx/tools/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-gcc: 1: Syntax error: “(” unexpected
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CC arch/mips/kernel/asm-offsets.s
/home/xxx/tools/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-gcc: 1: Syntax error: “(” unexpected
make[1]: *** [arch/mips/kernel/asm-offsets.s] Error 2
make: *** [prepare0] Error 2
——————————————————————————————————-

By: Niobos

Niobos — Tue, 14 Feb 2012 14:54:38 +0000

what version of gcc are you using? It seems like you're running a "too recent" version.

By: goctala

goctala — Mon, 06 Feb 2012 21:15:30 +0000

Thank you Harish, After I fixed the path I have another error:

cifs_debug.c: In function ‘cifsFYI_write’:
cifs_debug.c:430: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:430: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:430: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:430: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘oplockEnabled_write’:
cifs_debug.c:469: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:469: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:469: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:469: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘quotaEnabled_write’:
cifs_debug.c:509: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:509: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:509: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:509: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘linuxExtensionsEnabled_write’:
cifs_debug.c:549: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:549: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:549: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:549: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘lookupFlag_write’:
cifs_debug.c:589: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:589: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:589: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:589: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘traceSMB_write’:
cifs_debug.c:627: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:627: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:627: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:627: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘multiuser_mount_write’:
cifs_debug.c:666: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:666: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:666: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:666: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘extended_security_write’:
cifs_debug.c:705: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:705: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:705: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:705: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘ntlmv2_enabled_write’:
cifs_debug.c:744: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:744: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:744: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:744: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c: In function ‘packet_signing_enabled_write’:
cifs_debug.c:783: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:783: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:783: error: read-only variable ‘__gu_val’ used as ‘asm’ output
cifs_debug.c:783: error: read-only variable ‘__gu_val’ used as ‘asm’ output
make[2]: *** [cifs_debug.o] Error 1
make[2]: Leaving directory `/home/user/Desktop/dd-wrt_m/fs/cifs’
make[1]: *** [_modsubdir_cifs] Error 2
make[1]: Leaving directory `/home/user/Desktop/dd-wrt_m/fs’
make: *** [_mod_fs] Error 2