Description of problem: There is a error when add rules on arptables when use Request, Reply, ... alias Request should be 0001 (not 0100), Reply should be 0002 (not 0200). Version-Release number of selected component (if applicable): the current version on RHEL3 is 0.0.7-0.3E # rpm -qa|grep arptables_jf arptables_jf-0.0.7-0.3E How reproducible: Add a rule using options alias, example: arptables -A IN --target 172.16.20.14 --arpop Request -j DROP arptables -L -vn where say 0100 should be 0001 Then when I enter arptables -A IN --target 172.16.20.14 --arpop 0001 -j DROP the rules is added correctly, but if I save the rules with arptables-save > /etc/sysconfig/arptables and reboot the machine the rules are restored incorrectly, with option 0100. Steps to Reproduce: 1. arptables -A IN --target 172.16.20.14 --arpop Request -j DROP 2. arptables -L -vn 3. Where arp options say 0100 shold be 0001 Actual results: Chain IN (policy ACCEPT 345 packets, 9660 bytes) pkts bytes target in out source-ip destination-ip source-hw destination-hw hlen op hrd pro 0 0 DROP * * 0.0.0.0/0 10.1.209.10 00/00 00/00 any 0100 0000/0000 0000/0000 Expected results: Chain IN (policy ACCEPT 345 packets, 9660 bytes) pkts bytes target in out source-ip destination-ip source-hw destination-hw hlen op hrd pro 0 0 DROP * * 0.0.0.0/0 10.1.209.10 00/00 00/00 any 0001 0000/0000 0000/0000 Additional info: # uname -a Linux efbp1.sefaz.pe.gov.br 2.4.21-47.EL #1 Wed Jul 5 20:46:55 EDT 2006 i686 i686 i386 GNU/Linux All errata updates was applied on this machine.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.