Re: redundant ethernet interfaces

From: Ruslan Ermilov (ru_at_FreeBSD.org)
Date: 02/18/05

  • Next message: Matthew D. Fuller: "Re: nslookup problem on FreeBSD-5.3: problem with non FQN domain"
    Date: Fri, 18 Feb 2005 10:52:28 +0200
    To: Marko Lerota <marko.lerota@optima-telekom.hr>
    
    
    

    On Fri, Feb 18, 2005 at 09:23:09AM +0100, Marko Lerota wrote:
    > I have two nic bge0 and bge0, and I would like them
    > to have the same IP address in case that my redundant
    > switch stop responding. Bridge is not an option,
    > I tried with netgraph but I did not succeed.
    > Does anyone have some solution?
    >
    > I followed the examples from google groups and I stuck with
    > duplicated packets when both ethernets are plugged and
    > 50% packet loss when one ethernet is unplugged, damn !!#@!#@!$%^@$#@
    >
    > here is my config
    >
    > rc.conf
    > ifconfig_bge0="1.2.3.4 netmask 255.255.0.0 media 100baseTX mediaopt
    > full-duplex"
    > ifconfig_bge1="media 100baseTX mediaopt full-duplex"
    >
    > and /usr/local/etc/rc.d/bonding.sh
    >
    > #!/bin/sh
    > ifconfig bge1 up
    > kldload /boot/kernel/ng_ether.ko
    > kldload /boot/kernel/ng_one2many.ko
    > ngctl mkpeer bge0: one2many upper one
    > ngctl connect bge0: bge0:upper lower many0
    > ngctl connect bge1: bge0:upper lower many1
    > ngctl msg bge1: setpromisc 1
    > ngctl msg bge1: setautosrc 0
    > ngctl msg bge0:upper setconfig "{xmitAlg=1 failAlg=1 enabledLinks =[ 1
    > 1 ] }"
    >
    > manual for this sucks
    >
    This isn't going to work -- packets will be transmitted in round-robin
    manner, which is not what you want for failure protection. What you
    need is to use xmitAlg=2 (NG_ONE2MANY_XMIT_ALL) so that each frame is
    delivered out of all interfaces, and then enable STP on your switches.
    I didn't test it, but it should work. The example in the ng_one2many(4)
    manpage, like the one you quote above but with four interfaces, is to
    demonstrate how to set up a 400Mbit/s connection between two hosts.

    Cheers,

    -- 
    Ruslan Ermilov
    ru@FreeBSD.org
    FreeBSD committer
    
    



  • Next message: Matthew D. Fuller: "Re: nslookup problem on FreeBSD-5.3: problem with non FQN domain"

    Relevant Pages

    • Re: Intrusion Question
      ... >interfaces directly connected to PC at which program is installed. ... Yes, that is the entire purpose of a switch, as opposed to a hub, or the ... Install the desired ... the firewall, and what is being done to correct THAT problem? ...
      (alt.computer.security)
    • Re: hostname standard
      ... newhost # ssh oldhost ./unplug.sh ... IP aliases, that is logical interfaces, altrough I think Solaris ifconfig ... ARP flood to switch in order for switch to update it's ARP table. ...
      (comp.unix.solaris)
    • Re: Intra-switch VLANs Netgear
      ... The pictures don't match the commands...the interfaces are totally ... different and they don't mention what the configuration should be like ... on the other end of the switch. ... Isn't the point of having a layer 3 switch and vlans to be able to ...
      (comp.dcom.lans.ethernet)
    • Re: commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices - broke my
      ... I was doing that for a while, but now Debian and RedHat and most other modern distros have a udev rules file called something like: ... switch: ... A Debian netinst net-boot VLAN with support for PXE and OpenFirmware ... Most of those interfaces are virtual and created by custom "/etc/ ...
      (Linux-Kernel)
    • Re: [fw-wiz] PIX stateful failover and crossover cables
      ... The only time I know a switch is mandatory is when using the GBIC ... >where it was recommended that pix stateful interface traffic always ... >serial cable or LAN failover, however I cannot find it again, would ...
      (Firewall-Wizards)