🚀 go-pugleaf

In cox.internet.discussion.athomeconversion <EDRd8.4547$jC3.171632@news1.east.cox.net> Arthur Hagen <art@broomstick.com> wrote:
> With two machines on different subnets, will it route packets between them?

The RP114 will, at least. Actually the router part's no longer involved
once the switch learns the MAC addresses. Two different local nets does mean
two routes instead of one, but the RP114 has room for 10 and I don't know
anyone using 10 IP networks on a home LAN. You may be better off going to
something like Netgear's FR3xx series of routers, which offer more flexibility
and are still in the under-$500 range.

> And furthermore, how are the two machines going to get their IP from Cox?

You need to poke a hole through the firewall for DHCP, and disable the
DHCP server in the router. Basic stuff. The DHCP server needs to look at
the MAC information inside the DHCP packet instead of in the Layer 2 frame,
but how do you think non-local DHCP servers do it? DHCP across routers is
standard stuff on large networks.

> Have you *tried* it?  :-)

No, I haven't tried it, I've successfully done it.

> Which is kind of hard to do with dynamic and changing IPs, wouldn't you say?

With changing /32 networks, yes. But then, I tend to work with two
scenarios:

1. Public static IPs. The main purpose of giving each machine a public
   IP is to make them reachable from outside, and addresses that change
   on a regular basis makes that impossible. Pseudo-static IPs like the
   ones Cox gives out do work, though, because they don't change often
   ( at least mine hasn't changed since I got it ). If it ever changes
   you're going to lose outside connectivity until you find out the new
   address anyway, regardless of whether the routing tables are correct
   or not.
2. Private static IPs and NAT. In this case your internal network won't
   change, and the IP of the router isn't even mentioned explicitly in
   the routing and filter tables so whether it changes or not is irrelevant.

If you really need regularly-changing public dynamic IP addresses for your
machines, IMHO you'd better order large quantities of Tylenol/Advil/asprin
to go with the Cisco 2500 or similar that you're going to need.

I think we're talking at cross-purposes, because my usual solution to
the problem you pose is to not deal with the problem, just change the
configuration to something that's easier to deal with.

-- 
It does not do to leave a live dragon out of your calculations.
                                -- JRR Tolkien