Two interfaces on the same network

From: AL Chane (al_chane_at_issc.com.tw)
Date: 06/09/04

  • Next message: Roman Kurakin: "Re: Two interfaces on the same network"
    Date: Wed, 09 Jun 2004 11:21:56 +0800
    To: freebsd-net@freebsd.org
    
    

    Hi, there:

         I have two interfaces on my linux PC in the same network:

    >ifconfig eth0 172.20.1.30 netmask 255.255.255.0
    >ifconfig eth1 172.20.1.31 netmask 255.255.255.0

         Another Windows PC with IP 172.20.1.32 netmask 255.255.255.0

         I found that in the same network, Linux PC only use one interface
    eth0 for outbound/inbound traffics no matter what. Even if I use Windows
    PC (172.20.1.32) to ping Linux PC's eth1 (172.20.1.31), Linux still use
    eth0 to reply. That is, if I unplug eth0's wire, eth1 won't work too.

         Does anyone have the same issue on how to make two interfaces
    work in the same network? I search 2003 archive, some said it can be
    done by set second interface (eth1) netmask to 255.255.255.255, but
    i tried and it doesn't work for me.

         Helps from you are highly appreciated!

    Thanks

    AL

    _______________________________________________
    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: Roman Kurakin: "Re: Two interfaces on the same network"

    Relevant Pages

    • Network Puzzle with 2 NICs
      ... Windows can no longer ping eth0 but it can PING eth1 and eth1 can PING ...
      (comp.os.linux.networking)
    • Two interfaces on the same network
      ... eth0 for outbound/inbound traffics no matter what. ... Even if I use Windows ... PC to ping Linux PC's eth1, ... That is, if I unplug eth0's wire, eth1 won't work too. ...
      (RedHat)
    • speed up my LAN
      ... mii-tool -l -w eth0 ... Sep 25 01:09:01 dave kernel: eth1: Link changed: ... basic mode: autonegotiation enabled ... basic status: autonegotiation complete, link ok ...
      (comp.os.linux.networking)
    • Re: setting-up a dmz
      ... Not provide any actual log messages? ... No shorewall, i prefer a own debian iptables firewall:) ... eth1: link up, 10Mbps, half-duplex, lpa 0x0000 ... ADDRCONF: eth0: link is not ready ...
      (Debian-User)
    • Kernel upgrade 2.4.18-14 -> 2.4.23 (rh8)
      ... I just recompiled a new kernel, ... eth0: Broadcom BCM5701 Integrated Copper transceiver found ... eth1: Broadcom BCM5701 Integrated Copper transceiver found ... Dec 5 10:07:55 network: Setting network parameters: succeeded ...
      (RedHat)