[Gllug] networking problem

t.clarke tim at seacon.co.uk
Fri Jul 15 07:46:14 UTC 2011


Hi,
we have a small problem at work which I am hoping might be solved with a small
Linux box made up from an old PC  (coyote floppy distribution or similar would
be good!) :-

The problem is we have a device which is very old, unsupported now by the
manufacturer and no manuals available it seems,  which 'talks' to the host
on another network via a gateway of 192.0.3.6 programmed-in (we assume) as
its default gateway.  It looks very much like we are not going to be able to
change this routing, and the gateway of 192.0.3.6 will be disappearing shortly
(to be replaced by another with address 192.0.3.240);  don't ask me why - not my
doing!).   I believe the original decision was made before it was discovered
that re-programming the  device with a new gateway was going to be problematical

So, assuming re-programming the gateway on the device IS impossible, can we
cheat and shove a linux box on the LAN with an IP of 192.0.3.6 and a default
gateway of 192.0.3.240, so that the device will send its packets to the linux
box which will then forward (over the same eth0 interface) to 192.0.3.240, for
ultimate delivery to the far end?   It would seem this will work in theory, but
am I missing something??

Tim

--------------------------------------------------------------------------------
This E-Mail (and any files transmitted with it) is intended solely for the use
of the individual or entity to whom it is addressed. If you have received it in
error please notify the sender and delete the message.

Seacon Terminals Ltd, Company No. 1547396, registered in England and Wales
Registered Office:  Tower Wharf, Northfleet, Kent, DA11 9BD, England

--
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list