I didn't notice this until recently, but on our production web servers I use
IP aliasing to host multiple sites on one box. Pretty normal stuff. Here's
an ifconfig on one of these boxes:
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 208.156.59.51 netmask 0xffffff00 broadcast 208.156.59.255
inet 208.156.59.10 netmask 0xffffff00 broadcast 208.156.59.255
ether 00:10:5a:e4:87:22
media: 100baseTX <full-duplex>
supported media: autoselect 100baseTX <full-duplex> 100baseTX
<half-dupl
ex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex>
10baseT/UTP
xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255
ether 00:10:5a:e4:87:0d
media: 100baseTX <full-duplex>
supported media: autoselect 100baseTX <full-duplex> 100baseTX
<half-dupl
ex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex>
10baseT/UTP
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
Looks pretty good. The only problem is that connections from the local
machine will only connect to the _first_ (or "real") IP address for an
interface. A connection, for example, from this machine to 208.156.59.10
just hangs ...
I'm assuming that I've simply forgotten some configuration step. This box
is running 3.1-STABLE/May-9.
Chuck Youse
Director of Systems
cyo...@cybersites.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
