Date: Sat, 2 May 1998 16:06:52 -0400 (EDT) From: Dan Swartzendruber <druber@mail.kersur.net> To: freebsd-net@FreeBSD.ORG Subject: weird behavior with IP aliases Message-ID: <Pine.BSF.3.96.980502160057.2872A-100000@mail.kersur.net>
next in thread | raw e-mail | index | archive | help
I was just helping someone set up an apache web server on a 2.2.5 box. To serve virtual domains, we decided to use IP aliasing on the ethernet interface. It works, except for one odd thing: none of the alias IPs are accessible from the web server itself. E.g. take this case: 199.1.2.1 (primary address) 199.1.2.100 (alias address) if I am on the web server (199.1.2.1), I can ping (or otherwise see) address 199.1.2.1, but any attempt to hit 199.1.2.100 fails, although other hosts on the same ethernet segment can hit that address. If I look at the routing table, I can see that 199.1.2.1 is visible via the loopback interface, but the alias isn't. The aliases were set up just as recommended in the appropriate rc files, and the ifconfig commandd is obviously being executed, but just as obviously, something else isn't. What is the missing piece here (more clearly: I known I can make this work by adding the routes myself; I'm just curious if I didn't finish setting things up 100% or if there is a bug here?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980502160057.2872A-100000>