home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.hardware
- Path: sparky!uunet!gatech!destroyer!sol.ctr.columbia.edu!emory!nntp.msstate.edu!news
- From: fwp@CC.MsState.Edu (Frank Peters)
- Subject: Re: Using non-TCP/IP ethernet
- Message-ID: <1993Jan25.003221.20881@ra.msstate.edu>
- Keywords: ethernet interface network
- Sender: news@ra.msstate.edu
- Nntp-Posting-Host: jester.cc.msstate.edu
- Organization: Computing Center, Mississippi State University
- References: <1993Jan22.171043.23286@msc.cornell.edu> <1993Jan23.230534.4256@nobeltech.se>
- Date: Mon, 25 Jan 1993 00:32:21 GMT
- Lines: 17
-
- In article <1993Jan23.230534.4256@nobeltech.se> ppan@nobeltech.se (Per Andersson) says:
- : In article <1993Jan22.171043.23286@msc.cornell.edu> savage@msc.cornell.edu (Daniel Svitavsky) writes:
- : >
- : > Also, ifconfig shows the second ethernet card as having the same ethernet
- : >address as the first. Do Suns really have one hardware address per machine?
- :
- : One reason to do this might be that software licenses are fixed to the
- : machines ethernet-address, but making hardware kludges to support stupid
- : software is a bad thing IMO.
-
- Another reason to do it is simply to use fewer ethernet addresses.
-
- You can give interfaces separate ethernet addresses with the ifconfig
- command though.
- --
- Frank Peters - UNIX Systems Programmer - Mississippi State University
- Internet: fwp@CC.MsState.Edu - Phone: (601)325-7030 - FAX: (601)325-8921
-