Mailinglist Archive: opensuse (924 mails)

< Previous Next >
Re: [opensuse] SuseFirewall2 does not allow pings to ext network?
Hash: SHA256

On 2012-10-31 01:22, Marc Chamberlin wrote:
On 10/30/2012 12:49 PM, Carlos E. R. wrote:

Carlos - Perhaps, I can look into direct routing, and if I get it to work,
are you implying
that NAT is not fully working in SuSEFirewall2? Seem like a pretty serious
bug to me, IMHO!

No, I'm not implying its buggy. I'm wondering why are you using it to connect
two internal
networks. The default is to route.

Pings and NAT should be fairly straightforward functions that SuSEFirewall2
should handle
across two different private networks....

NAT has "side effects". It maybe that SuSEfirewall blocks ping only.

I was guessing that I simply hav.e something misconfigured, and your
suggestion of using direct
routing as a workaround comes as a surprise! I do know, that at some level
NAT must be working,
how else could all my systems on my private network be accessing the internet
without a
problem? So why shouldn't NAT work when I simply am trying to access my
external (private)

I don't know, and I do not have at my disposal a network to play with and find
out ;-)

Since these changes did not help matters, I have backed them out. So how do I
SuSEFirewall2 to do direct routing?

IIRC, like this:


But I'm more used to do it with routers, not PCs, so I don't remember offhand
the exact setting.

- --
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 "Celadon" (Minas Tirith))
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla -

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >