Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Bernd Eckenfels
On Wed, Jun 05, 2002 at 01:59:10PM -0300, Carlos Barros wrote: > >Intenet > > | > > | > > Gateway; Cisco: 194.224.7.1 > > | > > | > > | 194.224.7.9 > > Firewall > > | 194.224.7.10 > > | > > | > > -

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Carlos Barros
On Wed, Jun 05, 2002 at 11:23:09AM +0200, Davi Leal wrote: > > > iface eth0 inet static > > > address 194.224.7.9 > > > iface eth1 inet static > > > address 194.224.7.10 > > We own a ClassC network, 194.224.7.0. We offer an ISP service here at Spain: > > >Intenet > | > | > Gat

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Bernd Eckenfels
On Wed, Jun 05, 2002 at 01:59:10PM -0300, Carlos Barros wrote: > >Intenet > > | > > | > > Gateway; Cisco: 194.224.7.1 > > | > > | > > | 194.224.7.9 > > Firewall > > | 194.224.7.10 > > | > > | > >

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Carlos Barros
On Wed, Jun 05, 2002 at 11:23:09AM +0200, Davi Leal wrote: > > > iface eth0 inet static > > > address 194.224.7.9 > > > iface eth1 inet static > > > address 194.224.7.10 > > We own a ClassC network, 194.224.7.0. We offer an ISP service here at Spain: > > >Intenet > | > | > Ga

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Davi Leal
> > iface eth0 inet static > > address 194.224.7.9 > > iface eth1 inet static > > address 194.224.7.10 > > I dont think it is a particular good idea to do it like this with the ip > address. But if you do not have a transit network from your provider, you > can delete the both automatically added

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Davi Leal
> > iface eth0 inet static > > address 194.224.7.9 > > iface eth1 inet static > > address 194.224.7.10 > > I dont think it is a particular good idea to do it like this with the ip > address. But if you do not have a transit network from your provider, you > can delete the both automatically adde

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-05 Thread Dave Watkins
Do you have IP forwarding turned on? echo 1 > /proc/sys/net/ipv4/ip_forward At 15:46 4/06/2002 +0200, Davi Leal wrote: Hi there, We have an ISP: email, web, ftp, dns and radius servers. I'm trying to replace an old firewall (2.0.x kernel) with a new one (2.4.18 kernel). I am using the 'mimic' strat

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-04 Thread Dave Watkins
Do you have IP forwarding turned on? echo 1 > /proc/sys/net/ipv4/ip_forward At 15:46 4/06/2002 +0200, Davi Leal wrote: >Hi there, > >We have an ISP: email, web, ftp, dns and radius servers. I'm trying to >replace an old firewall (2.0.x kernel) with a new one (2.4.18 kernel). I am >using the 'mim

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-04 Thread Bernd Eckenfels
On Tue, Jun 04, 2002 at 03:46:42PM +0200, Davi Leal wrote: > iface eth0 inet static > address 194.224.7.9 > iface eth1 inet static > address 194.224.7.10 I dont think it is a particular good idea to do it like this with the ip address. But if you do not have a transit network from your provider,

Re: [interfaces + route] My new firewall doesn't forward packages

2002-06-04 Thread Bernd Eckenfels
On Tue, Jun 04, 2002 at 03:46:42PM +0200, Davi Leal wrote: > iface eth0 inet static > address 194.224.7.9 > iface eth1 inet static > address 194.224.7.10 I dont think it is a particular good idea to do it like this with the ip address. But if you do not have a transit network from your provider