Routing with SUSE 8.0

I want to use a SUSE 8.0 machine as a router for our LAN.
The connection and "pings" between the server and the clients work.
But only the server's internet connection works.

The guide i read says that it is required to set IPFORWARDING in the configuration file of the personal-firewall.
I did so und and also started the firewall.

Everytime i ping from a client with the firewall runnig directly to an internet ip the "internet answers" but if i ping a domain name nothing works, so it seems to be a problem with the named running on the server.

But if i turn of the firewall, the named works. A ping to an domain name shows the ip adress and then breaks. A traceroute shows that the request is send to the server and then breaks so, to my mind, it seems that in this case the ipforward doesn't work.

Any suggestions ?

The Personal Firewall is not intended for server/router use. Use SuSEfirewall2 instead (which also allows easy routing but is more secure and better configurable).

And if i would like to use the server without the firewall ? where do i tell the server to forward the requests ?

Use IPTables

Search here, I think theres a few examples etc..

Unless one is an expert with iptables, the SuSEfirewall2 script (which uses iptables, btw) is securer And since the router is directly on the internet, it should not run without a firewall.

I told him how to do what he asked! What he does with that information isn't my problem

The question was answered, wether or not it was the right question is another matter

You did not answer his question It was:

Obviously, if you have had any suggestions you should have replied with (yes, true, T, 1, on, ...) otherwise with (no, false, F, 0, off, ...)

Muhaha I was answering this question

Then the answer would have to be a location, e. g. "at the shell prompt". Afaik there is no UI in iptables

Back again

So, I configured SuSEfirewall2 and... WOHOO... nearly everything works.

After bootup i have to perform these commands:

cinternet -start
rcSuSEfirewall2 start

The first command...ok
But why the second ?
I told the runlevel editor to start everything with SUSEfirewall2 in Runlevel 3 and, because i found out that these ones seem to be required, all the personal firewall jobs, too.

And now... could you tell me, answer, suggest how to configure cinternet and firewall so that they start automatically at bootup ?

THX !

The second should not be necessary.

The personal-firewall script should _not_ be started if you intend to use SuSEfirewall2.

Dunno about cinternet (I use rp-pppoe), but for SuSEfirewall2 it should be sufficient to enable the three init scripts.

Try disabling the personal firewall, then init 1, init 3, run cinternet -start without the firewall and check whether your machine is protected (let someone do a portscan on you, e. g. a website).

HTH

ROFL OK I give up

THX. I'm gonna try it... hopefully it works

@ realnowwhereman: Deutsch ist eigentlich auch ne schöne Sprache

Yes. However, in this forum the internet's lingua franca, English, is used to allow everyone to follow discussions so that the entire community benefits (and is able to contribute). Btw, the English language's beauty's advantages' list is headed by its simplicity which significantly facilitates technical talk. Also, native English speakers are more tolerant towards their language's grammar's abuse by foreigners than other languages' native speakers are. Just consider this paragraph - if I were to post on a German board modifying the language to the extent of seeming so foreign to the German speakers there as my English probably does to the English-speaking people reading this, others would be sure to remark on my language.

To my mind your English is much better than mine. It's a desaster by now, i think i should return to school again *g*

But in order to say something about the "trouble" I had:
disabling the personal scripts WORKED

So thx a lot.

PS: If you also know about how to get BattleCom work with SuSEfirewall2... tell me. An other client of our little LAN would be very exited about that *g*