home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.protocols.tcp-ip      TCP and IP network protocols.      14,669 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 12,997 of 14,669   
   Dmitry V. Krivenok to Michael Shuldman   
   Re: UDP socket && sendto && EPERM   
   13 Aug 09 18:41:42   
   
   From: krivenok@orangesystem.ru   
      
   Michael Shuldman wrote:   
   > In comp.protocols.tcp-ip you (krivenok.dmitry@gmail.com) wrote:   
   >   
   >>  But I'm still confused about EPERM error.   
   >>  I'm going to examine Linux kernel source code to find out when   
   >>  exactly   
   >>  EPERM error is returned.   
   >   
   > Hi, I'm only curious, but did you find out what the problem was?   
      
   Hello!   
      
   Unfortunately, I didn't find out the cause of the problem.   
   I haven't enough time to dig into kernel source code, but the   
   problem is still in my todo list.   
      
      
   >   
   > I'm no linux expert, but I became curious enough and downloaded a   
   > version of the linux kernel (2.6.30) to take a peek.  I found one   
   > entry that I wonder if might be related to the problem you saw.   
   >   
   > Since you said you had a firewall configured, even though it was   
   > configured to pass all packets out ...   
   >   
   > In the file ip_output.c one of the comments says:   
   >   
   > " Marc Boucher    : When call_out_firewall returns FW_QUEUE,   
   >                     silently drop skb instead of failing with -EPERM."   
   >   
   > I did not immediately manage to find any function called that, so I   
   > did not examine how that function works, but perhaps it's related   
   > to the problem you saw?   
   >   
   > I'm just guessing now, but presumably that function was called in   
   > your case (since you had a firewall configured) and your sending   
   > eventually filled up the FW_QUEUE (whatever that is).   
   > Since there apparently was a bug in the kernel that made it return   
   > EPERM when that happened, that was perhaps what caused you problems?   
      
      
   It could be the cause of the problem.   
      
   Thank you very much for your response!   
      
      
   > Presumably disabling the firewall completely could help verify this   
   > theory.   
   >   
   > Maybe you could post an update if you found out what the error was?   
   >   
   > Regards,   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca