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 =
-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 ...
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
-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
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
-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 ...
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
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
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
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
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:
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
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.
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
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
[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
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 ...
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/
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
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
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 ...
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
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
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
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
[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
--- 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
-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
-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
--- 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
[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...
[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
+++
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:
[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
...
34 matches
Mail list logo
