Interesting, I had a similar sounding problem with a dual onboard Broadcom card.
I assumed it was a routing table issue like I described and decided that just hooking my two switches together was a beter option anyway so I didn't bother to look into the problem since that setup didn't require a gateway machine. I wonder of it was a FC2 issue after all? On Wed, 09 Feb 2005 19:46:32 -0700, R Hamann <[EMAIL PROTECTED]> wrote: > Wow! Found the error, but still can't believe it. > > The system was previously set up under RH 6.2 with two PIC NICs, the > onboard was disabled. The onboard and one NIC were 3com 3c509s. I've > had the onboard disabled and been trying to use the NIC. Googling the > problem I could find no definitive answers, but several people with > similar, non-deterministic like problems. One person suggested that > it was obvious that FC2 has a networking problem related to IRQs and > many people have had probs with the 3c59x, yet many people say "What > problems?" > > TO make a long story short, I took out the 3c509 NIC and reenabled > the onboard in the bios - everything is working now (at least, > networking is, I'm about to install Oscar after dinner!) > > Thanks, and I hope my trobles can help someone else before they spend > hours banging their head against the screen. > > Ron > > On Wed, 09 Feb 2005 18:45:51 -0700 > "R Hamann" <[EMAIL PROTECTED]> wrote: > > On Wed, 9 Feb 2005 17:14:45 -0800 > > "Bernard Li" <[EMAIL PROTECTED]> wrote: > >> Hey Ron: > >> > >> Can you show some examples of 'pings on the inside net'? > >> > >> I assume that you still have some hosts from your previous Scyld > >> installation, are those hosts really still up on the network? Is it > >> possible that they depended on the original headnode (now an OSCAR > >> headnode) for DHCP? > >> > >> Everything looks good from here... > >> > >> Cheers, > >> > >> Bernard > >> > >>> -----Original Message----- > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED] On Behalf Of R > >>>Hamann > > [EMAIL PROTECTED] root]# ping 192.168.1.100 > > PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data. > > From 192.168.1.1 icmp_seq=0 Destination Host Unreachable > > From 192.168.1.1 icmp_seq=1 Destination Host Unreachable > > From 192.168.1.1 icmp_seq=2 Destination Host Unreachable > > > > This is what it returns. In this case, I booted one disc with a > >livecd and manually assigned the address. Both machines are > >connected to the same switch. When I ping from the other machine, it > >returns nothing at all, the same way pinging a non-existent IP > >address usually works. > > > > In this case, it doesn't even look like the machine is even > >accessing the net properly. I used the same livecd on the master and > >it worked fine, both internal and external networks. > > > > This is really strange! > > > > R > > > > > > > > --- 192.168.1.100 ping statistics --- > > 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time > >3999ms > > , pipe 4 > > > > > > > >>> Sent: Wednesday, February 09, 2005 15:41 > >>> To: [email protected] > >>> Subject: [Oscar-users] Destination host unreachable > >>> > >>> I just did a fresh install of Fedora Core 2 on a machine that > >>> will be the master for an Oscar cluster. It was a Scyld > >>> cluster, and the upgrade didn't work. The ooutside NIC > >>> worked fine, the pings on the inside net kept returning > >>> "Destination Host Unreachable." > >>> > >>> So I followed my lab manager's advice and teh advice of the > >>> Oscar docs and Bernard and reloaded Fedora from scratch. > >>> > >>> Still, same problem. The internal NIC is a 3c509 (Tornado) > >>> and the outside NIC is an Intel Ethernet pro 100. > >>> > >>> I swiched the cards and cables so the outside NIC is the > >>> 3c509 and the inside NIC is the Intel. Same error. > >>> > >>> Is there some trick to a dual-netted box that I don't know? > >>> > >>> R > >>> > >>> (some info below, real ip's camoflaged) > >>> ifconfig results: > >>> [EMAIL PROTECTED] root]# ifconfig eth0 > >>> eth0 Link encap:Ethernet HWaddr 00:50:DA:58:45:7B > >>> inet addr:1xx.1xx.1xx.xx Bcast:1xx.1xx.1xx.255 > >>> Mask:255.255.255.0 > >>> inet6 addr: fe80::250:daff:fe58:457b/64 Scope:Link > >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >>> RX packets:22548 errors:0 dropped:0 overruns:1 frame:0 > >>> TX packets:16375 errors:0 dropped:0 overruns:0 carrier:0 > >>> collisions:1335 txqueuelen:1000 > >>> RX bytes:23087629 (22.0 Mb) TX bytes:1948423 (1.8 Mb) > >>> Interrupt:9 Base address:0xdc00 > >>> > >>> [EMAIL PROTECTED] root]# ifconfig eth2 > >>> eth2 Link encap:Ethernet HWaddr 00:90:27:34:5F:6B > >>> inet addr:192.168.1.1 Bcast:192.168.1.255 > >>> Mask:255.255.255.0 > >>> inet6 addr: fe80::290:27ff:fe34:5f6b/64 Scope:Link > >>> UP BROADCAST MULTICAST MTU:1500 Metric:1 > >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > >>> TX packets:1206 errors:0 dropped:0 overruns:1206 > >>>carrier:0 > >>> collisions:0 txqueuelen:1000 > >>> RX bytes:0 (0.0 b) TX bytes:50820 (49.6 Kb) > >>> Interrupt:10 Base address:0x4000 > >>> > >>> > >>> route results > >>> [EMAIL PROTECTED] root]# route -n > >>> Kernel IP routing table > >>> Destination Gateway Genmask Flags Metric Ref > >>> Use Iface > >>> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 > >>> 0 eth2 > >>> 1xx.1xx.1xx.0 0.0.0.0 255.255.255.0 U 0 0 > >>> 0 eth0 > >>> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > >>> 0 eth2 > >>> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 > >>> 0 lo > >>> 0.0.0.0 1xx.1xx.1xx.1 0.0.0.0 UG 0 0 > >>> 0 eth0 > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from > >>> real users. > >>> Discover which products truly live up to the hype. Start reading > >>>now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Oscar-users mailing list > >>> [email protected] > >>> https://lists.sourceforge.net/lists/listinfo/oscar-users > >>> > >> > >> > >> ------------------------------------------------------- > >> SF email is sponsored by - The IT Product Guide > >> Read honest & candid reviews on hundreds of IT Products from real > >>users. > >> Discover which products truly live up to the hype. Start reading > >>now. > >> http://ads.osdn.com/?ad_ide95&alloc_id396&op�ick > >> _______________________________________________ > >> Oscar-users mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real > >users. > > Discover which products truly live up to the hype. Start reading > >now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Oscar-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/oscar-users > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Oscar-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-users > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
