<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>Thank you for your help and sorry for my english.<br>I have a problem with mipv6 and a server SIP, SER (SIP Express Router).
The mipv6 path is "mipv6-2.0.2" in kernel 2.6.16.24-Ubuntu.<br><br>The problem occurs when a packet is too big (it must be fragmented), and go to the node what makes function of P-CSCF (Proxy in SIP) and Correspondent Node. If the P-CSCF is not a CN, all is OK. But if the node is CN, then i have the problem. The SER logs are:<br><br>................<br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: SER: new INVITE <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: parse_headers: flags=-1 <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: check_via_address(2001:720:1500:1B:FCFD:FF:FE0C:103, [2001:720:1500:1B:FCFD:FF:FE0C:103], 3) <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: ERROR: warning_builder: buffer size exceeded <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: WARNING: warning skipped -- too big <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: WARNING:vqm_resize: resize(0) called <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: DEBUG: reply sent out.
buf=0x8106270: SIP/2.0 1..., shmem=0xb5e8b330: SIP/2.0 1 <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: DEBUG: _reply_light: finished <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: DEBUG: mk_proxy: doing DNS lookup... <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8051]: check_via_address(2001:720:1500:1B:FCFD:FF:FE0C:103, [2001:720:1500:1B:FCFD:FF:FE0C:103], 3) <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8068]: DBG: tcp_main_loop: dead child 2 (shutting down?) <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: child process 8051 exited by a signal 11 <br>Nov 20 18:28:25 pcscfD kernel: [4296472.851000] <0>skb_under_panic: text:c02d2aad len:321 put:14 head:d62cfc00 data:d62cfbea tail:d62cfd2b end:d62cfd80 dev:eth0<br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: core was not generated <br>Nov 20 18:28:25 pcscfD kernel: [4297162.639000] ------------[ cut here ]------------<br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: INFO: terminating due to SIGCHLD <br>Nov 20 18:28:25
pcscfD kernel: [4297162.639000] kernel BUG at net/core/skbuff.c:112!<br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8059]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8052]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8053]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8054]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8055]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8056]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8057]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8058]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8060]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8061]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8062]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8063]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD
/usr/sbin/ser[8064]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8065]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8066]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8067]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8068]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8050]: INFO: signal 15 received <br>Nov 20 18:28:25 pcscfD kernel: [4297162.639000] invalid opcode: 0000 [#3]<br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8059]: Memory status (pkg): <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8052]: Memory status (pkg): <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8053]: Memory status (pkg): <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8054]: Memory status (pkg): <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8055]: Memory status (pkg): <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8056]: Memory status (pkg): <br>.......................<br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: hash =
2055 fragments no.: 1, unused: 0 ^I^I bucket size: 1048576 - 2097152 (first 1572864) <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: hash = 2059 fragments no.: 1, unused: 0 ^I^I bucket size: 16777216 - 33554432 (first 31934160) <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: TOTAL: 26 free fragments = 33537656 free bytes <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: ----------------------------- <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: shm_mem_destroy <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: destroying the shared memory lock <br>Nov 20 18:28:25 pcscfD /usr/sbin/ser[8049]: terminating due to SIGCHLD <br>##############################################################<br>The problem is in the MTU size, because if the packet is not fragmented, there is not a problem. But the INVITE packet
needs to fragment, what it means, i always have the same problem.<br><br>My questions are:<br><br>- Have anybody the same o similar problem?<br>- The MTU size is a problem in SER?<br>- Have anybody sent fragmented packets with SER?<br><br>Thanks for your help.<br></div></div></div><br>
<hr size=1><br><font face="Verdana" size="-2">LLama Gratis a cualquier PC del Mundo.<br>Llamadas a fijos y móviles desde 1 céntimo por minuto.<br><a href="http://us.rd.yahoo.com/mail/es/tagline/messenger/*http://es.voice.yahoo.com/">http://es.voice.yahoo.com</a></font></body></html>