Clarence Verge wrote:
>
> This was the suggestion: (I typed it enuf times to remember it)
> ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
Leaving out the defaults, this becomes
-------------------------
ifconfig eth0 192.168.0.1
-------------------------
I recommend that *before* doing this,
you add the following to /etc/hosts
---------------------
192.168.0.1 clark
192.168.0.2 lois
---------------------
This will enable you to use names instead of
numbers. Therefore, your ifconfig statement
becomes:
--------------------
ifconfig eth0 clark
--------------------
> The result was: (Something like)
> ISCGOBLEDEGOOK:IPADDR Operation not supported by device
> ISCMOREDEGOOK:NETMASK Operation not supported by device
Are you sure that eth0 is actually installed?
Try the following and see what comes up:
------------------
dmesg | grep eth0
------------------
If nothing comes up, then you've got no eth0.
This means your network card isn't activated.
Fix this with insmod <module for your card>
or modprobe <module for your card>.
That should give you a message about eth0.
Then you can proceed to ifconfig.
> Since the Dlink router is 192.168.0.1,
Is this the network card in your computer?
Or is it something else?
> I tried ifconfig by itself
This tells you which interfaces are up.
> and it seemed to be telling me that it was working
> fine in Loopback mode and there was a local address
> like 127.xxx. something.
This is the localhost (127.0.0.1). You'll probably
find it listed in /etc/hosts. It's just the local
address for the computer to network to itself. This
may sound silly, but it's quite useful. For example
you can set up a FTP server and then try out a FTP
client (on the same machine) by logging into localhost.
OK, let's summarize:
(1) assign names to IP numbers (/etc/hosts)
(2) activate network interface (insmod or modprobe)
(3) assign address to interface (ifconfig)
When you have done this, enter 'route' to check that
the routing for this interface as been done. I think
that recent versions of ifconfig automatically do the
routing. Older versions (like the one in BasicLinux)
require a separate command. Like this:
-------------------
ifconfig eth0 clark
route add lois
-------------------
This sets up a route between clark (192.168.0.1) and
lois (192.168.0.2). But, as I say, with a recent
version of ifconfig, an explicit route line should
be unnecessary.
(4) You are now ready to ping lois.
Do not hesitate to ask further questions about this.
It's really quite simple when you get used to it.
Cheers,
Steven
