Bringing up 2nd NIC card
Ken Schweigert
yellowdog-general@lists.terrasoftsolutions.com
Sat Mar 30 04:38:01 2002
David,
I suspect it's a routing issue. But first, let's make sure both interfaces came up:
[ken@byte-8 ken]$ /sbin/ifconfig -a
Then check your routing table:
[ken@byte-8 ken]$ /sbin/route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.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 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
This last line is your default gateway. Sometimes when you specify GATEWAY=
in your ifcfg-* files, it'll try to set both of them as default, thus breaking
everything. I would try setting those to be blank and modifying
/etc/sysconfig/network to have GATEWAY=65.112.29.33 and GATEWAYDEV=eth1.
If this doesn't fix it, post the results of the two commands above.
-ken
On Fri, Mar 29, 2002 at 12:01:43PM -0800, David McInnis wrote:
> Ken,
>
> First, I really appreciate all of your help on this issue.
>
> When my machine comes up and I try to ping say, 65.112.29.33, it
> attempts to ping FROM the 192.168.0.2 address. And not the 65.112.29.36
> address.
>
> It appears the eth0 is dead, even though the startup said [ok].
>
> I cannot ping the 65.112.29.36 address from an external machine.
>
> I cannot even do it from the same machine. Can you help here?
>
> Here are my settings.
>
> DEVICE=eth1
> ONBOOT=yes
> BOOTPROTO=none
> IPADDR=65.112.29.36
> NETMASK=255.255.255.248
> GATEWAY=65.112.29.33
>
> DEVICE=eth0
> ONBOOT=yes
> BOOTPROTO=none
> IPADDR=192.168.0.2
> NETMASK=255.255.255.128
> GATEWAY=192.168.0.1
>
>
> Thanks again,
>
> David
>
> -----Original Message-----
> From: yellowdog-general-admin@lists.terrasoftsolutions.com
> [mailto:yellowdog-general-admin@lists.terrasoftsolutions.com] On Behalf
> Of Ken Schweigert
> Sent: Friday, March 29, 2002 11:36 AM
> To: yellowdog-general@lists.terrasoftsolutions.com
> Subject: Re: Bringing up 2nd NIC card
>
> You can use the same modules as long as the kernel versions are the
> same.
> Some modules get the version put into them and will only work with that
> kernel version.
>
> This more recent message means that you changed the contents of
> modules.conf
> and haven't updated your modules.dep file. 'depmod -a' should fix this.
>
> -ken
>
>
> On Fri, Mar 29, 2002 at 11:30:34AM -0800, David McInnis wrote:
> > Thank you. The drivers were in the wrong directory. After I moved
> them
> > everything worked peachy. Just one more question.
> >
> > I have an identical machine that I am setting up as a mirror to the
> one
> > I just set up. Can I use the same pci-scan.o and rtl8139.o files that
> I
> > just compiled or do I need to rebuild them on the mirror machine?
> >
> > Also when I did 'modprobe rtl8139' I got the following message:
> >
> > Note: /etc/modules.conf is more recent than
> > /lib/modules/2.4.10-12a/modules.dep
> >
> > Is this significant? I tried "touch" on the files, but I still get
> this
> > message.
> >
> > David McInnis
> >
> >
> >
> > -----Original Message-----
> > From: yellowdog-general-admin@lists.terrasoftsolutions.com
> > [mailto:yellowdog-general-admin@lists.terrasoftsolutions.com] On
> Behalf
> > Of Ken Schweigert
> > Sent: Friday, March 29, 2002 10:31 AM
> > To: yellowdog-general@lists.terrasoftsolutions.com
> > Subject: Re: Bringing up 2nd NIC card
> >
> > David,
> >
> > In your /etc/modules.conf file put something like:
> > alias eth1 rtl8139
> >
> > You will also need to create a
> /etc/sysconfig/network-scripts/ifcfg-eth1
> > with the appropriate interface and IP address.
> >
> > Also, do a 'depmod -a' to recreate your dependancy file. If you don't
> > see any errors you should be able to do 'modprobe rtl8139' and it will
> > load pci-scan and then rtl8139.
> >
> > Then just do a '/etc/rc.d/init.d/network restart' and you should be
> > in business.
> >
> > Hope this helps.
> >
> > --
> > -Ken Schweigert, Aspiring Network Administrator
> > Byte Productions, LLC
> > http://www.byte-productions.com
> >
> >
> >
> > On Fri, Mar 29, 2002 at 10:21:08AM -0800, David McInnis wrote:
> > > I am running YDL 2.1 with kernel 2.4.10-12a.
> > >
> > > I have a network running on the integrated NIC that comes with my
> G4.
> > >
> > > I have added a second NIC (MacSense by xsense that uses the Realtek
> > > (rtl8139) chipset.) to this machine.
> > >
> > > I went to Web and found a driver, downloaded the source and compiled
> > > driver. This compilation yielded 2 files: pci-scan.o and
> rtl8139.o.
> > >
> > > I then do:
> > >
> > > insmod pci-scan.o
> > > insmod rtl8139.o
> > >
> > > to bring up the interface. Hey, it works.
> > >
> > > My problem is this. Where do I need to call these in order for the
> > > interface to come up at boot? I want both (the current eth0 and the
> > new
> > > eth1) to be activated at boot. Will they be inserted in that order
> (I
> > > have tried to insert rtl8139.o without the pci-scan.o and it fails)?
> > >
> > > Currently I have them in /lib/modules/2.4.10-12a/net.
> > >
> > > Thanks,
> > >
> > > David McInnis
> > >
> > >
> > > _______________________________________________
> > > yellowdog-general mailing list
> > > yellowdog-general@lists.terrasoftsolutions.com
> > >
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> > >
> >
> > _______________________________________________
> > yellowdog-general mailing list
> > yellowdog-general@lists.terrasoftsolutions.com
> > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> >
> > _______________________________________________
> > yellowdog-general mailing list
> > yellowdog-general@lists.terrasoftsolutions.com
> > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> >
>
> --
> -Ken Schweigert, Aspiring Network Administrator
> Byte Productions, LLC
> http://www.byte-productions.com
> 1.231.946.2983 ext. 206
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
--
-Ken Schweigert, Aspiring Network Administrator
Byte Productions, LLC
http://www.byte-productions.com