Problems getting 2 NICs to work.

From: Kevin Kimmell (kevin_at_dynamictrend.com)
Date: 05/17/04

  • Next message: Alexander Dalloz: "Re: Module is unknown" 
    Date: Mon, 17 May 2004 09:28:46 -0400
To: For users of Fedora Core releases <fedora-list@redhat.com>

    Hi.

    I've got several HP Proliant servers running mostly Fedora versions of
    redhat. I'm using kernel 2.4.22-1 right now on the ones that are
    problematic.

    These MBs on the HPs have dual gigabit ethernet controllers in them.
    /proc/pci reports them correctly as "Broadcom Corporation NetXtreme
    BCM5704 Gigabit Ethernet (rev 2)".

    I've got two public class C networks with two separate ISPs. When I
    initialize eth0 to either of my public IP ranges with their respective
    gateways everything works just fine. So now I'm trying to add an IP from
    the other ISP's range so that I've got multiple pathways to these public
    servers.

    Whether I add a virtual copy of eth0 with the other ISPs IP/gateway
    combo or if I plug eth1 into the switch and give it one, networking
    stops working. I should mention that both ISPs come in to the same
    router and are in the smae switch plane so all wires from the servers
    are on the same set of switches.

    Here's the route table when things are ok:
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    204.117.218.0 * 255.255.255.0 U 0 0 0 eth0
    169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
    127.0.0.0 * 255.0.0.0 U 0 0 0 lo
    default 204.117.218.254 0.0.0.0 UG 0 0 0 eth0

    What the hell is that 169.254.0.0 statement? I've searched hi and lo and
    can't figure it out. I'm making a blind guess that it's an IPv6 thing? I
    didn't put it there and removing it doesn't survive a reboot.

    Anyhow, at this point all networking is fine. I can ping and trace out
    and vice versa. Now, when I initialize eth1 here's the table:

    Destination Gateway Genmask Flags Metric Ref Use Iface
    12.168.88.0 * 255.255.255.0 U 0 0 0 eth1
    204.117.218.0 * 255.255.255.0 U 0 0 0 eth0
    169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
    127.0.0.0 * 255.0.0.0 U 0 0 0 lo
    default 204.117.218.254 0.0.0.0 UG 0 0 0 eth0

    As soon as this is activated, networking stops functioning. I can't ping
    in or out. Am I missing some key step? I know that it works becasue I'm
    running a firewall on another machine that's running a 2.4.20 kernel and
    it was autoconfigured and it's functioning properly.

    Can anyone give me a clue?

    Thanks,
    Kevin 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Alexander Dalloz: "Re: Module is unknown"

    Relevant Pages

    • Re: Fedora on servers
      ... > Nick Miller wrote: ... >> was wondering if anyone here has been using fedora in a production ... Most of the application servers' OSs are determined ... Proliant but no kernel after that will, like FC3, apparently. ...
      (Fedora)
    • Re: Fedora Makes a Terrible Server?
      ... I've had very few problems, kernel issues are not really the fault of the Fedora team, sometimes you hit quirks but these do get sorted out. ... How many years have you maintained these servers and how much damage does downtime cause? ... Fedora is OK if downtime doesn't matter. ... The only real issue is a stable kernel for your requirements, everything else is less important, also I have a habit of running everything in user-space so it's a lot easier to virtualize or switch out the underlying OS if required. ...
      (Fedora)
    • FreeBSD 6.1, crashes and a lack of vmcores
      ... These servers run under extremely high load through a majority of the day and run a mix of postfix, MySQL and custom filter software using MFS partitions. ... The biggest frustration in this is that of the few dozen crashes we've had I've only been able to get one successful dump. ... kernel: kernel dumps on /dev/ad0s1b ...
      (freebsd-hackers)
    • HOWTO - use KLIPS instead of the backport of NETKEY to enable ipsec0 adapter with openswan.
      ... # When using openswan on a box providing multiple VPN tunnels you need KLIPS ... NETKEY and enable KLIPS by building a custom kernel. ... to remember is your NIC's and your network capabilities under the Networking ... You will also need to install the kernel-package: ...
      (Debian-User)
    • Re: Patch 4/6 randomize the stack pointer
      ... ASLR is a code injection/ret2libc exploit defense, ... actually prevents some things not protected by kernel-level protections. ... not just on servers; ... Kernel data structures, no. ...
      (Linux-Kernel)