Re: More help needed please

jim.marnell_at_cca-int.com
Date: 06/24/04

  • Next message: santhosh: "RE: Problems in setting display variable for X Windows server"
    To: General Red Hat Linux discussion list <redhat-list@redhat.com>
    Date: Thu, 24 Jun 2004 15:18:18 -0400
    
    

    Thanks to all responders. Both nics are set to come up at boot time.
    Here's more info...
    [root@redfish root]# netstat -nr
    Kernel IP routing table
    Destination Gateway Genmask Flags MSS Window irtt
    Iface
    0.0.0.0 204.62.134.209 255.255.255.255 UGH 0 0 0
    eth0
    10.10.30.0 0.0.0.0 255.255.255.0 U 0 0 0
    eth1
    204.62.134.0 0.0.0.0 255.255.255.0 U 0 0 0
    eth0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
    lo
    0.0.0.0 204.62.134.248 0.0.0.0 UG 0 0 0
    eth0
    [root@redfish root]# ifconfig eth0
    eth0 Link encap:Ethernet HWaddr 00:10:5A:11:83:C0
              inet addr:204.62.134.209 Bcast:204.62.134.255
    Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
              RX packets:5899 errors:0 dropped:0 overruns:0 frame:0
              TX packets:824 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100
              RX bytes:590413 (576.5 Kb) TX bytes:94622 (92.4 Kb)
              Interrupt:10 Base address:0xe400

    [root@redfish root]# ifconfig eth1
    eth1 Link encap:Ethernet HWaddr 00:04:75:81:5A:01
              inet addr:10.10.30.248 Bcast:10.10.30.255 Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100
              RX bytes:0 (0.0 b) TX bytes:2880 (2.8 Kb)
              Interrupt:5 Base address:0xe800

    [root@redfish root]#
    That first routing entry should not be there and may be a bug. In an
    attempt to solve this problem I added a route on the eth1 interface via
    system settings/network. It didn't help so I removed it but it remains in
    my routing table.
    My real default route is the last entry.
    Do I need any routing in place for one nic to talk to the other in rh
    land?
    -Jim

    Ed Wilts <ewilts@ewilts.org>
    Sent by: redhat-list-bounces@redhat.com
    06/24/2004 02:57 PM
    Please respond to
    General Red Hat Linux discussion list <redhat-list@redhat.com>

    To
    General Red Hat Linux discussion list <redhat-list@redhat.com>
    cc

    Subject
    Re: More help needed please

    On Thu, Jun 24, 2004 at 02:37:39PM -0400, jim.marnell@cca-int.com wrote:
    > Anyone else care to take a stab at why my rh 8 box with 2 nics cannot
    talk
    > to each other. I'll try anything.
    > eth0 can ping itself
    > eth1 can ping itself
    > eth0 can ping eth1
    > eth1 CANNOT ping eth0
    >
    > ip_forward has been set to 1

    Do you have routes to get from where you are to where you want to go?

    # netstat -rn

    -- 
    Ed Wilts, RHCE
    Mounds View, MN, USA
    mailto:ewilts@ewilts.org
    Member #1, Red Hat Community Ambassador Program
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: santhosh: "RE: Problems in setting display variable for X Windows server"

    Relevant Pages

    • Re: Routing
      ... I can ping hosts on the 192.168.3.0/24 network, ... Subject: Routing ...
      (Debian-User)
    • Re: intermittent cable connection
      ... > Save the routing table at both times and compare them. ... network card fault is that even when network down, ...
      (comp.unix.admin)
    • changing destination address after routing
      ... I want to access eth0 through subnet 192.168.1.0/24 and eth1 through ... for it to make sense to the gateway after routing has ...
      (comp.os.linux.networking)
    • two nics to one lan
      ... Whatever happened caused the eth1 route to be non-functional, ... but all traffic bound to 172.16.59.0/24 was being routed through eth1. ... Unfortunately I don't have the routing table from then, ... was down) there was one well-configured route via eth0 for that subnet. ...
      (comp.os.linux.networking)
    • 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)