Re: [Shorewall-users] Port forwarding problem

[P. <o.p+S.P.A.M.@fobie.net>]

Tom Eastep (te...@sh...) wrote:
> On Sun, 2003-09-28 at 07:48, Tom Eastep wrote:
> > On Sun, 2003-09-28 at 05:35, =D6rjan Persson wrote:
> >=20
> > >=20
> > > Am I missing something? The internal network works fine from what
> > > I've understood. I have another gateway, 192.168.0.1, I have tried
> > > to use that as a gateway but that was also unsuccessfull.
> >=20
> > I suspect that you are trying to connect via eth2 but your default ro=
ute
> > is through eth0.
> >=20
> > See section 4.2.1 in the LARTC (link available from the Shorewall
> > "Useful Links" page).
> >=20
> > As an aside, why do you have separate zones for eth0 and eth2???? Do =
you
> > have different firewalling requirements for the two net zones?
> >=20
>=20
> Also, what is the point of having two different interfaces to the same
> subnet? Does your ISP support aggregation over the two separate links?
>=20

Hello,

Thanks for your answer, Tom! That was some really interesting reading
but I haven't really gotten it to work as I want to. But I'm still
trying. ;)

Yes - I have different firewall requirements for the two net zones. And
the both interfaces is DHCP-managed. So, I thought that would be the
best to do. But, from your answer, I guess that wasn't correct. :P

I guess I need to read some more about using shorewall with multiple
zones on the same interface. Thanks for a great software.

Cheers,
=D6rjan
--=20
     [x] icq - 496723     [x] url - fobie.net