All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommy McNeely <Tommy.McNeely@Sun.COM>
To: netfilter@lists.netfilter.org
Subject: OT: curious about eth0/eth1
Date: Tue, 07 Jan 2003 16:59:53 -0700	[thread overview]
Message-ID: <6620000.1041983993@leverage> (raw)


I am curious about why people choose to make a certain interface internal 
or external...

I have always made my "eth0" interface my inside interface.. and once I 
have the box UP and RUNNING (and firewalled), then bring up my outside 
interface "eth1" ... My primary network for smb/nfs/whatever is my inside 
network (thus eth0)... The outside interface is just a "extra interface" 
that I can add on (or move/change/delete) or even make it ppp0 if I happen 
to be changing ISP's :)

I notice several people pick eth0 as their outside interface, and sorta "oh 
yea" the rest of the inside network is on eth1.  I know the linux kernel 
could really care less what they are called, its mostly a "neatness" thing 
I guess... Also it seems like that leaves your box open to attack from the 
time it installs (if you do a NET based install) till the time you get 
around to actually putting a firewall on it.

Again.. I am just curious as to why some do it one way.. and some the 
other... the above is only MY opinion, and could be dreadfully wrong :)

Tommy



--
Tommy McNeely         --        Tommy.McNeely@Sun.COM
Sun Microsystems - IT Ops - Broomfield Campus Support
Phone:  x50888 / 303-464-4888  --  Fax:  720-566-3168



             reply	other threads:[~2003-01-07 23:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 23:59 Tommy McNeely [this message]
2003-01-08  3:47 ` OT: curious about eth0/eth1 Joel Newkirk
2003-01-08  8:21   ` Arnt Karlsen
2003-01-08 16:27   ` Tommy McNeely
2003-01-08 11:40 ` Maciej Soltysiak

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=6620000.1041983993@leverage \
    --to=tommy.mcneely@sun.com \
    --cc=netfilter@lists.netfilter.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.