[Cooker] drakgw

2003-03-11 Thread Florin
Hello,

I've made a small modification to the /usr/sbin/drakgw file:

1. manual modifications
the line 
if_(@cards > 1, loc_interface => [ grep { $_ ne $device } @cards ]),

has to be replaced with 

loc_interface => [ grep { $_ ne $device } @cards ],

and the line 
my $internal_domain_name =
network::network::read_dhcpd_conf()->{domain_name}[0] ||=
network::network::read_resolv_conf_raw()->{nameserver}[0] ||=
"homeland.net";

has to be replace with 

my $internal_domain_name = network::network::read_dhcpd_conf()->{domain_name}[0] ||= 
network::network::read_resolv_conf_raw()->{search}[0] ||= "homeland.net";

2. or get the latest drakgw file from:

http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/gi/perl-install/standalone/drakgw

3. or wait and get the latest drakxtools-newt package

hope it helps,
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/



Re: [Cooker] drakgw and the latest iptables

2003-02-28 Thread J.P. Pasnak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On February 28, 2003 08:55 am, Adam Williamson wrote:
> On Fri, 2003-02-28 at 14:36, J.P. Pasnak wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On February 27, 2003 08:42 am, Florin wrote:
> > > A simple rebuild of the iptables package fixes the masquerading
> > > problem ...
> > > make sure you get the latest iptables package and you won't get
> > > the invalid command error message with the latest kernel ...
> >
> > Is it just me or did iptables-1.2.7a-2mdk not hit any of the
> > mirrors?
>
> The .src.rpm did. Which is ironic =). I just grabbed that and rebuilt
> it.

Thanks.   Thought I was going crazy

- -- 
Live fast, die young,
you're sucking up my bandwidth.
- --
J.P. Pasnak, CD
CCNA
[EMAIL PROTECTED]
http://www.warpedsystems.sk.ca

 Kernel version: 2.4.21pre4-6mdk
Current Linux uptime: 18 hours 59 minutes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+X6CRBMRgzmzdk08RAsNrAKDYuy7ztaBY0ZzJffCwxhQUQI0vkQCgng5n
p43TQ5fIp0ApnDOPpx5shWM=
=NB0k
-END PGP SIGNATURE-




Re: [Cooker] drakgw and the latest iptables

2003-02-28 Thread Adam Williamson
On Fri, 2003-02-28 at 14:36, J.P. Pasnak wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On February 27, 2003 08:42 am, Florin wrote:
> > A simple rebuild of the iptables package fixes the masquerading
> > problem ...
> > make sure you get the latest iptables package and you won't get the
> > invalid command error message with the latest kernel ...
> 
> Is it just me or did iptables-1.2.7a-2mdk not hit any of the mirrors?

The .src.rpm did. Which is ironic =). I just grabbed that and rebuilt
it.
-- 
adamw




Re: [Cooker] drakgw and the latest iptables

2003-02-28 Thread J.P. Pasnak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On February 27, 2003 08:42 am, Florin wrote:
> A simple rebuild of the iptables package fixes the masquerading
> problem ...
> make sure you get the latest iptables package and you won't get the
> invalid command error message with the latest kernel ...

Is it just me or did iptables-1.2.7a-2mdk not hit any of the mirrors?
- -- 
Live fast, die young,
you're sucking up my bandwidth.
- --
J.P. Pasnak, CD
CCNA
[EMAIL PROTECTED]
http://www.warpedsystems.sk.ca

 Kernel version: 2.4.21pre4-6mdk
Current Linux uptime: 15 hours 48 minutes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+X3PuBMRgzmzdk08RAuZiAJ9z7rWwR4TYUICCGQG1JYHycXPJxwCgnWaQ
h70XQzWrmvEkGXRpOPfPpPM=
=0s7D
-END PGP SIGNATURE-




Re: [Cooker] drakgw and the latest iptables

2003-02-27 Thread J.P. Pasnak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On February 27, 2003 08:42 am, Florin wrote:
> A simple rebuild of the iptables package fixes the masquerading
> problem ...
> make sure you get the latest iptables package and you won't get the
> invalid command error message with the latest kernel ...

Excellent!   I'll give it a burst...
- -- 
Live fast, die young,
you're sucking up my bandwidth.
- --
J.P. Pasnak, CD
CCNA
[EMAIL PROTECTED]
http://www.warpedsystems.sk.ca

 Kernel version: 2.4.21pre4-6mdk
Current Linux uptime: 15 hours 0 minutes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+XjNyBMRgzmzdk08RAhYtAKCCcj/sRWR2h09MHa1v0+qUT/RXxwCggj6H
Pi0tD0LizIZv123a1SN8gQU=
=7Fih
-END PGP SIGNATURE-




[Cooker] drakgw and the latest iptables

2003-02-27 Thread Florin

A simple rebuild of the iptables package fixes the masquerading problem
...
make sure you get the latest iptables package and you won't get the
invalid command error message with the latest kernel ... 
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-27 Thread Florin

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/



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Francisco
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.




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Adam Williamson
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.
-- 
adamw




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Adam Williamson
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.

Yes, I agree. Basically, the bug is: for some reason, with my setup,
drakgw is generating a "loc eth1 detect" line in
/etc/shorewall/interfaces which it shouldn't be. The masquerading stuff
is unrelated, as you say. To be happy, I'd want current Cooker tested on
a setup which matches mine exactly: yours doesn't because, as you say,
you have four NICs :). Unfortunately this is my main working system and
I can't afford the inconvenience and wasted time of installing Cooker
from scratch on them, and I don't have any spare disk space to do a
fresh installation without wiping my current one. Otherwise I'd do this
test myself.

> How come you have it duplicated ? ... I cannot reproduce that here ... I
> have 4 nics and they are not duplicated ...  

I DON'T KNOW!!! That's the whole bug! That's what I've been going on
about for days! :). I *WANT* to know why drakgw is generating the loc
entry. It shouldn't be.

> Drakgw displays your Nics ? which ones ? and what do you select ?
> is this the automatic drakgw configuration or the expert mode one (this is 
> what I have chosen) ...

drakgw correctly detects that only my eth1 interface faces the local
network, and configures it. Whether I choose automatic or expert mode
doesn't matter, it generates the same faulty /etc/shorewall/interfaces
file.
-- 
adamw




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Florin

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 ...  

Drakgw displays your Nics ? which ones ? and what do you select ?
is this the automatic drakgw configuration or the expert mode one (this is 
what I have chosen) ...


>[EMAIL PROTECTED] (Adam Williamson) writes:

> On Wed, 2003-02-26 at 19:13, Florin wrote:
> > 1. what about /etc/sysconfig/network ?
> > 2. what about /etc/sysconfig/network-scripts/net_cnx_up ?
> > 3. ifconfig ?
> > 4. route -n ?
> > 5. grep -v ^# /etc/shorewall/{zones,interfaces,masq,policy,rules} |grep -v $^ 
> 
> 1:
> 
> HOSTNAME=aw280.pem.cam.ac.uk
> NETWORKING=yes
> DOMAINNAME=pem.cam.ac.uk
> GATEWAY=131.111.201.62
> GATEWAYDEV=eth0
> FORWARD_IPV4=true
> 
> 2:
> 
> #!/bin/bash
> if [ "x$1" == "x--boot_time" ]; then exit; fi
>  
> /etc/rc.d/init.d/network restart
> 
> 3:
> 
> eth0  Link encap:Ethernet  HWaddr 00:04:5A:5C:72:9D
>   inet addr:131.111.201.49  Bcast:131.111.255.255 
> Mask:255.255.0.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:400167 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:79020 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:100
>   RX bytes:237563999 (226.5 Mb)  TX bytes:7361449 (7.0 Mb)
>   Interrupt:10 Base address:0xcc00
>  
> eth1  Link encap:Ethernet  HWaddr 00:05:1C:09:44:E9
>   inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:9303 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:39202 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:66 txqueuelen:100
>   RX bytes:866614 (846.3 Kb)  TX bytes:56923030 (54.2 Mb)
>   Interrupt:12 Base address:0xd400
>  
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   UP LOOPBACK RUNNING  MTU:16436  Metric:1
>   RX packets:1355 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:1355 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:167924 (163.9 Kb)  TX bytes:167924 (163.9 Kb)
> 
> 4:
> 
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
> eth1
> 131.111.0.0 0.0.0.0 255.255.0.0 U 0  00
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0  00
> eth0
> 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
> lo
> 0.0.0.0 131.111.201.62  0.0.0.0 UG0  00
> eth0
> 
> (I don't know what the 169.254.0.0 stuff is doing there...)
> 
> 5:
> 
> /etc/shorewall/zones:netNet Internet zone
> /etc/shorewall/zones:locLocal   Local
> /etc/shorewall/interfaces:net   eth0detect
> /etc/shorewall/interfaces:loc   eth1detect
> /etc/shorewall/policy:loc   net ACCEPT
> /etc/shorewall/policy:fwnet ACCEPT
> /etc/shorewall/policy:net   all DROPinfo
> /etc/shorewall/policy:all   all REJECT  info
> /etc/shorewall/rules:ACCEPT net fw  tcp 22  -
> /etc/shorewall/rules:ACCEPT loc fw  tcp 22  -
> 
> (that's before I attempt to setup internet connection sharing, let me
> know if you want the output after I attempt to set it up).
> 
> As noted in private emails, if I remove one of the duplicate lines in
> /etc/shorewall/interfaces - the one which makes eth1 a member of loc,
> just leaving the one which makes it a member of masq - shorewall startup
> proceeds to a much later point then dies because an iptables command
> isn't correctly completed, which seems to be the bug you mentioned
> getting.

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



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Adam Williamson
On Wed, 2003-02-26 at 19:13, Florin wrote:
> 1. what about /etc/sysconfig/network ?
> 2. what about /etc/sysconfig/network-scripts/net_cnx_up ?
> 3. ifconfig ?
> 4. route -n ?
> 5. grep -v ^# /etc/shorewall/{zones,interfaces,masq,policy,rules} |grep -v $^ 

1:

HOSTNAME=aw280.pem.cam.ac.uk
NETWORKING=yes
DOMAINNAME=pem.cam.ac.uk
GATEWAY=131.111.201.62
GATEWAYDEV=eth0
FORWARD_IPV4=true

2:

#!/bin/bash
if [ "x$1" == "x--boot_time" ]; then exit; fi
 
/etc/rc.d/init.d/network restart

3:

eth0  Link encap:Ethernet  HWaddr 00:04:5A:5C:72:9D
  inet addr:131.111.201.49  Bcast:131.111.255.255 
Mask:255.255.0.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:400167 errors:0 dropped:0 overruns:0 frame:0
  TX packets:79020 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100
  RX bytes:237563999 (226.5 Mb)  TX bytes:7361449 (7.0 Mb)
  Interrupt:10 Base address:0xcc00
 
eth1  Link encap:Ethernet  HWaddr 00:05:1C:09:44:E9
  inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:9303 errors:0 dropped:0 overruns:0 frame:0
  TX packets:39202 errors:0 dropped:0 overruns:0 carrier:0
  collisions:66 txqueuelen:100
  RX bytes:866614 (846.3 Kb)  TX bytes:56923030 (54.2 Mb)
  Interrupt:12 Base address:0xd400
 
loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:1355 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1355 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:167924 (163.9 Kb)  TX bytes:167924 (163.9 Kb)

4:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
eth1
131.111.0.0 0.0.0.0 255.255.0.0 U 0  00
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0  00
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
lo
0.0.0.0 131.111.201.62  0.0.0.0 UG0  00
eth0

(I don't know what the 169.254.0.0 stuff is doing there...)

5:

/etc/shorewall/zones:netNet Internet zone
/etc/shorewall/zones:locLocal   Local
/etc/shorewall/interfaces:net   eth0detect
/etc/shorewall/interfaces:loc   eth1detect
/etc/shorewall/policy:loc   net ACCEPT
/etc/shorewall/policy:fwnet ACCEPT
/etc/shorewall/policy:net   all DROPinfo
/etc/shorewall/policy:all   all REJECT  info
/etc/shorewall/rules:ACCEPT net fw  tcp 22  -
/etc/shorewall/rules:ACCEPT loc fw  tcp 22  -

(that's before I attempt to setup internet connection sharing, let me
know if you want the output after I attempt to set it up).

As noted in private emails, if I remove one of the duplicate lines in
/etc/shorewall/interfaces - the one which makes eth1 a member of loc,
just leaving the one which makes it a member of masq - shorewall startup
proceeds to a much later point then dies because an iptables command
isn't correctly completed, which seems to be the bug you mentioned
getting.
-- 
adamw




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Florin

1. what about /etc/sysconfig/network ?
2. what about /etc/sysconfig/network-scripts/net_cnx_up ?
3. ifconfig ?
4. route -n ?
5. grep -v ^# /etc/shorewall/{zones,interfaces,masq,policy,rules} |grep -v $^ 

>Adam Williamson <[EMAIL PROTECTED]> writes:

> On Wed, 2003-02-26 at 14:00, Florin wrote:
> > drakgw assumes that you have configured your network with drakconnect and
> > parses the /etc/sysconfig/network-scripts/net_cnx_up files in order to
> > detect the net interface ... maybe this is not your case ...
> > 
> > Also, during the drakconnect setup, make sure you have chosen the right
> > gateway interface ... In my case, the "right" gateway interface is eth1,
> > but drakconnect has eth0 as default ... one might leave it as it is ...
> > and this not what one wants ...
> 
> Yes, I configured with drakconnect. The gateway device is eth0, the NIC
> which is connected to the college network, which is correct.
> 
> ifcfg-eth0 reads:
> 
> DEVICE=eth0
> BOOTPROTO=static
> IPADDR=131.111.201.49
> NETMASK=255.255.0.0
> NETWORK=131.111.0.0
> BROADCAST=131.111.255.255
> ONBOOT=yes
> NEEDHOSTNAME=yes
> 
> ifcfg-eth1 reads:
> 
> DEVICE=eth1
> BOOTPROTO=static
> IPADDR=192.168.1.1
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> BROADCAST=192.168.1.255
> ONBOOT=yes

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



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Adam Williamson
On Wed, 2003-02-26 at 14:00, Florin wrote:
> drakgw assumes that you have configured your network with drakconnect and
> parses the /etc/sysconfig/network-scripts/net_cnx_up files in order to
> detect the net interface ... maybe this is not your case ...
> 
> Also, during the drakconnect setup, make sure you have chosen the right
> gateway interface ... In my case, the "right" gateway interface is eth1,
> but drakconnect has eth0 as default ... one might leave it as it is ...
> and this not what one wants ...

Yes, I configured with drakconnect. The gateway device is eth0, the NIC
which is connected to the college network, which is correct.

ifcfg-eth0 reads:

DEVICE=eth0
BOOTPROTO=static
IPADDR=131.111.201.49
NETMASK=255.255.0.0
NETWORK=131.111.0.0
BROADCAST=131.111.255.255
ONBOOT=yes
NEEDHOSTNAME=yes

ifcfg-eth1 reads:

DEVICE=eth1
BOOTPROTO=static
IPADDR=192.168.1.1
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes
-- 
adamw




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Florin

drakgw assumes that you have configured your network with drakconnect and
parses the /etc/sysconfig/network-scripts/net_cnx_up files in order to
detect the net interface ... maybe this is not your case ...

Also, during the drakconnect setup, make sure you have chosen the right
gateway interface ... In my case, the "right" gateway interface is eth1,
but drakconnect has eth0 as default ... one might leave it as it is ...
and this not what one wants ...

>Adam Williamson <[EMAIL PROTECTED]> writes:

> On Wed, 2003-02-26 at 13:02, Florin wrote:
> 
> > > Well could you set your test setup up like mine - one machine with two
> > > NICs and a network internet connection, and one machine with one NIC
> > > connected to it - and send me the /etc/shorewall/interfaces file it
> > > generates, for comparison? It's good to know it works on a fresh Cooker,
> > > but I want to know what's going wrong on my setup, because it ought to
> > > work.
> > 
> > [EMAIL PROTECTED] root]# grep -v ^# 
> > /etc/shorewall/{zones,interfaces,masq,policy,rules} |grep -v ^$ 
> > 
> > /etc/shorewall/zones:netNet Internet zone
> > /etc/shorewall/zones:masq   Masquerade  Masquerade Local
> > /etc/shorewall/zones:locLocal   Local
> > 
> > /etc/shorewall/interfaces:net   eth1detect
> > /etc/shorewall/interfaces:masq  eth0detect
> > /etc/shorewall/interfaces:loc   eth2detect
> > /etc/shorewall/interfaces:loc   eth3detect
> > 
> > /etc/shorewall/masq:eth110.0.0.0/255.255.255.0 -> This is my
> > masqueraded network
> > 
> > /etc/shorewall/policy:masq  net ACCEPT
> > /etc/shorewall/policy:loc   net ACCEPT
> > /etc/shorewall/policy:fwnet ACCEPT
> > /etc/shorewall/policy:net   all DROPinfo
> > /etc/shorewall/policy:all   all REJECT  info
> > 
> > /etc/shorewall/rules:ACCEPT net fw  tcp 22,6566 -
> > /etc/shorewall/rules:ACCEPT masqfw  tcp 22,6566 -
> > /etc/shorewall/rules:ACCEPT loc fw  tcp 22,6566 -
> > /etc/shorewall/rules:ACCEPT masqfw  tcp 
> > domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp   -
> > /etc/shorewall/rules:ACCEPT masqfw  udp 
> > domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp   -
> > /etc/shorewall/rules:ACCEPT fw  masqtcp 631,515,137,138,139 -
> > /etc/shorewall/rules:ACCEPT fw  masqudp 631,515,137,138,139 -
> > 
> > hope this helps,
> 
> Thanks Florin. I think I'll run drakgw and then try taking out each of
> the duplicate eth1 lines in turn and see if doing that fixes it. I'd
> still love to know why they're being generated, though.

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



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Adam Williamson
On Wed, 2003-02-26 at 13:02, Florin wrote:

> > Well could you set your test setup up like mine - one machine with two
> > NICs and a network internet connection, and one machine with one NIC
> > connected to it - and send me the /etc/shorewall/interfaces file it
> > generates, for comparison? It's good to know it works on a fresh Cooker,
> > but I want to know what's going wrong on my setup, because it ought to
> > work.
> 
> [EMAIL PROTECTED] root]# grep -v ^# 
> /etc/shorewall/{zones,interfaces,masq,policy,rules} |grep -v ^$ 
> 
> /etc/shorewall/zones:netNet Internet zone
> /etc/shorewall/zones:masq   Masquerade  Masquerade Local
> /etc/shorewall/zones:locLocal   Local
> 
> /etc/shorewall/interfaces:net   eth1detect
> /etc/shorewall/interfaces:masq  eth0detect
> /etc/shorewall/interfaces:loc   eth2detect
> /etc/shorewall/interfaces:loc   eth3detect
> 
> /etc/shorewall/masq:eth110.0.0.0/255.255.255.0 -> This is my
> masqueraded network
> 
> /etc/shorewall/policy:masq  net ACCEPT
> /etc/shorewall/policy:loc   net ACCEPT
> /etc/shorewall/policy:fwnet ACCEPT
> /etc/shorewall/policy:net   all DROPinfo
> /etc/shorewall/policy:all   all REJECT  info
> 
> /etc/shorewall/rules:ACCEPT net fw  tcp 22,6566 -
> /etc/shorewall/rules:ACCEPT masqfw  tcp 22,6566 -
> /etc/shorewall/rules:ACCEPT loc fw  tcp 22,6566 -
> /etc/shorewall/rules:ACCEPT masqfw  tcp 
> domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp   -
> /etc/shorewall/rules:ACCEPT masqfw  udp 
> domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp   -
> /etc/shorewall/rules:ACCEPT fw  masqtcp 631,515,137,138,139 -
> /etc/shorewall/rules:ACCEPT fw  masqudp 631,515,137,138,139 -
> 
> hope this helps,

Thanks Florin. I think I'll run drakgw and then try taking out each of
the duplicate eth1 lines in turn and see if doing that fixes it. I'd
still love to know why they're being generated, though.
-- 
adamw




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-26 Thread Florin
[EMAIL PROTECTED] (Adam Williamson) writes:

> On Tue, 2003-02-25 at 19:05, Florin wrote:
> > Adam Williamson <[EMAIL PROTECTED]> writes:
> > 
> > > On Tue, 2003-02-25 at 18:10, Florin wrote:
> > > > Hi there,
> > > > 
> > > > it seems that the latest kernel has its masqueranding broken ... the
> > > > shorewall-> drakgw is therefore broken with a invalid command error
> > > > message ...
> > > 
> > > Hey Florin...does this have any bearing on my drakgw problem? Have you
> > > followed it up any further since I sent you my /etc/shorewall stuff
> > > yesterday?
> > 
> > Yes, I have installed a brand new cooker especially for these matters ...
> > 
> > I've just installed a new cooker here and it works on my 4-NICs test
> > machine ... network Internet connection ...
> > 
> > run shorewall restart in a terminal and you should get invalid command
> > after the masqueranding stuff ...
> > 
> > hope it helps ...
> 
> Well could you set your test setup up like mine - one machine with two
> NICs and a network internet connection, and one machine with one NIC
> connected to it - and send me the /etc/shorewall/interfaces file it
> generates, for comparison? It's good to know it works on a fresh Cooker,
> but I want to know what's going wrong on my setup, because it ought to
> work.

