Oleg Bartunov ([EMAIL PROTECTED]) said something to this effect on 01/02/2001:
> > You can explicitly bind an apache server to localhost.
> This works only if frontend and backend are on the same physical server.
> But it will not works even in this situation if you have several
> proxies running while you want backend accepts requests only from
> one specific proxy.
Bind an address on the 192.168.0 net as an alias on a real interface:
bash# /sbin/ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 200.200.200.200 netmask ffffff00 broadcast 200.200.200.255
ether 8:0:20:a2:e1:84
bash# /sbin/ifconfig le0:7 192.168.0.7 up
bash# /sbin/ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 200.200.200.200 netmask ffffff00 broadcast 200.200.200.255
ether 8:0:20:a2:e1:84
hme0:7: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.7 netmask ffffff00 broadcast 192.168.0.255
bash#
And then bind another address on the same private subnet to an interface
on another machine, and they can talk to each other via this network
(set the route correctly as well, naturally).
This interface will be invisible from the 'net.
(darren)
--
Life is full of misery, loneliness, and suffering - and it's all over
much too soon.
-- Woody Allen
