Subject: Re: How to find network device...
To: Lets Go Canes! <LetsGoCanes@webmail.bellsouth.net>
From: Brian Stark <bstark@siemens-psc.com>
List: netbsd-help
Date: 06/28/2000 15:41:11
On Wed, 28 Jun 2000, Lets Go Canes! wrote:
> Hi all.
>
> Just installed NetBSD on a Sony VAIO PCG-F360 laptop. This laptop has a docking station with an Ethernet port. I'm trying to configure the network, but first I need to know which device to use with ifconfig.
>
> So, how does one tell which device is the network adapter?
Can you post a copy of the output from "dmesg"? On my Sony VAIO PCG-N505VX
I see the following section from dmesg about my Ethernet card:
ex0 at cardbus0 dev 0 function 0: 3Com 3c575B-TX Ethernet
ex0: interrupting at 9
ex0: MAC address 00:50:da:99:e6:ae
tqphy0 at ex0 phy 0: 78Q2120 10/100 media interface, rev. 11
tqphy0: 10baseT, 100baseTX, auto
> On a related note, netstat -i lists the interfaces provided below.
> Can someone please confirm the identity of the inerfaces, and
> indicate what the unknown (to me) interfaces are?
>
> lo0 - loopback
> ppp0 - point-to-point
> ppp1 - point-to-point (different from ppp0?)
ppp1 is the second ppp network interface available.
> sl0 - SLIP
> sl1 - SLIP (different from sl0?)
sl1 is the second sl network interface available. I think you see how this
goes... you have the network interface name and the number at the end is
the number of that type of interface in the system, starting from 0.
> strip - ???
> strip - ??? (yes, it is listed twice; truncated name?)
"man 4 strip" reports "strip - Metricom Ricochet packet radio wireless
network device"
> tun0 - ??? IP tunnel of some sort?
> tun1 - ??? IP tunnel of some sort?
"man 4 tun" reports "tun - tunnel software network interface"
> gre0 - ???
> gre1 - ???
"man 4 gre" reports "gre - encapsulating network device"
> ipip0 - ???
> ipip1 - ???
"man 4 ipip" reports "ipip - encapsulating network device"
> eon0 - ???
Not really sure about this one. There are some references to this in the
directory /usr/src/sys/netinet:
palomino:bstark$ grep -i EON *
in.h:#define IPPROTO_EON 80 /* ISO cnlp */
in_proto.c:#include "opt_eon.h" /* ISO CLNL over IP */
in_proto.c:#ifdef EON
in_proto.c:#include <netiso/eonvar.h>
in_proto.c:#endif /* EON */
in_proto.c:/* EON (ISO CLNL over IP) */
in_proto.c:#ifdef EON
in_proto.c:{ SOCK_RAW, &inetdomain, IPPROTO_EON, 0,
in_proto.c: eoninput, 0, eonctlinput, 0,
in_proto.c: eonprotoinit, 0, 0, 0,
in_proto.c:#endif /* EON */
ip_state.c: * in fin_mp such that if someone uses it we'll get
ip_state.c: * in fin_mp such that if someone uses it we'll get
tcp_input.c: * soreceive. It's hard to imagine someone
tcp_output.c: * I'm not quite sure about this (could someone comment).
palomino:bstark$
Perhaps someone else could elaborate on this...
Looking at my notes, here are some RFCs that may be of some interest:
rfc1701.txt Generic Routing Encapsulation (GRE) (obsoleted by 2784????)
rfc1702.txt Generic Routing Encapsulation over IPv4 networks
rfc2003.txt IP Encapsulation within IP
rfc2004.txt Minimal Encapsulation within IP
rfc2784.txt Generic Routing Encapsulation (GRE)
Brian
-------------------------------------------------------------------------
| Brian Stark | Internet : bstark@siemens-psc.com |
| Siemens PT&D, Inc. | Voice : +1 763 536-4697 |
| Power Systems Control Division | Fax : +1 763 536-4919 |
| 7225 Northland Drive, Brooklyn Park, Minnesota 55428 USA |
-------------------------------------------------------------------------