>> > ifconfig eth0:2 220.127.116.115
>> > route add -host 18.104.22.1685 dev lo
>> > Make sure that your kernel has IP aliasing compiled in
>> Thanks for the tip -
>> one question though, What happens if one leaves out the line:
>> route add -host 22.214.171.1245 dev lo
>> The machine is currently running now with only the
>> ifconfig eth0:2 126.96.36.1995 part in place.
>> Any forseable problems by not setting the route?
Well, you can't _locally_ ping the machine. Remotely it will work,
so I don't see any real big problems with this. But it might casue
something strange in the future and you'll have a hard time finding
out what it is ..
Oh, Linux 2.1.x adds the route itself as soon as you up the interface.
In that case you don't need to add the route manually, ofcourse.
>Sorry to come into the middle of this, but I think what you need is
>route add -host 188.8.131.525 dev eth0:2
>I think you'll have to add the route to get out that interface, and it
>needs point to the aliased device. FWIW, I've got about a dozen
>virtuals running like that at tanet.net.
I don't know why yet, but all the docs recommend against adding a route
through the aliased device and say you really want to add the route through
"dev lo". Works fine BTW, the route is NOT used to get out of the machine,
it's only so you can reach that IP address locally.
Miquel van Smoorenburg | The dyslexic, agnostic, insomniac lay in his bed