On 6/26/20 1:34 AM, The Natural Philosopher wrote:
> What an incredibly stupid answer

I don't think it's as stupid as you think it is.  Nor did clients that
have paid me to configure things for them.

> What you need is of course a router with at least two ports, one for
> each subnet. You could build one out of a pi with an extra interface,
> but really almost any router that is capable of handling an ethernet
> presentation of the internet (cable or fiber to the premises, both of
> which use modems that end in an ethernet socket) can be used here.
> Yiou should be able to turn off NAT and set up[ a basic firewall on any
> old gash broadband router you have lying around that would work pn cable
> for example.

Those are perfectly viable options.

But the OP has clearly indicated that he does not want to route TCP/IP
(et al.) traffic between the systems.  He's going out of his way to NOT
do so.  His reasons for doing so don't matter.  He asked a question, and
I provided an answer.  I don't want, much less need your validation of it.



--
Grant. . . .
unix || die

--- SoupGate-Win32 v1.05