--- Benjamin Scott <[EMAIL PROTECTED]> wrote:
> There needs to be a router
(or should I be saying gateway) ...
The terms "gateway" and "router" are
pretty much synonymous for this
application. When one talks of a "gateway",
one usually means the specific
router that connects your local subnet to other
subnets (often the Internet at
large). The term "default gateway" means the
router which gets packets that
the local machine doesn't otherwise know where
to send.
> ... between the subnets to let them talk, and the packets will
pass on the
> ether twice: once from source to router; once from router to
destination.
Correct.
--- end of quote ---
Hmm, couldn't you configure a
static route in each computer for the other subnet, so they all know that both
subnets are on the same wire?
ie:
route add -net <other subnet> netmask
255.255.255.0 dev eth0
since DHCP was mentioned in the original message, you
should be able to add this route as a scope option, so whichever subnet a
machine falls within, it gets the opposite subnet added to it's route table...
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
