-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08 Aug 2003 10:22:32 -0400, Colburn wrote: > Very odd, in Service Configuration I had iptables checked, should they > not therefore have been "on" and started at bootup? I don't see any other reason why you would get the following: > Determining IP information for eth0 ... iptables: > No chain/target/match by that name failed, > Hostname: localhost.localdomain > iptables: Bad rule (does a matching rule exist in that chain?) Certainly, this is in "ifup eth0". The ifup script usually is protected against trying to insert rules when the firewall is not active (it checks whether the RH-Lokkit-0-50-INPUT chain is available). Did you modify it? The two iptables errors you get are reproducible upon executing the iptables commands in "ifup" when the firewall is disabled: # iptables -I RH-Lokkit-0-50-INPUT -m udp -s 0/0 --sport 53 -d 0/0 \ - --dport 1025:65535 -p udp -j ACCEPT iptables: No chain/target/match by that name # iptables -D RH-Lokkit-0-50-INPUT -m udp -s 0/0 --sport 53 -d 0/0 \ - --dport 1025:65535 -p udp -j ACCEPT iptables: Bad rule (does a matching rule exist in that chain?) > I ran both chkconfig iptables on and service iptables start > > FYI: The autosensing switch/hub light comes on during boot and when I > manually try to activate eth0 but still no activation. > > Where do I look next, please? This is separate from the iptables error. Those two iptables errors do not affect your network connectivity (they only punch a hole for DNS reply packets into the firewall). If you have problems with eth0 and your DHCP server, that is something different. Do you still see those iptables errors upon "ifup eth0"? - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/M7pc0iMVcrivHFQRAg3XAJ4lIcxPP5CG0AVpurCMcmRujMuxqwCfTnxx x2Ug7ZKl7XQLtTN7Q13wDqc= =EOX3 -----END PGP SIGNATURE----- -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
