From: David Jackson <david.jay.jackson@wcox.com>
To: Nathan <nate@nateworks.ca>
Cc: Linux-Admin <linux-admin@vger.kernel.org>
Subject: Re: Vitural Network Interfaces
Date: Wed, 10 Jul 2002 04:32:50 -0600 [thread overview]
Message-ID: <3D2C0D51.29C4C066@wcox.com> (raw)
In-Reply-To: Pine.LNX.4.33.0207092253530.23903-100000@willy.nateworks.ca
Nathan --
As far is the cable internet and router is concerned
Box A = eth0 --192.168.0.1 -->|router (port 1)| -->206.196.128.1:1 ->internet
Box B = eth0 --192.168.0.2 -->|router (port 2)| -->206.196.128.1:2 ->internet
and the LAN would still be 192.168.0.x?
Would you need to add a hub between router and the boxes?
TIA,
David
Nathan wrote:
> > A common reframe on http://linuxquestons.org is:
> >
> > 4 boxes each with one(1) nic card and each having a seperate connection through a router to the internet (CABLE/DSL).
> >
> > IN THEORY could you set up LAN using a virtual network interface on that
> > one nic card i.e.
>
> Yeap, we utalize this for talking to power control devices and the like.
>
> -Nate
>
> > eth0 ----->router ---->internet
> > eth0:1 --->LAN
> >
> >
> > Calk this one up to lack of sleep :)
> >
> > David
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> --
> --
> "Whoever undertakes to set himself up as a judge of Truth and Knowledge is
> shipwrecked by the laughter of the gods."
> Albert Einstein
>
> Chisolm's First Corollary to Murphy's Second Law:
> When things just can't possibly get any worse, they will.
> --
next prev parent reply other threads:[~2002-07-10 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 5:22 Vitural Network Interfaces David Jackson
2002-07-10 5:55 ` Nathan
2002-07-10 10:32 ` David Jackson [this message]
2002-07-10 17:41 ` Nathan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D2C0D51.29C4C066@wcox.com \
--to=david.jay.jackson@wcox.com \
--cc=linux-admin@vger.kernel.org \
--cc=nate@nateworks.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox