Hello Steffen, Wednesday, August 06, 2003, 11:51:12 PM, you wrote:
So it seems strange why the client connects to that address - seems to be the wrong one. Are you sure that there is really no routing for the client via eth2? Did you verified with tcpdump or similar tools?
According to the routing table the client can reach the 192.168.80.0 net via its default gateway 10.68.26.1, which has an ip adress in the 192.168.80.0 net. But why should it try to connect to 192.168.80.1 in the first place? Samba is configured with "time server = yes" and to use only eth0 and eth2 interfaces. If I read the logmessage it seems like a packet comes from the client with a source ip adress of 192.168.80.1? How´s that possible? Or do I misunderstand the log message?
There are situations, where rp_filter does not work. You can turn it off. SuSEfirwall2 turns it on, but you can change that. Somewhere there should be an echo "1" > ..../rp_filter, try to change the 1 to 0 like echo "0" > .../rp_filter and restart SuSEfirwall2.
Sorry, I cannot help much with SuSEfirwall2, maybe there is a better way to do that - but should solve you problem for the time you're looking for best solution :-)
How can I put that command in the SuSEfirewall2 script so that I don´t have to issue it manuelly after SuSEfirewall2 is restarted? -- Best regards, André mailto:Andre.Saenger@gmx.de