On Wed, 20 Sep 2006, Vittorio R. Tracy wrote:
Uhg, I think I found what I was doing wrong.
The route statement on the Director should have been:
route add -net xxx.xxx.134.144/29 eth0
route add -host xxx.xxx.134.150 dev eth0:1
as well you can't use ethernet aliases anymore and expect
then to work. They may and they may not. Their behaviour is
This was indeed a DUH! problem.
the "duh" problems can be quite hard.
I'll add this to the "connection refused" list
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!