ICMP reject types?
Maybe it's my ignorance, but I feel that REJECT target --reject-with option is somewhat broken - you can set icmp-net-prohibited or host-prohibited ICMP replies, which are discouraged and obsoleted by RFC 1812, but you cannot use 0/13 ICMP (Admin prohibited), which is the one recommended by the RFC. Can anyone comment?
Signature · 3 lines
Paweł Krawczyk, Kraków, Poland http://echelon.pl/kravietz/ horses: http://kabardians.com/ crypto: http://ipsec.pl/
Quoted 5 lines
Maybe it's my ignorance, but I feel that REJECT target --reject-with option is somewhat broken - you can set icmp-net-prohibited or host-prohibited ICMP replies, which are discouraged and obsoleted by RFC 1812, but you cannot use 0/13 ICMP (Admin prohibited), which is the one recommended by the RFC. Can anyone comment?
This item is actually on the TODO list and also has been coded by at least two people seperatelly.
Unfortunately adding this reject type imposes some compatibility issues with people having new libipt_REJECT.so and the old ipt_REJECT.o, which will simply result in a DROP in case this new option is specified.
One possible solution is to use an userspace patch in patch-o-matic, but Harald strongly disagrees with that and gets nautios when talking about them and says he will not include those patches.
Also you could use my patch, which applied on the netfilter tree, patches the libipt_REJECT.c and adds an item to patch-o-matic to patch the kernel module so you can use admin-prohib.
Note, that this patch has been done versus the old netfilter tree, when patch-o-matic was in userspace.
To avoid problems link the directories:
# ln -s patch-o-matic userspace/patch-o-matic while sitting in /netfilter.
http://dns.toxicfilms.tv/netfilter/admin_prohib.diff
This patch contains a partial solution to compatibility issues, but in this case, the issues come up with precompiled packages, and we're screwed again :(
If someone has and idea, how to put it all together in a clean and elegant way, please notify.
Best Regards,
Maciej Soltysiak
Mr. Krawczyk,
Quoted 6 lines · --- Pawe³ Krawczyk
Maybe it's my ignorance, but I feel that REJECT target --reject-with option is somewhat broken - you can set icmp-net-prohibited or host-prohibited ICMP replies, which are discouraged and obsoleted by RFC 1812, but you cannot use 0/13 ICMP (Admin prohibited), which is the one recommended by the RFC. Can anyone comment?
I can. I, and others, wrote patches to fix this problem, but they were rejected because Harald couldn't find one which didn't threaten to break userspace<->kernel synchroninity or introduce bugs or quirks into the behavior of iptables. If you need 0/13 ICMP packets in the REJECT target, I can send you an untested patch that will add it.
Quoted 5 lines
Signature · 3 lines
Pawe³ Krawczyk, Kraków, Poland http://echelon.pl/kravietz/ horses: http://kabardians.com/ crypto: http://ipsec.pl/
Brad
=====
Brad Chapman
Permanent e-mail: [email protected]
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
Quoted 5 lines · Pawe? Krawczyk
Maybe it's my ignorance, but I feel that REJECT target --reject-with option is somewhat broken - you can set icmp-net-prohibited or host-prohibited ICMP replies, which are discouraged and obsoleted by RFC 1812, but you cannot use 0/13 ICMP (Admin prohibited), which is the one recommended by the RFC. Can anyone comment?
please read the list archives. The problem is that adding a new different REJECT type is hurting binary compatibility between new iptables userspace command and old kernel.
Quoted 1 line
Pawe? Krawczyk, Kraków, Poland http://echelon.pl/kravietz/
Signature · 5 lines
Live long and prosper - Harald Welte / [email protected] http://www.gnumonks.org/ ============================================================================ "If this were a dictatorship, it'd be a heck of a lot easier, just so long as I'm the dictator." -- George W. Bush Dec 18, 2000