[Serusers] udp error

Stephen Miles smiles at callplus.co.nz
Thu Nov 6 21:00:38 CET 2003


Hi Jiri,

Thanks for that. It looks the same as what I am seeing.

What I have found is that if I can quess the port that the pix is going 
to use next and set that as my port i.e sip:stephenm at 202.180.76.97:60547 
it will work, I only get one way audio but thats no matter at the 
moment. What I have seen is that the register isn't even getting into 
the routing logic of ser when the port of the client is left set to 5060.

This doesn't happen for clients behind the same pix but with a 1 to 1 
nat setup, i.e I am the only person being natted behind the IP 
202.180.76.103. Other clients who are in the main nat pool and get 
natted behind .76.97 seem to have the problem because the pix is not 
keeping the ports original when it sends the request. I thought that the 
nathelper module was ment to address this?

Any idea?

Thanks in advance,
Stephen

Jiri Kuthan wrote:
> That's what I have (uname -a bellow). -jiri
> 
> root at fox:/var/log# grep "Resource temporarily unavailable" syslog |tail
> Nov  5 20:29:39 fox /home/srouter/bin/sr[7682]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 20:49:39 fox /home/srouter/bin/sr[8226]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 21:57:39 fox /home/srouter/bin/sr[8206]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 22:29:39 fox /home/srouter/bin/sr[8206]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 22:29:39 fox /home/srouter/bin/sr[8226]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 22:29:41 fox /home/srouter/bin/sr[8233]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 22:49:39 fox /home/srouter/bin/sr[8215]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  5 23:53:34 fox /home/srouter/bin/sr[13773]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  6 00:05:39 fox /home/srouter/bin/sr[13750]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> Nov  6 00:06:01 fox /home/srouter/bin/sr[13778]: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable 
> root at fox:/var/log# uname -a
> Linux fox 2.4.20-xfs #1 SMP Fri Mar 28 17:04:13 CET 2003 i686 GNU/Linux
> 
> 
> At 12:20 AM 11/6/2003, Stephen Miles wrote:
> 
>>Hi Jiri,
>>
>>Can you tell me which kernel you are using. I am using a 2.4.21 kernel at the moment, fairly standard with all the iptables support built in.
>>
>>Jiri Kuthan wrote:
>>
>>>At 03:59 AM 11/5/2003, Stephen Miles wrote:
>>>
>>>
>>>>Hi all,
>>>>
>>>>I am having a little problem involving a Cisco Pix firewall using nat.
>>>>
>>>>The error I am getting is: ERROR: udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable
>>>>
>>>>I can't seem to find any info about what this error means and the udp_server.c doesn't tell me much. 
>>>
>>>We occasionaly receive it at our server too on some kernels.
>>>I suppose that's a kernel problem with no known impact -- when
>>>kernel returns an error for UDP receiver the receiver starts all over again till no more error occurs.
>>>
>>>
>>>>Is it related to the port the Pix is trying to use when it re-writes the out bound request?
>>>
>>>it is not related to use of pix.
>>>-jiri 
>>
>>
>>
>>-----------------------------------------------------------------------------------------------
>>This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited.  If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.
> 
> 
> --
> Jiri Kuthan            http://iptel.org/~jiri/ 
> 



-----------------------------------------------------------------------------------------------
This message and any attachments contain privileged and confidential information. 
If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited.  If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.




More information about the sr-users mailing list