see below ..
Mit freundlichen Grüßen
Bruno Leonhardt
CLP Domino R5 Systemadministrator
___________________________________________________________________________________
AnalyTek Systemhaus
Hospitalstr. 2a
D-65589 Hadamar
Tel.: 06433/81403-15
Fax : 06433/81403-40
Besuchen Sie uns im Internet unter: http://www.analytek.de
Robert Szentmihalyi
Hi,
The firewall's NICs are configured as follows: eth0 62.245.134.130 netmask 255.255.255.240 connected directly to the web server via a cross-over cable
should not the default gateway of your webserver be 62.245.134.144 instead of 62.245.134.146?
As the NIC to which the web server is connect has 62.245.134.130, I'd rather say that the web server's default gateway ought to be 62.245.134.130. Try to ping 62.245.134.146 and 62.245.134.144 and see iff you can reach them.
Sorry, I mixed hat up yesterday. The firewall's interfaces are actually configured like this:
eth0 62.245.134.146 netmask 255.255.255.240 eth1 62.245.134.130 netmask 255.255.255.240
and the web server is connected to eth0, i.e. 62.245.134.146
I guess I have been working on this for too long...
I have tried to set the gateway of the web server to 62.245.134.144, but when routing is set up at boot time, I get a "network unreachable" error, athough I can ping 62.245.134.144. Any ideas?
ME: shouldn't the gateway ip be x.x.x.146 ??? the webserver is connected on (cross over) eth0 ( x.x.x.146 ) ... usually x.x.x.146 is ME: the standard gateway for the webserver ... am i wrong ???
Also, I don't understand, WHY the gateway should be 62.245.134.144. Could somebody please shed some light on that?
Cheers
Thiemo
Thanks for your help, Robert -- Where do you want to be tomorrow? Entracom. Building Linux systems. http://www.entracom.de -- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here