[tech] flame, moray's kernel and transparent proxying

Duncan Sargeant dunc at rcpt.to
Thu Sep 16 14:02:48 WST 1999


Warrick Mitchell wrote on Thu September 16, at 13:47 +0800:
> On Thu, Sep 16, 1999 at 01:45:52PM +0800, Ian McKellar wrote:
> > Hi,
> > 
> > I've worked out a way to give flame its own IP number without needing to
> > give it its own machine. We can use the transparent proxying code in linux
> > to redirect all requests to port 23 with a destination of flame's IP# (I
> > grabbed 130.95.13.10 - it doesn't seem to be used) to port 4242. We can do
> > this with all the other services that flame runs. I've set up ip aliasing
> > on moray (its now using 130.95.13.(9|10)), but moray's kernel doesn't seem
> > to have the nececary firewall options enabled to do the port redirection.

Can you do this without ditzy kernel options, with rlinetd dichro?

> [root at quigon]:~# nslookup 130.95.13.10
> Server: asia14-ofpe.perth.oilfield.slb.com
> Address: 163.184.30.2
> 
> Name:  q.rcpt.to Address:  130.95.13.10
> 
> It was in use and you knew about it unless someone has switched the
> machine off.
> 
> I would suggest you choose another ip address.

It was also marlin a while back.  ah well :-)


,dunc




More information about the tech mailing list