Collision on NIC

From: Erwane Breton (breton_at_erwane.net)
Date: 05/29/03

  • Next message: Matthew D. Fuller: "Re: Collision on NIC"
    Date: Thu, 29 May 2003 15:51:43 +0200
    To: freebsd-net@freebsd.org
    
    

    Hi,

    Few weeks ago, i discovered i have collision on my NIC for my Adsl ethernet modem (ed0). After research i found the other FreeBSD box i used, have same problem.

    Take a look.

    On my FreeBSD box
    Network interface status:
    Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll
    ed0 1500 <Link#1> 00:00:b4:bc:f0:b6 21852457 0 280187344 28530965 7 3906410421 8584
    ed0 1500 10/24 10.0.0.254 8 - 384 13 - 632 -
    xl0 1500 <Link#2> 00:50:da:4c:ed:c5 9470610 6 2735351753 13266752 0 2582350504 0
    xl0 1500 10.1.1/24 10.1.1.254 6212939 - 2395538679 8600799 - 1389994967 -
    lo0 16384 <Link#3> 513933 0 106611959 513933 0 106611959 0
    lo0 16384 your-net localhost 358554 - 78001172 358554 - 78001172 -
    tun0 1492 <Link#4> 21878874 0 4108172057 28557467 0 3406988782 0
    tun0 1492 start-213-41- xxxxxxxxx 192029 - 92763765 380021 - 60316512 -

    Lot of collisions (for 10 days uptime)

    # ifconfig
    ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet 10.0.0.254 netmask 0xffffff00 broadcast 10.0.0.255
            ether 00:00:b4:bc:f0:b6
    xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            options=3<RXCSUM,TXCSUM>
            inet 10.1.1.254 netmask 0xffffff00 broadcast 10.1.1.255
            ether 00:50:da:4c:ed:c5
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
            inet 127.0.0.1 netmask 0xff000000
    tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
            inet xxx.xxx.xxx.xxx --> xx.xx.xx.xx netmask 0xffffff00
            Opened by PID 20935

    # netstat -rn
    Routing tables

    Internet:
    Destination Gateway Flags Refs Use Netif Expire
    default 62.4.16.251 UGSc 153 44612 tun0
    10/24 link#1 UC 1 0 ed0
    10.0.0.254 00:00:b4:bc:f0:b6 UHLW 0 14 lo0
    10.1.1/24 link#2 UC 3 0 xl0
    10.1.1.10 00:10:b5:ae:06:da UHLW 10 11844185 xl0 862
    10.1.1.254 00:50:da:4c:ed:c5 UHLW 12 162524 lo0
    10.1.1.255 ff:ff:ff:ff:ff:ff UHLWb 2 4610 xl0
    62.4.16.251 213.41.144.146 UH 151 3820 tun0
    127.0.0.1 127.0.0.1 UH 3 410587 lo0

    All this route is generate BY FreeBSD. I haven't change anything

    I think the problem came from here. I have route to 10/24 use ed0 or my network (where other pc is connected (10.1.1.0) is on xl0.
    Maybe not come from here, i don't know.

    If someone have idea or same problem, and solution :)

    Thanks

    Erwan

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

  • Next message: Matthew D. Fuller: "Re: Collision on NIC"

    Relevant Pages

    • Re: Home Network, step by step?
      ... which one is my incoming internet connection? ... bfe0: flags=8843mtu 1500 ... >>recognise the information in the FreeBSD handbook. ... > to use one of the computers you already have and NAT. ...
      (freebsd-newbies)
    • Re: freebsd-net Digest, Vol 181, Issue 9
      ... FreeBSD 6.1 + ath0 + NAT ... connection to the Internet, and a Netgear WG311T wireless Ethernet card ... ath0: flags=8843 mtu 1500 ...
      (freebsd-net)
    • fxp0: discard oversize frame leads to icmp 36: ip reassembly time exceeded
      ... I've been searching through archives and many freebsd resources and can't ... I'm running a 5.4-STABLE freebsd firewall. ... to fix the problem by restricting mtu size, ...
      (freebsd-stable)
    • WinXP/FreeBSD - IPSec Tunnel Over Wireless (MTU Problems?)
      ... At this point, my problem is more with XP than with FreeBSD, ... a laptop running XP with a Netgear MA521. ... However, if it's an MTU issue, then ... large pings should also fail. ...
      (freebsd-questions)
    • FreeBSD PPPoE Problems
      ... Windows 2000 box has been configured to use ... From the FreeBSD box I can ping the ... flags=8843mtu ... nat port tcp 192.168.1.1:5800-5950 5800-5950 ...
      (freebsd-questions)