TXCSUM on bge0 breaks bridging

From: Damian Gerow (dgerow_at_afflictions.org)
Date: 04/25/05

  • Next message: Daniel O'Connor: "Re: [PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?"
    Date: Sun, 24 Apr 2005 18:39:41 -0400
    To: stable@freebsd.org
    
    

    Someone just helped me through a bridging problem I was having, and I
    thought I'd throw the problem out to the list to see if it's a bug, or at
    least, for archival purposes.

    I have a machine that I'm using as a workstation, that I would also like to
    use to bridge a home LAN. It has two interfaces: bge and fxp.

        bge0 -> 172.19.206.56
        fxp0 -> ipless

    When I bridged the two interfaces, the workstation could only talk on the
    bge side of the network, not the fxp side. Note that any device on either
    side of the network could speak to the other side.

    Some initial debugging:

        # sysctl net.link.ether.bridge
        net.link.ether.bridge.version: 031224
        net.link.ether.bridge.debug: 0
        net.link.ether.bridge.ipf: 0
        net.link.ether.bridge.ipfw: 0
        net.link.ether.bridge.copy: 0
        net.link.ether.bridge.ipfw_drop: 0
        net.link.ether.bridge.ipfw_collisions: 0
        net.link.ether.bridge.packets: 2687590
        net.link.ether.bridge.dropped: 0
        net.link.ether.bridge.predict: 70
        net.link.ether.bridge.enable: 1
        net.link.ether.bridge.config: fxp0 bge0
        #

    I tcpdump'ed on the fxp interface, and could see a device nab an address via
    DHCP, and an ARP to the device from my workstation seemed to work, but I
    could not ping it. It was pointed out to me that the fxp does off-board
    checksumming, and what would happen if I disabled the one on bge0? Well, it
    fixed the problem.

    I can have TXCSUM enabled *only* on fxp0, not on bge0: so long as TXCSUM is
    disabled on bge0, irregardless of the state of fxp0, I can talk to any
    device attached to fxp0.
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: Daniel O'Connor: "Re: [PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?"

    Relevant Pages

    • Re: fxp multicast forwarding problems
      ... msk0, fxp0 got totally hosed. ... I wonder if this is related to the problems with fxp multicast ... Enabling and disabling promiscuous mode ...
      (freebsd-stable)
    • fxp multicast forwarding problems
      ... Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. ... I was running PIM-SM and IGMPv2 router-mode on the box at the time. ... I wonder if this is related to the problems with fxp multicast transmission I saw back in April. ... Enabling and disabling promiscuous mode ...
      (freebsd-stable)
    • Re: fxp multicast forwarding problems
      ... msk0, fxp0 got totally hosed. ... I was running PIM-SM and IGMPv2 router-mode on the box at the time. ... I wonder if this is related to the problems with fxp multicast ... Enabling and disabling promiscuous mode ...
      (freebsd-stable)
    • Re: fxp EEPROM checksum mismatch in recent -CURRENT
      ... > Yesterday's -CURRENT fails to attach the onboard fxp on my Gigabyte ... > fxp0: Disabling dynamic standby mode in EEPROM ... > fxp0: MII without any PHY! ...
      (freebsd-current)