On Sat, 2005-02-19 at 16:20 -0700, G Gambill wrote:
> Putting the two NICs on seperate networks (192.168.xxx.30 and
> 192.168.yyy.30) solved the ping both with only one cable oportunity.
>
> Still unable to ping the onboard NIC (now 192.168.1.30 255.255.255.0 at
> eth0).
>
> I tested the cables (swaped them) and they are both show good.
>
> It is as if the onboard NIC (eth0 RH 8 box) is bad (not working). I can
> ping it from the RH 8 box itself and it respondes. I tried pinging from a
> Win 98 box (no firewall) and still only one NIC (eth1 192.168.123.30)
> respondes.
>
> How can I make sure I have the correct MAC address in
> network-scripts/ifcfg-eth0? If it were the PCI card I could pull it out and
> read it off the card. Would a wrong MAC address cause this?
----
NO - I doubt if you have it working with the right kernel module.
This of course assumes that the motherboard NIC (typically called
'integrated') is actually turned on in BIOS.
It would probably help if you ran a new distro which could properly
detect the hardware and install a kernel which may not be available in
RH 8.0 kernels.
If you want to use the RH 8.0 installation that you have already
started, get it up to date as best as you can - perhaps with the latest
kernel & iptools & initscripts you possibly can
www.fedoralegacy.org or
at least from a red hat mirror or from here...
<
ftp://ftp.redhat.com/pub/redhat/linux/updates/8.0/en/os/>
See if there's anything aliased in /etc/modules.conf that references the
eth0 adaptor and delete it. See if there's anything
in /etc/sysconfig/network-scripts/ifcfg-eth0 that references the kernel
module used and remove it.
then as root...
run 'depmod -ae' #rechecks modules.conf
run 'kudzu' and see if it detects the network adaptor.
It should detect the adaptor and ask if you want to migrate the settings
of eth0 to this new adaptor (yes is answer if that is the question).
My suspicion is that the motherboard NIC is a broadcom adaptor that may
not be supported by RH 8.0 type 2.4.lower_number_kernel but may be
supported by something in the 2.4.20 range - that is why the updating is
important.
if it fails to work or detect it...probably would be a good idea to post
relevant sections in output of 'lspci -v'
----
> >
> > It might be easier if we knew what you were trying to do.
> >
>
> Wanting this box to become a firewall between a WIFI router and my main
> network. Moving (eventually) the samba server function else where.
----
One of the problems with firewalls is that you have to keep updating
them and with RH 8.0 - I don't know the activity level of
fedoralegacy.org - if they stop releasing security updates for 8.0, it's
end of line. Probably best to use something like an RHEL 3 clone that
still has 3.5 years of security updates or debian - though I think the
clock is ticking on woody.
----
> Probably over kill, more of a learning curve.
>
> > For your testing purposes - it may help to try commands like...
> >
> > ifdown eth0
> > ifup eth1
>
> Good find. The cables are somewhat buried. Thanks.
----
amazing how much networking troubleshooting is helped by little things
like that.
Good luck - let me know what happens.
Craig
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)