ipq_get_msgerr: No such file or directory

ipq_get_msgerr: No such file or directory

[Robert Scott]

I am receiving this error code from ipq_get_msgerr.  The read is 
successful, and returns a non-zero positive number, but when I call 
ipq_message_type on the buffer used to read the packet, I get 
NLMSG_ERROR, and then, when I call strerror( ipq_get_msgerr( buffer ))  
where "buffer" is the second argument to ipq_read, I receive the error 
message "No such file or directory".

This has occurred on a Linux 2.6.8.1 kernel with version 1.2.9 of 
iptables.  The box where this occurred is acting as a bridge, and this 
started happening when the internet connection on one of its interfaces 
went down for a few hours.

Any ideas as to why this may be happening?

thanks,
--robert

ipq_get_msgerr: No such file or directory

[Robert Scott]

I am receiving this error code from ipq_get_msgerr.  The read is 
successful, and returns a non-zero positive number, but when I call 
ipq_message_type on the buffer used to read the packet, I get 
NLMSG_ERROR, and then, when I call strerror( ipq_get_msgerr( buffer ))  
where "buffer" is the second argument to ipq_read, I receive the error 
message "No such file or directory".

This has occurred on a Linux 2.6.8.1 kernel with version 1.2.9 of 
iptables.  The box where this occurred is acting as a bridge, and this 
started happening when the internet connection on one of its interfaces 
went down for a few hours.

Any ideas as to why this may be happening?

thanks,
--robert

Re: ipq_get_msgerr: No such file or directory

[Patrick McHardy]

Robert Scott wrote:
> I am receiving this error code from ipq_get_msgerr.  The read is 
> successful, and returns a non-zero positive number, but when I call 
> ipq_message_type on the buffer used to read the packet, I get 
> NLMSG_ERROR, and then, when I call strerror( ipq_get_msgerr( buffer ))  
> where "buffer" is the second argument to ipq_read, I receive the error 
> message "No such file or directory".
> 
> This has occurred on a Linux 2.6.8.1 kernel with version 1.2.9 of 
> iptables.  The box where this occurred is acting as a bridge, and this 
> started happening when the internet connection on one of its interfaces 
> went down for a few hours.
> 
> Any ideas as to why this may be happening?

There is only a single place where ip_queue returns -ENOENT, which is
when in ipq_set_verdict when the entry can't be found.

Regards
Patrick