On Sun, 5 May 2002, Amir Tal wrote: > On Saturday 04 May 2002 20:54, Guy Cohen wrote: > > What shows lsmod? > > problem solved. > looks like ipchains was also running, and it interuppted iptables.
the "service" ipchains probably ran 'modprobe ipchains' which loaded the module 'ipchains'. On kernel 2.4 this module is an emulation done by the iptables module. Therefore the iptables module was used by the ipchains module. lsmod would have shown that. > i did : > > /sbin/chkconfig --del ipchains > /sbin/service ipchains stop The following two were not necessary, but it is probably a good practice. > /sbin/modprobe -r ipchains > > then : > > /sbin/chkconfig --levels 2345 iptables on > > and then re-loaded iptables : > > /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE > > all works fine now.;) You should note that chkconfig has no immediate effect. chkconfig does two things (on my mandrake system): 1. manipulates the symlinks in /etc/rc?.d/ These symlinks are used by the sysv-style init process to determain which "services" to start when you switch to a certain runlevel (and this normally only happens on boot time 2. enable/disable xinetd services by editing the line ' enable=[onn|off]' in /etc/xinet.d/* This takes effect the next time you "reload" the xinetd service (send it SIGHUP) or start it. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
