there is a problem in the current kernel ... on the masquerading side ...
this might be your problem ... for the moment, the masquerading is broken
and this is required by drakgw ... 


>[EMAIL PROTECTED] (Francisco) writes:

> In my case the same computer with 9.0 in several partitions has perfect the 
> masquering, the 9.1 rc1 is in hdb13 and I can configure the masquering and 
> the shorewall, but:
> 
> Masquering: when I try to activate, it crashes hand send me again to the 
> mandrake control center for internet configurations
> 
> Shorewall: I select the options (activated ssh, ftp and cups) and OK; it seems 
> fine, but if I return to the shorewall configuration, nothing has been 
> recorded. Under 9.0 shorewall is runing fine.
> 
> 
> Francisco Alcaraz
> Murcia (Spain)
> 
> 
> 
> El Mi�rcoles, 26 de Febrero de 2003 22:45, Adam Williamson escribi�:
> > On Wed, 2003-02-26 at 20:57, Florin wrote:
> > > Hello again,
> > >
> > > eth1 should appear in the masq zone ... and not in the loc zone ... but
> > > then you need an older kernel in order to have your masquerading working
> > > because it's broken in the current kernel ... as I previously said.
> > > How come you have it duplicated ? ... I cannot reproduce that here ... I
> > > have 4 nics and they are not duplicated ...
> >
> > Additional: I just verified that if I do "urpme shorewall" and then "rm
> > -rf /etc/shorewall", so there's *no* existing shorewall configuration at
> > all, and then run drakgw (allowing it to install a fresh copy of
> > shorewall itself), it *still* generates an invalid
> > /etc/shorewall/interfaces file placing eth1 in both the loc and masq
> > zones. So it's not anything to do with the prior configuration of
> > shorewall.
> 
> 

-- 
Florin                  http://www.mandrakesoft.com
                        http://people.mandrakesoft.com/~florin/

Reply via email to