Re: Protocol not attached

["Leandro Sales" <leandroal@xxxxxxxxx>]

On Thu, Oct 2, 2008 at 1:47 AM, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote:
> | Then, is it necessary to report this issue in the kernel dev maillist?
> |
> Before you do, can you check whether this issue is due to loading
> modules on request. The DCCP protocol driver will return EUNATCH if it
> is not able to load the compiled-in CCID modules.
>
> The way to test this is: unload all DCCP modules, start application
> (with or without error), and then see which modules are loaded.
>
> If the compiled-in CCIDs have been loaded successfully from within DCCP
> then the problem is somewhere else.
>

Hello Gerrit and others,
   we compiled 2.6.27-rc4 with DCCP as module in my testbed desktop.

# modprobe -l
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_diag.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/ccids/lib/dccp_tfrc_lib.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/ccids/dccp_ccid2.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/ccids/dccp_ccid3.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_ipv6.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_ipv4.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp.ko
/lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_probe.ko

The module did not start in the boot (expected!). I then ran

"strace -f -e trace=network iperf -s -d -l 1424 -i 1"

and:

# lsmod
Module                  Size  Used by
dccp_tfrc_lib          17868  0
dccp_ipv6              14916  2
dccp_ipv4              14596  3 dccp_ipv6
dccp                   58176  2 dccp_ipv6,dccp_ipv4

DCCP did not load the dccp_ccid2 module. Is this the problem?

Just to let you know:
# cat /proc/sys/net/dccp/default/rx_ccid /proc/sys/net/dccp/default/tx_ccid
2
2

I then tested tested with 2.6.27-rc8, the same as with 2.6.27-rc4.

So, what is your opinion?

Thank you,
Leandro.
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html