question

Tue Mar 19 18:35:41 EST 2002

Hi William. When I tried to add eth0 to /etc/network interfaces, I got the following error:
/etc/network/interfaces: Too few parameters for line iface.

This is the way eth0 is listed:
auto eth0
iface eth0
eth0 gateway 192.168.0.1

This is the address for my internal gateway. I tried doing man /etc/network/interfaces, but my file was displayed. Does anyone know which parameters I have to add on the iface line? Thanks in advance! 
----- Original Message ----- 
From: William Hubbs <kc5eiv at kc5eiv.ddts.net>
To: <speakup at braille.uwo.ca>
Sent: Tuesday, March 19, 2002 3:25 PM
Subject: Re: question

> Hello Igor,
> 
> I'm not sure which distro you are using, but if you are using Debian,
> you just set up the interface definition as follows in
> /etc/network/interfaces:
> 
> 
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> 
> # The loopback interface
> auto lo
> iface lo inet loopback
> 
> # The first network card - this entry was created during the Debian installation
> # (network, broadcast and gateway are optional)
> auto eth0
> iface eth0 inet dhcp
> 
> # end of setup.
> 
> then as root type these commands:
> 
> ifdown eth0
> ifup eth0
> 
> At that point, pump should configure the interface and also create a
> /etc/resolv.conf.
> 
> William
> 
> On Tue, Mar 19, 2002 at 02:33:34PM -0500, Igor Gueths wrote:
> > Hi Victor. I have network access. There are two things that I don't have as of yet. 1 of them is Dns, and the other is I don't have it set to configure the interfaces with pump on start-up. Does anyone know how I could go about doing this? Thanks!
> > ----- Original Message ----- 
> > From: Victor Tsaran <tsar at sylaba.poznan.pl>
> > To: <speakup at braille.uwo.ca>
> > Sent: Monday, March 18, 2002 9:15 PM
> > Subject: Re: question 
> > 
> > 
> > > Hi, Igor!
> > > Loopback interface will work regardless of whether your physical network
> > > card working or not. Loopback interface, 127.0.0.1, is present in Linux by
> > > default. So your card is not working properly if it is not detected by
> > > ifconfig.
> > > Vic
> > > 
> > > ----- Original Message -----
> > > From: "Igor Gueths" <igueths at yahoo.com>
> > > To: <speakup at braille.uwo.ca>
> > > Sent: Tuesday, March 19, 2002 12:24 AM
> > > Subject: Re: question
> > > 
> > > 
> > > > Hi Victer. The card is actually recognized, and the
> > > > module seems to load fine. In fact, when I do
> > > > ifconfig, I get status messages. Something like this:
> > > > Loopback=127.0.0.1. Netmask=255.255.0.0. Mtu=16300.
> > > > Then it goes on to display packet stats. At least I
> > > > got an mtu reading that wasn't 0, so I believe that
> > > > this could indicate that the interface is functioning.
> > > > Is this so? By the way, to answer your question on the
> > > > SMC cards, I actually have a Linksys card that uses
> > > > the tulip module.
> > > > What I'm planning to do something like ifconfig eth0
> > > > -dhcp to configure the interface based on dhcp. Also,
> > > > sorry for the long response time, its just that mail
> > > > over here was down for about two days, and its back
> > > > up. -I have also noticed an interesting atribute in
> > > > kernel 2.4.18. Every time -I press the del key,
> > > > dec-talk says numlock on. COuld this have to do with
> > > > an incorrect keymap being loaded at boot time? Thanks
> > > > in advance!- Victor Tsaran <tsar at sylaba.poznan.pl>
> > > > wrote:
> > > > > Hi, Igor!
> > > > > Is there a possibility that your netcard module
> > > > > conflicts with another
> > > > > module which kicks it out? Can you do a full "dmesg"
> > > > > trace and see what
> > > > > happens there? Also, if I remember correctly,
> > > > > tulip.o module was for SMC
> > > > > cards, right? If yes, then I think there was some
> > > > > update to that module last
> > > > > year. But that might not apply to you since you are
> > > > > using the newest kernel,
> > > > > is that so?
> > > > > Also, I think that your card might be recognized by
> > > > > the hardware detection
> > > > > tool, but the module itself does not load. Perhaps
> > > > > you should check your
> > > > > /etc/modules.conf or edit your /etc/rc.d/rc.local to
> > > > > have your module load
> > > > > at startup.
> > > > > Vic
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup at braille.uwo.ca
> > > > >
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > > >
> > > > __________________________________________________
> > > > Do You Yahoo!?
> > > > Yahoo! Sports - live college hoops coverage
> > > > http://sports.yahoo.com/
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup at braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > > >
> > > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup at braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > 
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com