-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Will,
On 5/22/2009 2:01 PM, will trillich wrote: > Hmm. This sounds kinda like something we ran into lately -- maybe this > will help you: > - our server had TWO nic cards, one for internal 10.10.*.* one for > external 208.*.*.* > - we'd accidentally set up 'default gateway' on both > > This meant the system was confused as to where to send replies. I recently had a sever misconfiguration in a slightly different way: the default route was set to use an eth device that wasn't physically connected to anything, and the server's primary IP address was also bound to that device. The symptoms were that no outgoing connections could be made successfully, but that incoming connections worked just fine. This was on a Linux 2.4 kernel, which appears to route the replies without a problem even with such an egregious misconfiguration: the kernel appeared to be smart enough to send replies to the "right place" regardless of the stupidity of the configuration. In what environment did this default route misconfiguration cause unreliable responses? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkoW+5MACgkQ9CaO5/Lv0PAIZACgwGFY2HpaUbGUg99CRrS3RGtj S5MAnjyriSd0OZm/lEbBnLr+bQmP6uHA =MOIv -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