[EMAIL PROTECTED] root]# grep -v ^# 
/etc/shorewall/{zones,interfaces,masq,policy,rules} |grep -v ^$ 

/etc/shorewall/zones:netNet Internet zone
/etc/shorewall/zones:masq   Masquerade  Masquerade Local
/etc/shorewall/zones:locLocal   Local

/etc/shorewall/interfaces:net   eth1detect
/etc/shorewall/interfaces:masq  eth0detect
/etc/shorewall/interfaces:loc   eth2detect
/etc/shorewall/interfaces:loc   eth3detect

/etc/shorewall/masq:eth110.0.0.0/255.255.255.0 -> This is my
masqueraded network

/etc/shorewall/policy:masq  net ACCEPT
/etc/shorewall/policy:loc   net ACCEPT
/etc/shorewall/policy:fwnet ACCEPT
/etc/shorewall/policy:net   all DROPinfo
/etc/shorewall/policy:all   all REJECT  info

/etc/shorewall/rules:ACCEPT net fw  tcp 22,6566 -
/etc/shorewall/rules:ACCEPT masqfw  tcp 22,6566 -
/etc/shorewall/rules:ACCEPT loc fw  tcp 22,6566 -
/etc/shorewall/rules:ACCEPT masqfw  tcp 
domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp   -
/etc/shorewall/rules:ACCEPT masqfw  udp 
domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp   -
/etc/shorewall/rules:ACCEPT fw  masqtcp 631,515,137,138,139 -
/etc/shorewall/rules:ACCEPT fw  masqudp 631,515,137,138,139 -

