Definition of interfaces in ifconfig

From: Charles Howse (chowse_at_charter.net)
Date: 08/16/03

  • Next message: clayton rollins: "Re: Definition of interfaces in ifconfig" 
    To: <freebsd-newbies@freebsd.org>
Date: Sat, 16 Aug 2003 15:05:41 -0500

    Hello List,

    When I do:
    # ifconfig

    I see the following interfaces listed:

    tx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet 192.168.254.3 netmask 0xffffff00 broadcast 192.168.254.255
            inet6 fe80::2e0:29ff:fe11:ff8a%tx0 prefixlen 64 scopeid 0x1
            ether 00:e0:29:11:ff:8a
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
    sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
    faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
            inet6 ::1 prefixlen 128
            inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
            inet 127.0.0.1 netmask 0xff000000
    ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500

    I know tx0 is my one and only nic, we can keep it.
    I assume lp0 is the parallel port, don't need it, don't plan to do any
    printing from this machine.
    I assume lo0 is the loopback interface, that's cool.
    I know I don't need a PPP or SLIP interface, I have a LAN connection to
    the Internet.

    I've grepped LINT and GENERIC with no joy for the definitions, I've
    Googled with no joy so far, there are no man pages for these devices,
    where can I find out what they are?

    I realize the only ones actually running are tx0 and lo0, but wouldn't
    it be OK to remove the ones I'll never need?

    Can I get rid of some of these guys? How?

    Thanks,
    Charles

    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"

  • Next message: clayton rollins: "Re: Definition of interfaces in ifconfig"

    Relevant Pages

    • Re: FRS Only replicates on inbound connection, no changes go out.
      ... Mike Drechsler - SPAM PROTECTED EMAIL ... protocol can go higher than this on a physical interface that supports larger packet sizes such as gigabit ethernet. ... Ethernet has just become so common that you might assume that 1500 is somehow tied to basic TCP/IP specifications. ... LDAP will work just fine with MTU values lower than 1500 unless you are thinking about the problem experienced with Windows 2003 sp1 or the MS05-019 patch resolved in a hotfix referred to in KB article 898060? ...
      (microsoft.public.windows.server.active_directory)
    • Re: Panic in 6.2-PRERELEASE with bge on amd64
      ... interface is enough to completely panic the driver and then the kernel, ... I added some sysctls and found it annoying to have to do down/up ... Similarly for the mtu ioctl. ... As this was connected to a gigE switch with mtu left at 1500 I supposed ...
      (freebsd-stable)
    • Re: 6.2 mtu now limits size of incomming packet
      ... Incoming interface must have mtu set to the same mtu as all other hosts on the same L2 network. ... Thus the router can accept the incoming packet but may drop and notify on a frame that is too large to exit the outgoing interface. ...
      (freebsd-net)
    • Re: Problem with large pings with dont fragment set
      ... > pings with the DF bit set over a GRE tunnel. ... I don't know about GRE tunnels but they very likely add ... > the MTU on the tunnel interface is 552. ...
      (comp.os.linux.networking)
    • Re: Dropped packets via ISR
      ... I also used ping plotter... ... Tried changing from full duplex to half duplex to auto and that did ... "1) Interface MTU at 1500 is fine. ...
      (comp.dcom.sys.cisco)