Solved my own problem--sort of. The one thing I forgot to mention is that I have wireless Internet service here. My interface to that is Ethernet to a Hybrid cable modem. Cycling power on the cable modem cleared up all my routing problems with it. On Tue, 4 Jan 2000, Ron Oliver wrote:
Running SuSE 6.3 (2.2.13 kernel.) The machine in question is our gateway machine. Our Internet connection is via eth0; a private intranet is on eth1, with the gateway providing Internet access for the intranet via masquerading.
We have two IP addresses on the Internet. One is on eth0, the other on eth0:0. This used to work just fine. Now, however, TCP connections (e.g.: SMTP) to the aliased interface from the Internet fail. Connections from the intranet work fine. Also, eth0:0 can be pinged from the Internet.
Now, if I switch the IP addresses around, so that the IP address from the alias interface is now on the "real" interface and vice versa, both IP addresses are available for SMTP connections. This remains true even if I change the IP addresses back to their original values. After a while, though, the aliased interface is not available for TCP, although it can still be pinged.
I've tried "route add -host ..." for the aliased interface; it doesn't help.
-- Ron Oliver (mailto:roliver-suse@quantum-networks.com) -- 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/Doku/FAQ/