hope this helps,
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-25 Thread Adam Williamson
On Tue, 2003-02-25 at 19:05, Florin wrote:
> Adam Williamson <[EMAIL PROTECTED]> writes:
> 
> > On Tue, 2003-02-25 at 18:10, Florin wrote:
> > > Hi there,
> > > 
> > > it seems that the latest kernel has its masqueranding broken ... the
> > > shorewall-> drakgw is therefore broken with a invalid command error
> > > message ...
> > 
> > Hey Florin...does this have any bearing on my drakgw problem? Have you
> > followed it up any further since I sent you my /etc/shorewall stuff
> > yesterday?
> 
> Yes, I have installed a brand new cooker especially for these matters ...
> 
> I've just installed a new cooker here and it works on my 4-NICs test
> machine ... network Internet connection ...
> 
> run shorewall restart in a terminal and you should get invalid command
> after the masqueranding stuff ...
> 
> hope it helps ...

Well could you set your test setup up like mine - one machine with two
NICs and a network internet connection, and one machine with one NIC
connected to it - and send me the /etc/shorewall/interfaces file it
generates, for comparison? It's good to know it works on a fresh Cooker,
but I want to know what's going wrong on my setup, because it ought to
work.
-- 
adamw




Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-25 Thread J.P. Pasnak

Florin said:

> Adam Williamson <[EMAIL PROTECTED]> writes:
>
>> On Tue, 2003-02-25 at 18:10, Florin wrote:
>> > Hi there,
>> >
>> > it seems that the latest kernel has its masqueranding broken ... the
>> > shorewall-> drakgw is therefore broken with a invalid command error
>> > message ...
>>
>> Hey Florin...does this have any bearing on my drakgw problem? Have you
>> followed it up any further since I sent you my /etc/shorewall stuff
>> yesterday?
>
>
> run shorewall restart in a terminal and you should get invalid command
> after the masqueranding stuff ...

Doing:

#shorewall debug start 2> /tmp/trace

would appear to confirm a problem with MASQUERADE, but it appears to load
and reload just fine

-- 
Live fast, die young,
You're sucking up my bandwidth.

J.P. Pasnak, CD
CCNA
http://www.warpedsystems.sk.ca



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-25 Thread Florin
Florin <[EMAIL PROTECTED]> writes:

> Adam Williamson <[EMAIL PROTECTED]> writes:
> 
> > On Tue, 2003-02-25 at 18:10, Florin wrote:
> > > Hi there,
> > > 
> > > it seems that the latest kernel has its masqueranding broken ... the
> > > shorewall-> drakgw is therefore broken with a invalid command error
> > > message ...
> > 
> > Hey Florin...does this have any bearing on my drakgw problem? Have you
> > followed it up any further since I sent you my /etc/shorewall stuff
> > yesterday?
> 
> Yes, I have installed a brand new cooker especially for these matters ...
> 
> I've just installed a new cooker here and it works on my 4-NICs test
> machine ... network Internet connection ...
> 
> run shorewall restart in a terminal and you should get invalid command
> after the masqueranding stuff ...
> 
> hope it helps ...


it worked after I changed the kernel ... and installed a 9.0 one ... no
more invalid error messages ...
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-25 Thread Florin
Adam Williamson <[EMAIL PROTECTED]> writes:

> On Tue, 2003-02-25 at 18:10, Florin wrote:
> > Hi there,
> > 
> > it seems that the latest kernel has its masqueranding broken ... the
> > shorewall-> drakgw is therefore broken with a invalid command error
> > message ...
> 
> Hey Florin...does this have any bearing on my drakgw problem? Have you
> followed it up any further since I sent you my /etc/shorewall stuff
> yesterday?

Yes, I have installed a brand new cooker especially for these matters ...

I've just installed a new cooker here and it works on my 4-NICs test
machine ... network Internet connection ...

run shorewall restart in a terminal and you should get invalid command
after the masqueranding stuff ...

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



Re: [Cooker] drakgw, shorewall and the latest kernel

2003-02-25 Thread Adam Williamson
On Tue, 2003-02-25 at 18:10, Florin wrote:
> Hi there,
> 
> it seems that the latest kernel has its masqueranding broken ... the
> shorewall-> drakgw is therefore broken with a invalid command error
> message ...

Hey Florin...does this have any bearing on my drakgw problem? Have you
followed it up any further since I sent you my /etc/shorewall stuff
yesterday?
-- 
adamw




[Cooker] drakgw, shorewall and the latest kernel

2003-02-25 Thread Florin
Hi there,

it seems that the latest kernel has its masqueranding broken ... the
shorewall-> drakgw is therefore broken with a invalid command error
message ...
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/



Re: [Cooker] drakgw dosn't works on a fresh cooker install

2002-12-31 Thread Florent BERANGER
can you reproduce this bug ? 
When do you think it'll be fixed ? 
Thx, 
  Florent 
 
Selon Florent BERANGER <[EMAIL PROTECTED]>: 
 
