Re: iptables deactivate "getportbyname"

[Manuel Scheub <manuel.scheub@kraftcom.de>]

Am 15.01.2013 15:35, schrieb Jan Engelhardt:
> On Tuesday 2013-01-15 15:26, Manuel Scheub wrote:
>> Am 15.01.2013 13:51, schrieb Jan Engelhardt:
>>> On Tuesday 2013-01-15 13:14, Manuel Scheub wrote:
>>>> after an upgrade of iptables from version 1.4.3.2 to 1.4.16.3, some rules
>>>> doesn't work anymore.
>>>> e.g. all rules with protocol UDP an port information:
>>>>
>>>> #iptables -A INPUT -p udp -i eth0 --dport 67 --sport 68 -j ACCEPT
>>>> iptables v1.4.16.3: Port "67" does not resolve to anything.
>>> Hrm. I cannot reproduce this so far, but I have a suspicion:
>>> Do you have some libc other than glibc, perhaps?
>> Sorry to be such a noob - what exactly do you mean?
> Do you run glibc, eglibc, µClibc, Bionic, or Something Completely Different™?
> Please tell us details about the system you have.
>
>> #./configure --with-kernel=/opt/linux-2.6.23 --with-xtlibdir=/usr/lib/iptables
>>
>> Maybe I need to upgrade my kernel-sources?
> The kernel is not required at all.

I have a production system which is really, really old for generating 
firmware for embedded devices, and I run glibc:

# /lib/libc.so.6
GNU C Library stable release version 2.3.2

so, anyway - I thought there is a simple solution, but now I think it's 
time to upgrade my whole development system!
However, thank you very much!