Colleagues, can someone help me sort out a routing table issue?
True confessions — I have never done this before. I've tried reading about route tables and remain confused.

Like most home networks, I have a private class-C LAN at 192.168.x.y.
My work wants me to add some parts in class-B 172.x.y.z to separate their stuff from my stuff and from "family" foolishness.

My Routing Issues:

• How to route from 172.x.y.z through my 192.168.x.y LAN and out to the public internet?
• How to allow select work-at-home devices to safely access work resources like printers, scanners and such?
• Is this a problem for a Virtual LAN with managed switches?
• Can this be accomplished by routing without pulling more house LAN wire? (The work stuff is not wifi enabled and would exist in a single room?)

I'd love someone to have great suggestions for how to proceed.

Thank you in Advance,
~~~ 0;-Dan

I heartedly recommend Ralph Becker's IP Subnetting Tutorial.

Don't be put off by the web 3.0 look. It is easily the best introduction to subnetting that I have ever seen. When I first met this reference, it was on a *.edu site. My guess is that, when he left the university,the author posted it to his personal site.

The only caveat I might add is that it likely does not address IPv6, as it looks just like it did when I first saw it.

1 members found this post helpful.

> How to route from 172.x.y.z through my 192.168.x.y LAN and out to the public internet?
At home network, we can use a sub-network range inside Class B or C, such as 172.10.49.x or 192.168.168.x.

The 172.10.49.10 use static IP address and set default gateway to 192.168.168.254.

There are two NICs on 192.168.168.254. The if0 connect to home network and if1 connect to Internet.
The if0 use static IP address, 192.168.168.254.
sudo route add 172.10.49.10 dev if0

The if1 use DHCP to get Internet gateway and DNS.

1 members found this post helpful.

Most of the parts connected at 192.168.*.* are using wifi. Wire net connections are servers or printers or mesh network parts.

My work dictates the 172.xxx address block.

I propose to get everything talking to everything. That done, I can then start to wall things off.
It seems that it will be easier to work through open doors that to try and work around closed ones.

I'm running a three node mesh network for 192.xxx. The primary node is then connected to my ISP provided gateway. I expect to get another router/AP from work that will implement the 172.* LAN both wire and wifi.

Thank you for your reply,
~~~ 0;-Dan

I have documents and data files that I propose to capture to blueray media. Do you know how I might write multiple, separate sets of data as folder-trees or archives onto an blueray disk. {grin, blush} My brain grew up in the days of tape reels and disk "packet writers".

I have a blueray read/write/re-write drive.

Thanks,
~~~ 0;-Dan

Do you connect to your work over a VPN and does the VPN server assign 172.x.x.x address? If so what type of VPN?.

I would guess your work IT people want you to isolate everything work related from your home network including printers etc.

1 members found this post helpful.

Could you please clarify your issue ? What does "My work wants me to add some parts" mean ?
Where is your home 192.168.x.y in the global net ? And where is their 172.x.y.z in the global net ?
Please reply michaelk's question.

Consider the typical in-house LAN lives in a Class-C "private network" address space.
I want to introduce a Class-B "private network" into the same building -- my house.
With two networks in the house, I want to route between them. Thus the route table request.

The following might help you understand the topologies.

{public internet} =z= {ISP gateway using their DHCP assignment}
{gateway DHCP to LAN router} =z= {myRouter}
{myRouter DHCP to in-house LAN 192.168.x.y } =z= {wire connected servers and printers and switches}
=ZZ= {wifi connections to laptops, phones, etc}
=ZZ= {wifi connections to IOT}
NOTE --- All switches are "managed" for when I learn how to configure a virtual LAN.

My work wants to add {work Router} beside {myRouter} serving {their IP address} in-house.
In part this will isolate their LAN from all IOT and "guest" devices on my in-house.

Thank you for the reply,
~~~ 0;-Dan