iptables forwarding not working/iptables-save not saving

[Antonio Olivares]

Dear fellow testers,

I am trying to setup a little dhcp server at school for my machines that my students use
at school.  Iptables is not saving :(

[root@localhost ~]# rpm -qa iptables*
iptables-1.4.1.1-2.fc10.i386
iptables-ipv6-1.4.1.1-2.fc10.i386


Thanks,

Antonio

[Rick Stevens]

Antonio Olivares wrote:
>  Dear fellow testers,
>  
>  I am trying to setup a little dhcp server at school for my machines that my students use
> at school.  Iptables is not saving :(
>  
>  [root@localhost ~]# rpm -qa iptables*
>  iptables-1.4.1.1-2.fc10.i386
>  iptables-ipv6-1.4.1.1-2.fc10.i386 
If you're using the iptables command to directly change your setup, you
have to use

	iptables-save >/etc/sysconfig/iptables

to save the current setup.  On boot, the system does an

	iptables-restore </etc/sysconfig/iptables

to restore those settings.  Or you can edit /etc/sysconfig/iptables
yourself directly and do a "service iptables restart" to make them
apply.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer                      ricks(a)nerd.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-           If it's stupid and it works...it ain't stupid!           -
----------------------------------------------------------------------

[Robin Laing]

Rick Stevens wrote:
>  Antonio Olivares wrote:
> > Dear fellow testers,
> >
> > I am trying to setup a little dhcp server at school for my machines 
> > that my students use at school.  Iptables is not saving :(
> >
> > [root@localhost ~]# rpm -qa iptables*
> > iptables-1.4.1.1-2.fc10.i386
> > iptables-ipv6-1.4.1.1-2.fc10.i386
>  
>  If you're using the iptables command to directly change your setup, you
>  have to use
>  
>      iptables-save >/etc/sysconfig/iptables
>  
>  to save the current setup.  On boot, the system does an
>  
>      iptables-restore </etc/sysconfig/iptables
>  
>  to restore those settings.  Or you can edit /etc/sysconfig/iptables
>  yourself directly and do a "service iptables restart" to make them
>  apply.
>  ----------------------------------------------------------------------
>  - Rick Stevens, Systems Engineer                      ricks(a)nerd.com -
>  - AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
>  -                                                                    -
>  -           If it's stupid and it works...it ain't stupid!           -
>  ----------------------------------------------------------------------
>   
Man, I wish I had seen this post last month when I was fighting with 
iptables.

Thank you.

-- 
Robin Laing

[mike cloaked]

Rick Stevens-3 wrote:
>  
>  
>  If you're using the iptables command to directly change your setup, you
>  have to use
>  
>  	iptables-save >/etc/sysconfig/iptables
>  
>  to save the current setup.  On boot, the system does an
>  
>  	iptables-restore </etc/sysconfig/iptables
>  
>  to restore those settings.  Or you can edit /etc/sysconfig/iptables
>  
>   
Previously 
service iptables save
used to work  - does this not work for the newest systems?

-- 
View this message in context:
http://www.nabble.com/iptables-forwarding-not-working-iptables-save-not-s...
Sent from the Fedora Test List mailing list archive at Nabble.com.

[Mads Kiilerich]

Mike Cloaked wrote:
>  Rick Stevens-3 wrote:
>    
> > If you're using the iptables command to directly change your setup, you
> > have to use
> >
> > 	iptables-save >/etc/sysconfig/iptables
> >
> > to save the current setup.  On boot, the system does an
> >
> > 	iptables-restore </etc/sysconfig/iptables
> >
> > to restore those settings.  Or you can edit /etc/sysconfig/iptables
> >     
>  Previously 
>  service iptables save
>  used to work  - does this not work for the newest systems?
>     
Yes, it works, and it plays tricks with storing temporarily in 
/etc/sysconfig/iptables.save to get the selinux domains rights. If it 
doesn't work then ... something is broken ;-)

Redirecting directly as described above doesn't work with selinux.

/Mads