> Here the logs when I try to (re)configure the Internet connection sharing  
> (doesn't seem to works fine) :  
>   
> [root@cosmic cosmicflo]# drakgw  
> Use of uninitialized value in numeric eq (==) at  
> /usr/lib/libDrakX/interactive.pm line 303 (#1)  
> (W uninitialized) An undefined value was used as if it were already  
> defined.  It was interpreted as a "" or a 0, but maybe it was a mistake. 
>  
> To suppress this warning assign a defined value to your variables.  
>   
> To help you figure out what was undefined, perl tells you what operation 
>  
> you used the undefined value in.  Note, however, that perl optimizes 
your 
>  
> program and the operation displayed in the warning may not necessarily  
> appear literally in your program.  For example, "that $foo" is  
> usually optimized into "that " . $foo, and the warning will refer to  
> the concatenation (.) operator, even though there is no . in your  
> program.  
>   
> TODO: XSetInputFocus if force_focus  
> TODO: ensure focus stuff  
> Use of uninitialized value in numeric gt (>) at  
> /usr/lib/perl5/vendor_perl/5.8.0/MDK/Common/Math.pm line 133 (#1)  
> Use of uninitialized value in split at  
> /usr/lib/perl5/vendor_perl/5.8.0/MDK/Common/String.pm line 138 (#1) 
>  
> TODO: XSetInputFocus if force_focus  
> TODO: ensure focus stuff  
> Use of uninitialized value in subtraction (-) at  
> /usr/lib/libDrakX/interactive/gtk.pm line 533 (#1)  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/netconnect.pm line 563 (#1)  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/netconnect.pm line 565 (#1)  
> Use of uninitialized value in string ne at /usr/sbin/drakgw line 205 (#1)  
> TODO: XSetInputFocus if force_focus  
> TODO: ensure focus stuff  
> Use of uninitialized value in string eq at /usr/lib/libDrakX/interactive.pm 
>  
> line 266 (#1)  
> TODO: XSetInputFocus if force_focus  
> TODO: ensure focus stuff  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 19 (#1)  
> TODO: XSetInputFocus if force_focus  
> TODO: ensure focus stuff  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 41 (#1)  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 41, <> line 14 (#1)  
> Use of uninitialized value in join or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 36, <> line 147 (#1)  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 41, <> line 147 (#1)  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 41, <> line 53 (#1)  
> Use of uninitialized value in concatenation (.) or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 41, <> line 189 (#1)  
> Use of uninitialized value in join or string at  
> /usr/lib/libDrakX/network/shorewall.pm line 36, <> line 87 (#1)  
> Le service shorewall n'est pas pris en charge par chkconfig  
>Warning: Zone loc is empty  
>Error: Unknown interface 192.168.1.0/255.255.255.0  
> /sbin/service: line 148:  2671 Terminated  $debug  
> $servicedir/$service $options  
> Arrêt de dhcpd :[  OK  ]  
> Arrêt de named :[  OK  ]  
> SIOCDELRT: No such process  
>Warning: Zone loc is empty  
>Error: Unknown interface 192.168.1.0/255.255.255.0  
>Warning: Zone loc is empty  
>Error: Unknown interface 192.168.1.0/255.255.255.0  
> Le service shorewall n'est pas pris en charge par chkconfig  
> TODO: XSetInputFocus if force_focus  
> TODO: ensure focus stuff  
> Use of uninitialized value in subtraction (-) at  
> /usr/lib/libDrakX/interactive/gtk.pm line 533, <> line 1 (#1)  
> Use of uninitialized value in split at  
> /usr/lib/perl5/vendor_perl/5.8.0/MDK/Common/String.pm line 138, <>  
> line 1 (#1)  
> [root@cosmic cosmicflo]#  
>   
>   
> When I try to activate the connection sharing (it's doesn't works but 
without 
>  
> error message for the user ( :(  ),it's always desactivated after) :  
>   
> [root@cosmic cosmicflo]# drakgw  
> Use of uninitialized value in numeric eq (==) at  
> /usr/lib/libDrakX/interactive.pm line 303 (#1)  
> (W uninitialized) An undefined value was used as if it were already  
> defined.  It was interpreted as a "" or a 0, but maybe it was a mistake. 
>  
> To suppress this warning assign a defined value to your variables.  
>   
> T

[Cooker] drakgw dosn't works on a fresh cooker install

2002-12-31 Thread Florent BERANGER
Here the logs when I try to (re)configure the Internet connection sharing 
(doesn't seem to works fine) : 
 
[root@cosmic cosmicflo]# drakgw 
Use of uninitialized value in numeric eq (==) at 
/usr/lib/libDrakX/interactive.pm line 303 (#1) 
(W uninitialized) An undefined value was used as if it were already 
defined.  It was interpreted as a "" or a 0, but maybe it was a mistake. 
To suppress this warning assign a defined value to your variables. 
 
To help you figure out what was undefined, perl tells you what operation 
you used the undefined value in.  Note, however, that perl optimizes your 
program and the operation displayed in the warning may not necessarily 
appear literally in your program.  For example, "that $foo" is 
usually optimized into "that " . $foo, and the warning will refer to 
the concatenation (.) operator, even though there is no . in your 
program. 
 
TODO: XSetInputFocus if force_focus 
TODO: ensure focus stuff 
Use of uninitialized value in numeric gt (>) at 
/usr/lib/perl5/vendor_perl/5.8.0/MDK/Common/Math.pm line 133 (#1) 
Use of uninitialized value in split at 
/usr/lib/perl5/vendor_perl/5.8.0/MDK/Common/String.pm line 138 (#1) 
TODO: XSetInputFocus if force_focus 
TODO: ensure focus stuff 
Use of uninitialized value in subtraction (-) at 
/usr/lib/libDrakX/interactive/gtk.pm line 533 (#1) 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/netconnect.pm line 563 (#1) 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/netconnect.pm line 565 (#1) 
Use of uninitialized value in string ne at /usr/sbin/drakgw line 205 (#1) 
TODO: XSetInputFocus if force_focus 
TODO: ensure focus stuff 
Use of uninitialized value in string eq at /usr/lib/libDrakX/interactive.pm 
line 266 (#1) 
TODO: XSetInputFocus if force_focus 
TODO: ensure focus stuff 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/shorewall.pm line 19 (#1) 
TODO: XSetInputFocus if force_focus 
TODO: ensure focus stuff 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/shorewall.pm line 41 (#1) 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/shorewall.pm line 41, <> line 14 (#1) 
Use of uninitialized value in join or string at 
/usr/lib/libDrakX/network/shorewall.pm line 36, <> line 147 (#1) 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/shorewall.pm line 41, <> line 147 (#1) 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/shorewall.pm line 41, <> line 53 (#1) 
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/libDrakX/network/shorewall.pm line 41, <> line 189 (#1) 
Use of uninitialized value in join or string at 
/usr/lib/libDrakX/network/shorewall.pm line 36, <> line 87 (#1) 
Le service shorewall n'est pas pris en charge par chkconfig 
   Warning: Zone loc is empty 
   Error: Unknown interface 192.168.1.0/255.255.255.0 
/sbin/service: line 148:  2671 Terminated  $debug 
$servicedir/$service $options 
Arrêt de dhcpd :[  OK  ] 
Arrêt de named :[  OK  ] 
SIOCDELRT: No such process 
   Warning: Zone loc is empty 
   Error: Unknown interface 192.168.1.0/255.255.255.0 
   Warning: Zone loc is empty 
   Error: Unknown interface 192.168.1.0/255.255.255.0 
Le service shorewall n'est pas pris en charge par chkconfig 
TODO: XSetInputFocus if force_focus 
TODO: ensure focus stuff 
Use of uninitialized value in subtraction (-) at 
/usr/lib/libDrakX/interactive/gtk.pm line 533, <> line 1 (#1) 
Use of uninitialized value in split at 
/usr/lib/perl5/vendor_perl/5.8.0/MDK/Common/String.pm line 138, <> 
line 1 (#1) 
[root@cosmic cosmicflo]# 
 
 
When I try to activate the connection sharing (it's doesn't works but without 
error message for the user ( :(  ),it's always desactivated after) : 
 
[root@cosmic cosmicflo]# drakgw 
Use of uninitialized value in numeric eq (==) at 
/usr/lib/libDrakX/interactive.pm line 303 (#1) 
(W uninitialized) An undefined value was used as if it were already 
defined.  It was interpreted as a "" or a 0, but maybe it was a mistake. 
To suppress this warning assign a defined value to your variables. 
 
To help you figure out what was undefined, perl tells you what operation 
you used the undefined value in.  Note, however, that perl optimizes your 
program and the operation displayed in the warning may not necessarily 
appear literally in your program.  For example, "that $foo" is 
usually optimized into "that " . $foo, and the warning will refer to 
the concatenation (.) operator, even though there is 

Re: [Cooker] drakgw

2002-09-22 Thread David Walser

--- Florin <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (David Walser) writes:
> 
> > --- Florin <[EMAIL PROTECTED]> wrote:
> > > for some compatibility reasons with the dhcp
> wizzard
> > > ... the default
> > > configuration is now to set the internal LAN to
> > > 192.168.1.0/255.255.255.0
> > > and not to 192.168.0.0/255.255.255., as before.
> > > 
> > > Ths internal IP address is now 192.168.1.1 and
> not
> > > 192.168.0.1 as before
> > > :o)
> > 
> > BOO!!!  :o(
> > 
> > Can you explain?  What's wrong with the DHCP
> wizard? 
> > Can't it just be fixed.
> 
> I don't see where is the problem ?
> You can use the advanced option and choose
> 192.168.0.1 ...

Ok, that's good.  Didn't want to have to redo my whole
DNS and DHCP configs.

> I don't understand your rude BOO thing ...

Not trying to be rude.

Really though, could the DHCP wizard possibly be fixed
to not necessitate that change?  Do you know?

> have a nice day,

You too Florin.  You've done a great job.

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com




Re: [Cooker] drakgw

2002-09-22 Thread Florin

[EMAIL PROTECTED] (David Walser) writes:

> --- Florin <[EMAIL PROTECTED]> wrote:
> > for some compatibility reasons with the dhcp wizzard
> > ... the default
> > configuration is now to set the internal LAN to
> > 192.168.1.0/255.255.255.0
> > and not to 192.168.0.0/255.255.255., as before.
> > 
> > Ths internal IP address is now 192.168.1.1 and not
> > 192.168.0.1 as before
> > :o)
> 
> BOO!!!  :o(
> 
> Can you explain?  What's wrong with the DHCP wizard? 
> Can't it just be fixed.

I don't see where is the problem ?
You can use the advanced option and choose 192.168.0.1 ...

I don't understand your rude BOO thing ...

have a nice day,
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/




Re: [Cooker] drakgw

2002-09-20 Thread David Walser

--- Florin <[EMAIL PROTECTED]> wrote:
> for some compatibility reasons with the dhcp wizzard
> ... the default
> configuration is now to set the internal LAN to
> 192.168.1.0/255.255.255.0
> and not to 192.168.0.0/255.255.255., as before.
> 
> Ths internal IP address is now 192.168.1.1 and not
> 192.168.0.1 as before
> :o)

BOO!!!  :o(

Can you explain?  What's wrong with the DHCP wizard? 
Can't it just be fixed.

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com




Re: [Cooker] drakgw

2002-09-20 Thread Florin

[EMAIL PROTECTED] ("J.P. Pasnak") writes:

> > you are right ... the disable function is broken.
> >
> > I will fix it ASAP.
> 
> Thanks.

ok, it's fixed in the cvs ... you'll get it in the next drakxtools
package.

Here below is the patch:


--- drakgw  2002-09-20 17:38:21.0 +0200
+++ /home/florin/drakgw 2002-09-20 17:37:12.0 +0200
@@ -49,6 +49,7 @@
 my $rc_firewall_generic = "/etc/rc.d/rc.firewall";
 my $rc_firewall_drakgw = "/etc/rc.d/rc.firewall.inet_sharing";
 my $rc_firewall_24 = "/etc/rc.d/rc.firewall.inet_sharing-2.4";
+my $masq_file = "/etc/shorewall/masq";
 my $dhcpd_conf = "/etc/dhcpd.conf";
 my $cups_conf = "/etc/cups/cupsd.conf";
 
@@ -134,9 +135,10 @@
my $wait_disabl = $in->wait_message('', _("Disabling servers..."));
stop_daemons();
}
-   foreach ($dhcpd_conf, $rc_firewall_24) {
+   foreach ($dhcpd_conf, $masq_file) {
renamef($_, "$_.drakgwdisable") or die "Could not rename $_ to 
$_.drakgwdisable" 
}
+   sys("/etc/init.d/shorewall restart >/dev/null");
log::l("[drakgw] Disabled");
$::Wizard_finished = 1;
$in->ask_okcancel('', _("Internet connection sharing is now disabled."));
@@ -155,7 +157,7 @@
 What would you like to do?"),
   [ __("enable"), __("reconfigure"), __("dismiss") ]);
if ($r eq "enable") {
-   foreach ($dhcpd_conf, $rc_firewall_24) {
+   foreach ($dhcpd_conf, $masq_file) {
rename($_, "$_.old") if -f $_;
rename("$_.drakgwdisable", $_) or die "Could not find configuration. 
Please reconfigure.";
}
@@ -287,7 +289,7 @@
  _("I can keep your current configuration and assume you already 
set up a DHCP server; in that case please verify I correctly read the Network that you 
use for your local network; I will not reconfigure it and I will not touch your DHCP 
server configuration.
 
 The default DNS entry is the Caching Nameserver configured on the firewall. You can 
replace that with your ISP DNS IP, for example.
-
+ 
 Else, I can reconfigure your interface and (re)configure a DHCP server for you.
 
 ", $device),

have a nice day,
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/




Re: [Cooker] drakgw

2002-09-20 Thread J.P. Pasnak

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On September 20, 2002 09:01 am, Florin wrote:
> [EMAIL PROTECTED] ("J.P. Pasnak") writes:
> > !,
>
> You can of course use the advanced options and read/use/set to the
> old 192.168.0.1 Ip address.

Forgot about that :)

>
> > And attempts to disable connection sharing produce the following:
> >
> > Could not rename /etc/rc.d/rc.firewall.inet_sharing-2.4 to
> > /etc/rc.d/rc.firewall.inet_sharing-2.4.drakgwdisable at
> > /usr/sbin/drakgw line 138.
>
> you are right ... the disable function is broken.
>
> I will fix it ASAP.

Thanks.

- -- 
Live fast, die young,
you're sucking up my bandwidth.
- --
J.P. Pasnak, CD
CCNA
[EMAIL PROTECTED]
http://www.warpedsystems.sk.ca

 Kernel version: 2.4.19-13mdk
Current Linux uptime: 12 hours 38 minutes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9iz8cBMRgzmzdk08RAgsuAJwO0Mjf2uq3Xmi7EeA/fh/cXIOilACgiJYp
Z5V1ecNS+nfNPmAKdyjDkRg=
=7rfI
-END PGP SIGNATURE-





Re: [Cooker] drakgw

2002-09-20 Thread Florin

[EMAIL PROTECTED] ("J.P. Pasnak") writes:

> !,
> 
>   When reconfiguring drakgw, it reverts the internal LAN to 192.168.1.1, 
> no what what the internal network card is set to, or what the previous 
> drakgw setting was.   Very annoying.  I have a few non-DHCP devices on 
> the internal network...

for some compatibility reasons with the dhcp wizzard ... the default
configuration is now to set the internal LAN to 192.168.1.0/255.255.255.0
and not to 192.168.0.0/255.255.255., as before.

Ths internal IP address is now 192.168.1.1 and not 192.168.0.1 as before
:o)

You can of course use the advanced options and read/use/set to the old
192.168.0.1 Ip address.

>   And attempts to disable connection sharing produce the following:
> 
> Could not rename /etc/rc.d/rc.firewall.inet_sharing-2.4 to 
> /etc/rc.d/rc.firewall.inet_sharing-2.4.drakgwdisable at 
> /usr/sbin/drakgw line 138.

you are right ... the disable function is broken.

I will fix it ASAP.

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




[Cooker] drakgw

2002-09-20 Thread J.P. Pasnak

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

!,

When reconfiguring drakgw, it reverts the internal LAN to 192.168.1.1, 
no what what the internal network card is set to, or what the previous 
drakgw setting was.   Very annoying.  I have a few non-DHCP devices on 
the internal network...

And attempts to disable connection sharing produce the following:

Could not rename /etc/rc.d/rc.firewall.inet_sharing-2.4 to 
/etc/rc.d/rc.firewall.inet_sharing-2.4.drakgwdisable at 
/usr/sbin/drakgw line 138.


- -- 
Live fast, die young,
you're sucking up my bandwidth.
- --
J.P. Pasnak, CD
CCNA
[EMAIL PROTECTED]
http://www.warpedsystems.sk.ca

 Kernel version: 2.4.19-13mdk
Current Linux uptime: 11 hours 50 minutes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9izSCBMRgzmzdk08RAqanAKCprWYYngLf88CFXJyHBAMiwwf/9wCdF8i5
HP52oggwtNsKjvrDv+thSOc=
=V8Qf
-END PGP SIGNATURE-





Re: [Cooker] drakgw problem with speedtouch modem

2002-09-18 Thread Florin

[EMAIL PROTECTED] ("Florent BERANGER") writes:

> Is that problem resolved  (internet reconnection broken
> and drakgw freeze) ?
> 
> 
> I tried to send messages yesterday but I didn't saw it
> in my cooker mailbox.

I have just tried that with the latest cooker and the very lates drakgw/drakfirewall
... and in order to make it work ... you have to unplug/replug the modem. 

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




[Cooker] drakgw problem with speedtouch modem

2002-09-18 Thread Florent BERANGER

Is that problem resolved  (internet reconnection broken
and drakgw freeze) ?


I tried to send messages yesterday but I didn't saw it
in my cooker mailbox.
--
EXCEPTIONNEL!
Tiscali lance les forfaits Internet Illimités,
à partir de 15,95EUR / mois.
Pour en profiter,cliquez ici: http://register.tiscali.fr/forfaits/
Offres soumises à conditions.