On Wed, Jan 12, 2000 at 11:59:09PM -0800, Randolph Fritz wrote:
| On Wed, Jan 12, 2000 at 11:14:20PM -0800, Rob Hudson wrote:
| > On Wed, Jan 12, 2000 at 11:09:09PM -0800, Randolph Fritz wrote:
| > | On Wed, Jan 12, 2000 at 07:45:50PM -0800, Rob Hudson wrote:
| > | > On Wed, Jan 12, 2000 at 07:30:06PM -0800, Randolph Fritz wrote:
| > | > | On Wed, 12 Jan 2000, Rob Hudson wrote:
| > | > |
| > | > | > Right now, if I type 'ifconfig eth0 up', it doesn't set the IP,
| > | > | > netmask, etc properly, and I can't ping the other system on the
| > | > | > network. But if I type 'ifconfig eth0 192.168.1.2 netmask
| > | > | > 255.255.255.0 up', everything works great.
| > | > |
|
| Hmmmm...Rob, after the system is up, but before you run your own
| "ifconfig" command, try typing:
|
| /etc/rc.d/init.d/network status
|
| That will tell you if the device was configured by the script.
If I, however, run ...
----------------------------------------------------------------------
root> /etc/rc.d/init.d/network reload
Bringing up alias eth0
SIOCSIFADDR: No such device
SIOCSIFFLAGS: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
SIOCSIFFLAGS: No such device
[FAILED]
root>
----------------------------------------------------------------------
Does that tell you anything? [ 10 minute pause ] ... It did me. :)
Problem solved:
I changed the file ifcfg-eth0:0 to ifcfg-eth0, and then the network
script seemed to be able to find it. There might be a parse problem
when looking for ifcfg-* files that can't find the eth0:0. (???)
It did the trick, though. But then, on reboot, the network script
was run before the pcmcia script, which caused it to fail. So I
just bumped the pcmcia up before the networking, (changed the
S45pcmcia softlink to S08pcmcia where the networking is S10network)
and now everything works upon boot.
Is the normal naming convention ifcfg-eth0 or ifcfg-eth0:0 ?
Thanks for all the help.
-Rob.
