Bay 12 Games Forum

Sadly, the US business world is not one with a history of honoring public trusts or obligations.

Rather, you would see them preferentially lawyer up, soak in money meant for public trusts, then not deliver, and use the lawyers to argue it was legal.

For precedent, see the broadband spending bills of the 90s meant to get us digital fiber infrastructure.  Some fiber was laid, but most of the money was just siphoned out.

https://www.huffpost.com/entry/the-book-of-broken-promis_b_5839394

Functional ice sculptures

The tradcath and fundiprot angles are not conserved, but both inhabit the religious sphere of thought.


The fundiprots are the ones railing about baby jesus crying. (they outnumber the tradcaths. A thing that makes the tradcaths sad pandas.)

See for instance, this religious testimonial page.

On the drive home I was consumed with guilt and regret. I cried the whole way home. Ironically, it also poured rain the entire night. I felt like Jesus was crying for what I had done.

They both assert that an embryo of mere seconds age is a baby, but the fundiprots go for the tearjerking, and claims of jesus's tears.

The circus of comestibles presents:

FUN WITH FONDUE!

The firebird tribe is very upset by this stereotyping!

Drunken orgy

Ideally, i would get one with ddwrt or openwrt support. (Check both projects for supported hardware)

https://wiki.dd-wrt.com/wiki/index.php/Supported_Devices

https://openwrt.org/toh/start

Ddwrt is better for novices.

Openwrt for real admins who like to administer over ssh.


Either will give you access to all the things.

I would look for a gigabit or faster router, with 64mb (or larger) flashrom, and 512m or larger ram, supported br ddwrt. (In your case. It has a better gui management portal)

Adding the custom route would be very straightforward.

So, you have a bandwidth intensive application, that you want to live within a specific network.

Do you intend to have that network completely isolated from the network, or would some routing rules be sufficient? (we can configure that subnet to have no route to the internet. Only a route to the internet-enabled subnet.)


also, I need to know the exact models/brands of router you have acquired.



General idea:


OBS network:

192.168.2.X
Has a path in the routing table for that subnet, for how to get to 192.168.1.X, but no "all other networks" route. this means it can see, and communicate with your other network but not the internet.

Main windows network:

192.168.1.X
Has a route to the OBS subnet, and a route to the "all other networks" (aka, the internet).



Nitty gritty:

The OBS network is configured with a static IP address on its WAN port. (the one that normally plugs into an internet modem of some kind.) That number is a 192.168.1.X type number.  (in this case, 192.168.1.254) The WAN port has a patch cable connecting it to an arbitrary port on the main router.

It is configured to dole out DHCP addresses in the 192.168.2.X subnet.  Devices connected to its main ports will get addresses in that range.

It has a routing table that looks like this:


Network destination Netmask         Gateway Interface Metric
0.0.0.0         0.0.0.0         127.0.0.1       127.0.0.1 10                <----This is the "All other routes" route.  We point it at the reserved "Myself" address. This blackholes all other networks as 'undeliverable.'
192.168.1.0         255.255.255.0         192.168.2.1 192.168.1.254 10                <----This is the route that tells traffic outbound to the internet enabled network what interface to get to that network over. This is the hard set IP for the WAN port
192.168.2.0         255.255.255.0         192.168.2.1 192.168.2.1 10                <----This is the route that says all traffic destined inside the 192.168.2.X network should use the router's internal network address (hard set) as the routing number



The main router has a routing table that looks like this:

Network destination Netmask         Gateway      Interface         Metric
0.0.0.0         0.0.0.0           192.168.1.1        [WAN IP]         10                <----This is the "All other routes" route.  This will be set by the DHCP functionality of the internet enabled router, as it negotiates with the ISP.
192.168.1.0         255.255.255.0           192.168.1.1      192.168.1.1 10                <----This is the default route for within the subnet. Says to use the router's IP for all local traffic routing tasks.
192.168.2.0         255.255.255.0           192.168.1.254      192.168.1.254 10                <----This is the route to get to the 192.168.2.X network. Says to forward all traffic intended for that network to that that local IP address. This is the statically assigned IP of the WAN port of the other router.



The instructions for how to set up these manual routes will be specific for that model of router.