![](https://seccdn.libravatar.org/avatar/7e64484b1fd6889d6f831db2ff9f1510.jpg?s=120&d=mm&r=g)
OK! great!
Did you add this route also to route.conf? I'm
not sure, but i think a simple route add from the
console won't stick after a reboot. Please
correct me if i wrong.
Mazzel, Marcel
---- Begin Original Message ----
From: stephane parenton
Stephane,
My guess is that the rules on the firewall are not complete yet. You have to allow access from the lan network to the internet and the NAT-network. If i'm correct, you can check if
the
packages are dropped/denied by the firewall in the firewall logfile (/var/log/ ).
well, i'll check that also, but jeffrey taylor did answer me about the routes... I've added route add 192.168.0.x gw xxx.xxx.xxx.aaa (the eth0 ip) and here it works at least.... now i can take a rest and tune the system more precisely.... thank you everyone for answering..... Regards Stephane Parenton -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com ---- End Original Message ---- Get your Free E-mail at http://thepenguin.zzn.com ____________________________________________________________ Get your own FREE Web and POP E-mail Service in 14 languages at http://www.zzn.com.
![](https://seccdn.libravatar.org/avatar/d42b908138545ad2c25507327dedead4.jpg?s=120&d=mm&r=g)
Marcel Broekman wrote:
OK! great!
Did you add this route also to route.conf? I'm not sure, but i think a simple route add from the console won't stick after a reboot. Please correct me if i wrong.
no, it won't stick.... But i think that there is a place to put scripts so they are launched at each reboot, after the system launches every needed stuff and before any user can login... I'll add this to route.conf and find the place for the other bits of the script to be launched anyway... Stephane
participants (2)
-
Marcel Broekman
-
stephane parenton