Hello,
I am trying to set up a private net alias (192.168.) on one of my machines.
There are several difficulties, I guess some of them are Digital-specific.
First problem is that for some reason amd (not the system automounter, but
the _other_ automoutner that we keep for historical reasons) seems to bind to the
private net address. This should be overcomable by creating the private net
alias after amd and other essential servers start. Is there a better way
to handle this situation?
Routing. Once the private net alias is up, the kernel sets the route for
the local (public) net to the gateway. This is wrong. And the gateway
sends ICMP redirects every time the machine under investigation sends
something to the public local net, which obviously creates lots of ICMP noise.
Other OSes behave differently (and I believe - properly) : Kernel does not
set up the route for the local public net to the gateway. I would
appreciate receiving any suggestions on what could be wrong in my
setup, general tips and tricks on how to make public and private net
cooperate on the same interface, same machine and same physical segment
(no routing between public and private net is needed).
Thanks.
VSG
Received on Wed Oct 21 1998 - 18:50:12 NZDT